a QSBN company Sheet 05 · Sample report Get the sample report

HomeSample report

Inside a 360° Security Assessment report.

Every 360 SAM ends with two documents. A board presentation tells management where the company stands and what it costs. A detailed findings report gives IT the evidence and the fix for every issue. Below are excerpts from both, for a fictional company.

Part 1 · Board presentation

Progress is visible. The remaining risk is concentrated.

The board sees one maturity score, what has improved, what is still open and what it is likely to cost. Every statement is tied to evidence in the detailed report.

Sample data · a fictional sample company · board presentation, June 2026

Maturity, 2024 → 2026

1 2 3 4 Target L3 2024 · 2.3 2026 · 2.5

Improved from Basic to Standardized, still below the recommended Level 3. The 2024 survey used CIS v8.0, so read it as a trend rather than a one-to-one comparison.

Source: CSAT 2024 and 2026 reports

Executive message

Progress is visible, but the remaining risk is concentrated in areas attackers commonly exploit first: identities, exposed remote access, vulnerable software and data classification.

Source: board presentation, executive summary

At a glance

Entra ID accounts without MFA
16
Applications with known risks
22
Shared SharePoint documents
53
Endpoints missing critical updates
0

Source: overview and recommendations

Improved since 2024

  • Email trustSPF, DKIM and DMARC in place for the main domains.
  • Backup resilienceBackups properly managed and kept off-site.
  • Identity foundationMicrosoft Entra ID and AD used for most authentication.
  • Endpoint managementIntune inventory, Windows almost fully up to date, central anti-malware.
  • Security visibilitySecure Score, Cloud Secure Score, Azure Policy and external scan evidence added.

Still open

  • Data protectionWeak classification and labelling; DLP coverage incomplete.
  • Identity hygieneMFA gaps, dormant users, local and admin account hygiene.
  • Vulnerability managementCritical and high CVEs, end-of-life products, risky applications.
  • Service providersSupplier access, security requirements and offboarding need a formal process.
  • Incident readinessIncident response and penetration testing need annual tests and an owner.
  • AI governanceNew in 2026: shadow AI, logging and sensitive-data controls.

Threat map

Each business risk plotted by likelihood and impact. The top-right quadrant gets priority.

Estimates from IBM Cost of a Data Breach 2025, NetDiligence 2024, PwC 2025, Gartner

Annualised Loss Expectancy

Expected cost of security incidents over two years, at today's maturity versus Level 3 and Level 4. Reaching Level 3 roughly halves it.

0100k200k300k400k 04812162024 Months
Current maturity $383k Level 3 $183k Level 4 $124k

USD, accumulated over 24 months · IBM/Ponemon 2025, NetDiligence 2024, PwC 2025, Gartner

Recommended board message

“The organisation has improved its security maturity, but must now close recurring gaps in identity, data protection, vulnerability management, AI governance and external exposure to reach a sustainable Level 3 posture.”

Every control, scored.

The overall score is built up from all 18 CIS controls, plus additional questions on governance and AI. You can see at a glance which controls hold the organisation back.

1 · Enterprise asset inventory2.0
2 · Software asset inventory2.3
3 · Data protection2.0
4 · Secure configuration2.2
5 · Account management2.3
6 · Access control management2.3
7 · Continuous vulnerability mgmt2.7
8 · Audit log management3.0
9 · Email & browser protections2.8
10 · Malware defences3.0
11 · Data recovery3.5
12 · Network infrastructure mgmt3.2
13 · Network monitoring & defence2.7
14 · Security awareness training2.0
15 · Service provider management2.0
16 · Application software securityn/a
17 · Incident response mgmt2.5
18 · Penetration testing2.0
AQ · IT governance2.4
AQ · Data governance2.8
AQ · AI usage & governance1.8
Level 3 target

Source: board presentation, CIS maturity and additional questions

Part 2 · Detailed findings report

Finding, risk, fix. For every issue.

Each finding is backed by CSAT data from the environment, explained in business terms and mapped to a CIS control and a Zero Trust pillar. Three examples from the sample:

Microsoft Entra ID accounts

CIS 5 · Zero Trust: Identities

Finding

  • Multiple disabled accounts
  • Accounts without MFA or Conditional Access

Risk

  • Dormant accounts can be misused without anyone noticing
  • Without MFA, a username and password are enough to reach company data

Recommendation

  • Clean up unused accounts on a regular, automated schedule
  • Enforce MFA and Conditional Access for untrusted locations and devices

Software assets

CIS 2 · Zero Trust: Apps

Finding

  • End-of-life software still installed
  • Possible shadow IT: Dropbox on 4 endpoints
  • Potentially unwanted software on 2 endpoints

Risk

  • No more security updates for known vulnerabilities
  • Documents shared externally with no control over who has access

Recommendation

  • Upgrade every product that has reached end of support
  • Remove risky apps and set an approved-software list

