Executive Summary
A concise written account for leadership of what was examined, what the evidence supports, and where uncertainty remains.
F/01Flagship Report
Critical Service Disruption & Cyber Resilience
Evidence Report
Can you demonstrate what happens if a critical digital service fails?
Cyber Analysis produces an independent written report examining what the available evidence shows about how a critical digital service depends on systems, suppliers and decisions, and what that means if the service is disrupted.
The report does not test live systems. It examines the evidence the organisation supplies, within a scope agreed before work begins.
02Purpose
Why Organisations Commission This Report
Boards, executives and risk owners are increasingly asked to explain how essential services would be affected by disruption.
Plans and policies often exist. What is harder is showing how the service actually depends on systems, suppliers and people, and which assumptions have been demonstrated.
This report sets out what the evidence supports, what it does not, and what remains unresolved.
03Scope
Questions the Report Examines
The exact questions are agreed during scoping. Depending on the agreed focus, the report may examine the following.
- Which digital services does the organisation regard as critical, and on what basis?
- What systems, data, identities and suppliers does each service depend on?
- Where do single points of dependency appear in the evidence?
- Who holds authority to make decisions if the service is disrupted?
- Which recovery assumptions are documented, and which have not been demonstrated?
- What does the evidence not yet allow the organisation to say with confidence?
04Client Inputs
What the Organisation Supplies
The report is based on evidence supplied by the organisation. Its findings can only be as complete as that evidence. Typical inputs include the following.
- Identification of the service or services in scope
- Architecture, configuration or dependency documentation already held
- Supplier and contract information relevant to the service
- Incident, continuity and recovery plans, and any records of their use
- Governance records: roles, risk registers, decision logs
- Access to agreed individuals for structured discussion
05Method
How the Analysis Is Conducted
The report follows the Cyber Analysis Methodology.
Observations are recorded first. Evidence is examined. Potential concerns are examined against the available evidence. Those that cannot be substantiated are recorded as unverified rather than presented as established findings.
Conclusions are stated only to the extent the evidence allows.
To see this reasoning in practice, read the illustrative case examples. They are illustrative and do not describe real client engagements.
A full fictional sample of this report shows the exhibits, dependency table, findings and deliverable format.
06Deliverables
What the Written Report Contains
Deliverables are confirmed in the agreed scope. Their depth depends on the evidence supplied.
Dependency Analysis
A written analysis of the systems, data, suppliers and decisions the service relies upon, as described by the evidence supplied.
Evidence Register
A record of the evidence examined, its source and date, and which findings it supports.
Substantiated Findings
Findings stated only where supported by evidence, each referenced to the register, with concerns that were examined and not supported recorded as such.
Unresolved Questions
Questions the evidence could not answer, set out for leadership and the teams responsible for the service.
07Limitations
What the Report Does Not Provide
The report is a focused, evidence-based analysis of agreed questions, not a full-scope consultancy audit. It is not any of the following.
Where evidence is incomplete, the report says so rather than filling the gap with assumption.
Not a penetration test or vulnerability scan
Not an incident response or recovery service
Not a business continuity or disaster recovery certification
Not a compliance audit or attestation
Not a live disruption exercise or technical simulation
Not a guarantee that the service will remain available or recover
08Independence
Independence
Cyber Analysis does not recommend products or vendors.
Cyber Analysis does not use its reports to sell implementation services.
Every Cyber Analysis report is produced independently using the same evidence-led methodology regardless of organisation, technology, vendor or outcome.
09Engagement
How a Scoped Engagement Begins
- 01
Initial enquiry
Email hello@cyber-analysis.com describing the service of concern and the decision the report is intended to support.
- 02
Scoping discussion
The service, questions, evidence available and boundaries are discussed.
- 03
Scope agreed in writing
Work begins only once the scope and deliverables are agreed.
- 04
Evidence and analysis
Supplied evidence is examined using the Cyber Analysis Methodology.
- 05
Written report
The report is delivered in the agreed form.