Key takeaways
- Compliance automation is software that connects to your systems, tests security controls continuously, keeps dated evidence and maps it to frameworks such as ISO/IEC 27001, SOC 2, NIS2 and DORA.
- It automates five things: control monitoring, evidence collection, policy and staff records, first drafts of security questionnaires and the mapping of one control onto several frameworks.
- It does not set scope, carry out the risk assessment, take treatment decisions, fix the gaps it finds or issue certificates.
- ISO/IEC 27001 certificates come from accredited certification bodies and SOC 2 reports from independent CPA firms: the platform prepares the evidence, the auditor forms the opinion.
- Choose on framework depth, integrations with your real stack, quality of the raw evidence, data portability and how the auditor works inside the tool.
Compliance automation is software that connects to your cloud, identity, code, device and HR systems, checks continuously whether security controls are working, keeps dated evidence and maps it to frameworks such as ISO/IEC 27001, SOC 2, NIS2 and DORA. It handles evidence, monitoring, policy tracking and questionnaire drafts. It does not set scope, judge risk, fix gaps or issue certificates.
That split is where most expectations go wrong. The software takes over the mechanical side of compliance. The side that needs judgement, such as what sits in scope and which risks you accept, stays with your people and your auditor.
What compliance automation actually automates
Behind the label there are five recurring functions. Not every platform covers them equally, and the gaps between products are usually in the last two.
Continuous control monitoring
The platform connects through integrations to the systems where controls really live: cloud providers, identity provider, code repositories, device management, ticketing, HR system. It then tests at regular intervals whether a condition holds, for example whether multi-factor authentication is on for every admin account or whether logs are kept for the period your policy states. When a condition fails, it opens an issue instead of letting the gap surface during the audit.
The change is in frequency. A check run once a year describes one day; a check run every hour describes the year. EU law asks for exactly this kind of recurring test. Article 32(1)(d) of the GDPR lists among security measures "a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing". For financial entities, Article 9(1) of DORA (Regulation (EU) 2022/2554) says they "shall continuously monitor and control the security and functioning of ICT systems and tools".
Evidence collection and retention
Every test produces a dated artefact: an API response, a configuration export, a closed ticket, a list of users. The platform stores it against the control it documents, so nobody has to rebuild after the fact who did what and when. This is where the return is fastest, because manual evidence gathering is the most repetitive part of any certification.
Policies and people
The third area is about documents and staff. The platform manages the policy lifecycle (version, approval, periodic review), distributes policies, records acceptance and tracks security training. It also follows joiners and leavers: access granted on day one, revocation recorded on the last day. Auditors ask for these records every time, and when they are collected by hand they are rarely complete.
Security questionnaires
Customer security reviews are the newest function. The platform builds a knowledge base from your policies and past answers and drafts responses to new questionnaires. Vanta's questionnaire page, for example, describes AI-generated answers produced for you to review and approve (vanta.com/products/questionnaire-automation, read on 11/11/2026). That is the right model: the draft is quick, the answer your company sends is still signed off by a person who knows whether it is true.
One control, many frameworks
The fifth function is where the economics change. Access management, for example, appears in different wording in Annex A of ISO/IEC 27001:2022, in the SOC 2 Trust Services Criteria, in Article 21 of NIS2 and in Article 32 of the GDPR. A compliance automation platform keeps a single control library and maps it onto each framework, so evidence is collected once and presented several times. Organisations working on two certifications at once, such as ISO 27001 and SOC 2, gain the most.
What it does not automate
This is the part sales material tends to compress. What stays outside the software:
- Scope. Deciding which sites, services and systems enter the certification or the regulatory perimeter is a business choice before it is a technical one. Getting it wrong weighs on everything that follows.
- Risk assessment. ISO/IEC 27001 is built around risk assessment. The platform can host the risk register; it cannot fill it with the judgement of people who know the business.
- Treatment decisions. Reducing, transferring, accepting or avoiding a risk are management decisions. Under NIS2, Article 20(1) of Directive (EU) 2022/2555 asks management bodies to approve the cybersecurity risk-management measures and oversee their implementation. A green dashboard does not change who is accountable.
- Remediation. The platform tells you that eight accounts lack multi-factor authentication. Switching it on, handling the exceptions and convincing the people who resist is work for people and systems. Article 21(4) of NIS2 asks entities that find they do not comply to take the necessary corrective measures without undue delay: the software helps you notice, it does not do the fixing.
- The audit. An ISO/IEC 27001 certificate is issued by an accredited certification body; in the EU, each member state appoints a single national accreditation body under Article 4(1) of Regulation (EC) No 765/2008. A SOC 2 report is issued by an independent auditor: the AICPA describes SOC as a suite of service offerings that CPAs may provide on an organisation's controls. We explain how to pick an auditor in ISO 27001 certification bodies.
The last point deserves to be explicit. The platform prepares the material on which the auditor forms an opinion; it does not anticipate that opinion. For a buyer the consequence is simple: how quickly a tool gets you to a report says nothing about the quality of the report.
Which frameworks it covers
Most platforms in this category cover the same core set, with different depth. For a European organisation the four that matter most are these.
- ISO/IEC 27001. The certifiable standard for an information security management system, and the natural spine of a control library. Evidence collection fits Annex A controls well; clauses on context, leadership and risk need human work.
- SOC 2. An attestation report on the AICPA Trust Services Criteria, issued by an independent CPA firm. It reuses much of the ISO 27001 evidence; the difference between report types is in SOC 1 vs SOC 2.
- NIS2. Directive (EU) 2022/2555 applies through each member state's national law. Article 21(2)(f) asks for "policies and procedures to assess the effectiveness of cybersecurity risk-management measures", which is precisely the record continuous monitoring produces. Incident notification, the supply chain and scope under national law remain your work. More on the NIS2 service page.
- DORA. For financial entities, Article 6(5) of Regulation (EU) 2022/2554 requires the ICT risk management framework to be documented and reviewed at least once a year (periodically for microenterprises) and after major ICT-related incidents. A platform keeps that documentation current between reviews; the register of information on contractual arrangements with ICT third-party service providers (Article 28(3)) and resilience testing still need dedicated work. See the DORA service page.
Many platforms also list the GDPR and ISO/IEC 42001 for AI management systems. On the privacy side, a dedicated tool may fit better: we compared the options in GDPR compliance software.
An example: how Vanta describes it
AmagisTech is a Vanta partner, so we use it as a concrete example, with every claim taken from the vendor's own pages (read on 11/11/2026).
- Monitoring. Vanta describes automated, hourly tests on controls, with continuous visibility on compliance posture and evidence collected for the audit (vanta.com/products/automated-compliance).
- EU frameworks. It has dedicated NIS 2 and DORA pages with pre-built or pre-mapped controls, scoping of the entities, systems or vendors in perimeter, and risk workflows that the vendor says are aligned with ISO 27005 (vanta.com/products/nis2, vanta.com/products/dora).
- Reuse. The framework mapping section of its ISO 27001 page, which shows how much existing evidence other frameworks can reuse, puts SOC 2 at 80% (vanta.com/products/iso-27001). It is the vendor's own figure, useful as an order of magnitude, not as an independent measure.
- Audit. You can bring your own auditor or pick one from the vendor's network, auditors can be given access to test source data, and in the vendor's words You decide what auditors see (vanta.com/products/audit).
Nothing on these pages presents the platform as the certifier: the audit page is built around an auditor you bring or choose. That is consistent with the split above.
How to choose a compliance automation platform
Framework depth, not framework count
The question is not how many frameworks appear on the list but which ones have a maintained control library and a cross-mapping you do not have to build by hand. Ask how quickly the library is updated when a standard gets a new edition or a regulator issues new technical rules.
Integrations with the stack you have
This criterion rules out the most products. List the systems evidence has to come from and check the native integrations one by one. A largely on-premises estate with custom applications and decentralised identities integrates far less than a cloud-native one, and whatever is not integrated goes back to manual uploads inside the platform.
Quality of the evidence
Ask to see the raw evidence the tool produces for one real control, not the dashboard summary. Can you tell which system it came from, when it was collected and over which population (all accounts or a sample)? Auditors reason about completeness and traceability, not colours.
Data portability
Evidence, policies, risk register and the history of exceptions are company records. Check before signing that they export in a format readable without the platform, and what stays accessible when the contract ends. A compliance history readable only inside one tool is a dependency, and it shows at the worst moment: a vendor change close to an audit.
The audit workflow and the supply chain
Ask how your auditor works inside the tool: read-only access, evidence packs by period, a format your certification body has already seen. If you also need to assess your own suppliers, check whether vendor reviews are in the same platform; our guide to third-party risk management covers what that process involves.
When it makes sense, and when it is premature
It pays off in three recognisable situations: several frameworks to maintain together, a mostly cloud stack where integrations cover a large share of controls, and a recurring cycle of surveillance audits and customer questionnaires that repeats every year.
It is premature in the opposite cases. If scope is not defined and no risk assessment exists, the tool arrives before the decisions it is meant to document. If the estate is mostly on premises, much of the evidence stays manual. If there is one framework, stable and small in scope, a well-kept register and discipline may still be enough for one more cycle.
If you want to know whether this category fits your certification or regulatory programme, or whether something else comes first, talk to us: we start from your scope and the stack you actually run, and we work on both sides of the line, the platform and the scope, risk and audit preparation around it.
