Join our Newsletter — 33% off our NHI Course
Home› Guides› System Security Plan Template and Guide: Sections, Wording…
Template Audit, Assurance & Compliance

System Security Plan Template and Guide: Sections, Wording and Evidence for Assessors

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

A System Security Plan that describes intended controls rather than the deployed system is the fastest way to fail a NIST SP 800-171, CMMC or FedRAMP assessment. The SSP is the one document every assessor reads first: under CMMC Level 2 an assessment cannot be completed without a current one, and its name, date and version are recorded with the result. This template gives numbered sections you can adopt as-is, with [Organisation] style placeholders, built from the content NIST SP 800-171 Rev. 3 requirement 03.15.02 asks for and the conventions used in FedRAMP and OSCAL plans. It is for compliance leads, system owners and engineers writing or rebuilding an SSP for a CUI enclave, a federal cloud service or any system that needs a defensible control narrative. For the wider programme context, see the NIST SP 800-171 and CMMC 2.0 Guide.

How to use this template

  • Replace every placeholder: text in [square brackets] is yours to complete. Delete guidance notes in italics before issue.
  • Describe what is deployed: write implementation statements in the present tense about real configurations, products and people. Planned items go in section 8, not in the narrative.
  • Reference, do not paste: SP 800-171 Rev. 3 guidance says an SSP can be a collection of documents. Reference policies, diagrams and inventories by name and version rather than copying them, but keep a written narrative for every requirement.
  • Pick one numbering scheme: CMMC Level 2 assesses SP 800-171 Rev. 2 numbering (for example 3.12.4); Rev. 3 uses 03.15.02; FedRAMP uses SP 800-53 Rev. 5 control IDs. Write to the scheme your assessor uses and keep a crosswalk for the others.
  • Protect the document: 03.15.02 requires the SSP to be protected from unauthorised disclosure. It is a map of your defences; mark and store it accordingly.
ProgrammeWhere the SSP requirement sitsWhat the assessor does with it
NIST SP 800-171 Rev. 303.15.02 System Security PlanChecks the eight content elements, review frequency and protection
CMMC Level 2CA.L2-3.12.4 (Rev. 2 numbering); 32 CFR 170.24Gate: no current SSP, no completed assessment; cannot be on a POA&M; SSP version recorded in eMASS
FedRAMPSP 800-53 PL-2, FedRAMP SSP template with appendicesReads every control implementation statement; planned or partial items are "Other than Satisfied"
Federal systems generallyNIST SP 800-18 Rev. 2 (June 2026), SP 800-53 PL-2Uses the plan as the basis for assessment and authorisation

1. Document control

  • Title: [System name] System Security Plan.
  • Version and date: [x.y], [date]. The CMMC assessment records the SSP name, date and version; do not change the version during an assessment without telling the lead assessor.
  • Owner: [System owner name and role]. Approver: [Senior official, for example the Affirming Official or authorising official].
  • Review frequency: this plan is reviewed [at least annually] and after any significant change defined in section 9 (03.15.02.b).
  • Marking and distribution: [CUI marking or internal classification]; distribution limited to [roles].
  • Change log: table of version, date, author, summary of change, approver.

2. System identification and categorisation

  • System name and identifier: [name], [internal ID, CAGE codes or FedRAMP package ID where applicable].
  • Purpose: [one paragraph on the mission or business function the system supports].
  • Information types: [list: CUI categories such as export-controlled technical data, FCI, personal data, other] (03.15.02.a.02).
  • Categorisation: [FIPS 199 impact level or the CUI baseline applied], with the rationale.
  • Applicable requirements: [SP 800-171 Rev. 2 or Rev. 3, CMMC level, FedRAMP baseline, contract clauses such as DFARS 252.204-7012].
  • Operational status: [operational, under development, undergoing major change].

3. System boundary and environment

