Insights

CMMC Level 1 in Plain English: The 15 FAR Safeguards Behind Your Annual Self-Assessment

November 13, 2026

CMMC Level 1 asks every supplier that handles Federal Contract Information to meet 15 basic safeguards from FAR 52.204-21, score every one of them MET with no POA&Ms, and affirm that result in SPRS each year. Here is what each safeguard means in practice for Inland Empire aerospace and defense suppliers, with links to the official rules.

Who CMMC Level 1 applies to

CMMC Level 1 is built around Federal Contract Information (FCI). FAR 52.204-21 defines FCI as information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government. It excludes information the Government provides to the public and simple transactional information, such as what is needed to process payments.

For many Inland Empire machine shops, fabricators, distributors, and service firms supporting aerospace and defense work, that describes everyday contract data: purchase orders with non-public details, drawings or specifications that are not marked as Controlled Unclassified Information (CUI), schedules, and correspondence with a prime or the Government. If the contract data you handle includes CUI, Level 1 is not enough on its own. FAR 52.204-21 states that it does not relieve contractors of other safeguarding requirements, including those for CUI.

What the Level 1 self-assessment actually requires

The CMMC program rule at 32 CFR 170.15 sets out the Level 1 (Self) process:

1. Every Level 1 security requirement must be scored MET. Plans of Action and Milestones (POA&Ms) are not permitted at Level 1, so a partially implemented control is not a passing result.

2. The self-assessment is repeated annually, and the results are entered in the Supplier Performance Risk System (SPRS). At a minimum, the SPRS entry includes the CMMC level, CMMC status date, assessment scope, the CAGE code or codes for the systems in scope, and the compliance result.

3. The assessment uses the objectives in NIST SP 800-171A (June 2018) for the requirements that map to Level 1, substituting FCI wherever an objective refers to CUI.

4. Evidence used for the assessment must be kept for six years from the CMMC status date.

5. Before award of a contract or subcontract that requires Level 1 (Self), the company must have achieved that status and submitted an affirmation in SPRS for all systems in scope.

Under 32 CFR 170.22, the affirmation is made by an Affirming Official: a senior-level representative with authority to attest that the company has implemented, and will maintain, all applicable requirements. For Level 1, an affirmation is due when the self-assessment is completed and annually after that. Treat it as a signed statement by leadership, not a checkbox for whoever manages IT.

The 15 safeguards, grouped into plain English

The 15 requirements come straight from FAR 52.204-21(b)(1). Grouped by what they protect:

Who can get in, and what they can do

Limit system access to authorized users, processes acting on their behalf, and authorized devices. Limit users to the transactions and functions they are permitted to perform. Identify users, processes, and devices, and authenticate them before allowing access. In practice: individual accounts (no shared logins), removal of access when people leave, and administrator rights only for those who need them.

Outside connections and public information

Verify and control connections to and use of external systems, such as personal devices, personal cloud storage, and partner systems. Control what information is posted or processed on publicly accessible systems, including your website and social media, so FCI is not published by accident.

Physical security

Limit physical access to systems, equipment, and operating environments to authorized people. Escort visitors and monitor visitor activity, keep audit logs of physical access, and control physical access devices such as keys, badges, and door codes. NIST mapping splits this visitor requirement into three separate objectives, so a visitor log alone does not cover it.

Media disposal

Sanitize or destroy media containing FCI before disposal or reuse. That includes retired laptops, copier and plotter hard drives, USB drives, and paper.

Network boundaries

Monitor, control, and protect communications at the external boundary and key internal boundaries of your systems, typically with a properly managed firewall. Put publicly accessible system components on subnetworks that are physically or logically separated from internal networks, so a guest Wi-Fi network or public-facing server does not sit on the same network as your business systems.

Patching and malware protection

Identify, report, and correct system flaws in a timely manner. Provide protection from malicious code at appropriate locations, update it when new releases are available, and perform periodic scans plus real-time scans of files from external sources as they are downloaded, opened, or executed. CISA's Known Exploited Vulnerabilities Catalog is a practical way to decide which patches cannot wait.

Common gaps we look for

When small defense suppliers review Level 1, the same issues come up again and again: shared shop-floor or front-office logins, former employees whose accounts were never disabled, no written record of who has physical keys or alarm codes, guest Wi-Fi on the same network as business systems, old drives thrown out without sanitization, and patching that depends on someone remembering. None of these needs an enterprise budget to fix, but each one has to be fully addressed because Level 1 allows no POA&Ms.

Multifactor authentication is not one of the 15 FAR requirements, but it is a practical way to strengthen the identify-and-authenticate controls. See CISA's multifactor authentication guidance.

Practical next steps

1. Confirm which contracts and prime-contractor flowdowns include FAR 52.204-21 or CMMC requirements, and whether any of your contract data is CUI.

2. Define your assessment scope: the people, devices, systems, and locations that process, store, or transmit FCI.

3. Walk through all 15 requirements using the NIST SP 800-171A objectives, and collect evidence such as screenshots, policies, logs, and visitor records.

4. Fix every gap before you score. Level 1 is all MET or not met.

5. Enter the results in SPRS, have your Affirming Official submit the affirmation, and put the annual renewal on the calendar.

6. Keep your evidence for six years.

For the current status of CMMC phase-in, read our earlier post, CMMC Phase II Is Paused. Your Self-Assessment Work Is Not.

How Integrity Security Defense Corp can help

Integrity Security Defense Corp helps Inland Empire aerospace and defense suppliers prepare for CMMC Level 1 and Level 2 self-assessments, and runs the day-to-day controls behind them through managed IT and managed cybersecurity. We are not a C3PAO, we are not an authorized CMMC assessor, and we do not certify companies. We help you understand your scope, close gaps, and keep evidence organized so your Affirming Official can sign with confidence. To talk through where you stand, contact us or call (909) 310-2022.

Official sources

Next step

Get a practical review of where you stand.

Integrity Security Defense Corp helps Inland Empire defense contractors with CMMC readiness and managed cybersecurity. We are not a C3PAO and do not perform official certification assessments.