Resources · Blog
Blog
Articles and guides, newest first. Part of the Resources hub.
Latest posts
- GuideDORANIS2ISO 27001· 4 min read
What a new framework version changes — and what it must never touch
A framework pack gets a new version. Which applicability decisions carry over, which need review, which are gone — and why the old adoption must stay frozen.
Read → - GuideISO 27001· 5 min read
ISO 27001 clause 9 without the slide deck: internal audit and management review on a derived posture
Clause 9 asks for monitoring, internal audit and management review. When posture is computed from records, the review is a delta between two frozen snapshots.
Read → - GuideNIS2· 5 min read
NIS2 incident reporting: the 24-hour, 72-hour and one-month path as a runbook, not a policy
Article 23 sets three deadlines and asks different questions at each. Who decides "significant", who notifies whom, and which records the answers come from.
Read → - ArticleDORANIS2ISO 27001· 4 min read
A backup restore drill is evidence — if you record it like one
DORA, NIS2 and ISO 27001 ask whether you can restore, not whether you back up. What turns a restore test into evidence: date, scope, control, the gap it found.
Read → - GuideDORA· 4 min read
The DORA register of information in 30 minutes: a walkthrough of the checklist
Run the register-of-information checklist with three people in half an hour: which records to open first, what "Partly" usually means, and what to do next.
Read → - ArticleDORANIS2ISO 27001· 5 min read
Four-eyes per flow: what a second approver actually changes — and when a single-admin tenant may switch it off
Segregation of duties is only real when the system refuses a self-approval. Which three flows carry it, what an approver may do, how an exception is audited.
Read → - ArticleDORANIS2ISO 27001· 4 min read
Evidence recency: why "twelve months" is not a rule, and what to measure instead
Auditors do not ask how old evidence is; they ask whether it still shows the control operating. Measure recency per control against its own review period.
Read → - GuideDORANIS2ISO 27001· 4 min read
Provider → service → function: the three links most third-party obligations read back to
DORA Art. 28, NIS2 Art. 21(2)(d) and ISO 27001 supplier controls all assume you know which provider delivers which service to which function. Model it once.
Read → - GuideDORANIS2ISO 27001· 5 min read
Applicability has five scopes — and "tenant-wide" is usually the wrong first answer
A requirement rarely applies to a whole organisation. Deciding applicability per asset, IT service, business solution or process makes "not applicable" hold up.
Read → - GuideDORA· 5 min read
The DORA testing programme is a scoping problem before it is a testing problem
DORA Article 24 asks for a yearly, risk-based testing programme. The hard part is not the test: it is deriving scope from the inventory and closing every gap.
Read → - ArticleDORANIS2ISO 27001· 4 min read
Why a compliance percentage should never be typed into a box
A posture number somebody typed is a slide, not a fact. What deriving posture from adoption, applicability, coverage and evidence means — and why you freeze it.
Read → - GuideISO 27001· 5 min read
The Statement of Applicability is a decision log, not a checklist
ISO/IEC 27001 asks for the one thing most SoAs lack: the reason. Keeping applicability, justification and implementation status as records that outlive audits.
Read →
See it on your own frameworks
A walkthrough on a workspace set up for your sector. No trial sign-up, no credit card.