How is Athena different from Secureframe, Strike Graph, Paramify, Risk Cognizance, SMPL-C, or Kiteworks?

Those platforms optimize the contractor's readiness workflow — live SPRS tracking, AI controls dashboards, fast SSP/POA&M drafting, continuous control monitoring, LLM document analysis, or CUI data movement. Athena adds the assessor-facing submission layer that almost none of them ship: SAR narrative drafting, eMASS-ready JSON packaging, OSCAL output, and cryptographic provenance (SHA-256 + chain-of-custody) for every artifact a C3PAO or DIBCAC assessor opens on engagement day.

Does Athena replace Secureframe, Strike Graph, or Paramify?

No — Athena is the assessor-side submission layer that sits on top of whatever readiness GRC you already use. Bring evidence from any tool; Athena drafts the SAR, generates the POA&M with prioritized remediation, scores SPRS, and exports eMASS / OSCAL packages with provenance.

What does Athena export for a CMMC Level 2 assessment?

SAR draft with citations, POA&M with milestone estimates, SPRS scoring package, eMASS-ready JSON, OSCAL package, evidence binder with SHA-256 hashes, and a chain-of-custody manifest signed for the assessor.

What must a CMMC SSP contain?

Under 3.12.4 the SSP must describe the system boundary, the environment of operation, how each security requirement is implemented, and the relationships with or connections to other systems — and it must be periodically updated. In practice it documents how you meet all 110 NIST 800-171 requirements.

Is the SSP required for CMMC Level 2?

Yes — and it's foundational. Without a current SSP you effectively can't be assessed: it's the document the assessor reads to understand your environment and how you implement each control. A missing or thin SSP is a showstopper, not a minor finding.

How often should the SSP be updated?

Periodically and whenever the environment changes materially. A static SSP that no longer matches your systems will fail objective [f] and undermine the rest of your evidence. Version-control it and update it as controls and scope change.

CMMC 3.12.4 (System Security Plan): What an SSP Must Contain & What Assessors Actually Check

Control: NIST SP 800-171 Rev. 2 §3.12.4 · CMMC Practice: CA.L2-3.12.4 · Updated June 2026

Plain-English answer

3.12.4 requires a System Security Plan (SSP) that describes your system boundary, the environment of operation, how each security requirement is implemented, and your connections to other systems — kept current. It's the master document an assessor reads to understand your program; everything else is evidence supporting what the SSP claims.

Who this applies to

Every organization seeking CMMC Level 2 for a CUI environment. No current SSP = effectively unassessable.

Why it matters

The SSP is the spine of your assessment. A thin or stale SSP doesn't just fail 3.12.4 — it undermines the credibility of every other control. It carries a weighted SPRS deduction if unmet (verify the exact value against the DoD Assessment Methodology).

Control lineage

CMMC Practice: CA.L2-3.12.4
NIST 800-171 Rev. 2: §3.12.4 — develop, document, and periodically update system security plans that describe system boundaries, environments of operation, how security requirements are implemented, and relationships with or connections to other systems.
NIST 800-171A objectives: [a] an SSP is developed; [b] it describes the system boundary; [c] it describes the environment of operation; [d] it describes how the security requirements are implemented; [e] it describes relationships/connections to other systems; [f] it is periodically updated.

What the assessor will EXAMINE

The SSP itself — boundary, environment, per-requirement implementation, and external connections.
Whether each of the 110 requirements has an implementation statement (or a POA&M reference).
Version history showing it's updated, not written once and shelved.
Consistency between the SSP and the actual evidence/configuration.

What the assessor will INTERVIEW & TEST

Interview: "Walk me through your boundary and how you implement [a sampled control]." — the SSP narrative should match what staff say and what the evidence shows.
Test: Pick several controls and confirm the SSP's implementation statement matches reality.
Test: Check the SSP's last-updated date and that recent changes are reflected.

Evidence examples (produce these)

A complete, version-controlled SSP covering boundary, environment, all 110 requirements, and connections.
Per-requirement implementation statements (or POA&M references for gaps).
Change/version log showing periodic updates.

Common failure patterns

A template SSP with generic statements that don't match the actual environment.
Boundary or external connections not clearly described — objectives [b]/[e] fail.
SSP written once and never updated, so it contradicts current configuration.
Controls left blank or vaguely "implemented" with no specifics.

SPRS impact & POA&M

SPRS: 3.12.4 carries a weighted deduction (verify the exact value). POA&M: the SSP is foundational — confirm its POA&M eligibility against current CMMC rules; in practice you want the SSP itself complete before assessment.

Assessor-ready summary

You're good on 3.12.4 when a version-controlled SSP describes your boundary, environment, per-requirement implementation, and connections; it matches your evidence and what staff describe; and it's updated as the environment changes.

SSP out of date or never finished? Athena regenerates an objective-mapped SSP on every evidence change. See SSP automation →

Athena prepares organizations for CMMC Level 2; certification rests with C3PAOs/DIBCAC. Verify all control facts against NIST SP 800-171 Rev. 2, NIST SP 800-171A, and current CMMC rules.