The CISO's regulatory calendar for 2027: NIS2, DORA and the EU AI Act in one plan

For European CISOs, regulation has become a planning problem as much as a security problem. Three major pieces of EU law now overlap, each with its own timeline, scope and authority. Treating them as separate projects leads to duplicated work and gaps between teams. Here is a practical calendar for the year ahead and a way to run the three together.

Where things stand

NIS2. The deadline for transposing NIS2 into national law was 17 October 2024. Most member states were late, but by mid-2026, 22 of 27 had a law in force. In many countries registration windows have opened or closed, and the focus is moving from implementation to supervision and audits. Poland, for example, brought its amended National Cybersecurity System Act into force on 3 April 2026, with a twelve-month period to implement risk management obligations.

DORA. The Digital Operational Resilience Act has applied to financial entities since 17 January 2025. Regulators now expect registers of ICT third-party arrangements, tested incident processes and resilience testing, not plans.

EU AI Act. The prohibitions and the rules on general-purpose AI already apply. The Digital Omnibus on AI, in force since 27 July 2026 as Regulation (EU) 2026/1744, moved obligations for stand-alone high-risk AI systems to 2 December 2027 and those for AI embedded in regulated products to 2 August 2028. The extra time is useful, but building an AI inventory and classifying systems takes months.

"A deferred deadline is like the gap between lightning and thunder," says Alexis Hirschhorn, CEO of Acuna GRC, ISO/IEC 42001 Lead Auditor and CISSP with more than 25 years in information security. "It tells you how far away the storm is, not that it has passed. The organisations I see doing well used the Omnibus to plan their AI inventory properly, not to put it off."

A calendar for 2027

Q1 – Consolidate. Bring NIS2, DORA (if relevant), ISO 27001 and GDPR into one control library. Identify shared controls: access management, incident handling, supplier risk, business continuity. Assign one owner per control.

Q2 – Prove it works. For every control, define the evidence and collect it. Run a tabletop exercise against the NIS2 reporting timeline (24-hour early warning, 72-hour notification, one-month final report) and, for financial entities, DORA's incident classification.

Q3 – AI inventory. List every AI system the organisation builds or uses, classify it under the AI Act, and decide which ISO/IEC 42001 practices to adopt. Plan for the December 2027 deadline now rather than in autumn.

Q4 – Board reporting and audit readiness. NIS2 makes management bodies accountable for approving and overseeing cybersecurity measures. Give the board a regular view of risks, decisions and progress across all three regulations, and record their training.

Three mistakes to avoid

Reading the AI Act delay as a pause. The prohibitions and the general-purpose AI rules are already live, and an AI inventory is needed long before December 2027.

Leaving supplier risk to procurement alone. NIS2 and DORA both expect security to assess critical suppliers and follow up on findings. A questionnaire filed once a year will not satisfy either.

Reporting activity instead of decisions. Boards need to see which risks were accepted, which investments were approved and what changed as a result, not a list of completed tasks.

Run it as one programme

The biggest saving comes from treating the three laws as one programme with shared controls, shared evidence and one risk register.

"Across more than 200 audits, I have seen the same valley mapped three times by three different teams," says Hirschhorn. "NIS2, DORA and the AI Act each get their own survey, but the rivers are in the same place on every map: access, suppliers, incidents, continuity. Draw them once, then add what is genuinely specific to each law."

This is where purpose-built tooling helps. Acuna GRC, a Swiss AI-native governance, risk and compliance platform, is designed for exactly this kind of multi-framework work, covering NIS2, DORA, the EU AI Act, ISO 27001 and ISO 42001 in one place.

Whatever tooling you use, the principle is the same: one control, one owner, one set of evidence, reused for every regulator who asks. For a CISO juggling three timelines, that is the difference between a calendar that holds and one that slips.

 

★
★
★
★
★
Votes: 0
E-mail me when people leave their comments –

Scott is a Marketing Consultant and Writer. He has 10+ years of experience in Digital Marketing. If you need more information please contact on readdive@gmail.com.

You need to be a member of CISO Platform to add comments!

Join CISO Platform

Join The Community Discussion

CISO Platform

A global community of 6K+ Senior IT Security executives and 40K+ subscribers with the vision of meaningful collaboration, knowledge, and intelligence sharing to fight the growing cyber security threats.

Join CISO Community Share Your Knowledge (Post A Blog)
 

 

 

Turbo Talks: Safe AI Agents — Guardrails, Scope Enforcement and Governance

  • Description:

    Turbo Talks is a free 20-minute live session series on agentic AI pentesting and AI safety for security leaders, hosted by CISO Platform. Technology partner: FireCompass.

    Speaker: Bikash Barai, Founder & CEO, FireCompass

    As offensive AI agents get more capable, control becomes the harder problem. Practical guardrails and governance for deploying them safely.

    Time: 11:30 AM ET / 7:30 PM GST / 9:00 PM IST ·…

  • Created by: Priyanka Aash
  • Tags: turbo talks, agentic ai, ai safety

CISOPlatform Breakfast Mumbai: Offensive Security for CISOs

  • Description:

    Theme: Offensive Security for CISOs — Validating Exposure at Attacker Speed

    A closed-door breakfast for CISOs and heads of security. Peer discussion under the Chatham House rule, not a product presentation.

    What the table will work through

    1. Exploit windows in days, not months. Edge devices, CI/CD and AI gateways were all exploited within weeks of disclosure this autumn (GitLab CVE-2026-97229, Cisco ASA/FTD…
  • Created by: Priyanka Aash
  • Tags: ciso breakfast, mumbai, offensive security, pentesting

CISOPlatform Dinner Delhi: Red Team Stories and 2027 Priorities

  • Description:

    Theme: Red Team Stories and Offensive Security Priorities for 2027

    An invite-only dinner for CISOs and security leaders in Delhi. Informal peer conversation under the Chatham House rule.

    Conversation starters

    • What did attackers (or your red team) find first in your environment, and what did you change after?
    • AI agents on both sides: attackers automating exploitation, and defenders using agents to pentest.
    • Your top…
  • Created by: Priyanka Aash
  • Tags: ciso dinner, delhi, offensive security, red teaming

CISOPlatform Dinner Delhi: Red Team Stories and 2027 Priorities

  • Description:

    Theme: Red Team Stories and Offensive Security Priorities for 2027

    An invite-only dinner for CISOs and security leaders in Delhi. Informal peer conversation under the Chatham House rule.

    Conversation starters

    • What did attackers (or your red team) find first in your environment, and what did you change after?
    • AI agents on both sides: attackers automating exploitation, and defenders using agents to pentest.
    • Your top…
  • Created by: Priyanka Aash
  • Tags: ciso dinner, delhi, offensive security, red teaming