CMMC Practice Requirement:

Track, review, approve, or disapprove, and log changes to organizational systems.

CMMC Requirement Explanation:

By documenting, testing, and approving changes you reduce the chance of negative impacts resulting from changes. Unapproved changes often create business operation and security risk.

Example CMMC Implementation:

Document all proposed changes to your IT systems. This includes operating system updates, software deployments, security setting changes, and IT infrastructure changes. Establish a "change control board" consisting of IT staff and persons with business operation responsibilities. Discuss proposed changes before deployment to your production environment. Identify any potential security and business operation risks associated with a proposed change. Only deploy proposed changes after they have been approved by the change control board.

Scenario(s):

- Scenario 1:

Alice a system administrator wants to deploy security updates to her company's Windows 10 workstations. She creates a ticket on her IT ticketing system documenting the proposed change and the testing she has already completed. Every two weeks the change control board reviews proposed changes. The board reviews Alice's proposed change and approves the deployment of updates for Friday night at 7:00 PM. After deploying the updates no issues are reported an Alice closes her ticket.
 

Discover Our NIST SP 800-171 Solutions:

 /assets/images/compliance_accelerator_white.png

Compliance Accelerator

For contractors seeking compliance
 /assets/images/quantum_assessor_white.png

Quantum Assessor

For IT service providers
 /assets/images/supply_chain_logo_white.png

Supply Chain Verifier

For contractors seeking to verify partner compliance