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 does CMMC 3.12.1 require?

Periodically assess the security controls in your systems to determine whether they are effective in their application. You must define how often you assess your controls and then actually run those assessments — confirming controls work as intended, not just that they exist on paper.

Does 3.12.1 mean I have to hire a C3PAO every year?

No. 3.12.1 is your own internal, periodic self-assessment of control effectiveness — separate from the formal CMMC certification assessment by a C3PAO. You define the cadence (e.g., annually) and method; the point is ongoing internal verification that controls are working.

How is 3.12.1 different from 3.12.3?

3.12.1 is a periodic point-in-time assessment of control effectiveness. 3.12.3 is continuous monitoring of controls on an ongoing basis. Together they form an assess-then-monitor cycle: 3.12.1 checks effectiveness periodically; 3.12.3 keeps watching between assessments.

CMMC 3.12.1 (Security Control Assessment): Evidence Examples & What Assessors Actually Check

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

Plain-English answer

3.12.1 requires you to periodically assess your security controls to determine whether they're effective in their application. Two parts: define how often you assess, and actually do it — verifying controls work as intended. This is your own internal assessment cycle, distinct from the formal C3PAO certification.

Who this applies to

Every organization seeking CMMC Level 2 for a CUI environment.

Why it matters

Controls drift. A periodic effectiveness assessment is how you catch a control that quietly stopped working before an assessor — or an attacker — does. 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.1
NIST 800-171 Rev. 2: §3.12.1 — periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
NIST 800-171A objectives: [a] the frequency of security control assessments is defined; [b] security controls are assessed with the defined frequency to determine if the controls are effective in their application.

What the assessor will EXAMINE

A policy/plan defining the assessment frequency (e.g., annual control self-assessment).
Completed assessment results/reports dated on that cadence, covering the in-scope controls.
Findings from the assessments flowing into the POA&M.
SSP narrative for 3.12.1 and linkage to the assessment method.

What the assessor will INTERVIEW & TEST

Interview: "How often do you assess your controls, what method do you use, and what did the last one find?" — point to the defined cadence and the latest report.
Test: Confirm the most recent assessment actually happened on schedule and covered the in-scope controls.
Test: Verify findings led to corrective action (POA&M items), not just a filed report.

Evidence examples (produce these)

Assessment policy/plan stating the frequency and method.
Dated control-assessment reports (e.g., the annual self-assessment against all 110 requirements).
Evidence findings were tracked to closure or onto the POA&M.
SSP section 3.12.1 referencing the above.

Common failure patterns

Controls implemented but never periodically assessed — objective [b] fails.
No defined frequency, so assessments are ad hoc — objective [a] fails.
An assessment was run once at setup and never repeated.
Assessment findings never become corrective actions.

SPRS impact & POA&M

SPRS: 3.12.1 carries a weighted deduction (verify the exact value). POA&M: confirm 3.12.1's POA&M eligibility against current CMMC rules before assuming it can be deferred.

Assessor-ready summary

You're good on 3.12.1 when an assessment frequency is defined; control-effectiveness assessments run on that cadence and cover the in-scope controls; findings drive corrective action and POA&M items; and the SSP matches the practice.

When did you last verify your controls actually work — not just exist? Book a DIBCAC-style readiness assessment →

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.