← All Insights
NIS2 · CRA · ISO 27001 · Germany & DACH

TheComplianceSprint

Start with a clear picture. Agree a practical scope. The Compliance Sprint helps organise existing structures, open items and possible next steps across NIS2, CRA and ISO 27001. It does not promise audit readiness or conformity.

// sprint_tracker.live ◉ ACTIVE
01 — Baseline & open questions ASSESS
02 — Risks & priorities PRIORITISE
03 — Documentation & governance ALIGN
04 — Awareness & incident readiness NEXT STEPS
Agreed results & handover PENDING
01Agreed scope
4Phases
3Frameworks
01

Compliance Takes Too Long

Traditional ISO 27001 implementations span 12–18 months. Consultancies bill by the hour and incentivise complexity. SMEs cannot afford the time or the cost.

02

Requirements Are Ambiguous

NIS2, CRA, and ISO 27001 use overlapping, technical language. Most organisations cannot map what they already do to what regulators actually require without expert guidance.

03

Audit Prep Is Reactive

Evidence is gathered under pressure in the weeks before an audit. Gaps surface too late to close. The result is a stressful, expensive scramble that repeats every cycle.

04

Governance Is Undocumented

Roles and responsibilities exist informally. Without a RACI framework and documented procedures, regulators cannot verify accountability — regardless of actual security maturity.

05

Risk Is Not Quantified

Risk registers either do not exist or list assets without scored severity. Unquantified risk cannot be prioritised, resourced, or reported to the board with confidence.

06

Incidents Have No Playbook

NIS2 mandates incident reporting within 24 hours of awareness. Without a tested incident response procedure, that deadline cannot be met — and regulators will notice.

A structured route
to practical next steps

Work is individually scoped after an initial discussion. Phases and outcomes depend on your starting point, agreed scope and contribution; no fixed duration or audit result is promised.

PHASE 01

Orientation & Gap Analysis

Discuss the starting point, existing security work and open questions with leadership and IT. Review applicable requirements for the agreed scope and record possible gaps and assumptions.

CyberCheck Basic Gap Register Stakeholder Interviews
→
PHASE 02

Risk Assessment

Consider risks against agreed criteria and available information. Identify priority actions and management decisions together.

ISO 27005 Risk Register Quick-Wins
→
PHASE 03

Documentation & Governance

Organise roles, responsibilities and existing IT operations documentation for the agreed scope. An overview can make status, evidence and open issues visible.

RACI IT Ops Docs Compliance Overview
→
PHASE 04

Awareness & Incident Readiness

Depending on the agreed need, consider awareness, incident response arrangements or a tabletop exercise. Findings and further work are agreed with your team.

Awareness Workshop NIS2 IR Playbook Tabletop Exercise
Outputs Gap Analysis Report ISO 27005 Risk Register RACI Framework IT Operations Docs Compliance Overview NIS2 IR Procedure Awareness Workshop Prioritised next steps

What You Leave
With

Possible outputs are agreed after scoping. They support your internal work; they do not guarantee external audit readiness or conformity.

⬡

Gap Analysis Report

A prioritised view of open items across agreed frameworks, with potential next actions and sequencing to discuss.

◎

ISO 27005 Risk Register

A risk overview based on the agreed criteria and available information, including potential owners and actions.

▣

RACI Governance Framework

Role and responsibility assignments for the agreed areas, for review and confirmation by your organisation.

◈

IT Operations Documentation

Potential procedure topics include patch management, access control and backup, based on your infrastructure and scope.

◇

Compliance Overview Document

An overview of relevant requirements, current status, evidence locations and open questions for internal use.

△

NIS2 Incident Response Procedure

Potentially includes roles, detection, escalation, reporting considerations and post-incident review, subject to agreed scope and a separately planned exercise.

○

Security Awareness Workshop

A workshop may be considered for an agreed audience and topics such as phishing, social engineering and incident reporting.

⬟

Agreed results overview

Summarise the agreed work, evidence references and remaining actions in a practical format for your organisation.

Compliance Sprints
in the Field

Selected audit experience illustrates how findings and corrective actions were handled in specific client situations. Results depend on each organisation and assessment.

ISO 27001 Stage 2 · Zürich

Legal AI Technology Company

Two-week sprint. 100% of Stage 1 findings addressed. 2 minor non-conformities raised — both resolved with accepted corrective action records. Certification confirmed by the British Assessment Bureau.

ISO 27001 Internal Audit · Austria

Medical Diagnostics Provider

Two-week internal audit with Vanta access. 15 evidence gaps identified and mapped to specific controls. Report delivered day 14 and uploaded to Vanta with a timestamped audit trail. Led to a 6-month vCISO retainer.

Compliance is not a documentation exercise — it starts with understanding your infrastructure and open decisions. A scoped sprint can organise that knowledge and make practical next steps visible.
— Axel Hoehnke · ISO 27001 Lead Auditor · ISO 42001 Lead Auditor

Built for
These Organisations

SMEs Under NIS2

  • Essential & important entities under the NIS2 Directive
  • No dedicated compliance function in-house
  • Audit deadline within 3–6 months
  • Need structured governance documentation

Scale-Ups & SaaS

  • Seeking ISO 27001 certification for enterprise sales
  • Customer due-diligence questionnaires piling up
  • Engineering-led culture without compliance process
  • Want a clearer view of open customer-review or audit preparation items

Hardware Manufacturers

  • Need to clarify whether specific products fall within the CRA
  • Need to distinguish product, role and possible sectoral exclusions
  • Need to understand the applicable CRA work and evidence
  • May need separate product-scope or technical documentation support

Regulatory
Frameworks Addressed

We can discuss overlapping requirements where they apply to your organisation or products. The CRA is assessed against the specific product and role, not applied as a blanket framework to every software or network-connected service.

ISO 27001:2022
Information security management system. Annex A controls mapped to your existing infrastructure. Gap register cross-referenced to certification requirements.
NIS2 Directive
EU Directive on network and information security for essential and important entities. Incident response, risk management, and supply chain measures addressed.
EU Cyber Resilience Act
A product-based Regulation: determine scope, manufacturer or other role, possible sectoral exclusions, remote data processing and relevant critical categories. Article 13 manufacturer duties differ from Article 14 reporting duties; those reporting duties apply from 11 September 2026, while the CRA generally applies from 11 December 2027.
BSI / ENISA Baseline
CyberCheck Basic assessment aligned to BSI IT-Grundschutz and ENISA good practices — providing an independent baseline against European national standards.
ISO 27005
Information security risk management. Risk scoring methodology, likelihood and impact matrices, risk register structure, and treatment decision framework.
Initial scoping discussion

Discuss a practical
compliance scope

An initial discussion to clarify context, current state and a suitable scope.
Fees, timeframe and possible outputs are agreed individually.

Discuss the scope

Please do not send confidential documents in your initial enquiry.

A focused review can help distinguish substantiated answers, available evidence and open actions. No confidential questionnaire upload is needed to start.

Explore the questionnaire review