CMMC Level 2 is built on the 110 requirements in NIST SP 800-171. It does not require a penetration test outright, but it does require periodic assessments of your security controls and regular vulnerability scanning. A penetration test is one of the strongest ways to show those controls work. CMMC Level 3 goes further and requires penetration testing at least annually.
Coastline tests the systems that handle Controlled Unclassified Information, so you find the gaps before your C3PAO assessor does.
We scope each engagement around your CUI environment. Every CMMC engagement can include:
We test how far an attacker gets from a single compromised account, including privilege escalation in Active Directory.
VPNs, remote access and internet-facing systems, tested for the weaknesses attackers exploit first.
We check that systems outside your CUI enclave really cannot reach it.
Findings note the NIST SP 800-171 requirements they affect, so your team knows which practices need work.
A report with every finding, its risk and how to fix it, written so you can feed it into your System Security Plan and POA&M.
Related: Active Directory security assessment and internal penetration testing.
Not outright. Level 2 is built on the 110 requirements in NIST SP 800-171, which call for periodic assessments of your security controls (CA.L2-3.12.1) and regular vulnerability scanning (RA.L2-3.11.2). A penetration test is one of the strongest ways to show an assessor that those controls actually work.
Yes. Level 3 adds requirements from NIST SP 800-172, including CA.L3-3.12.1e, which calls for penetration testing at least annually or whenever significant security changes are made to the system.
Early enough to fix what we find. Whether you are submitting a self-assessment score in SPRS or preparing for a C3PAO or government-led assessment, testing first gives your team time to remediate, update your System Security Plan and close out POA&M items.
Yes. We test from outside your CUI boundary to confirm that systems outside the enclave cannot reach the systems inside it. If they can, the report shows exactly how, so you can fix it before your assessment.
Yes. DoD paused the Phase 2 C3PAO requirements in July 2026, but Phase 1 self-assessments are still required and NIST SP 800-171 compliance is still enforced through self-assessments and select government-led assessments. A penetration test is one of the strongest ways to back up the controls you attest to.
A scan covers the vulnerability scanning requirement (RA.L2-3.11.2), but it only lists known weaknesses. A penetration test shows whether an attacker can actually use them to reach CUI, which is what your controls are supposed to prevent.
Yes. If CUI lives in Microsoft 365 GCC High, Azure Government, AWS GovCloud or a custom web application, those can be in scope. We set scope around where your CUI actually lives.
At least once a year and after significant changes to systems that handle CUI. At Level 3 that schedule is a requirement (CA.L3-3.12.1e).