REKKY logo Sec Ops Consulting © 2026 REKKY Consulting LLC

CMMC Level 1

Check the 15 requirements yourself.

This is a free self-check for a small defense supplier that handles Federal Contract Information. Share it with whoever runs your computers and network. It runs in your browser. Nothing is stored and nothing is sent to this site.

This is an informal readiness check. It is not the SPRS self-assessment, not a score, not a certification, and not legal advice. You perform the self-assessment. You submit the result in SPRS. Your affirming official signs the affirmation. REKKY Sec Ops Consulting does not certify your company and is not affiliated with the Department of War (DoD) or the Cyber AB. We are not a C3PAO and we are not a CMMC certification body. This is not a guarantee of a passing result, a score, or a contract award.

What Level 1 is

Level 1 is the basic safeguarding of Federal Contract Information. That is information provided by or generated for the government under a contract, and not intended for public release. The 15 requirements are in FAR 52.204-21. The company enters the result in SPRS. An affirming official signs an annual affirmation. The artifacts are kept for six years from the CMMC Status Date.

A Level 1 self-assessment under FAR 52.204-21 and 32 CFR 170.15 applies where a contract requires it of a company that handles Federal Contract Information.

Your people still do this work. If you ask us to help later, we work around your normal operations, and we'll need access to the right areas and the right people while we do.

The 15 questions

Answer yes, no, or not sure. Not sure is an honest answer. It is listed with the gaps. The words are plain English. They are not a substitute for FAR 52.204-21, and they are not legal advice.

Are only authorized people, the programs that act for them, and their devices allowed onto the systems that hold Federal Contract Information?

In a small shop. In a small shop this is the list of who can log on, which computers they use, and which software is allowed to touch job files from the government.

Evidence. A current user list, or a screenshot of the accounts that can sign in.

Can each person do only the tasks they are allowed to do on those systems?

In a small shop. The person who quotes a job should not also be the only one who can change payroll, unless that is a duty you have named.

Evidence. A short note of who can do what, or the permission screen for one shared system.

Do you check and control connections from your systems to outside systems?

In a small shop. That includes the email provider, a cloud file folder, a customer portal, and a vendor who logs in from their own office.

Evidence. A list of outside connections, or the setting that shows which ones are allowed.

Do you control what is posted or processed on a public website or a public page?

In a small shop. A photo of a part, a job traveler, or a drawing on the company website can be Federal Contract Information if it came from the contract.

Evidence. The name of the person who approves public posts, or a recent post that was reviewed before it went up.

Can you name the people, the programs acting for them, and the devices on the systems that hold Federal Contract Information?

In a small shop. This is knowing which laptop, which shop computer, and which login belongs to which person.

Evidence. An asset list with a name next to each computer, or directory accounts tied to a person.

Does each person prove who they are before they can get in?

In a small shop. A unique password, a badge, or a second check such as a code sent to a phone. A password the whole shop shares, stuck to a monitor, does not do this.

Evidence. The sign-in screen that asks for a password, or the setting that turns on a second check.

Do you wipe or destroy drives, disks, and paper that hold Federal Contract Information before you throw them out or reuse them?

In a small shop. An old shop computer, a USB stick, and a printed traveler all count. Putting them in the trash does not.

Evidence. A note of the last drive you wiped or shredded, and who did it.

Is physical access to the systems, the equipment, and the work space limited to people who are allowed in?

In a small shop. The shop door, the office where the computers sit, and the cabinet with the drawings.

Evidence. A lock, a key list, or the names of people who have a key.

Do you escort visitors, watch them, keep a log of who came in, and control keys and badges?

In a small shop. A customer, an inspector, or a delivery driver in the office. Someone walks with them, and you write the visit down.

Evidence. A visitor log from a recent visit, and the place keys are kept.

Do you watch, control, and protect network traffic at the edge of the shop network and at the important internal lines?

In a small shop. The router or firewall between the shop and the internet, and the line between the office computers and a public terminal if you have one.

Evidence. The firewall or router settings, or the name of the person who checks them.

Are public-facing pieces, such as guest Wi-Fi or the company website, separated from the internal network?

In a small shop. Guest Wi-Fi that cannot see the shop computers. The company website is not the same network as the drawings.

Evidence. A guest network name that is separate, or a simple sketch of the two networks.

Do you find flaws, tell someone, and fix them in a reasonable time?

In a small shop. A software update the vendor has already released, or a broken backup someone has written down.

Evidence. A recent update record, or a list of open problems with a name next to each one.

Do you protect against malicious code in the places where it can get in?

In a small shop. Antivirus or endpoint protection on the shop computers and on the laptops that leave the building.

Evidence. The protection screen showing it is turned on for those computers.

Do you update that protection when the vendor releases a new version?

In a small shop. The antivirus definitions, not a one-time install from years ago.

Evidence. The screen that shows the last update date.

Do you scan the systems on a schedule, and scan files from outside when they are downloaded, opened, or run?

In a small shop. A repeating scan, and a scan of a customer file or an email attachment before someone opens it.

Evidence. A scan log, or the setting that scans downloads.

If a question was unclear, send feedback. A reply is not promised.

What to do next

Close the gaps you marked, or bring the printed page to the people who run those systems. The result stays on this device.

The self-assessment kit is $497 a year. It is a checklist, plain-English guidance, policy templates, an evidence index, and an annual reminder. Your people still gather the evidence during normal operations. Continue to the kit.

Nothing from this check is stored here.

Questions

Is this self-check the SPRS self-assessment?

No. This is an informal readiness check. It is not the SPRS self-assessment. Your company still performs the self-assessment, submits the result in SPRS, and an affirming official signs the affirmation.

Does this self-check certify a company for CMMC Level 1?

No. This is not a certification, not a score, and not legal advice. REKKY Sec Ops Consulting does not certify your company and is not affiliated with the Department of War (DoD) or the Cyber AB. We are not a C3PAO and we are not a CMMC certification body.

What should we do after the self-check?

Close the gaps you marked, or use the result to prepare. The self-assessment kit is $497 a year. Nothing from this check is stored on the site.