[Organisation] defines the authorisation boundary of [System] as the components listed in section 6 and shown in the diagrams below (03.15.02.a.01 and a.04).

  • Boundary diagram: [reference: diagram name and version] showing every component, enclave edge and external connection.
  • Data flow diagram: [reference] showing how CUI enters, moves, is stored and leaves, including backups and email.
  • Locations: [sites, cloud regions, tenants such as a GCC High or AWS GovCloud account].
  • Out-of-scope systems: [list], with the separation that keeps them out (for example, a KVM-only VDI endpoint, a separate tenant, firewall rules).
  • Threats of concern: [summary of the threat assessment, for example credential theft, ransomware, supplier compromise] (03.15.02.a.03).

Guidance: for CMMC, classify assets as CUI Assets, Security Protection Assets, Contractor Risk Managed Assets, Specialized Assets or Out-of-Scope Assets using 32 CFR 170.19. See the CMMC Scoping Guide.

4. Roles and responsibilities

RoleNamed individualResponsibilities in this plan
System owner[Name]Accountable for the plan and its accuracy; approves changes
Senior official or Affirming Official[Name]Approves the plan; affirms compliance where required
Information security lead[Name]Maintains implementation statements, POA&M and evidence
System administrators[Names or team]Operate controls; provide configuration evidence
Identity and access administrator[Name]Account lifecycle for human and non-human identities
External service provider contacts[Provider, contact]Deliver controls listed in the responsibility matrix

03.15.02.a.07 requires the plan to identify individuals in system roles. Use names, not only job titles, and update them when people move.

5. Interconnections and external service providers

  • Interconnections: for each connection list [connected system, owner, direction, data types, protocol and port, agreement reference such as an interconnection security agreement], consistent with SP 800-53 CA-3.
  • Cloud service providers: for each offering record [name, FedRAMP authorisation level and package ID or equivalency evidence, services used]. Reference the customer responsibility matrix and state which requirements are inherited, shared or customer-owned.
  • Other external service providers: for each managed service (MSP, MSSP, SOC, help desk) record [service description, responsibility matrix reference, how its staff authenticate into the boundary].
  • Inheritance wording: state what is inherited and from whom; do not describe the provider's internal implementation.

6. Asset and identity inventory

[Organisation] maintains the following inventories for [System]; each is referenced by name and version.

  • Hardware and virtual components: [inventory reference] with asset category, owner, location and operating system (SP 800-53 CM-8).
  • Software and SaaS: [inventory reference], including versions and where CUI is processed.
  • Human accounts: [count by role, privileged versus standard, source directory].
  • Non-human identities: service accounts, API keys, OAuth applications, certificates, managed identities and AI agents with access to the boundary, each with [owner, purpose, authentication method, secret storage location, rotation period, last review]. See the Service Account Inventory Template.
  • Cryptographic modules: [module name, FIPS 140 certificate number, where used], supporting SC.L2-3.13.11 or SC-13.

Guidance: an SSP that lists people but not service accounts leaves the identification and authentication narrative unprovable. Assessors ask how each process authenticates and where its credential lives. See Audit Readiness for AI Agents and NHIs.

7. Requirement implementation statements

For each requirement or control in the applicable baseline, record the following (03.15.02.a.05 and a.06):

FieldContent
Requirement ID and title[for example 3.5.3 Multi-factor authentication]
StatusImplemented, Partially implemented, Planned, Not applicable, Inherited
Responsible role[role from section 4]
Implementation statementWho does what, with which technology and setting, how often, and for which components
Inheritance[provider and responsibility matrix line], if any
Evidence[artefact names: configuration export, policy section, log sample, ticket]
Not applicable rationaleWhy the requirement does not apply, for example no wireless in the boundary

Example statement (replace with your own facts): "[Organisation] enforces multi-factor authentication for all interactive users of [System] through [IdP] conditional access policy [policy name], requiring [phishing-resistant method]. Non-interactive service accounts listed in inventory [ref] are excluded from MFA and are instead restricted to [named hosts or workload identity], with credentials stored in [vault] and rotated every [n] days. The policy is reviewed [quarterly] by [role]."

  • Write each part: for multi-part requirements, address every part and objective explicitly.
  • No copy and paste: FedRAMP guidance warns against copying statements between controls; assessors read repeated text as unimplemented.
  • Be testable: name settings, policy names and frequencies an assessor can verify in an interview or demonstration.