AI usage from web behaviour

CIS 9 · Zero Trust: Apps

Finding

  • Several AI tools in use
  • Public language models used without organisational approval or controls

Risk

  • Work information, including personal data, may leave the organisation
  • Possible breach of data protection rules and company policy

Recommendation

  • Standardise on one AI provider
  • Control app use with Defender for Cloud Apps and train employees on shadow IT

Source: detailed report and board presentation, findings summary

Part 2 · External vulnerability scan

66 scanner results. 17 real findings.

Raw scanner output is noisy. We remove duplicates and validate before anything reaches the report. In the sample's second scan, 66 raw results became 17 distinct findings, each with evidence, risk and an action.

17findings on the public perimeter

  • CriticalInternet-exposed, unauthenticated Redis affected by CVE-2025-49844
  • HighAdditional Redis Lua vulnerabilities
  • HighPossible exposure of configuration, backup and repository files
  • HighPossible admin and diagnostic interface exposure
  • HighInternet-facing development application
  • MediumCleartext HTTP, missing CSP, permissive CORS, directory indexing, weak cookies and 3 more
  • LowPublic SSH, legacy SHA-1 SSH MACs, missing privacy headers, disclosed repository metadata

Source: detailed report, external scan of 6 October 2026

Critical VA-SAMPLE-001

Internet-exposed, unauthenticated Redis affected by CVE-2025-49844

Asset
Sample external host : 6379 · Open, confirmed
Evidence
Redis 4.0.14 found on TCP/6379. Full server information was returned without credentials, which confirms unauthenticated access. The version matches CVE-2025-49844 (CVSS 10.0). The exploit itself was not run.
Risk
Remote code execution through a crafted Lua script. This could lead to data theft or manipulation, persistence, lateral movement and service disruption.
Action
Contain immediately. Remove port 6379 from the internet, upgrade to a patched release, require authentication, rotate reachable secrets, then retest from outside.

Example finding card · one of 17

  1. 0–7 days

    Block public Redis access and patch it. Isolate the development application. Enforce HTTPS. Rotate secrets if exposure is confirmed.

  2. 7–30 days

    Disable directory indexing, harden cookies and browser headers, restrict SSH and remove legacy SSH algorithms.

  3. 30–90 days

    Retest externally, capture before-and-after evidence, and track residual risk and owners in the CSAT register.

Part 2 · Phishing simulation

One email. Eleven clicks.

The campaign imitated an MFA re-verification request with a corporate-style login page. Anyone who clicked was redirected to a short training page on the warning signs.

Delivered
98
Clicked
11 11.2%
Submitted login
2 2.1%

Source: phishing campaign, CIS Control 14

Scenario
“Action Required: Multi-Factor Authentication (MFA) Re-Verification”
Duration
1 day, approved mailboxes only
Safeguard
Submissions are recorded as events. Real passwords are not stored.
Reported by
Department, to focus coaching rather than to blame

Awareness gaps

  • Hard to spot suspicious sender domains and URLs
  • Credential-harvesting pages not recognised
  • Phishing report button used inconsistently

Strengths

  • No clicks or submissions in HR or Finance
  • The SOC received many user questions and reports

From findings to a plan with dates.

Everything above comes together in one roadmap, grouped by urgency and by its effect on maturity. Quick wins come first, and capital projects get time to be budgeted.

  1. 0–30 days

    Immediate

    • Enforce MFA for all users and remote access
    • Patch critical and high CVEs, remove risky apps
    • Review inactive and non-compliant devices
    • Validate VPN exposure, logging and certificates
    • Review PII findings and external sharing
    • Issue a temporary AI usage policy
  2. 30–90 days

    Short term

    • Deploy LAPS and admin hygiene controls
    • Baseline Conditional Access, clean unused accounts
    • Intune compliance and browser standards
    • Phase out end-of-life apps and OS
    • DLP and classification labels for priority data
    • Monthly vulnerability review
  3. 3–6 months

    Medium term

    • SIEM as the central hub for security logs
    • Expand classification and Purview DLP
    • Supplier access reviews and contract requirements
    • Incident response tabletop and annual pen test
    • Defender for Cloud and Azure governance reporting
    • Continuous vulnerability management
  4. 6–12+ months

    Strategic

    • Reach CIS Level 3 across weak controls
    • Zero Trust architecture and network modernisation
    • Device hardening baseline, refreshed every six months
    • Application allow-listing and governance
    • AI governance and formal risk management
    • Privileged access workstations and BC/DR testing

KPIs to track the programme: MFA coverage, critical patch SLA, external exposure status, DLP and classification coverage, supplier access reviews, incident exercises completed.

Source: board presentation, prioritised remediation roadmap

Want the full report?

We'll share the complete sample, both the board presentation and the detailed report, and show you how yours would look.