Key takeaways
- Compliance software for information security and data protection brings risks, controls, policies, and evidence for frameworks such as ISO 27001, NIS2, GDPR, SOC 2, TISAX, ISO 42001, and the EU AI Act into one system. Whistleblowing and anti-corruption tools are a different product category.
- A platform usually pays off from two frameworks or an annual audit cycle onward. A company with fewer than 30 employees that has to prove one framework once can often manage with spreadsheets, templates, and a consultant.
- Software does not make a company compliant: for ISO 27001, an accredited certification body checks whether controls work in daily operations, and a SOC 2 Type II report covers an observation period of typically 3 to 12 months.
- The license is rarely the largest cost item. For a company with 50 to 200 employees in the German-speaking market, the classic consulting route to ISO 27001 certification alone costs €37,000 to €80,000 in year one by our own breakdown, excluding internal staff time.
- A structured selection in five steps typically takes 6 to 10 weeks and ends with a pilot on a real control area, not with the best demo.
Compliance software promises to make audits predictable and evidence available at any time. The market is confusing, though: the same term covers whistleblowing tools, enterprise GRC suites for large corporations, and automation platforms for cloud companies. This guide sorts the categories, shows the criteria that actually matter in a selection, and also tells you when you do not need a platform at all.
What Is Compliance Software?
It is a system in which a company manages its regulatory requirements, the measures that address them, and the evidence for those measures. Instead of keeping risk assessments in spreadsheets, policies on shared drives, and evidence in email threads, everything sits in one place, with owners, deadlines, and history.
What this guide covers
This guide covers software for information security, data protection, and AI compliance. That means frameworks such as ISO 27001, NIS2, the GDPR, SOC 2, TISAX, ISO 42001, and the EU AI Act.
Classic corporate compliance tools are a different category. They include whistleblowing systems under the EU Whistleblower Directive (EU) 2019/1937, which requires internal reporting channels at employers with 50 or more workers, as well as tools for anti-corruption, gift registers, and code-of-conduct training. If one of those duties is your trigger, look there. If your trigger is a customer asking for an ISO 27001 certificate, or the question of whether you have properly documented your GDPR obligations, you are in the right place.
Compliance software, GRC software, and ISMS software
The three terms overlap, but they do not mean the same thing:
- ISMS software represents an information security management system under ISO 27001: scope, risk assessment, the 93 controls in Annex A, the Statement of Applicability, and internal audits.
- GRC software (governance, risk, and compliance) is the umbrella term from the corporate world. GRC tools often also cover financial risk, internal control systems, and internal audit, and they are built for large teams with their own compliance department.
- Compliance management software as used in this guide connects several information security and data protection frameworks in one control set and collects evidence as automatically as possible through integrations.
In practice, vendors use the terms interchangeably. What matters is not the label but which frameworks a compliance tool actually covers and how much work it takes off your team.
Four Solution Approaches Compared
Before you compare vendors, decide on the basic approach. In the information security and data protection market there are four common routes, and they differ mainly in how much work stays with your own team.
| Approach | Suited for | Strengths | Limits | Typical effort for your own team |
|---|---|---|---|---|
| Spreadsheets and documents | Small teams with one framework and experience in the topic | No license costs, ready immediately, full flexibility | No history, no automatic evidence, depends on individuals | High, every update is manual |
| Consultant-led project | Companies without their own security or privacy role that need a single certificate | Expert guidance, clear project scope up to the audit | Knowledge and documentation often stay with the consultant; ongoing operation after the audit is usually not included | Medium, part of the implementation stays in-house |
| Enterprise GRC suite | Large corporations, public authorities, and critical infrastructure operators with their own compliance department | Deep configurability, coverage beyond IT, established methods | Long rollout, often with an implementation partner; few ready-made integrations with cloud tools | High during rollout, then dependent on your own team |
| Compliance automation platform, with or without expert support | Startups, scale-ups, and mid-sized companies with a cloud stack and several frameworks | Automatic evidence through integrations, one control set for several frameworks | Without expert support, the professional assessment stays with the team; less suited to purely on-premises environments | Low to medium, depending on the level of support |
The real trade-off is in the last column. Spreadsheets save license costs and cost the most internal time instead; they typically break when an auditor wants to see the state of six months ago. A consultant project takes work off your plate but often ends with the certificate, even though ISO 27001 runs on a three-year cycle with annual surveillance audits. Our article on the ROI of compliance automation works through how manual and automated compliance compare in effort and return.
The fourth row is deliberately split in two. Pure self-service software provides structure and automation but leaves the judgment of whether a measure is adequate for your risk to you. Platforms with expert support also provide specialists who share exactly that judgment.
Do You Need a Platform at All?
Not every company needs a compliance platform. Whether the investment pays off depends mainly on four factors: the number of frameworks, how often you are audited, the size of your team, and pressure from customers.
Number of frameworks. With a single framework, such as a one-off ISO 27001 project, the benefit of a shared control set is small. From two frameworks onward, the math changes: a large share of the requirements in ISO 27001, NIS2, and SOC 2 overlap, and without mapping you maintain the same measure several times.
Audit frequency. An ISO 27001 certification is valid for three years, with surveillance audits in the first and second years and recertification in the third. A SOC 2 Type II report is usually renewed annually. If you face at least one external audit every year, you are not collecting evidence once but continuously. Our guide to ISO 27001 certification explains what the cycle requires in detail.
Team size. In companies with fewer than 30 employees, the person responsible often knows every system personally. From around 50 employees, several teams, and a growing tool stack, it becomes hard to track access rights, suppliers, and changes by hand.
Customer pressure. When enterprise customers send security questionnaires or make a certificate a contract condition, compliance becomes a sales question. Since national NIS2 laws took effect, in Germany on December 6, 2025, covered entities also ask their suppliers for evidence of information security, even when those suppliers are not covered by NIS2 themselves. Our guide to the NIS2 Directive explains how far these obligations reach.
When spreadsheets and a consultant are enough
An honest case against the platform: a company with 20 employees, a single framework, a one-off request from a customer, and one person on the team with ISO 27001 experience. Here, well-structured templates and a few consulting days for the gap analysis and audit preparation are often enough. The platform becomes interesting as soon as a second framework comes along or the maintenance effort after the first audit becomes visible.
Can you implement it on your own?
Yes, if two conditions are met: someone on the team has taken an ISMS through an audit before, and that person can realistically spend a large share of their working time on the rollout. If either is missing, the risk shifts to the audit. A platform shows you which controls are open, but not whether your risk assessment or your scope will hold up in front of a certification body.
External support pays off mainly in three situations: a first certification under time pressure, a customer requirement with a fixed date, and NIS2 obligations that make management personally responsible and call for a professional assessment. The expert support criterion below describes the forms that support can take.
A common misconception: "The software makes us compliant"
Software does not make any company compliant. For ISO 27001, an accredited certification body, accredited by a national accreditation body such as DAkkS in Germany or UKAS in the UK, checks whether your controls work in daily operations. A SOC 2 report under the AICPA's Trust Services Criteria describes whether controls worked over a period of time. A tool can collect evidence, track deadlines, and make gaps visible. People and processes decide whether access rights are actually reviewed and incidents actually reported. If you buy software as a shortcut around that work, you will have a well-filled system at the audit and still have nonconformities.
The Selection Criteria That Actually Matter
An independent consultant would put the following eight criteria on the list too. In practice, they decide more than any feature overview.
1. Framework coverage and control mapping
First, check whether the frameworks you need in the next 24 months are not just named but covered in substance. For ISO 27001, that means all 93 controls in Annex A of the 2022 version, whose transition period from the 2013 version ended on October 31, 2025. For NIS2, it means the ten cybersecurity risk-management measures in Article 21(2), the reporting process under Article 23, and the management body duties under Article 20 of the directive, as transposed into national law.
The mapping between frameworks matters at least as much. An access control should be implemented and evidenced once and then count for ISO 27001, SOC 2, and NIS2 at the same time. Our worked example shows a shared control set for ISO 27001, GDPR, and SOC 2 in practice.
A common misconception: more frameworks in the brochure mean a better fit. A list of 30 logos says nothing about how deeply a framework is covered. For your two most important frameworks, ask which requirements are prefilled, which evidence is generated automatically, and which you have to create yourself. A vendor that covers three frameworks thoroughly fits better than one that lists twenty and delivers only a checklist for each.
The number of controls per framework is hard to compare between vendors as well. Some map the 93 Annex A controls one to one, others split a requirement into several testable controls or merge similar requirements from several frameworks into one shared control. A higher number therefore means neither more coverage nor more work. Ask to see how each control traces back to the requirement in the standard, and whether you can add your own controls, for example for customer requirements, internal policies, or a standard the vendor has not prepared.
2. Automated evidence and integrations
The biggest ongoing effort in compliance operations is evidence collection: screenshots of configurations, exports from the identity provider, proof of fixed vulnerabilities. A platform only saves time if it pulls this evidence directly from your systems, such as cloud providers, identity management, code repositories, HR systems, and ticketing systems.
Do not just count integrations; check their depth. An integration that only establishes a login is different from one that checks daily whether a deadline for fixing a vulnerability has passed. Our integration with Aikido for vulnerability evidence shows what that looks like in practice.
3. Expert support or software only
This is where the market splits most clearly. Pure self-service software assumes you have someone who can judge ISO 27001 or the GDPR professionally, typically an internal information security officer or data protection officer. Platforms with expert support also provide that expertise, from questions on demand to appointment as your external CISO or external DPO.
Clarify three things in the conversation: who exactly advises you, and what qualifications does that person hold? Is the support included in the price or billed by the hour? And who remains your contact after the audit? Our article on the three levels of managed compliance explains the collaboration models and how much responsibility stays with the company in each.
The decision does not have to be all or nothing. Many companies set up the platform themselves and bring in support only for the parts that need experience: the gap analysis, the risk assessment, the internal audit under clause 9.2, and support during the certification audit.
4. EU data residency and sovereignty
A compliance platform holds the most sensitive data set you hand to a service provider: risk assessments, open vulnerabilities, incident files, the record of processing activities. That is why asking about a data center in the EU is not enough.
Also ask where the contracting party is headquartered, which subprocessors are used, and whether the vendor is subject to a legal system that allows authorities outside the EU to access data. The US CLOUD Act of 2018 applies regardless of storage location if the vendor is controlled from the US. Our article on EU data sovereignty explains why that turns vendor choice into a compliance decision.
5. Audit readiness and auditor access
On audit day, what counts is whether the auditor finds evidence quickly and traceably. Check whether the platform offers dedicated access for internal and external auditors, whether the Statement of Applicability under ISO 27001 clause 6.1.3 can be exported directly, and whether every piece of evidence is versioned with a timestamp and an owner.
The last point is underestimated. An auditor asks not only about today's state but about the state on a specific date within the observation period. A system that only shows the current state helps little there.
6. Usability for non-specialists
Most controls are owned not by the compliance team but by colleagues in IT, HR, engineering, and procurement. If these people can only use the platform after training, tasks end up back with the information security officer.
So in the demo, test a typical task from a control owner's perspective, such as approving a policy or uploading a piece of evidence. Also pay attention to the interface language, because not every control owner outside IT is comfortable working in a second language.
Do all employees have to work in the tool? Usually not. Only the compliance owners and control owners work in it actively. Everyone else has two touchpoints: acknowledging policies and completing training. Ask how that works, for example through a single sign-on login or a link in an email, whether the acknowledgment is stored as evidence, and whether these people count as licensed users. Also check which languages the training is available in and whether you can add your own content.
7. AI features and their governance
Almost every vendor now advertises AI, for example for policy drafts, answers to security questionnaires, or mapping evidence. The benefit is real. At the same time, the AI processes exactly the data you most want to protect.
Ask four questions: which model from which provider is used, and where does processing take place? Is your data used for training? Does a person review AI output before it enters your documentation? And does the contract explicitly cover AI processing? Since February 2, 2025, Article 4 of the EU AI Act has also required companies that use AI to ensure sufficient AI literacy among their staff. If you also want to build an AI management system, you will find the requirements in our guide to ISO 42001.
8. Contract terms, exit, and data export
Switching vendors is the moment when contract details come back to bite. Check the term, notice periods, and price adjustment clauses. More importantly: in what format do you get your data back at the end of the contract, with evidence, history, and timestamps, or only as a table of control statuses?
Article 28(3)(g) GDPR already requires the processor to return or delete personal data at the end of the contract. Beyond that, get written confirmation that a complete export is possible at no extra cost.
Framework-specific selection
If a single framework is clearly the priority, the specific criteria are worth a look. Our buyer's guide to ISO 27001 software and compliance tools covers the categories of ISMS software and what to look for when preparing for certification.
For ISO 27001, it is also worth looking closely at who maintains the Statement of Applicability and prepares the internal audits under clause 9.2. The standard requires both before the certification body decides on the certificate, and with software alone both remain the team's job.
NIS2 adds its own requirements: the reporting process with deadline tracking, registration with the competent authority, and evidence for management. Our buyer's guide to NIS2 compliance software shows how to choose suitable software for it.
What Compliance Software Costs
The costs consist of five blocks, and the license is rarely the largest. For an honest comparison, calculate the total cost of ownership over at least three years, a full ISO 27001 cycle.
License. The price usually depends on the number of employees or users, the number of frameworks, the number of legal entities or sites in scope, and the modules you book, such as privacy, vendor management, or training. Whether expert services are included makes the biggest difference between offers.
Implementation. Platforms with ready-made integrations can be in productive use within weeks. Enterprise GRC suites often need an implementation partner and several months.
Internal staff time. The most frequently forgotten item. Whoever maintains the platform, collects evidence, and prepares audits is missing elsewhere. Plan with realistic shares of a full-time position, not with leftover time.
Audit fees. The certification body bills its audit days regardless of the software. For ISO 27001, the number of audit days depends on the number of people in scope; under the audit time table in ISO/IEC 27006, 86 to 125 people means 12 days for initial certification. In practice, the certification body may deviate from this by up to 30 percent.
Consultants. External support for the gap analysis, policies, and audit preparation, if the software does not include expert support.
The classic consulting route to ISO 27001 certification serves as a reference point. The breakdown below is our own, not a study; it reflects the German-speaking market and includes neither software licenses nor internal staff time.
| Cost item (classic ISO 27001 consulting route) | Startup (under 50 employees) | Scale-up (50 to 200 employees) |
|---|---|---|
| Gap analysis and preparation | €5,000 to €15,000 | €10,000 to €25,000 |
| Implementation | €10,000 to €20,000 | €15,000 to €35,000 |
| Certification audit fees | €8,000 to €14,000 | €12,000 to €20,000 |
| Total cost, year 1 | €23,000 to €49,000 | €37,000 to €80,000 |
| Annual surveillance audit (from year 2) | €4,000 to €7,000 | €6,000 to €10,000 |
These figures cover a single framework. When SOC 2, NIS2, or TISAX come along, each project grows separately on the consulting route, while a platform with a shared control set reuses part of the work.
A common budgeting mistake: many managing directors compare only license prices and are surprised in year two that the cheapest license was the most expensive solution. Software that does not collect evidence automatically shifts the cost into your team's working time, where it shows up in no quote.
What changes at 500 employees?
Several items grow at once. The license scales with employees and entities, the certification body plans more audit days because they depend on the number of people in scope, and more control owners have to be involved. Companies of this size also often consist of several legal entities, which raises the question of whether a joint certification or separate scopes make more sense.
The cost table above covers companies with up to 200 employees. Reliable figures for a larger group only come from quotes for your specific setup. Request them with your headcount, entities, sites, and frameworks so that the quotes are comparable.
A practical example
The following figures are illustrative. A SaaS company with 90 employees achieved its ISO 27001 certification with a consultant almost three years ago; recertification is now due. Two enterprise customers also want a SOC 2 Type II report, and a customer covered by NIS2 has sent a supply chain security questionnaire. The ISMS lives in spreadsheets maintained by an IT team lead who spends about half of their working time on it.
For the initial certification, the company chose the classic consulting route, which by our breakdown costs €37,000 to €80,000 in year one for a company of this size. With 90 people in scope, the audit time table in ISO/IEC 27006 sets 12 audit days for an initial certification. A second consulting project for SOC 2 would redo parts of the same work, because the controls for access control, change management, and suppliers are largely identical.
With three requirements in twelve months, there is a strong case for a platform with a shared control set. The decisive question is a different one: does the team lead have the depth for SOC 2 and NIS2, or do they need certified experts alongside them? That determines whether pure software or a platform with support is the cheaper option.
How to Run the Selection in Five Steps
A structured selection of a compliance platform typically takes 6 to 10 weeks. If you have to decide faster, shorten the long list, not the pilot.
- Define requirements and scope (2 to 3 weeks, owner: information security officer or compliance lead together with management). Record which frameworks you need in the next 24 months, which systems are in scope, who internally has time, and which audit dates are fixed.
- Build a long list by category (about 1 week, owner: project lead). Assign vendors to the four solution approaches and remove all that do not cover your most important framework in substance. Three to five candidates are enough.
- Run demos with a fixed scenario (2 to 3 weeks, owner: project lead with a control owner from IT). Give every vendor the same scenario, for example: evidence access rights for a cloud system and assess a supplier. That way you compare workflows, not presentations.
- Check references (about 1 week, in parallel with step 3, owner: project lead). Talk to at least one customer of similar size that has already passed an external audit using the platform.
- Run a pilot or proof of value (2 to 4 weeks, owner: information security officer with the future core team). Build a real control area in the platform, such as access control or supplier management, and measure how much evidence is generated automatically.
Questions for the software demo
The following questions separate robust platforms from well-rehearsed presentations in a demo.
| Question | What to look for |
|---|---|
| Show us how one control is evidenced for ISO 27001 and SOC 2 at the same time. | One piece of evidence, several frameworks, no duplicate maintenance |
| How do you arrive at your number of controls per framework, and can we add our own controls? | Traceable mapping to the requirement in the standard, plus custom controls and frameworks |
| Do you support other standards such as VdS 10000 or BSI IT-Grundschutz? | Prepared content or the option to set up the standard yourself |
| Which evidence is generated automatically for our tech stack, and which stays manual? | A concrete list instead of a total number of integrations |
| Which evidence do you pull from Microsoft 365 and from endpoint management such as Intune? | Specific checks such as MFA status, encryption, and patch level |
| How often do automated checks run, and what happens when one fails? | Frequency, notification, and an assigned task |
| Can we reconstruct the state of a control on a date six months ago? | Versioning with timestamp and owner |
| How does our auditor work in the platform, and what do they see? | Dedicated access, clear permissions, export of the Statement of Applicability |
| Can we import our existing ISMS? | Risks, policies, Statement of Applicability, and evidence carried over instead of an empty template |
| How do we set up a group with a holding company and subsidiaries? | Joint or separate scopes, shared controls, and permissions per entity |
| Who advises us professionally, with what qualifications, and is that included in the price? | Named contacts instead of generic support |
| Where is our data stored, and where is the contracting party headquartered? | Data center and the vendor's legal jurisdiction |
| Which subprocessors do you use, including for AI features? | A complete, dated list |
| Is our data used to train AI models? | A clear answer backed by the contract |
| How do we assess a new supplier, and when is the assessment repeated? | A fixed review cycle with tasks |
| Which language do our control owners work in, and how long does a typical task take them? | Interface in their language and short paths for non-specialists |
| Which languages is the training available in, and can we add our own training? | Your workforce's languages, custom content, and proof of completion |
| Using our scenario, show us what your platform does better than spreadsheets or another tool. | A workflow shown live on your scenario instead of general promises |
| In what format do we receive all our data at the end of the contract, including evidence and history? | A complete export at no extra cost |
How Kertos Approaches These Criteria
Kertos is a compliance automation platform with expert support, the fourth approach in the table above. The platform covers ISO 27001, NIS2, the GDPR, SOC 2, TISAX, ISO 42001, and the EU AI Act in one shared control set. It collects evidence through more than 300 integrations, it is hosted in the EU, and the interface is available in German, English, and French.
Alongside the software, certified experts in information security and data protection work with customers. The company decides how closely: its own team leads and Kertos equips it, certified experts support it from implementation to audit, or Kertos appoints an external CISO or external DPO. In every option, management's responsibility under the GDPR and NIS2 stays with the company.
For the audit, internal and external auditors get their own access to the platform, and the Statement of Applicability can be exported directly. So far, every customer Kertos has taken into an audit has passed. Kertos customers particularly point out that the platform replaces scattered spreadsheets and manual workflows:
"We needed a data protection system that scales with fast growth and meets ISO 27001 requirements, without burning internal resources. We also wanted it to replace a mix of manual processes, spreadsheets and outdated tools."
Jennis B., Implementation Specialist, Small-Business (50 or fewer emp.), G2
If you want to test the criteria in this guide against a concrete scenario, book a demo with your own tech stack and frameworks.
Frequently Asked Questions
What is compliance software?
Compliance software is a system in which a company manages regulatory requirements, measures, and evidence in one place, with owners, deadlines, and history. In information security and data protection, it covers frameworks such as ISO 27001, NIS2, GDPR, SOC 2, and TISAX and collects evidence as automatically as possible through integrations. Whistleblowing and anti-corruption tools belong to a different category.
What is the difference between GRC software and compliance software?
GRC software is the umbrella term for governance, risk, and compliance and, in large corporations, often also covers financial risk, internal control systems, and internal audit. Compliance software for information security and data protection is narrower and focuses on frameworks such as ISO 27001, NIS2, and the GDPR. Many vendors use the terms interchangeably; what matters is which frameworks a tool covers in substance.
How much does compliance software cost?
The costs consist of the license, implementation, internal staff time, audit fees, and consultants where needed, and the license is rarely the largest item. As a reference, the classic consulting route to ISO 27001 certification for a company with 50 to 200 employees in the German-speaking market costs €37,000 to €80,000 in year one by our breakdown, excluding software licenses and internal staff time. Compare offers over a three-year certification cycle.
Do small businesses need compliance software?
Not always. A company with fewer than 30 employees, a single framework, and a one-off customer request can often manage with templates and a few consulting days. A platform usually pays off as soon as a second framework comes along or annual audits are due.
Can compliance software guarantee certification?
No. For ISO 27001, an accredited certification body decides after a two-stage audit, and a SOC 2 report is issued by an independent auditor. Software makes sure controls, policies, and evidence are complete and current; whether the measures work in daily operations depends on the people and processes in the company.






