← Back to blog

All Security Requirements Say the Same Thing: 12 Processes Cover the World

Every New Framework Costs More Time and Money Than It Should

Most organisations handle compliance one project at a time. GDPR in 2018. NIS2 now. DORA for the financial sector. AI Act next year. Each time, consultants are hired, a new working group is formed, a new checklist is drawn up.

The result is parallel tracks that never converge. The GDPR project has no idea what the NIS2 project is doing. The vendor review under DORA has zero connection to the data processing agreement review under GDPR. Leadership receives reports from three directions that are really all about the same underlying problem: lack of control.

It is inefficient. But it stems from a misconception: that each framework is unique and requires its own solution.

An organisation that works systematically with 12 core processes will, in practice, be compliant with 80 to 90 percent of the world's security requirements — digital, physical, legal and organisational.

All Frameworks Ask the Same Fundamental Questions

Whether a framework originates from the EU, the USA, China, Brazil or Sweden, they all ask your organisation the same six fundamental questions:

  • Do you know what you have and what needs protecting?
  • Do you understand the risks to your business?
  • Do you control who has access to what?
  • Can you detect and respond to incidents?
  • Can you continue to deliver even when disruptions occur?
  • Can you demonstrate that you follow your own rules?

These six questions translate into 12 processes. Not technical configurations, not checklists. Processes: structured, owned and measurable ways of working.

  1. Governance and management accountability
  2. Risk management
  3. Information classification and data protection
  4. Policies and guidelines
  5. Identity and access control
  6. Technical security controls
  7. Logging, monitoring and detection
  8. Incident management and reporting
  9. Business continuity and recovery
  10. Supplier and third-party management
  11. Training and awareness
  12. Audit, review and improvement

The frameworks GDPR, NIS2, DORA, AI Act, ISO 27001, NIST CSF, Säkerhetsskyddslagen, HIPAA, PCI-DSS, SOC 2, CCPA, PIPL, LGPD and CRA are all covered by these 12 processes. The prioritisation and depth vary, but the underlying structure is identical.

What This Actually Means for Leadership

Multi-framework mapping is not a technical tool. It is a governance tool. It gives leadership answers to three questions that would otherwise require three separate consulting engagements:

  • Where are we today? Which of the 12 processes are mature, which are weak and which are missing?
  • Which frameworks are relevant to us? And how well does our current capability cover them?
  • What do we do next? A prioritised action plan based on risk, not on what happens to be in the news.

An organisation with good maturity across all 12 processes can receive a new regulatory requirement and, instead of launching a new project, map the gap against existing capability. That is the difference between building a security capability and chasing checklists.

The Board's Role

Process 1, governance and management accountability, is not one of twelve. It is the foundation for all the others. The board and executive team must own the risks, make decisions and follow up. That is what NIS2 requires, what DORA specifies and what ISO 27001 builds its management system on.

It cannot be delegated to IT. It cannot be purchased as a service. It must be integrated into how the organisation is governed, budgeted and reported.