CMMC Level 1 Requirements: A Practical Readiness Guide for Small Contractors
CMMC Level 1 requirements are a practical cybersecurity obligation for covered defense contractors and subcontractors handling Federal Contract Information, or FCI. Readiness depends on the systems that handle that information, the safeguards actually implemented and the required assessment and affirmation process.
This guide is educational, not a determination of your contract requirements or CMMC status. Review your solicitation, contract clauses and current official guidance. A consultant can help with preparation, but hiring a provider does not itself establish your organization's status.
Confirm whether Level 1 fits your information and contract
FCI generally means information provided by or generated for the government under a contract that is not intended for public release, with exclusions described in FAR 52.204-21. It is not interchangeable with Controlled Unclassified Information, or CUI.
If your organization handles CUI, Level 1 may not be sufficient for the applicable work. Do not assume a website-only review addresses the broader information systems used by your company. Review contract requirements with your contracting and security contacts before selecting a scope or service.
Understand the 15 safeguards and 17 requirements
FAR 52.204-21 lists 15 basic safeguarding requirements. CMMC Level 1 assessment guidance maps these into 17 security requirements across six domains. The counts describe different presentations of the same baseline rather than two unrelated sets of obligations.
- Access Control: limit access to authorized users and appropriate functions; control external connections and public information.
- Identification and Authentication: identify and authenticate users and relevant processes or devices.
- Media Protection: sanitize or destroy media containing FCI before disposal or release for reuse.
- Physical Protection: limit physical access and manage visitors and access devices.
- System and Communications Protection: protect communications at system boundaries and separate public-facing components appropriately.
- System and Information Integrity: address flaws and malicious code, including relevant updates and scans.
Use the official assessment guidance for each requirement's objectives and the FAR clause for the underlying safeguards. A short domain summary is not a substitute for testing the individual requirements.
Scope the systems that handle FCI
Trace how FCI enters, moves through and leaves your organization. Consider email, shared drives, laptops, cloud services, mobile devices, printed output and backups. Identify the people and vendors with access, and document the assessment boundary.
A hypothetical contractor that receives nonpublic project information by email and saves it to a shared drive should examine both those services and the devices used to access them. Declaring only one laptop in scope while ignoring the shared repository would not reflect the actual information flow.
Gather evidence of what is implemented
For each requirement, identify the configuration, record or observed practice that supports the result. Evidence may include account and access records, system settings, media disposal procedures, visitor records and malware protection settings, depending on the objective.
A policy saying employees should use individual accounts does not establish that shared accounts have been removed. A purchased security product does not establish that it is deployed, configured and maintained. Match documentation to actual practice and resolve discrepancies before assessing.
Know the assessment and affirmation responsibilities
Level 1 uses an annual self-assessment, rather than a third-party certification assessment. Required results are submitted through the Supplier Performance Risk System, or SPRS, and an authorized affirming official provides the required affirmation. Review 32 CFR 170.15 and 170.22 for the current process and responsibilities.
Level 1 does not permit a conditional status based on a Plan of Action and Milestones. The applicable requirements must be met, not merely scheduled for future implementation. Do not substitute a consultant's report for the company's required submission and affirmation.
Build a repeatable maintenance routine
Assign owners for accounts, device updates, malicious-code protection, physical access and evidence. Review changes when staff leave, vendors change or new tools begin handling FCI. Put the annual reassessment and affirmation cycle on the calendar with enough time to resolve gaps.
Additional security measures may be worthwhile even when they are not standalone Level 1 requirements. Distinguish recommendations from required assessment items so your team understands both the compliance baseline and its broader risk decisions.
Use outside support without confusing responsibility
Our done-for-you CMMC Level 1 service is published at $3,995 and describes assessment preparation, remediation and documentation support. Review the service page and confirm the scope against your environment before engaging. The provider relationship is not a government-issued certification or an automatic MET result.
For a small contractor, the most useful first step is a reliable information-flow inventory and a requirement-by-requirement gap review. Follow current official sources for contract rollout and program changes rather than assuming a static blog article settles every timing question.