Skip to content
EA

If it needs evidence from several people and someone to sign it off, hand it to EA.

Browse the full library

NIST 800-171 and Cybersecurity Maturity Model Certification (CMMC) Level 2 · For defence suppliers

Your network changes. Your System Security Plan keeps up.

EA drafts it from your own configurations, policies and records, along with the self-assessment behind your Supplier Performance Risk System (SPRS) score and a plan of action for each gap. Where a record is missing, EA asks the person who holds it and follows up. Your Compliance Director approves each part.

Try EA free. No card needed.

Organisations that run work on EA

The work

Running the controls is one job. Writing them down is another.

  • The plan ages with the network

    Your System Security Plan (SSP) describes the network as it stood the last time someone had a free week. Since then a file server has moved and a new laptop build has gone out.

  • One requirement, several objectives

    Each of the 110 requirements splits into assessment objectives, and each objective needs its own evidence. Most of it sits with the same few administrators who run the network.

  • The affirmation comes round

    Your affirming official confirms compliance every year, and the full assessment comes round every three. Each date lands whatever else the administrators have on that month.

Get the SSP current once, and each affirmation after it is a check rather than a rebuild.

What EA does

Your environment, written down as it really is.

Five steps take the paperwork around your controlled unclassified information (CUI) from where it stands today to an affirmation your affirming official can make.

01 / 05

  1. EA

    Reads your current SSP, network diagrams, asset list and policies, and lines each one up against the requirements of the revision your contract names. Knowledge Library 

    Your team

    The Compliance Director confirms the CUI boundary and the revision.

  2. EA

    Drafts how each requirement is met from your configuration exports, runbooks and procedures, with the source beside each description. EA Agent 

    Your team

    The Systems Administrator corrects whatever has changed since the source was written.

  3. EA

    Takes each requirement through its assessment objectives and marks it met, not met or “Needs evidence”, such as a quarter’s missing log review. It sends one request per owner for the records it can’t find, and follows up. Autofill  EA Agent 

    Your team

    The Compliance Director’s team sees what is still due. The visitor log comes back from the Facilities Manager, the missing review from the Systems Administrator.

  4. EA

    Drafts a plan of action entry for each requirement not yet met, where the rule allows one: what’s missing, the fix, who owns it and a milestone date inside the 180-day limit on a Level 2 plan of action. EA Agent 

    Your team

    Owners set dates they can keep, the Compliance Director agrees them, and a reminder you set flags the closeout self-assessment before the 180 days run out.

  5. EA

    Brings the SSP, the assessment and the plan of action together with who approved each part. A section someone edits afterwards goes back to the Compliance Director. Approvals 

    Your team

    The Compliance Director approves, your team enters the score in SPRS, and your affirming official makes the affirmation.

Illustrative data: stage by stage

See EA take one requirement family from policy to plan of action.

Book a demo

Next year

Each change reaches the SSP before the affirmation does.

  • When your team records a change

    Add a new configuration export or asset list, and EA redrafts the SSP sections that cited the old one for their owner to check.

  • The yearly affirmation

    EA rechecks each requirement’s evidence and the plan of action’s dates, so your affirming official sees what has moved since last year.

  • The three-year assessment

    When the three-year assessment comes round, it starts from every affirmation since, with each requirement’s records attached, whether your team runs it or a certified assessor does.

Illustrative data: one requirement’s approval record
Approval record · requirement 3.5.3 multifactor authenticationLocked
Requirement
3.5.3 Multifactor authentication
System Security Plan
Identification and authentication section
Evidence
Identity provider’s policy export and sign-in records
Owner
Systems Administrator
Approved by
Compliance Director
Review date
1 March Current

When a prime asks about your status, start from what you’ve approved.

Primes and customers send their own questionnaires about NIST 800-171. With the SSP and assessment approved, most of what they ask has an answer on file, and your score is quoted exactly as you recorded it.

EA’s own security

The SSP maps your defences. You choose who opens it.

EA works from the documents you choose: the SSP, network diagrams, policies and configuration exports. Whether any of them is marked as CUI is your Compliance Director’s call. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.

  • Hosted your way

    EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.

  • Access

    Single sign-on, which you can enforce, and an access list for each workspace.

  • Support access

    EA staff see your data only in a time-limited window you open.

  • Testing

    An independent firm runs a penetration test on EA every year.

  • Security contact

    EA’s security team is at security@eaglobal.ai.

In the demo, see the access list on a System Security Plan workspace.

Book a demo

Why EA for NIST 800-171

Your own team, a consultant or software.

Compared withWhat it does wellWhat EA adds
Doing it yourselvesThe people who built the network know it best.EA writes it up from their records, so they check the SSP instead of drafting it.
A consultantKnows how an assessor reads each requirement.EA writes up the SSP, evidence and plan of action, so each engagement starts from where your network stands today.
Compliance softwareHolds the requirement list and tracks status.EA drafts the SSP itself, gathers the records only people hold, and takes each part to your Compliance Director.

FAQ

Questions about the SSP, the score and the assessors.

From your own self-assessment against the 110 requirements. EA works through each requirement with its evidence and assembles the record; your team works out the score, your Compliance Director approves the assessment, and your team enters the score in SPRS. Your affirming official, a senior official in your organisation, makes the affirmation.

Your own team, for now. While certification is suspended (since 13 July 2026) and the programme is reviewed, contracts ask for the Cybersecurity Maturity Model Certification (CMMC) Level 2 self-assessment, and the Department of Defense can still run its own assessment of a supplier. If contracts ask for certification again, a certified third-party assessor does it. Either way, EA prepares the SSP, the assessment record and the plan of action they look at.

EA bases each finding on the records you’ve handed it and shows them beside it. If your incident response plan was last tested two years ago, EA marks the testing objective “Needs evidence” and asks its owner for a current record. Nothing counts until your Compliance Director approves it, and the affirmation stays with your affirming official.

Yes. Access can be set for a single document, so the diagrams can stay with the Systems Administrator and your Compliance Director while the rest of the team drafts the SSP around them.

The writing. The consultant advises on scope and how requirements are read; EA writes up the SSP, works through the evidence, and brings them the requirements where a reading is needed.

Yes, whether that’s an SSP from two years ago, an assessment spreadsheet or only your policies. Our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.

The one your contract names. CMMC currently builds on Revision 2, and NIST published Revision 3 in May 2024. Your Compliance Director confirms the revision at the start, and EA drafts the SSP and the assessment against it.

Your next affirmation, without the weekend rewrite.

A plan of action, from the first gap to your Compliance Director.