Sightadel

Tool · Matrix

One piece of evidence, several frameworks.

Sixteen topics, twelve frameworks. The matrix shows where requirements overlap and where they only partly do. Select your frameworks and tap a cell for the explanation.

Show frameworks

● covered◐ partly– not a topic of its ownQualitative assessment; your scope is what counts.

Coverage of topics by framework
TopicISO/IEC 27001ISO 9001ISO/IEC 42001NIS2GDPRBSI C5:2026DORANIST CSF 2.0SOC 2HACCP§ 390 SGB VEU AI Act
Risk management
Access control
Vendors and service providers
Incident management and reporting
Emergency and business continuity
Training and awareness
Document control
Internal audit
Management review
Data protection
Cryptography
Logging and monitoring
Vulnerabilities and patches
Asset management
AI governance
Food safety
Select a cell

Tap or point to a cell in the matrix. This box then shows what the framework requires on that topic.

Explanation

Why frameworks overlap so often.

Most regulations ask the same basic questions: who is responsible, what is risky, what is being done, and how can it be evidenced.

If you have built up ISO 27001 and then hear about NIS2, you are right to ask whether everything starts from scratch. The answer is almost always: no. Risk management, access control, vendor management, incident handling, training – these topics appear in almost every information security regulation. They are just named slightly differently each time and audited in varying depth.

Same topic, different perspective

An ISO standard asks whether your management system has planned, implemented, reviewed and improved a topic. A law such as NIS2 or DORA asks whether specific obligations are met and deadlines kept. The GDPR looks at the rights of the people whose data you process. An audit report such as SOC 2 or a C5 attestation assesses whether controls work as described. The topic stays the same. What changes is the question the auditor asks.

What ● and ◐ mean

A full dot means: the framework addresses the topic explicitly and with its own requirements. A half dot means: the topic appears, but only at the margins, for a narrower purpose or without specific requirements. A dash does not mean the topic is unimportant. It is simply not a subject of its own in this framework. Every assessment is deliberately rough. How much you can actually reuse depends on your scope: which sites, processes and systems are included and how good your evidence already is today.

One piece of evidence, several frameworks

The biggest effort rarely lies in understanding a standard, but in maintaining the evidence. An access policy, a record of a recovery test, a vendor contract with security clauses – such evidence often serves several frameworks at once. If you store it in separate folders for each project, you maintain it several times and at some point lose track of which version applies.

In Sightadel, every piece of evidence is stored once in the evidence archive and assigned to the matching controls of several frameworks. If a document expires or changes, you see which frameworks are affected. For anything a framework additionally requires, such as the NIS2 reporting deadlines or the data protection impact assessment under the GDPR, you add specific supplementary evidence.

Where the matrix ends

The matrix does not replace a gap analysis. It shows you where to look, not what you are missing. For the detailed work, you go through the controls of a framework one by one. That is exactly what the guided assessments in Sightadel are built for.

Questions and answers

Questions about the framework matrix

More in our FAQ or directly via our contact form.

Why are there no percentages for the overlap?

Because a number suggests a precision that does not exist. How much can be reused depends on your scope, your processes and the maturity of your documentation. The matrix therefore only shows where topics overlap and explains each assessment in one sentence.

Does ● covered mean that one piece of evidence is enough for both frameworks?

Not automatically. It means that both frameworks address the topic explicitly. Depth, deadlines and audit approach can differ. A well-maintained piece of evidence is a good starting point; often only one detail needs adding.

Which combinations are particularly common?

ISO 27001 with NIS2, ISO 27001 with the GDPR, and ISO 9001 with HACCP. Cloud providers add BSI C5 or SOC 2, financial entities DORA. If you develop or use AI, you add ISO 42001 or the obligations under the EU AI Act.

How does Sightadel use these overlaps?

Evidence is stored once in the evidence archive and assigned to the matching controls of several frameworks. If a document changes, you see which frameworks are affected. Duplicate filing and conflicting versions disappear.

Store evidence once, use it many times.

14 days, full access, no payment details. Everything you set up carries over into the paid plan.