Skip to main content

Nutmeg Tech | Managed IT Support, Cybersecurity & Predictable IT Budgets

CMMC Level 1 Checklist: Prepare for 2026 Compliance

If you're a Department of Defense contractor, there's a good chance CMMC language is already showing up in contracts, subcontractor flow-downs, or prime contractor questionnaires. That usually starts the same way. An operations leader asks whether the company is “already compliant,” IT starts hunting for policies and screenshots, and someone realizes Federal Contract Information sits in more places than anyone expected. CMMC Level 1 is the entry point. It applies to organizations handling Federal Contract Information, and the official Department of Defense assessment guide defines it around 15 basic safeguarding requirements drawn from FAR 52.204-21 in the DoD CMMC Level 1 Assessment Guide. It isn't a broad governance exercise. It's a focused, practical baseline. A useful CMMC Level 1 checklist shouldn't just restate every practice. It should help a contractor close the gaps that most often create trouble during self-assessment and annual affirmation. The seven controls below do that. They center on access, identity, physical security, network boundaries, patching, malware protection, and media disposal. Each section uses a compliance-in-a-box approach. What to do. What good evidence looks like. How to verify it. What usually goes wrong. For small and midsize contractors, that's the difference between saying controls exist and being prepared to prove they work. 1. AC.1.001 Limit Information System Access to Authorized Users Access control fails in ordinary ways. A former employee still has Microsoft 365 access. A shared workstation auto-logs in. A vendor remote support account never expires. Those aren't exotic security failures. They're everyday admin shortcuts that turn into Level 1 findings. For this control, the organization needs to define who may access systems that store, process, or transmit FCI, then enforce that access. In plain language, not everyone gets a key to every door. An estimator may need access to a contract folder, but not to accounting systems. A help desk technician may need temporary admin rights, but not standing access to sensitive file shares. What done right looks like Strong evidence is usually simple and operational: Named user access lists: A current roster of authorized users for systems with FCI. Role-based permissions: Microsoft 365 groups, Active Directory security groups, or line-of-business system roles aligned to job function. Joiner mover leaver process: HR and IT records showing access is granted, changed, and removed in a controlled way. Restricted remote access: VPN, remote support, and admin portals limited to approved users. A manufacturer bidding on DoD work might keep FCI in SharePoint, Outlook, and an ERP system. Done right, the contract manager, estimator, and approved program staff can access those locations. The warehouse supervisor doesn't have that access unless there's a business need. Practical rule: If the company can't explain why a person has access to FCI, that access probably shouldn't exist. Verification should include a real access review, not a policy-only review. Pull a user list from Microsoft 365, file servers, firewall VPN users, and any business application that touches FCI. Then compare that list to current staff and job responsibilities. Organizations that want a stronger operational model can also borrow from established access control best practices and pair logical access with physical controls such as Wisenet Security access control solutions. Common mistakes are predictable. Shared folders open to “Everyone.” Old admin accounts. Contractors left active after a project ends. Access requests approved in email but never documented anywhere central. 2. IA.1.076 Identify Information System Users Accountability starts with one rule. Every action on a system should trace back to a specific user, process, or device. When that chain breaks, investigation becomes guesswork. Shared accounts are the usual problem. A team uses one login for a production workstation. A generic mailbox has direct sign-in rights. A field laptop is passed around under the same local account. That may feel convenient, but it defeats traceability. Compliance in a practical environment What works is unique identity everywhere FCI touches the environment. In most small organizations, that means each employee has an individual Microsoft 365 or Active Directory account, individual VPN access, and an individual login for line-of-business applications. If a service account exists, it should have a documented purpose, limited scope, and controlled credentials. Evidence should make that uniqueness obvious: Directory records: Active Directory, Entra ID, Google Workspace, or application user lists showing named accounts. System logs: Sign-in logs tied to individual accounts. Account standards: A naming convention and documented process for creating and disabling accounts. No shared credentials for critical systems: Especially email, file storage, VPN, and admin platforms. A practical test helps. Ask three questions. Can the company tell who accessed a contract file? Can it tell which account logged into the firewall? Can it identify which technician used remote admin tools on a server? If the answer is “not really,” this control isn't mature enough. When a team says, “Everyone uses the same account, but we trust each other,” that's not identity management. That's a blind spot. A common exception involves shared inboxes like contracts@ or bids@. Those can still work if users access them through their own named account and not with a shared password. The system should still record who did what. The trade-off is convenience versus accountability. Level 1 clearly favors accountability. If a process depends on shared credentials, that process needs redesign. 3. PE.1.131 Limit Physical Access to Systems A locked server room still matters. So does a reception process, badge control, and a clean way to secure laptops in offices and branch locations. Physical security gets overlooked because many teams think “cyber” only means software. Level 1 doesn't make that mistake. An organization needs to restrict physical access to systems that handle FCI. In a small office, that may mean locking networking gear in a closet, placing servers in a badge-controlled room, securing file cabinets containing printed contract documents, and making sure visitors aren't left wandering near workstations. Evidence that actually holds up Good evidence usually includes: Door controls: Badge access, keys, or coded locks for server rooms and telecom closets. Visitor procedures: Sign-in sheets, escorts, and reception practices.

