When your product processes documents that others cannot afford to lose, security stops being a technical feature and becomes a condition of sale. Doing things well is not enough. Your clients need to be able to check it, and the quickest way for them to do so is to ask for a certification.
That is the situation at Stelo AI. Its platform uses artificial intelligence to classify, extract data from and verify the authenticity of documents such as payslips, bank statements, tax returns and deeds, and it works for financial institutions, insurers, leasing companies and public administrations. As Valentí Canadell, its CEO and co-founder, puts it, as well as doing things very well, they have “the responsibility to be seen to do so”.
Each type of client asks for a different certification
The order in which a company gets certified is rarely a theoretical decision. Clients set it.
In Stelo’s case, the first was ISO 27001, because it was the one most requested by its early clients in the financial and insurance sectors. That makes sense: banks and insurers operate under intense supervision and pass that pressure on to their technology suppliers through security questionnaires, audits and contractual clauses. A valid ISO 27001 certificate answers a large share of those questions in one go.
When Stelo wanted to start working with the public administration, the requirement changed. For that client, Spain’s National Security Framework (Esquema Nacional de Seguridad, or ENS) became essential.
What the ENS is and why it affects private suppliers
The ENS is regulated by Royal Decree 311/2022 and is the mandatory security framework for the information systems of the Spanish public sector. What many private companies discover late is that it also applies to them when they provide services or solutions to the public sector. It is the contracting administration itself that must require its suppliers to comply with the ENS.
The ENS classifies systems into three categories, basic, medium and high, according to the impact an incident would have. The category determines which security measures must be applied and how conformity is demonstrated: in the basic category a self-assessment and a declaration of conformity are enough, while medium and high require a certificate of conformity issued by an accredited certification body following an external audit, repeated at least every two years.
If you already have ISO 27001, you are not starting from scratch
The good news for a company that already holds ISO 27001 is that a significant part of the work is done. Both frameworks share the same logic: risk analysis, policies approved by management, defined roles, incident management, access control, continuity and continual improvement. Spain’s National Cryptologic Centre (CCN) publishes a specific guide, CCN-STIC 825, that maps ENS measures to ISO 27001 controls.
But they share a logic, not identical requirements. It is worth being clear on a few differences before planning the project:
- System categorisation. In ISO 27001 you choose the scope; in the ENS you must also assess each security dimension and assign a category to the system, which determines the mandatory measures.
- More prescriptive measures. Annex II of Royal Decree 311/2022 sets out 73 measures, with reinforcements depending on the category. Some are more detailed than the equivalent ISO 27001 control.
- Specific roles. The ENS requires separate roles for the information owner, the service owner, the security manager and the system manager.
- Relationship with CCN-CERT. The ENS includes incident notification obligations to CCN-CERT that are not part of ISO 27001.
The efficient approach is to treat both frameworks as a single management system with two reference standards, rather than running two parallel systems with duplicated documentation.
A good product is not the same as an auditable system
Valentí explains it clearly: from the start they had a very solid product in technical, security and data protection terms. What they did not have, and what made it obvious they needed a partner, was everything else: the policies, processes and records that make it possible to obtain a certification and, above all, to keep it and pass audits year after year.
It is a distinction we often see in technology companies. Security exists, but it lives in the technical team’s heads and in the infrastructure configuration, not in approved documents, evidence records or procedures an auditor can review. ISO 27001 and the ENS do not just reward having controls; they require you to show that they work and are reviewed systematically.
That is why the goal should not be just to pass the first audit. An ISO 27001 certificate runs on a three-year cycle with annual surveillance audits, and the ENS requires periodic re-audits. If the internal team does not take ownership of the system, every audit feels like an exam. For Valentí, one of the main benefits of the support has been exactly that: learning to make the information security system their own and to operate more efficiently and in a compliant way day to day.
Identify the weaknesses first, then prioritise
In a certification project, the most expensive mistake is trying to fix everything at once. Useful work starts with a diagnosis that identifies which gaps would prevent you from passing the audit and which can be addressed later within the continual improvement cycle.
Valentí highlights precisely this part of the work with PrivaLex: identifying the main weaknesses that needed addressing and being very tactical about how to remedy them, so as to reach each audit on time and without major issues. When the product cannot stop, that prioritisation is what makes it possible to get certified without slowing the business down.
Data protection builds trust too
Security certifications cover part of what regulated clients ask about. The other part is data protection, especially when the product handles personal documentation as sensitive as payslips, bank details or tax information.
In Stelo’s case, PrivaLex also acts as its external Data Protection Officer (DPO). The GDPR allows the DPO to be an external professional and requires their contact details to be published and communicated to the supervisory authority, which in Spain is the Spanish Data Protection Agency (AEPD). For Valentí, it is a question of credibility: when their clients see an experienced DPO in the contract and know that the appointment has been notified to the AEPD, it reassures everyone, starting with themselves.
What to learn from the Stelo case
If your company sells software to regulated sectors, these are the ideas that matter most:
- Let demand set the order. Start with the certification your current clients ask for most and plan the next one when you open a new market.
- Design a single management system. If you will need ISO 27001 and the ENS, build them on the same documentation and risk base.
- Distinguish technical security from an auditable system. Good controls are not enough; you need policies, processes and records that prove they work.
- Prioritise the gaps. A good initial diagnosis avoids spreading effort too thinly and arriving at the audit with surprises.
- Think about maintenance from day one. Certifications are renewed and audited periodically; the internal team needs to know how to run the system.
- Do not forget data protection. An experienced DPO, properly notified to the AEPD, is also part of the trust you sell.
Frequently Asked Questions
Yes, when they provide services or solutions to the Spanish public sector. Royal Decree 311/2022 includes public sector suppliers within its scope, and the contracting administration must require them to comply with the ENS.
Basic category systems can demonstrate conformity through a self-assessment and a declaration of conformity. Medium and high category systems need a certificate of conformity issued by an accredited certification body following an external audit.
Medium and high category systems must undergo an ordinary audit at least every two years, and an extraordinary audit whenever there are substantial changes.
No. ISO 27001 makes the path much easier because it shares the risk management logic and many of the controls, but the ENS requires you to categorise the system, apply the measures in Annex II of Royal Decree 311/2022, define specific roles and pass its own audit.
The certificate is valid for three years, with annual surveillance audits and a recertification audit at the end of the cycle.
Yes. Article 37 of the GDPR allows an external professional to be appointed as DPO under a service contract. In any case, their contact details must be published and the appointment notified to the supervisory authority, which in Spain is the AEPD.
