Guide

Cyber Risk Assessment Report Example and Template

Follow one fictional SaaS risk from an evidence sample to a reviewed finding, an executive summary and a sequenced action plan. Copy the outline for your own review.

By Nick Shevelyov 5 min read

What should a cyber risk assessment report include?

A cyber risk assessment report records the scope of a security review, the evidence examined, the resulting findings, and the actions and decisions they call for. A COO or CTO should be able to use it to decide which risks to fund, address first, or formally accept. The report should also give the reader enough detail to judge how far the conclusions apply.

NIST SP 800-30 Rev. 1, Appendix K describes an example report with an executive summary, detailed results, and supporting appendices. It is guidance for federal organizations and offers an adaptable structure. For the assessment method itself, see the cybersecurity risk assessment guide.

Fictional SaaS example

This educational example from vCSO.ai uses a fictional B2B SaaS company, illustrative dates, and simulated evidence. The support team uses a helpdesk platform with a bulk export feature that produces files of customer tickets. The scoped review covers privileged access to the export function and the logging around it. The helpdesk vendor’s internal controls and API integrations fall outside the scope.

Evidence sample

In the example, the assessors review the application’s export-permission listing, authentication configuration, and logging settings on March 10. They confirm which roles need export access with Support Operations.

Evidence Source Observation in the example
E1 Export-permission listing 14 accounts have bulk export permission.
E2 Support Operations access review Five of the 14 accounts still have access after a role change removed the need for it.
E3 Authentication configuration and access listing One of the remaining nine accounts is shared and uses a local password outside single sign-on.
E4 Logging and alert configuration Export logs are retained for 30 days. No bulk export alert is configured.

Reviewed technical finding

Field Finding F-03
Title Excess and shared access to support ticket exports
Evidence Five of 14 accounts retain access after a role change (E1, E2). One shared account uses a local password outside single sign-on (E3). Export logs are retained for 30 days, and bulk exports trigger no configured alert (E4).
Plausible consequence Someone with a compromised or misused export account could download customer support records. The export could go unnoticed until its log entry expires.
Open coverage Vendor-side access and API token permissions were outside scope. The evidence sample establishes the configuration at review time.
Confidence High for the observed settings. Whether export access was misused remains undetermined.
Rating and rationale Pending. Confirm the sensitivity of the records in scope and estimate the likelihood of unauthorized export before applying the organization’s likelihood and impact criteria.
Accountable owner Head of Support Operations
Review A second assessor checks the finding against E1–E4 on March 12.

Executive summary

The review examined privileged access to the helpdesk export function from March 3 through 12. Five of 14 accounts no longer need bulk export rights. One shared account bypasses single sign-on, and bulk exports trigger no alert. This creates a path for customer support data to leave the company without timely detection. Support Operations owns the response. By March 20, leadership needs to decide whether to restrict export to named Support Leads while Engineering improves detection.

For the separate task of turning findings into a recurring board briefing, see the cybersecurity board reporting guide.

Sequenced action plan

Step Action Owner Dependency Evidence of completion Illustrative target
1 Remove export permission from the five accounts that no longer need it Head of Support Operations Confirm access needs with managers Recheck the updated permission listing against the five accounts identified in E1 and E2. March 20
2 Move the legitimate workflow to individually assigned access and retire the shared account Identity and IT Lead Identify the workflow and approve the named operators Verify the account identified in E3 is disabled and the named operator can run an authorized test export. April 3
3 Send export events to central logging, alert on bulk exports, and apply the approved retention period Platform Engineering Lead Confirm logs identify the operator and agree on retention Match a test export to the named operator in central logs. Confirm the alert reaches the response owner and verify the approved retention setting. April 17

Executive decision. The COO decides by March 20 whether to limit export rights to named Support Leads while the work is in progress. If leadership needs a temporary exception, record the business reason, residual exposure, approver and expiry, then revisit it when the controls are tested.

Copyable report outline

CYBER RISK ASSESSMENT REPORT — [Company] — [Report date]

1. Executive summary
   Scope reviewed: [systems, period]
   Key risks: [findings that require leadership attention]
   Decisions requested: [decision, decision owner, due date]

2. Scope and coverage
   In scope: [systems, data, access granted]
   Open coverage: [items left uncovered and why]
   Evidence sources: [listings, configurations, interviews, dates]

3. Findings (repeat per finding)
   ID and title: [F-xx, title]
   Observed evidence: [what was seen, sample size, date]
   Plausible consequence: [what could follow]
   Open coverage: [what this finding could not confirm]
   Confidence: [level and reason]
   Rating: [rating and basis]
   Accountable owner: [role]
   Decision needed: [decision and date]
   Review: [reviewer role, date]

4. Action plan
   Action | Owner | Dependency | Validation evidence | Target date

5. Appendices
   [Evidence index, rating criteria, glossary]

How can you tell whether an assessment report is useful?

Use these questions when comparing proposals or reviewing a delivered report.

  • Does the report name the systems and period reviewed and identify gaps in coverage?
  • Can you trace each finding to dated evidence?
  • Does it explain the potential consequence and how confident the assessor is?
  • Do priority actions have an owner, a due date, and a way to verify completion?
  • Which decisions need executive approval, and when?
  • Who reviewed the findings and resolved corrections?

The fractional CISO hiring guide offers questions to ask when a provider shares a work sample. vCSO.ai’s Cyber Risk Assessment and Fractional CISO Leadership service can start with a scoped evidence review and deliver a reviewed technical report, an executive summary and a prioritized action plan. Access and coverage are agreed at kickoff. Implementation and ongoing leadership are scoped separately.

Ready to turn this into a working plan?

Our team helps growth-stage companies, PE/VC sponsors, and cybersecurity product teams translate security questions into board-ready decisions. First call is strategy, not vendor pitch.

Scope an assessment