Insights / SSP
SSP

The SSP: the document your whole package is judged through.

What separates SSPs assessors accept from placeholders: true boundaries, specific implementation statements, and automation that keeps them current.

Ausper Technology · July 20, 2026 · Insight · SSP · Documentation

The System Security Plan (SSP) is the spine of every authorization package: the document that says what the system is, where its boundary sits, and how every applicable control is implemented. Assessors read it first and judge everything else through it. A weak SSP taxes the entire package.

What a good one contains

A boundary that is true. Diagrams matching reality, data flows included, inheritance explicitly drawn. Unclear boundaries are a common source of assessment rework. Implementation statements with specifics. 'AC-2: Account management is performed' is a placeholder. 'Accounts are provisioned via ServiceNow workflow X with approval Y, reviewed quarterly per SOP Z, evidence at location W' is a statement. Current facts. Versions, owners, interconnections. Stale SSPs signal unmanaged systems.

Keeping it alive

The SSP dies between assessments unless it's wired to reality: generated and updated from the systems of record (CMDB, control tracker, pipeline) rather than hand-edited annually. The same automation spine powers continuous ATO, which is why we treat SSP generation as engineering work.

Common questions

What is a System Security Plan?
The document that describes the system, draws its authorization boundary, records its categorization, and states how every applicable control is implemented. Assessors read it first and check everything else against it.
What makes an SSP fail review?
Implementation statements that restate the control instead of describing this system, a boundary diagram that does not match what was built, and inherited controls claimed without a customer responsibility matrix.
How do you keep an SSP current?
Generate what can be generated (inventory, ports and protocols, data flows, baseline configuration) from the systems that already know them, and tie the narrative sections to change control.

Related reading

Put this to work

Working on this now?

Tell us where your program stands and we'll tell you what we would do next.

Talk to Ausper