Security engineer working through evidence in a data center

PL-2System security and privacy plans

System security plan development, done right

We document your system boundary, categorization and how every selected NIST 800-53 control is implemented, so customers and assessors can trust it.

25+ yearsIT and cybersecurity leadership
CISO, CISSPC|CISO certified assessor
Southern CaliforniaOn-site from Irvine
NationwideRemote assessments
Security leader with her governance team
PL-2The control that requires the plan

Why the plan matters

The document every NIST 800-53 review starts with

A system security plan, required by control PL-2 in NIST SP 800-53, describes the system, its boundary and environment, its security categorization, and how each selected control is implemented or planned. Customers that rely on SP 800-53 often ask for it during procurement and annual reviews, and every assessor reads it before testing anything.

Many organizations have no plan, or a plan written for a system that no longer exists. In our fictional sample report, the missing plan was its own finding, and outdated architecture diagrams made two others harder to fix.

We write the plan with your team, or repair the one you have, based on what operates today. When it is combined with a NIST 800-53 assessment, every implementation statement is checked against evidence.

  • New plan or update of an existing one
  • Boundary, data flows and interconnections
  • Implementation statement for every selected control
  • Inherited and shared controls clearly marked

What goes in the plan

What a complete system security plan contains

SectionWhat we document
System identificationSystem name, owner, authorizing official or customer contact, purpose and operational status
CategorizationFIPS 199 ratings for confidentiality, integrity and availability, information types and the overall impact level
Boundary and environmentWhat is inside the system, what is outside, cloud services, locations and users
Architecture and data flowsCurrent diagrams of the network, components, data flows and ports and protocols
InterconnectionsConnections to other systems and external services, with agreements and security requirements
RolesWho is responsible for the system, for security and for each control family
Control implementationFor every selected control: implemented, partially implemented, planned or inherited, and how
Tailoring decisionsControls scoped out, compensating controls and organization-defined parameters, with the reason for each

How we build it

Four steps to a plan you can hand to a customer

01

Discover

Interviews with system, IT and security owners, plus your existing documents and diagrams.

02

Map

Boundary, data flows, interconnections and inherited controls confirmed against the real environment.

03

Write

Implementation statements for each control, in plain language with clear responsibilities.

04

Review

A walkthrough with your team; gaps found while writing go into your POA&M.

Example

What a good implementation statement looks like

Vague statements are the most common weakness in a plan. Here is a statement written the way we write them, for a fictional system.

IA-2Identification and Authentication (Organizational Users)Partially implementedSample · fictional company
Responsible role
IT Director, with the Security Lead reviewing quarterly
How it is implemented
All workforce accounts authenticate through Entra ID. MFA is required by a Conditional Access policy for every user; administrators use phishing-resistant methods.
Gap and plan
Legacy authentication is still allowed for one service account. Blocking it is tracked as a POA&M item with a 30-day target.
Evidence
Conditional Access policy export and the monthly MFA registration report, stored in the compliance folder

Doing it well

What makes a plan credible

A plan is only useful if it matches reality and can be maintained.

Written for the system you run

We describe the environment as it operates today, including cloud services and suppliers, and we flag anything that does not match what the plan used to say.

Specific, not aspirational

Each statement names a role, a technology, a frequency and where the evidence lives. ‘The organization ensures access is appropriate’ tells an assessor nothing; ‘the IT Director reviews Azure and Microsoft 365 access quarterly using access reviews’ does.

Honest about gaps

Controls that are not fully in place are marked as partially implemented or planned, with a link to the matching plan of action and milestones item. A plan that claims everything is in place rarely survives an assessment.

Easy to keep current

We deliver an editable document and a short maintenance routine, so the plan is updated with every major change rather than rewritten every few years.

Ali Hassani, CISO and CISSP, founder of OC Security Audit

Who leads the assessment

Led by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA.

Ali writes and reviews system security plans with the people who run the system, so the plan reflects real operations and holds up when a customer or assessor reads it.

FAQ

Questions about this page

What is a system security plan?

It is the document required by NIST SP 800-53 control PL-2 that describes a system, its boundary, its security categorization and how each selected security control is implemented or planned.

Do we need an SSP if we are not a federal agency?

Often yes. Customers that rely on NIST SP 800-53, including state and local government customers and many enterprises, ask for a system security plan or an equivalent document during procurement and reviews.

Can you update our existing plan instead of starting over?

Yes. We review the plan against the current environment, correct the boundary and diagrams, rewrite weak implementation statements and record new gaps as plan of action and milestones items.

How long does an SSP take to write?

It depends on the size of the system and the number of controls. A focused plan can take two to three weeks; a full Moderate-baseline plan takes longer. We confirm the timeline and price after scoping.

Does a system security plan prove compliance?

No. The plan describes how controls are implemented; an assessment tests whether they actually operate. Many clients combine the plan with a NIST 800-53 assessment.

ocsa audit hero executive crossed arms

Get a system security plan you can stand behind

Tell us about your system and we will propose a scope and a fixed price in writing.

Or call 949-777-5567