Guide
Choosing compliance management software for regulated industries
Turn regulatory duties into verifiable implementation: distinguish legal registers, internal controls and GRC, then compare them using your own control process.


A regulatory change has been assessed. Yet the business department still does not know what to change. IT is working on another priority. At the next audit, the search for the decision and its implementation begins again.
This selection aid helps establish whether you need a legal register, a GRC platform or a specialist solution. You then use one control process to test whether business, compliance and IT teams can work together.
Which compliance problem do you want to solve?
“Compliance” can refer to very different tasks. A whistleblowing system receives reports. A legal register supports identifying and maintaining applicable rules. A GRC platform organises risks, internal controls and their implementation. These tasks are not interchangeable.
| Your bottleneck | Primary software requirement | What else needs clarification |
|---|---|---|
| Changes are identified too late | Maintained legal content, change service and ownership of interpretation | Which legal fields and countries are actually covered? |
| Departments implement requirements differently | Custom control requirements, owned measures and binding processes | How are local deviations decided? |
| Every audit triggers another evidence search | Evidence with period, scope and implementation context | Who judges whether it answers the review question? |
| Management receives conflicting status reports | Shared assessment basis, open decisions and traceable history | Which decision should reporting enable? |
For banks focused on ICT resilience, selection must additionally assess functions, BIA and providers. Our DORA register data quality guide provides a focused starting point. A general compliance catalogue is insufficient.
Use this template in these measures
Implementation measure
Approve and follow through supplier services
Mapped requirements (5)
- A.5.19 · Informationssicherheit in Lieferantenbeziehungen (DE)
Supporting contribution
Sections 1 and 2 connect the specific service, responsibility, risk-based assessment and approval in the existing record. Actual assessment and decisions must be made for your own services.
- A.5.20 · Berücksichtigung der Informationssicherheit in Lieferantenvereinbarungen (DE)
Supporting contribution
Section 3 supports appropriate security agreements and traceable deviation decisions. Actual agreement, legal review and implementation remain necessary.
- A.5.21 · Management der Informationssicherheit in der IKT-Lieferkette (DE)
Supporting contribution
Section 3 includes relevant ICT subcontractors, critical components, integrity and support in selection and agreements. Real supply-chain information and suitable evidence still need to be obtained and evaluated.
- A.5.22 · Überwachung, Überprüfung und Änderungsmanagement von Lieferantendienstleistungen (DE)
Supporting contribution
Section 5 connects regular and change-triggered service reviews with change decisions and corrections in the existing record. Reviews, evaluation and follow-up work must actually be carried out.
- A.5.23 · Informationssicherheit bei Nutzung von Cloud-Diensten (DE)
Supporting contribution
Sections 4 and 5 support the cloud lifecycle through specific task allocation, your own use, reviews, changes and exit. They do not prove actual configuration or implementation.
Further framework mappings of this measure
TISAX · 6.1.1
VDA ISA 6.0.3 · Partial contribution
The joint workflow supports risk-based selection and assessment of security-relevant services, suitable agreements and review of contractors and partners. Actual assessments, completed agreements, review results and applicable additional requirements remain to be evidenced. This is not a separate cloud ISA crosswalk or a claim to full objective fulfilment.
Read the source ↗
The decisive distinction: Record an obligation or manage its implementation
Take a requirement affecting several companies. First establish where it applies and who made that assessment. Then define the internal rule: what should happen in which process? Measures, owners and required evidence follow from that.
A traffic light on the requirement does not eliminate this work. If “implemented” means only that a policy was uploaded, application and effectiveness remain unresolved. For information security, ISO/IEC 27001 describes systematic management of information security risks; the existence of a file does not replace this management approach.
Practical example: A provider’s access must be revoked when its contract ends. Procurement knows the end date, IT knows the accounts and the business department knows which access is still needed. A dependable workflow defines the handover, decisions on exceptions and verification of revocation. A policy alone does not connect these three roles.
What Kopexa specifically does
In Kopexa, you model your own frameworks and controls, for example for your internal control system. Measures describe actual implementation and are mapped to suitable controls. Evidence is attached to those measures. You can therefore associate one implementation with several requirements without maintaining separate evidence collections.
For provider access, the defined revocation process is the implementation; the documented verification result is its evidence. Whether that evidence suffices for every mapped requirement remains a subject-matter assessment. Our evidence reuse guide explains this boundary.
BPMN processes make handovers and decisions visible. Versioned documents with approvals record which rule applies. The Workforce Hub brings approved policies to relevant employees; reading and quizzes can be documented. Objectives and KPIs then help assess whether the process works: is access removed on time, or are tasks merely closed?
If you also need a legal change service, whistleblowing channel or regulatory reporting route, assess those services separately. The Kopexa functions described here organise implementation of your security and compliance requirements.
Compare offers without an arbitrary ranking
Give each provider the same sanitised requirement and process change. Assess three outcomes:
- Traceability: Someone not involved can explain applicability, decision and implementation.
- Adaptability: A new location or changed requirement can be incorporated without overwriting the previous assessment state.
- Workload: Business, compliance and IT teams perform their own steps; the central coordinator need not chase every handover by telephone.
Also capture follow-on costs: legal content, setup, migration, permissions, additional frameworks and later adaptations. A low licence price loses its advantage if every control change becomes a consulting project.
Start with one control process
An existing control process with several participants is suitable for the two-week guided Kopexa trial. Aim for a complete run, including an exception and evidence. Transfer further requirements afterwards.
Prepare using the ISMS requirements checklist with PDF download. It covers information security; add your sector-specific legal and supervisory duties. If you already operate a broader internal control system, bring its control and approval model too.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Does a GRC platform replace a legal register?
Not automatically. A legal register and its change service help identify applicable obligations. A GRC platform supports operational implementation. Assess legal coverage, update services and process functions separately.
How can we compare compliance software meaningfully?
Ask several providers to take the same requirement through applicability, decision, implementation, exception and evidence. Assess traceability and ongoing effort rather than feature count alone.
Sources
- ISO/IEC 27001 — ISO [Accessed ]