IA.L3-3.5.3e
Block Untrusted Assets
Requirement
Assessment objectives
An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.
Determine if:
- aSystem components that are known, authenticated, in a properly configured state, or in a trust profile are identified;
- bAutomated or manual/procedural mechanisms to prohibit system components from connecting to organizational systems are identified; and
- cAutomated or manual/procedural mechanisms are employed to prohibit system components from connecting to organizational systems unless the components are known, authenticated, in a properly configured state, or in a trust profile.
From the CMMC Level 3 Assessment Guide v2.13 · publisher approved 2026-11-08.
How to implement
Level 3 requires that nothing connects to your systems unless it is known (in the inventory), authenticated, in a properly configured state, or matches a defined trust profile. Level 2 already gives you an inventory, device authentication and baselines; this adds enforcement at every connection point so unknown or non-compliant devices are blocked or quarantined, using automated tools (device compliance plus Conditional Access, network access control) and manual or procedural measures (disabled switch ports, approval before connection). Automated enforcement on the network side usually means buying a NAC product or service.
The minimum for a small organization · Expert CMMC's reading, not official text
Identify what makes a component trusted: known, authenticated, properly configured or in a trust profile [a], usually written down; name the automated or procedural mechanisms that keep other components off your systems [b]; and use them [c]. Device compliance rules on cloud access, network access control with posture checks, shut unused switch ports and an onboarding approval are common choices for a small Level 3 contractor. Whichever you use, expect to explain how it works; for a manual method, the guide's considerations ask whether it is outlined in detail so anyone can follow it without making an error (L3 guide p.43).
Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.
- 1Required outcomePolicyIdentify your trust criteria (known, authenticated, properly configured, or in a trust profile), the components or classes of component that meet them, and the automated or manual/procedural mechanisms that keep other components off.[a][b]SourceCMMC Assessment Guide Level 3 v2.13objectives [a] and [b], p.41
Quoted words
- “System components that are known, authenticated, in a properly configured state, or in a trust profile are identified”
- “Automated or manual/procedural mechanisms to prohibit system components from connecting to organizational systems are identified”
- 2Recommended wayPolicyFor objectives [a] and [b], write down your trust criteria, the components or classes of component that meet them and the mechanisms that keep other components off, name the mechanism at each connection point, and write any manual method in enough detail that anyone can follow it without error. The guide's assessment considerations ask, for a manual method, whether it is outlined in detail so any user will be able to follow it without making an error, and, for an automated method, whether the organization can explain how the technology performs the task (L3 guide p.43).[a][b]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.43 IA.L3-3.5.3e
- 3Required outcomeTechnicalEmploy those mechanisms to prohibit system components from connecting to organizational systems unless they are known, authenticated, properly configured or in a trust profile.[c]
You can tell it worked when at each connection point you named, a device that does not meet your trust criteria is refused when it tries to connect.
SourceCMMC Assessment Guide Level 3 v2.13objective [c], p.41Quoted words
- “Automated or manual/procedural mechanisms are employed to prohibit system components from connecting to organizational systems unless the components are known, authenticated, in a properly configured state, or in a trust profile”
- 4Recommended wayPolicyDefine the trust criteria in the SSP: known (listed in the authoritative inventory), authenticated (device certificate or directory join), properly configured (meets the CM baseline: supported OS, patched within policy, EDR running, disk encryption and firewall on), and any trust profiles for classes of devices that cannot meet all criteria (printers, OT, lab equipment). Name the enforcement points: wired and wireless network, VPN or ZTNA, and cloud applications.[a]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- 5Recommended wayTechnicalCloud and application access: Intune or Google endpoint management compliance policies that mirror the baseline, and Conditional Access or context-aware access that blocks CUI applications from any device that is unknown or non-compliant.[b][c]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- 6Recommended wayTechnicalWhere a sign-in rule requires a compliant device (Conditional Access with Intune), make sure only devices you manage can pass it: assign an Intune compliance policy for each platform you allow (Windows, macOS, iOS, Android); set 'Mark devices with no compliance policy assigned as' to Not compliant (Endpoint security > Device compliance > Compliance policy settings; Microsoft's default is Compliant, so a device with no policy passes); choose the compliance status validity period (default 30 days) and any grace period on the 'Mark device noncompliant' action on purpose; and pilot the rule on a small group, or in report-only mode, before enforcing it so nobody is locked out.[c]
You can tell it worked when an enrolled device with no compliance policy assigned, and an unmanaged laptop, are both refused at sign-in to the CUI apps, while a pilot user's compliant device gets in.
Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e - 7Recommended wayTechnicalNetwork access: 802.1X with posture checks on wired and wireless networks, placing unknown or non-compliant devices in a quarantine or remediation VLAN; VPN or ZTNA that checks device certificate and posture before connecting. Assign trust-profile devices (printers, OT) to restricted segments with MAC authentication bypass and tight ACLs.[b][c]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- 8Recommended wayProcessManual and procedural mechanisms: shut down unused switch ports, enable port security, lock network closets, require an approved onboarding ticket (inventory entry, baseline applied, enrollment) before any new component is connected, and give visitors and vendors only the isolated guest network.[b][c]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- 9Recommended wayTechnicalDetect what slips through: use EDR device discovery, NAC visibility or scheduled network scans to find devices that are not in the inventory, alert on them, and remove or quarantine them (ties to CM.L3-3.4.2e and CM.L3-3.4.3e).[c]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- 10Recommended wayProcessReview blocked and quarantined events and trust profiles monthly, test enforcement at least quarterly with an unknown and a deliberately non-compliant device, and record results.[a][c]Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
Evidence to collect
Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.
A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.
Device trust criteria and trust profiles[a]
Unknown device detection and response records[c]
Quarterly enforcement test results[c]
The detail for 7 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.
Free with an account. Create a free account or sign in.
How assessors check
What an assessor examines, asks and tests: 3 notes.
Free with an account. Create a free account or sign in.
Tools and products
Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.
35 dated vendor facts and notes on 6 products for this practice: what each assumes, what it does not cover and what stays yours.
Free with an account. Create a free account or sign in.
Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.
Common pitfalls
- Enforcing compliance for cloud apps but leaving wired network ports open to anything plugged in.Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.42 IA.L3-3.5.3eandCMMC Assessment Guide Level 3 v2.13p.43 IA.L3-3.5.3e
- Compliance policies that only check enrollment, not the actual baseline settings that define 'properly configured'.Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.42 IA.L3-3.5.3eandCMMC Assessment Guide Level 3 v2.13p.43 IA.L3-3.5.3e
- Trust profiles for printers and OT that are really 'allow everything' with no segmentation.Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.42 IA.L3-3.5.3eandCMMC Assessment Guide Level 3 v2.13p.43 IA.L3-3.5.3e
- Unused switch ports left live in conference rooms and the shop floor.Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.41 IA.L3-3.5.3e
- A quarantine VLAN that can still reach CUI systems.Expert CMMC's adviceseeCMMC Assessment Guide Level 3 v2.13p.43 IA.L3-3.5.3e
Platform notes
- Microsoft 365 (GCC / GCC High)
- Google Workspace
- On-premises or MSP-managed
Notes for 3 platforms.
Free with an account. Create a free account or sign in.
Related practices: IA.L3-3.5.1e, CM.L3-3.4.2e, CM.L3-3.4.3e, CM.L2-3.4.1, CM.L2-3.4.2, AC.L2-3.1.1
Editorial implementation guidance published November 20, 2026. It is not part of the official requirement and does not replace the assessment guide.
Crosswalk
Full crosswalkThe NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.
NIST SP 800-172 (Feb 2021)
3.5.3eSP 800-172 Rev 3
03.05.03E—
SP 800-53 Rev 5
CM-8(3)CIA-3(4)CSSI-4(22)CHow these were reachedHide how these were reached
- CM-8(3) · System Component Inventory | Automated Unauthorized Component Detection
- C SP 800-172 (Feb 2021) Appendix C
- IA-3(4) · Device Identification and Authentication | Device Attestation
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-172 Rev 3 03.05.03E → 800-53 Rev 5 IA-3(4)
- C SP 800-172 (Feb 2021) Appendix C
- SI-4(22) · System Monitoring | Unauthorized Network Services
- C SP 800-172 (Feb 2021) Appendix C
Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.
Where each link comes from (6 links from 4 official documents)
32 CFR 170.14 Office of the Federal Register / GPO
- IA.L3-3.5.3e → 3.5.3e“Level 3 security requirement”32 CFR 170.14(c)(4), Table 1, item (ix)
Further discussion
Practice guide notes
Implementation guidance
Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.
In plain language
Stop components from connecting unless they are known, authenticated, properly configured or covered by a trust profile.
Implementation example
Example from the source assessment guide (not a mandatory implementation): In a Windows environment, you authorize devices to connect to systems by defining configuration rules in one or more Group Policy Objects (GPO) that can be automatically applied to all relevant devices in a domain [a]. This provides you with a mechanism to apply rules for which devices are authorized to connect to any given system and prevent devices that are not within the defined list from connecting [b,c]. For instance, universal serial bus (USB) device rules for authorization can be defined by using a USB device’s serial number, model number, and manufacturer information. This information can be used to build a trust profile for a device and authorize it for use by a given system. You use security policies to prevent unauthorized components from connecting to systems [c]. Example 2 You have been assigned to build trust profiles for all devices allowed to connect to your organization’s systems. You want to test the capability starting with printers. You talk to your purchasing department, and they tell you that policy states every printer must be from a specific manufacturer; they only purchase four different models. They also collect all serial numbers from purchased printers. You gather this information and build trust profiles for each device [a,b]. Because your organization shares printers, you push the trust profiles out to organizational systems. Now, the systems are not allowed to connect to a network printer unless they are within the trust profiles you have provided [b,c]. Example 3 Your organization has implemented a network access control solution (NAC) to help ensure that only properly configured computers are allowed to connect to the corporate network [a,b]. The solution first checks for the presence of a certificate to indicate that the device is company-owned. It next reviews the patch state of the computer and forces the installation of any patches that are required by the organization. Finally, it reviews the computer’s configuration to ensure that the firewall is active and that the appropriate security policies have been applied. Once the computer has passed all of these requirements, it is allowed access to network resources and defined as a trusted asset for the length of its session [a]. Devices that do not meet all of the requirements are automatically blocked from connecting to the network [c].
Evidence examples
Examples suggested by the source guide (not an exhaustive or mandatory checklist): Configuration management policy; identification and authentication policy; system and information integrity policy; procedures addressing system component inventory; procedures addressing device identification and authentication; procedures addressing device configuration management; procedures addressing system monitoring tools and techniques; configuration management plan; security plan; system design documentation; system configuration settings and associated documentation; system inventory records; configuration management records; system monitoring records; alerts/notifications of unauthorized components within the system; change control records; system audit records; system monitoring tools and techniques documentation; documented authorization/approval of network services; notifications or alerts of unauthorized network services; system monitoring logs or records; other relevant documents or records
Common mistakes
Leaving open network ports where any unknown device can connect and get an address on the CUI network.
Track this in a workspace
The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Source: DoD CIO · https://dodcio.defense.gov/CMMC/