Skip to main content

Sample deliverable

Every figure is a placeholder

What lands on your desk at the readout.

Four documents. The structure below is what you receive. The rows are examples of the kind of finding we report, not data from a client.

Document 1 of 4

Findings register

Ranked by how much exposure the fix removes for the effort it takes. Each row names the posture assumption it breaks and who owns the fix.

RankAreaAssumption brokenEvidenceFixEffortOwner
1Patch latencyWe have weeks to patch.N (your figure) internet-facing hosts patched a median of N (your figure) days after the fix shipped.Emergency patch lane for edge systems.MediumInfrastructure
2Detection and responseAn analyst will catch it in triage.Isolating a compromised host needs N (your figure) manual approvals.Pre-authorise isolation for defined alert classes.SmallSecurity operations
3ExposureWe know what we have online.N (your figure) hosts answering on the internet that are missing from the inventory.Decommission, or bring under management.SmallInfrastructure
4Your own AIInternal assistants only see what their user can.ASSISTANT (your figure) reads SYSTEM (your figure) through one shared service token.Per-user authorisation on tool calls.MediumEngineering
5IdentityService accounts are low risk.N (your figure) non-expiring keys with administrative scope.Rotate, scope down, add expiry.LargePlatform

Document 2 of 4

Your clock

Three intervals, measured from your own records, each with the method used so your team can re-measure after the fixes land.

  • Fix available to patched, edge systems

    N (your figure) days, median

    Source: patch records, N (your figure) months

  • Alert raised to first analyst action

    N (your figure) hours, median

    Source: alert history, N (your figure) alerts

  • Decision to host isolated

    N (your figure) minutes

    Source: runbook walk-through

Document 3 of 4

90-day adjustment plan

The register turned into a sequence: small fixes that shorten the clock first, larger ones after. Every item has one owner.

Days 1 to 30

  • Pre-authorise host isolation for defined alert classes. Finding 2 · Security operations
  • Decommission unmanaged hosts or bring them into the inventory. Finding 3 · Infrastructure

Days 31 to 60

  • Stand up an emergency patch lane for edge systems. Finding 1 · Infrastructure
  • Per-user authorisation on assistant tool calls. Finding 4 · Engineering

Days 61 to 90

  • Rotate and scope down service-account keys, with expiry. Finding 5 · Platform
  • Re-measure the clock using the methods in document 2. Security lead

Document 4 of 4

Board brief

Two pages in plain language, written to be read without the security lead in the room.

  • What changed

    Why autonomous attackers alter the risk the company carries, in three paragraphs.

  • Where we stand

    The three clock intervals and the five findings, without the technical detail.

  • What we are asking for

    The decisions and budget the 90-day plan needs, and what the board gets back at day 90.

Get these four documents with your own numbers in them.

Fixed scope, 3 weeks.

Request the assessment