CMMC Level 1 Requirements

CMMC Level 1 requirements consist of the 15 basic safeguarding requirements in FAR 52.204-21, verified through an annual self-assessment, posted in the Supplier Performance Risk System (SPRS), and affirmed by a senior company official. All 15 must be met; Level 1 does not allow a Plan of Action and Milestones (POA&M) to close gaps later.

If you are researching CMMC Level 1 requirements, you are likely trying to answer a practical set of questions:

  • What controls are required for Level 1?

  • How does Level 1 differ from Level 2?

  • Is certification required or just self-assessment?

  • How does this align with NIST 800-171 or basic cybersecurity practices?

  • What evidence do auditors or customers expect?

  • How do we implement this without overbuilding the system?

CMMC Level 1 is intentionally narrow in scope. It is designed to establish foundational cybersecurity practices for organizations handling Federal Contract Information (FCI). It is not a full security program—but it is still auditable, enforceable, and operational.

This guide lists all 15 requirements, explains what each one means in practice, and shows how to implement them in a way that holds up under contract scrutiny.

Hero illustration (shield with lock, checklist, and professionals; sits between Section 1 and Section 2) → Shield, lock, and checklist illustration representing the 15 CMMC Level 1 requirements

What Is CMMC Level 1?

CMMC Level 1 (Foundational) represents the baseline cybersecurity expectations under the Department of Defense (DoD) Cybersecurity Maturity Model Certification program, commonly called CMMC 2.0 and codified at 32 CFR Part 170.

It is focused on protecting Federal Contract Information (FCI)—not Controlled Unclassified Information (CUI).

Level 1 requires:

  • Implementation of all 15 basic safeguarding requirements from FAR 52.204-21

  • An annual self-assessment (no third-party certification required)

  • Posting the results in SPRS

  • Annual affirmation of compliance by a senior official of the organization

A completed self-assessment with all 15 requirements met gives the organization a CMMC status of Level 1 (Self).

Organizations pursuing broader cybersecurity maturity often align Level 1 implementation with structured frameworks such as CMMC 2.0 Compliance Consulting to ensure scalability toward Level 2.

Where CMMC Level 1 Stands in October 2026

The DFARS rule that puts CMMC into DoD contracts (clause 252.204-7021) took effect on November 10, 2025. That started Phase 1 of the rollout, in which solicitations can require Level 1 or Level 2 self-assessment status as a condition of award.

On July 13, 2026, the Department suspended Phase 2, which would have made third-party (C3PAO) Level 2 certification the default for many contracts starting November 10, 2026, and launched a review of the program. That suspension did not change Level 1:

  • The 15 requirements still apply wherever FCI is handled under a contract containing FAR 52.204-21.

  • Level 1 self-assessments, SPRS posting, and annual affirmations remain required when a contract calls for them.

  • The safeguarding requirements themselves have been contractual since FAR 52.204-21 took effect in 2016.

Further program changes may follow the review, so check the DFARS clauses and CMMC level named in each solicitation.

What Is Federal Contract Information (FCI)?

FCI is information that is:

  • Provided by the government or generated for the government under a contract to develop or deliver a product or service

  • Not intended for public release

  • Not simple transactional information, such as what is needed to process payments

FCI that also meets the definition of CUI requires Level 2 protection.

Examples include:

  • Contract performance details

  • Technical instructions

  • Operational schedules

  • Internal communications tied to government work

If your organization handles FCI—even indirectly—you are expected to meet Level 1 requirements.

The 15 CMMC Level 1 Requirements

CMMC Level 1 aligns directly with FAR 52.204-21(b)(1). The 15 requirements are grouped into six domains. Each is listed below with its CMMC identifier.

Access Control (AC): 4 requirements

  • AC.L1-b.1.i – Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)

  • AC.L1-b.1.ii – Limit system access to the types of transactions and functions that authorized users are permitted to execute

  • AC.L1-b.1.iii – Verify and control or limit connections to and use of external systems

  • AC.L1-b.1.iv – Control information posted or processed on publicly accessible systems

Identification and Authentication (IA): 2 requirements

  • IA.L1-b.1.v – Identify system users, processes acting on behalf of users, and devices

  • IA.L1-b.1.vi – Authenticate (verify) the identities of those users, processes, or devices before allowing access

Media Protection (MP): 1 requirement

  • MP.L1-b.1.vii – Sanitize or destroy system media containing FCI before disposal or release for reuse

Physical Protection (PE): 2 requirements

  • PE.L1-b.1.viii – Limit physical access to systems, equipment, and operating environments to authorized individuals

  • PE.L1-b.1.ix – Escort visitors and monitor visitor activity, maintain audit logs of physical access, and control and manage physical access devices

System and Communications Protection (SC): 2 requirements

  • SC.L1-b.1.x – Monitor, control, and protect communications at external boundaries and key internal boundaries

  • SC.L1-b.1.xi – Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks

