Many companies don’t realize how difficult it is to document security until a customer or auditor asks for proof that a supplier is handling data responsibly. Claims regarding digital signatures and compliance with eIDAS are not sufficient on their own if operations have not been independently verified. An ISAE 3000 statement solves this very problem by providing an auditor-verified description of the controls that protect your documents and personal data.
The problem: trust cannot be documented with promises
Most vendors claim that their solution is secure, but a statement of intent holds no value in an audit or a procurement process. When a procurement officer, an internal compliance function, or a government agency needs to evaluate a vendor, they require evidence that has been verified by an independent third party. Without such evidence, the assessment often boils down to a lengthy questionnaire that ultimately reflects only the supplier’s own responses. It is precisely this documentation gap that an independent audit opinion is designed to close, because it shifts the assessment from the supplier’s own words to an auditor’s conclusion.
What ISAE 3000 Is
ISAE 3000 is an international auditing standard for assurance engagements other than audits of historical financial data. In practice, it is used when an independent auditor issues a statement regarding a supplier’s controls in areas such as information security and data protection. For a document management and signing platform, this means that a third party has reviewed how the system handles access, logging, and data protection, and that the conclusion is set forth in a statement that you can share with your own stakeholders.
The Difference Between Type 1 and Type 2
A Type 1 statement describes and assesses whether the controls are appropriately designed as of a given date. A Type 2 statement goes further and tests whether the same controls have actually been effective over a defined period, typically six to twelve months. For a customer, a Type 2 statement is therefore more valuable because it documents that security is not only on paper but also functions in day-to-day operations over time. A Type 1 statement may be sufficient for a new solution where there is not yet an operational period to test, whereas for an established provider, you should expect a Type 2 statement. When you receive a statement, you should therefore always check what type it is and what period it covers before placing any weight on the conclusion.
The Relationship with the GDPR and Data Processors
When a vendor processes personal data on your behalf, the company is a data processor under the GDPR, and you must enter into a data processing agreement. ISAE 3000 is often used as the document that substantiates the vendor’s ability to comply with the agreement. If the vendor uses other services, you should also examine the chain of subprocessors and the requirements for them; how signature data is processed is described in more detail in our overview of the GDPR and e-signatures.
Special Considerations in the Public Sector
Public organizations are often subject to stricter requirements for vendor management, and an audit report is frequently included as a documentation requirement in tenders and contracts. For municipalities, ministries, and government agencies, ISAE 3000 can therefore be decisive in determining whether a solution can be implemented at all. We describe these typical requirements in more detail in our overview of Digital Signing in the Public Sector, where record-keeping and retention also play a role.
What You Should Specifically Look for in a Report
Always read the auditor’s conclusion first, and note whether the attestation is Type 1 or Type 2, as well as the period it covers. Next, review the control objectives relevant to your use case—such as access control, encryption, and incident management—and pay attention to any deviations the auditor has noted. A deviation isn’t necessarily a “no,” but it tells you where to ask follow-up questions of the provider. Also pay attention to the scope of the statement so you know whether the systems you actually use are included in the audit. Finally, compare the statement with the legal validity of the signature itself, as described in our article on EIDAS and signature levels.
How ISAE 3000 Complements Your Overall Compliance
ISAE 3000 covers operations and controls, while legal validity is ensured by the signature level and GDPR compliance in data processing. Together, they provide a solid foundation for ensuring that documents meet both internal and external requirements. If you’d like to see how the declaration fits into the overall workflow, start with our overview of Digital Document Management and the underlying Digital Signing Platform.
Esben Emborg
Today, I work at Addo Sign with communications and marketing, drawing on my experience in design and digital products to make complex topics easier to understand and more accessible.