System Security Plan — Acme Defense Services (Sample)
| Field | Value |
|---|---|
| Document Title | Acme Defense Services System Security Plan |
| Document ID | ACME-SSP-001 |
| Version | 2.1 |
| Effective Date | 2026-01-15 |
| Next Review Date | 2027-01-15 |
| Classification | Controlled — Handled as CUI |
| Approved By | Samira Patel, CEO (2026-01-12) |
| Document Owner | Jordan Chen, IT Director |
1. System Description
1.1 System Name and Identification
- System Name: Acme Defense Services CUI Environment (ACME-CUI-ENV)
- System Type: Cloud-hosted SaaS and IaaS environment
- Primary Function: Support for defense engineering services under active prime contracts DoD-1234-5678 (CTI-designated technical data for communications systems) and DoD-2345-6789 (engineering services subcontract under Lockheed prime contract, CTI and Export-Controlled data).
1.2 Organizational Context
Acme Defense Services is a 12-person defense engineering consultancy based in Arlington, VA. The organization was founded in 2022 and performs electromagnetic design and analysis services for DoD prime contractors and one direct DoD contract. All personnel are US persons as required by the export-controlled nature of project data.
1.3 CUI Categories Handled
Per the National Archives CUI Registry, the categories handled:
- Controlled Technical Information (CTI): Technical data with military application. Primary source: engineering analyses, CAD models, simulation results, design documentation exchanged with DoD customers and prime contractors.
- Export Controlled (EXPT): Information subject to ITAR controls. Applies to the design data for communications systems under contract DoD-1234-5678.
1.4 Authorization Boundary Summary
The CUI environment consists entirely of cloud services in the US government cloud regions:
- Microsoft 365 GCC High tenant (acme-defense.onmicrosoft.us)
- Azure Government subscription (subscriptions: Acme-Production, Acme-Engineering)
- Company-managed endpoints (Windows 11 laptops and iPhones enrolled in Microsoft Intune)
No on-premise servers or traditional data centers are used. All CUI is stored and processed in Microsoft's FedRAMP High/DoD IL5-authorized cloud regions or on managed endpoints that connect to those services through conditional access policies.
1.5 Key Personnel
| Role | Name | Authority |
|---|---|---|
| CEO / Senior Agency Official | Samira Patel | Accepts residual risk; approves the SSP and POA&M |
| IT Director / System Owner / Acting ISSO | Jordan Chen | Manages technical security program; owns this document |
| IT Administrator | Priya Sharma | Executes day-to-day security operations |
| Security Liaison (rotating Q1/Q2 2026) | Priya Sharma | Reviews audit logs and security alerts |
| Security Liaison (rotating Q3/Q4 2026) | Marcus Okoye | Reviews audit logs and security alerts |
| Engineering Manager | David Liu | Approves engineering team CUI access |
| Operations Manager | Aisha Johnson | Approves operations team CUI access |
Pages 3–12 cover the full Access Control family (3.1.1–3.1.22) with specific tools, named roles, and evidence pointers.