Three routes into scope
Where you start depends on what is forcing the decision
Some teams arrive with a named obligation, some with a sector operating model, and some with something that happened last week. All three routes lead into the same service catalogue.
By regulatory obligation
The same requirement can be assessed or built
An audit answers where the entity stands and what is in scope. An implementation builds what is missing and hands ownership to the people who run the process.
NIS2
Entity scope, management accountability, risk-management measures, incident handling and supplier oversight.
DORA
ICT risk governance, incident process, resilience testing, continuity and third-party arrangements.
ISO 27001
ISMS gap analysis and internal audit, risk treatment, Statement of Applicability and certification readiness.
GDPR
Processing, data-subject rights, suppliers, retention, security measures and breach handling.
ISO 9001
Quality management where security controls have to survive the same audit and review cycle.
IT system controls
Access, change, logging and continuity controls as a customer, insurer or auditor asks to see them.
Whistleblower protection
Confidential reporting channels, case governance, data protection and follow-up action.
Digital accessibility
Expert and manual assessment of WCAG conformance across real user journeys.
By industry
Risk looks different depending on the service at stake
By situation
The most common reasons for a first conversation
None of these routes describe your position?
Share the operating context and the requirement you need to close. We will come back with a scope that fits.