8. Exceptions, plans of action and planned controls

  • Enduring exceptions: [requirement, reason the requirement cannot be fully met, mitigations, approver]. Under CMMC, an enduring exception described in the SSP with mitigations is assessed as MET.
  • Temporary deficiencies: [requirement, operational plan of action reference, review dates, progress].
  • POA&M: reference [POA&M name and version], with weakness, milestones, owner and due date per item (03.12.02, SP 800-53 CA-5). Remember the CMMC limits on what may go on a POA&M.
  • Specialized assets: for OT, IoT, test equipment or government-furnished equipment, describe how each is managed under risk-based policies.

9. Plan maintenance and review

  • Significant change triggers: new CUI location, new cloud or external service provider, change of identity provider, boundary or network redesign, new AI tool with access to CUI, merger or system retirement.
  • Review cycle: [annual] full review by [role]; [quarterly] update of inventories and the POA&M; review after every incident affecting the boundary.
  • Continuous monitoring link: results of control monitoring (03.12.03, CA-7) feed status changes into section 7.
  • Approval: each new version is approved by [senior official] and the prior version archived for [retention period, at least six years where CMMC evidence rules apply].

Implementation guidance

  1. Start from the boundary, not the controls. Draft sections 3, 5 and 6 first. Most weak SSPs fail because the scope is vague, which makes every implementation statement unprovable.
  2. Collect evidence while writing. For each statement, capture the artefact that proves it. If no artefact exists, the requirement is not yet implemented: move it to section 8.
  3. Run a mock read. Ask someone independent to test five statements against the live system. Fix any where the system differs from the text.
  4. Consider machine-readable output. NIST OSCAL defines an SSP model with metadata, import-profile, system-characteristics, system-implementation, control-implementation and back-matter. A structured source makes crosswalks and updates easier, even if you still export a document.
  5. Keep it alive. Tie SSP updates to change management so that a new SaaS tool or service account cannot enter the boundary without a plan update. See the Change Management Policy Template.
Common SSP failureWhy it failsFix
Restating the requirement textShows no implementationName the tool, setting, role and frequency
Future tense ("will implement")Planned is not implementedMove to section 8 with a POA&M entry
No non-human identitiesIdentification and authentication objectives cannot be verifiedAdd the NHI inventory in section 6
Missing provider responsibility matrixInherited controls cannot be creditedObtain and reference the CRM or ESP matrix
Not applicable without rationaleAssessors find many N/A items do applyWrite the reason and the evidence
Stale names and diagramsInterviews contradict the documentQuarterly update tied to change management

Measure the plan's health with a few simple indicators: percentage of requirements with linked evidence, number of statements changed since the last review, age of the boundary diagram, open POA&M items past due, and percentage of in-scope non-human identities with a named owner. For the assessment that consumes this plan, see the CMMC 2.0 Level 2 Assessment Guide and the FedRAMP Guide.

Sources: NIST: SP 800-171 Rev. 3 (requirement 03.15.02) · NIST: SP 800-18 Rev. 2, Developing Security, Privacy, and Cybersecurity Supply Chain Risk Management Plans for Systems · NIST: SP 800-53 Rev. 5 (PL-2) · NIST: OSCAL System Security Plan Model · eCFR: 32 CFR 170.24 CMMC Scoring Methodology · FedRAMP: System Security Plan guidance (legacy playbook)

This template is provided for guidance and must be adapted to your organisation. It is not legal advice. Related NHI Mgmt Group resources: NIST SP 800-171 and CMMC 2.0 Guide · CMMC 2.0 Level 2 Assessment Guide · CUI Guide · Information Security Policy Template

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.