Study guide
6.3 System & Communications Protection (SC) Domain: Boundary Defense & Cryptography
CMMC Certified CMMC Professional CCP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Logistics
1.1 Exam Structure, Current Logistics & Official Blueprint 1.2 Eligibility, Training, Retakes & Certification Maintenance 1.3 Study Strategy, Blueprint Mapping & Authoritative Sources
2 Chapter 2: The CMMC Ecosystem & Stakeholder Roles
2.1 Governance & Oversight: DoD, DIBCAC, Cyber AB & ISACA 2.2 Industry Roles: C3PAOs, OSCs, Consultants, ATPs & APPs 2.3 Assessor Roles: CCP, CCA, Lead CCA, QA & Certifying Official
3 Chapter 3: Code of Professional Conduct & Ethics
3.1 Applying the CMMC Code of Professional Conduct 3.2 Conflicts of Interest, Independence & Consulting vs Assessment Boundaries 3.3 Confidentiality, Incident Escalation & Misconduct Reporting
4 Chapter 4: Legal Authorities, Federal Rules & Standards
4.1 FCI vs CUI: Statutory Foundations, E.O. 13556 & 32 CFR Part 2002 4.2 FAR, DFARS & 32 CFR Part 170 4.3 NIST Standards Hierarchy: SP 800-171, SP 800-171A & SP 800-172
5 Chapter 5: CMMC Model Architecture & Maturity Levels
5.1 CMMC Three-Level Architecture, Assessment Types & Affirmation 5.2 Level 1: 15 FAR Safeguarding Requirements & Annual Self-Assessment 5.3 Level 2 & Level 3: CUI Protection and Assessment Authority
6 Chapter 6: CMMC Domains: Access Control, Identity & Boundary Defense
6.1 Access Control (AC) Domain: 22 Practices & Core Implementation 6.2 Identification & Authentication (IA) Domain: MFA & Credential Management 6.3 System & Communications Protection (SC) Domain: Boundary Defense & Cryptography
7 Chapter 7: CMMC Domains: Audit, Configuration, Maintenance & Media
7.1 Audit & Accountability (AU) Domain: Logging, Review & Non-Repudiation 7.2 Configuration Management (CM) Domain: Baselines, Changes & Least Functionality 7.3 Maintenance (MA) & Media Protection (MP) Domains: Sanitization & Tool Control
8 Chapter 8: CMMC Domains: People, Physical, Incident Response & Integrity
8.1 Awareness & Training (AT) & Personnel Security (PS) Domains: Screening & Training 8.2 Physical Protection (PE): Level 1 FAR Requirements & Level 2 Mapping 8.3 Incident Response (IR), System Integrity (SI) & Risk Assessment (RA/CA) Domains
9 Chapter 9: CMMC Scoping Methodology & Boundary Definition
9.1 Scoping Fundamentals: Organizational Scope, Level 1 & Level 2 9.2 The 5 Asset Categories: CUI, SPA, CRMA, Specialized & Out-of-Scope 9.3 Boundary Definition, Data Flow Diagrams & Secure Enclave Isolation
10 Chapter 10: Cloud Service Providers, ESPs & Supply Chain Flowdown
10.1 Cloud Service Providers (CSPs): FedRAMP Moderate Equivalency & DFARS 7012 10.2 External Service Providers (ESPs/MSPs/MSSPs) & Shared Responsibility Matrices 10.3 Subcontractor Flow-Down, Supply Chain Governance & SPRS Scoring
11 Chapter 11: CMMC Assessment Process (CAP): Planning & Evidence Gathering
11.1 CAP Preliminary Proceedings & Phase 1 Pre-Assessment 11.2 CAP Phase 2: Assess Conformity to Security Requirements 11.3 Assessment Objectives, Evidence Sufficiency & Limited Correction
12 Chapter 12: CMMC Assessment Process (CAP): Reporting, POA&M & Closeout
12.1 CAP Phase 3: Complete and Report Assessment Results 12.2 Level 2 POA&M Rules, Exclusions & 180-Day Closeout 12.3 CAP Phase 4: Certificate Issuance & POA&M Closeout
6.3 System & Communications Protection (SC) Domain: Boundary Defense & Cryptography
Key Takeaways Explain This Topic AI
System and Communications Protection contains 16 Level 2 requirements; 3.13.1 and 3.13.5 also map to the two Level 1 SC safeguarding requirements.
Boundary, architecture, shared-resource, public-component, default-deny, and split-tunneling objectives define results; firewalls, DMZs, VLANs, and gateways are implementation examples rather than universal products.
Requirements 3.13.8 and 3.13.16 protect CUI in transit and at rest, while 3.13.11 requires FIPS-validated cryptography whenever cryptography is used for CUI confidentiality.
Keep the middle numbers exact: 3.13.9 terminates network connections, 3.13.10 manages cryptographic keys, and 3.13.11 governs FIPS validation.
Collaborative devices, mobile code, VoIP, and session authenticity must be controlled against their objectives without inventing mandatory protocols, cipher lists, or monitoring products.
Last updated: August 2026
System & Communications Protection: Boundaries, Sessions & Cryptography
The SC family contains 16 Level 2 requirements . Requirements 3.13.1 and 3.13.5 also map to Level 1. The family protects boundaries, architecture, transmissions, stored CUI, communications sessions, cryptography, collaborative devices, mobile code, and VoIP.
Boundary and architecture requirements
Requirement 3.13.1 monitors, controls, and protects communications at external boundaries and key internal boundaries. The organization identifies those boundaries and shows the mechanisms and activities that enforce them. Continuous packet inspection, a particular firewall brand, or one diagram style is not stated universally.
Requirement 3.13.2 employs architectural designs, software-development techniques, and systems-engineering principles that promote effective information security. 3.13.3 separates user functionality from system-management functionality, and 3.13.4 prevents unauthorized and unintended information transfer through shared system resources. Separate management networks and bastions may help, but logical access controls or other designs can satisfy the objective when supported.
Requirement 3.13.5 implements physically or logically separated subnetworks for publicly accessible components. A DMZ is a common design. The team verifies actual separation and allowed paths, not the label on a network segment.
Traffic and split tunneling
Requirement 3.13.6 denies network communications traffic by default and allows it by exception. The team traces approved flows to firewall, router, host, cloud, or application rules and verifies that the effective configuration implements the default-deny result. A broad rule needs evidence of its authorized purpose; the requirement is not a command to search for one literal ACL string.
Requirement 3.13.7 prevents remote devices from simultaneously establishing non-remote connections with organizational systems and communicating through another connection to external networks. Full-tunnel VPN is a common implementation, but the objective is the prevented simultaneous path. The assessor evaluates the actual remote-device architecture rather than claiming that one VPN product is mandatory.
CUI confidentiality and cryptography
Requirement 3.13.8 implements cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless alternative physical safeguards protect it . Protected distribution systems or controlled physical paths may be relevant alternatives in limited circumstances. Ordinary internet transmission typically relies on cryptography.
Requirement 3.13.16 protects the confidentiality of CUI at rest. Encryption is a common mechanism, but the requirement is outcome-oriented and can interact with physical and access safeguards. If cryptography is used to protect CUI confidentiality for either requirement, 3.13.11 requires FIPS-validated cryptography.
FIPS validation attaches to the cryptographic module and its validated operational environment or configuration, not merely to AES, TLS, or another algorithm name. Evidence should identify the exact module, version, certificate, security policy, deployed configuration, and data path. The current CMVP record and transition rules matter. “FIPS capable” is not proof that the deployed function operates inside the validation boundary.
Requirement 3.13.10 establishes and manages cryptographic keys for cryptography used in organizational systems. Generation, distribution, storage, access, rotation or replacement, recovery, revocation, and destruction are evaluated as applicable. It is 3.13.10—not 3.13.9.
Connections and communications technologies
Requirement 3.13.9 terminates network connections associated with communications sessions at the end of sessions or after an organization-defined period of inactivity. This is distinct from key management and from the user-session termination requirement in Access Control.
Requirement 3.13.12 prohibits remote activation of collaborative computing devices and indicates their use to users present at the device. Authorized exceptions and technologies are evaluated against the assessment objectives.
Requirement 3.13.13 controls and monitors mobile code. The organization identifies covered technologies and allowed or prohibited use based on risk. Not every script is automatically mobile code, and CMMC does not publish one universal allowlist.
Requirement 3.13.14 controls and monitors VoIP use. Network segmentation, configuration, call controls, monitoring, or encryption may support the result depending on architecture; the requirement does not universally prescribe SRTP, a VLAN, or a vendor.
Requirement 3.13.15 protects communications-session authenticity. Relevant evidence can include protocol configuration, certificate validation, mutual authentication, or other mechanisms that prevent impersonation and session hijacking.
Evidence sequence
For an SC scenario:
Trace CUI, management, public, remote, and provider flows across the actual scope.
Map the fact to the exact numbered requirement and assessment objectives.
Examine architecture, rules, configuration, module validation, keys, and records.
Interview network, system, security, and service-provider personnel.
Test representative allowed, denied, remote, session, or cryptographic behavior where appropriate.
Confirm that inherited or shared-provider claims match the CRM and operational evidence.
A diagram showing a DMZ does not prove separation if routing bypasses it. A VPN screenshot does not prove split tunneling is prevented on the sampled endpoints. A CMVP certificate does not prove the product uses that validated module in the assessed configuration. The finding follows the complete evidence chain.