10 Cybersecurity Best Practices for Small Businesses

Small businesses are frequent targets. One commonly cited industry roundup noted that 43% of SMBs experienced at least one cyberattack in a 12-month period, which lines up with what I see in the field: attackers go after the companies that are easiest to access, not the ones with the biggest name. For a small business, the consequences include more than a few suspicious emails. A single incident can interrupt payroll, lock staff out of Microsoft 365 or Google Workspace, expose customer or patient data, stall invoicing, and turn an ordinary week into a costly recovery project. Owners usually feel the impact in lost time, outside consulting fees, and frustrated customers before they ever see it in a formal incident report. The good news is that small business security is usually a prioritization problem, not a technology problem. You do not need an internal security team or a six-figure tool stack to reduce risk. You need the basics in place, in the right order, with clear ownership. That is how this guide is structured. Each practice below is presented as a working checklist with expected cost ranges, typical implementation timelines, and examples of where it fits in a real small business environment. It is designed to help you decide what to handle internally, what to hand to your IT provider, and when it makes sense to bring in an MSP for help with rollout, monitoring, or recovery planning. If you want a practical example of where to start, this guide to multi-factor authentication best practices for business systems is the kind of control that delivers fast risk reduction without a long project. The goal is straightforward. Reduce the odds of a breach, limit the damage if one happens, and make recovery predictable. 1. Implement Multi-Factor Authentication Across All Systems Passwords fail all the time. Staff reuse them, save them in browsers, share them over email, or hand them to a fake login page. MFA adds a second check, so a stolen password alone usually isn’t enough to get in. Start with the accounts that would hurt most if compromised: business email, Microsoft 365 or Google Workspace, VPN, remote desktop access, accounting platforms, and any admin account. For a small law office, that means client documents and email. For a manufacturer, it means remote access into file shares, ERP systems, or plant-support systems. What to do first Authenticator apps usually beat text-message codes because they’re harder to intercept and easier to standardize. Microsoft Authenticator and Google Authenticator are common choices. If the business already uses a cloud identity platform, adding single sign-on can reduce login friction while keeping MFA in place. A basic rollout can often start in days, not months. The cost is usually low if the company already pays for a business email or identity platform that includes MFA features. The bigger cost is staff support during setup and account recovery. Practical rule: Turn on MFA for email and admin accounts before doing anything else. If email falls, attackers often reset passwords everywhere else. For businesses that need a clearer rollout path, Nutmeg’s MFA best practices guide is a useful reference. A few details matter: Prioritize critical systems: Secure email, VPN, cloud storage, and admin consoles first. Store recovery codes safely: Keep backup codes off the user’s device and under controlled access. Plan for lost phones: Create a documented process for re-enrollment so one broken device doesn’t stop work. 2. Establish Regular Employee Security Awareness Training Email phishing is still one of the cheapest and most reliable ways to get into a small business. Attackers do not need to break technical controls if an employee approves a fake login, opens a malicious attachment, or changes payment details based on a spoofed message. That makes training a priority early in the roadmap, usually right after MFA. Training should match the employee’s role, not a generic annual presentation. Finance staff need examples of invoice fraud, payroll diversion, and vendor bank-change scams. Front desk and office managers need practice spotting fake shared documents, delivery notices, and password reset emails. Nonprofits and faith-based organizations should cover donation fraud, impersonation of leadership, and urgent requests that rely on trust and speed. What good training looks like Good awareness training is short, repeated, and tied to a reporting process. New hires should get it during onboarding. Existing staff should get refreshers every quarter, with occasional phishing tests to measure whether people are catching the warning signs or still clicking. For a small business, this is usually a moderate-effort project. A basic program can be set up in 1 to 2 weeks if the company already uses Microsoft 365, Google Workspace, or an outside training platform. Costs range from low if training is included in current subscriptions, to moderate if you add phishing simulations, custom content, or managed administration through an MSP. The trade-off is straightforward. More frequent training creates better habits, but it also creates fatigue if every lesson feels repetitive or disconnected from daily work. Keep sessions brief, use examples from your own environment, and track whether employees report suspicious messages faster over time. That is a better measure than completion rates alone. This human firewall overview from Nutmeg Technologies gives a practical explanation of how to build that reporting culture. Training should cover: Credential theft signs: Fake sign-in pages, repeated MFA prompts, unusual login alerts, and password reset messages that create urgency. Payment fraud checks: Confirming account changes or wire requests through a known phone number or separate channel. Safe reporting: Giving staff a simple way to flag suspicious emails without worrying they will be blamed for asking. Attachment and link handling: Pausing before opening invoices, shared files, compressed folders, and login links from unexpected senders. Staff should treat "urgent," "confidential," and "do this now" as cues to verify first. Not cues to comply faster. 3. Deploy and Maintain Endpoint Protection One infected laptop can turn into a business-wide incident fast. Endpoint protection reduces that risk by blocking known malware, flagging suspicious behavior,