Frameworks
One product. Several rulebooks.
One set of evidence.
Complia holds requirements from regulations, standards and your own policies side by side – each with its source and version – so evidence collected once can support every requirement it actually meets.
With dedicated product workflows
- EU Cyber Resilience ActRegulation (EU) 2024/2847Cybersecurity requirements for hardware and software products sold in the EU – including vulnerability and incident reporting.Read more
- ISO/IEC 27001:2022Information security management systems – RequirementsRequirements for an information security management system – often expected by customers, partners and procurement.Read more
- IEC 62443-4-1 and 4-2Security for industrial automation and control systemsSecurity for industrial automation and control systems – secure development and technical requirements for components.Read more
- MIL-STD-882EDepartment of Defense Standard Practice: System SafetySystem safety for defence systems – identify hazards, assess risk and record who accepted the residual risk.Read more
More in the standards catalogue
These regulations are available as ready-made article structures with links to the official text. Requirements are applied, owned and evidenced like any other source; the structure is marked unchecked until your team has verified it against the official text.
Ready-made structures in the catalogue
- Machinery RegulationRegulation (EU) 2023/1230 on machineryHealth and safety for machinery placed on the EU market – now including protection against corruption and safe control systems.Read more
- EU AI ActRegulation (EU) 2024/1689 laying down harmonised rules on artificial intelligenceRisk-based rules for AI systems – from prohibited practices to obligations for high-risk systems and general-purpose models.Read more
- NIS2Directive (EU) 2022/2555 on a high common level of cybersecurityCybersecurity risk management and incident reporting for essential and important entities.Read more
- DORARegulation (EU) 2022/2554 on digital operational resilience for the financial sectorDigital operational resilience for financial entities – and what their ICT suppliers are asked to show.Read more
Your own standards, on equal terms
Internal policies, customer specifications, industry standards – anything your products must meet becomes a requirement source, handled exactly like the built-in frameworks.
- 01
Bring it in the way you have it
Paste rows from Excel, upload a CSV or JSON file – or let document analysis read a PDF or a scanned document and propose the requirements. Nothing is added until a person approves it.
- 02
Published as versions
A standard is published as a numbered edition that is never edited afterwards. Each product locks the edition it follows; a new edition shows exactly what changed before anyone adopts it.
- 03
Yours or your organisation's
Keep a standard personal while you build it, or publish it to your organisation so every team applies the same requirements.
- 04
Next to the official frameworks
Your requirements get owners and evidence like any other, and can be cross-mapped to the CRA, ISO/IEC 27001 and the rest – so one piece of evidence supports both.
Standard texts stay licensed
ISO and IEC standards are sold under licence. Complia works with their structure and reference numbers; the wording stays in the copy your organisation has bought.
See it with your own product.
We go through your requirements, owners and next steps in a walkthrough.