System and Information Integrity (SI): 4 requirements

  • SI.L1-b.1.xii – Identify, report, and correct system flaws in a timely manner

  • SI.L1-b.1.xiii – Provide protection from malicious code at appropriate locations

  • SI.L1-b.1.xiv – Update malicious code protection mechanisms when new releases are available

  • SI.L1-b.1.xv – Perform periodic scans of systems and real-time scans of files from external sources as files are downloaded, opened, or executed

These requirements are intentionally basic—but they must be implemented consistently and demonstrably.

Why some sources list 17 practices: Earlier CMMC material split the physical protection requirement (PE.L1-b.1.ix) into three separate practices. The final 32 CFR 170 rule returned to the FAR's original 15. The obligations are the same.

A note on clause numbers: Under the Revolutionary FAR Overhaul, contracts issued under agency class deviations may cite these same safeguarding requirements under a new clause number (FAR 52.240-93 in the FAR Council's model deviation text). Check the clause cited in your contract; the 15 requirements have not changed.

For organizations that want a structured validation approach, a CMMC Compliance Checklist can help map each requirement to evidence and controls.

What “Implementation” Actually Means

A common mistake is assuming Level 1 is informal. It is not.

You are expected to demonstrate:

  • Defined access controls across systems

  • Controlled user provisioning and deprovisioning

  • Active antivirus or endpoint protection

  • Patch management practices

  • Physical access controls (even in small environments)

  • Logging and monitoring where applicable

This is where organizations often benefit from alignment with a NIST Compliance Consultant perspective—ensuring controls are not only present but defensible.

Scoping: Which Systems the Requirements Apply To

The 15 requirements apply to the assets that process, store, or transmit FCI. Getting this boundary right is the first decision in any Level 1 self-assessment, because it determines what you have to protect and what evidence you need.

Under 32 CFR 170.19, scoping for Level 1 works like this:

  • In scope: People, technology, facilities, and external service providers that process, store, or transmit FCI

  • Specialized assets: Internet of Things and industrial IoT devices, operational technology, government-furnished equipment, restricted information systems, and test equipment are not part of the Level 1 self-assessment

  • Out of scope: Assets that do not process, store, or transmit FCI

Many small and mid-sized contractors reduce effort by keeping FCI in a defined set of systems—a specific cloud tenant, file share, or enclave—rather than letting it spread across the whole network.

Required Evidence for Level 1

Even though Level 1 is self-assessed, evidence is still expected.

Typical evidence includes:

  • Access control policies or system configurations

  • User access lists and account management records

  • Antivirus deployment screenshots or reports

  • Patch/update logs

  • Physical access procedures or badge logs

  • Network diagrams or segmentation descriptions

Evidence does not need to be overly formal—but it must be:

  • Consistent

  • Repeatable

  • Available upon request

Self-Assessment Requirements

Under CMMC 2.0:

  • Level 1 requires an annual self-assessment against all 15 requirements

  • Each requirement is scored MET or NOT MET; every requirement must be MET to achieve Level 1 (Self) status

  • POA&Ms are not permitted at Level 1, so gaps must be closed before you post results

  • Results must be submitted into the Supplier Performance Risk System (SPRS)

  • A senior official (the Affirming Official) must affirm continuing compliance, and the affirmation must be renewed annually

  • Prime contractors must flow the Level 1 requirement down to subcontractors that handle FCI

This is not a passive checkbox. False attestation carries legal and contractual risk, including potential False Claims Act exposure.

For a step-by-step walkthrough of the assessment itself, see our CMMC Level 1 self-assessment guide.

Organizations often formalize this process within broader governance structures supported by ISO consulting services to ensure consistency and accountability.

Common Misunderstandings About Level 1

“Level 1 Is Just IT Hygiene”

Incorrect.

Level 1 includes:

  • Organizational accountability

  • Defined access control processes

  • Physical security expectations

  • Evidence-based validation

It is a management system problem—not just an IT configuration task.

“We Don’t Need Documentation”

Also incorrect.

While formal documentation is not explicitly required, you still need:

  • Defined practices

  • Repeatable processes

  • Evidence of implementation

Without this, self-assessment becomes unverifiable.

“We Can Ignore It Until Required”

Risky.

FAR 52.204-21 has been included in contracts since 2016, so many organizations are already contractually bound to the 15 requirements. Since November 10, 2025, DoD solicitations can also require a current Level 1 (Self) status in SPRS before award. Waiting introduces:

  • Contract eligibility risk

  • Delays in bidding or onboarding

  • Increased remediation cost under pressure

Relationship to CMMC Level 2

CMMC Level 1 and Level 2 are not incremental in a simple sense—they are structurally different.

Level 1:

  • Focuses on FCI

  • Requires 15 basic safeguarding requirements

  • Allows self-assessment only, with no POA&Ms

Level 2:

  • Focuses on CUI

  • Requires 110 controls (aligned with NIST SP 800-171 Rev. 2)

  • Requires either a self-assessment or a third-party (C3PAO) certification, depending on the contract; new C3PAO requirements were paused in July 2026 pending the DoD review

The 15 Level 1 requirements map to a subset of the NIST SP 800-171 controls, so a well-built Level 1 program becomes the foundation for Level 2 rather than throwaway work. For a side-by-side view of all three levels, see CMMC certification levels.

Organizations planning long-term DoD engagement typically design Level 1 with forward alignment to Level 2.

This is where integration with ISO 27001 certification consulting becomes valuable—ensuring scalability of security controls.

How to Implement CMMC Level 1 Effectively

A disciplined approach follows a structured sequence.

Step 1 – Define Scope

  • Identify systems handling FCI

  • Map data flows and user access

  • Establish system boundaries

Step 2 – Map Requirements to Controls

  • Align each of the 15 practices to existing controls

  • Identify gaps in access control, patching, or monitoring

Step 3 – Implement Missing Controls

  • Configure user access restrictions

  • Deploy endpoint protection

  • Establish patching cadence

  • Implement basic network protections

Step 4 – Define Operational Processes

  • User onboarding and offboarding

  • Incident reporting and response

  • Media handling and disposal

  • Physical access control

Step 5 – Collect Evidence

  • Screenshots, logs, configurations

  • Policies or procedures where needed

  • Records of control execution

Step 6 – Perform Self-Assessment

  • Validate each requirement against evidence

  • Document results clearly

  • Submit to SPRS

Organizations often embed this within broader governance models supported by enterprise risk management frameworks to ensure ongoing oversight.

Timeline for Level 1 Implementation

Typical timelines vary based on maturity:

  • Small organizations with basic controls: 2–4 weeks

  • Organizations with limited structure: 1–3 months

  • Multi-system environments: 2–4 months

The biggest driver is not technical complexity—it is organizational clarity and discipline.

Cost Considerations

Level 1 costs are relatively low compared to higher maturity frameworks, but still include:

  • Internal time and resources

  • Potential tool upgrades (endpoint protection, patch management)

  • Advisory or consulting support

Because Level 1 is self-assessed, there is no third-party assessment fee. For how costs change at Level 2 and Level 3, see how much CMMC certification costs.

Organizations often use Level 1 as a low-cost entry point into structured compliance programs.

Common Implementation Risks

Organizations frequently struggle with:

  • Undefined system scope

  • Inconsistent access control practices

  • Lack of evidence for implemented controls

  • Over-reliance on IT without governance oversight

  • No repeatable process for annual reassessment

These are not technical failures—they are system design failures.

Integrating CMMC Level 1 Into a Broader System

High-performing organizations do not treat Level 1 as a standalone requirement.

They integrate it into:

  • Risk management processes

  • Internal audit programs

  • Management review cycles

  • Continuous improvement systems

This reduces duplication and builds toward scalable compliance maturity.

Benefits of Meeting CMMC Level 1 Requirements

Even at a basic level, compliance strengthens:

  • Eligibility for DoD contracts

  • Customer confidence in cybersecurity practices

  • Internal control over systems and data

  • Operational discipline

  • Readiness for higher-level certifications

For many organizations, Level 1 is the entry point into structured governance—not the end state.

Is CMMC Level 1 Worth It?

If your organization:

  • Works with the Department of Defense

  • Handles Federal Contract Information

  • Plans to expand into government contracting

  • Wants to establish baseline cybersecurity discipline

Then Level 1 is not optional—it is foundational.

It establishes the minimum standard for participation in the defense industrial base.

CMMC Level 1 Requirements: Common Questions

Is CMMC Level 1 a certification or a self-assessment?

Level 1 is a self-assessment. Your organization evaluates itself against the 15 requirements, posts the results in SPRS, and a senior official affirms compliance. No C3PAO is involved, although the government retains the right to verify what you report.

Can we use a POA&M to meet CMMC Level 1?

No. POA&Ms are not permitted at Level 1, so all 15 requirements must be MET at the time you post your self-assessment. Any gap has to be closed before you can claim Level 1 (Self) status.

Do subcontractors have to meet CMMC Level 1 requirements?

Yes, if they handle FCI. Prime contractors are required to flow the CMMC requirement down to subcontractors that process, store, or transmit FCI, and each subcontractor posts its own self-assessment in SPRS.

How often does the Level 1 self-assessment have to be repeated?

Annually. Both the self-assessment and the senior official's affirmation must be renewed every year to keep a current Level 1 (Self) status. Treat it as a recurring process with an owner and a calendar date, not a one-time project.

Did the July 2026 Phase 2 suspension change Level 1?

No. The suspension paused the move to third-party Level 2 certification. Level 1 self-assessment, SPRS posting, and annual affirmation requirements remain in effect where contracts require them.

If You’re Also Evaluating…

The most effective starting point is a structured CMMC gap analysis followed by a controlled implementation aligned directly to the 15 Level 1 requirements.

Contact us.

info@wintersmithadvisory.com
‪(801) 477-6329‬