CMMC Level 1: A Practical Roadmap for Companies Starting From Zero
If your company is being asked about CMMC Level 1 for the first time, the process can feel larger than it is.
The place to start is not with a new security platform or a stack of compliance documents.
Start by answering three questions:
Do we need Level 1? Where does Federal Contract Information exist? And are the required safeguards actually working?
CMMC Level 1 applies to organizations that need to protect Federal Contract Information, or FCI, within contractor information systems. It is based on the 15 basic safeguarding requirements in FAR 52.204-21.
For an organization that has never been assessed, a practical roadmap can be broken into five steps.
1. Confirm What Your Contract Requires
Before building a compliance program, determine whether your current or anticipated contract actually requires CMMC Level 1.
Review the solicitation, contract, subcontract, and applicable flow-down requirements.
Then identify whether your organization receives or generates FCI.
FCI is generally nonpublic information provided by or generated for the government under a contract to develop or deliver a product or service. Publicly available information and basic transactional information, such as information needed to process payments, are excluded from the definition.
This first step matters because the objective is not to make your entire company “CMMC compliant.”
The objective is to protect the systems that process, store, or transmit the information covered by the requirement.
2. Find Where FCI Actually Lives
Next, map how FCI moves through your business.
Ask:
Who receives it?
Where is it stored?
Is it sent through email?
Does it reside in Microsoft 365, file shares, cloud applications, or local computers?
Which employees need access?
Which vendors or subcontractors may receive it?
Which systems transmit or protect it?
Do not assume the answer.
A small organization may discover that FCI touches only a limited number of people and systems. Another may find that it has spread across email, shared drives, laptops, and cloud applications.
That discovery defines the environment you need to secure.
Keeping that environment appropriately scoped can also make Level 1 easier to operate and maintain.
3. Assess the 15 Safeguarding Requirements
Once the scope is understood, compare the environment against the 15 basic safeguards in FAR 52.204-21.
Those requirements address fundamentals such as:
limiting access to authorized users;
controlling what authorized users can do;
controlling connections to external systems;
protecting information exposed through public systems;
identifying and authenticating users and devices;
securely disposing of media;
restricting physical access;
protecting network communications;
separating publicly accessible systems from internal systems;
correcting system flaws;
protecting against malicious code; and
scanning for malicious content.
For a company starting from zero, this should be treated as a current-state assessment, not a paperwork exercise.
For each requirement, determine:
Is it implemented? Who owns it? How does it work? What evidence proves it?
If you cannot answer those questions, you have identified work for the roadmap.
4. Close the Gaps Before You Assess
This is where Level 1 differs from simply completing a checklist.
Current DoD rules require a Final Level 1 status. Level 1 does not have the conditional-status option available at Levels 2 and 3.
Practically, that means you should not plan to submit an assessment with known Level 1 safeguards left unresolved.
Close the gaps first.
For many smaller businesses, the remediation may involve basic IT improvements rather than major cybersecurity investments:
cleaning up user accounts;
enforcing appropriate authentication;
tightening access permissions;
improving endpoint protection;
applying software updates;
securing network boundaries;
controlling removable media;
improving visitor and physical-access practices; or
documenting how existing controls operate.
The goal is not to buy more technology.
The goal is to make the required safeguards consistently work.
5. Document, Self-Assess, and Maintain
Once the safeguards are operating, collect enough evidence to support the self-assessment.
That might include configuration records, screenshots, access lists, procedures, system settings, inventory information, or other evidence demonstrating how the requirement is satisfied.
Then complete the Level 1 self-assessment and required submission through the applicable DoD process.
Under current DFARS rules, a Final Level 1 status is considered current for one year, and contractors must maintain an annual affirmation of continuous compliance.
That last phrase matters:
continuous compliance.
Level 1 should not become an annual scramble.
If an employee leaves, remove access.
If a new device is introduced, secure it.
If antivirus stops updating, address it.
If FCI begins moving through a new application, determine whether that application now falls
within the protected environment.
The organization should be able to maintain the safeguards as part of normal IT operations.

For an organization starting from scratch, the roadmap can be straightforward:
Understand → Scope → Assess → Remediate → Validate → Maintain
You do not need to begin with an expensive compliance platform.
You do not need to build an enterprise security program overnight.
And you should not begin by writing policies for controls that are not actually operating.
Start with the environment you have, determine where FCI exists, evaluate the 15 requirements, close the gaps, collect evidence, and make the controls part of normal operations.
That creates something more valuable than a successful self-assessment.
It creates a stronger IT foundation for the business—and a much better starting point if customer or contractual requirements eventually move the organization toward CMMC Level 2.
Don’t Know Where to Start?
Socium Security helps small and mid-sized organizations translate CMMC requirements into practical cybersecurity improvements.
For a first-time Level 1 organization, that means helping determine scope, understand the current environment, identify gaps, prioritize remediation, and establish the evidence needed to support an informed self-assessment.
The objective is simple:
Know what you need to protect. Make the safeguards work. Be able to prove it.



