Domain 7Security OperationsCORE

Patch Management & Change Governance

Formal change management process (request, impact analysis, CAB approval, testing, rollback plan), configuration baselines, and vulnerability remediation SLAs.

Domain: Domain 7: Security Operations•Updated: 2026-08-26
#Change Management#Configuration Management#Patch Management#CAB#Baseline Management

CISSP Domain 7: Patch Management & Change Governance — Mindmap Review Study Guide

═══════════════════════════════════

PART 1: MERMAID MINDMAP

═══════════════════════════════════

mindmap
  root((Patch and Change Management))
    Patch Management
      Proactive Process
      Known Vulnerabilities Limitation
        Zero Days
      Determine Patch Availability
        Threat Intelligence
        Vendor Notification
          Windows and iOS
          RSS and Twitter
        Proactive Checking
          Agent Scanning
          Agentless Scanning
          Passive Fingerprinting
      Timing and Deployment
        Automated Patching
        Manual Patching
    Change Management
      Process Overview
      Change Request
        Root Cause Analysis
      Assess Impact
      Emergency Change
      Approval Process
        Change Control Board
        Change Advisory Board
        Emergency Change Advisory Board
      Build and Test
      Notification
      Implement
      Validation
        Test New Functionality
        Regression Testing
      Version and Baseline
        Disaster Recovery Plans

═══════════════════════════════════

PART 2: TECHNICAL DEFINITIONS & CONCEPTS

═══════════════════════════════════

Patch Management

Proactive Process

Patch Management — The proactive process consisting of the following ordered steps:

  1. Monitor for new vulnerabilities and patch releases
  2. Acquire or create patches
  3. Evaluate them
  4. Prioritize
  5. Schedule the installation
  6. Deploy
  7. Verify
  8. Document
  9. Update baselines

Proactive Process Goal — To create a consistently configured environment that is secure against known vulnerabilities, ensuring all required systems are patched in a timely manner.

Known Vulnerabilities Limitation

Zero Days — Unknown vulnerabilities for which no patch is currently available.

  • ⚠️ EXAM TIP: Patch management can only patch for known vulnerabilities; it cannot patch for zero days.

Determine Patch Availability

Determine Patch Availability — The first step in the patch management process. Organizations must proactively identify if new patches are available, as most software and systems lack auto-update features or built-in notifications.

Threat Intelligence — The process of gathering information about new threats and threat actors to identify vulnerabilities that could be exploited by newly identified threats.

Vendor Notification — Identifying the need to patch when a vendor announces a patch is available.

  • Systems with built-in notifications (e.g., Windows, iOS) alert automatically.
  • Other systems require organizations to subscribe to vendor mailing lists, RSS feeds, or Twitter accounts.

Proactive Checking — Proactively scanning systems to ensure compliance with baselines and verify that all required patches have been installed in a timely manner.

Scanning Methods

Method Description Primary Use Case
Agent A small piece of software installed on a system to monitor and report its current patch level. Standard internal systems where software installation is permitted.
Agentless No software is installed on the target; a scanning tool connects to and queries the system for its patch level. Systems where installing an agent is not feasible or desired.
Passive (Fingerprinting) Inspecting network packets sent by the system to determine exact version and patch level based on subtle differences in packet construction. Systems not directly in organizational control (e.g., vendor-managed systems).

Timing and Deployment

Timing — Ensuring patches are installed timely. If a new vulnerability is actively being exploited, the patch may need to be deployed extremely rapidly as an emergency change.

Deploy — Installing patches while minimizing organizational impact, often performed in the middle of the night and coordinated with operations.

Deployment Methods

Method Description Use Case & Limitations
Automated Using software to automate patch installation (e.g., Windows Auto Update). Good for deploying quickly across many systems. Bad for high-value/mission-critical servers, as automated patching often breaks existing functionality.
Manual A system administrator manually installs the patch and verifies it. Used for high-value systems to ensure the patch fixed the issue and to perform regression testing to verify no existing functionality is broken.

Change Management

Process Overview

Change Management — The process that ensures the costs and benefits of changes are analyzed and that changes are made in a controlled manner to reduce risk.

Change Management Process — A rigorous, ordered process to ensure changes are made in a controlled manner:

  1. Change Request
  2. Assess Impact
  3. Approval
  4. Build & Test
  5. Notification
  6. Implement
  7. Validation
  8. Version & Baseline Updates

Change Request

Change Request — The initiation of the change management process. Requests can originate from a system owner wanting new functionality, a customer identifying a bug, threat intelligence indicating a need to patch, or the results of a root cause analysis.

Root Cause Analysis — An investigative process following an incident, the results of which can trigger a change request to prevent recurrence.

Assess Impact

Assess Impact — A mandatory evaluation performed for every change request to determine the effort, cost, and potential negative impact on the organization and customers.

  • ⚠️ EXAM TIP: The impact assessment drives the rest of the process, dictating the degree of approvals required, the level of testing and validation, and who needs to be notified.

Change Types Based on Impact

Change Type Description
Standard (Minor) Change Requires little effort and has zero impact on customers.
Massive Change Requires hundreds of hours of development, millions of dollars, and significantly impacts multiple stakeholders and customers.
Emergency Change A high-priority patch or fix that must be deployed immediately (e.g., “yesterday”) due to active exploitation or critical failure.

Emergency Change

Emergency Change — A high-priority change (often a critical patch) that bypasses standard timelines to be deployed immediately to mitigate active exploitation or severe risk.

Approval Process

Approval — A flexible process driven by the impact assessment, severity, and effort required. Minor changes may allow auto-approval, while major changes require multiple levels of approval signed in triplicate.

  • ⚠️ EXAM TIP: Approvals are not just required right before implementation; they may be required through multiple steps in the change management process.

Approval Boards

Board Acronym Focus Area
Change Control Board CCB Approves changes within specific projects.
Change Advisory Board CAB Approves changes related to the entire service lifecycle.
Emergency Change Advisory Board ECAB Focuses exclusively on emergency changes.

Build and Test

Build and Test — The step where changes (e.g., new software, patches, physical security systems like a new camera or front gate) are built and tested before deployment into the production environment.

Notification

Notification — Informing relevant stakeholders (system owners, management, administrators, customers, regulators) about a change.

  • ⚠️ EXAM TIP: Notifications occur throughout the entire process: before, possibly during, and after a change has been made.

Implement

Implement — The step where the actual change is executed and made in the environment.

Validation

Validation — Testing performed after implementation to ensure the change was successful and did not introduce new issues.

Validation Testing Types

Testing Type Purpose
Test New Functionality Validates that the new functionality the change was supposed to provide is working correctly.
Regression Testing Specifically validates that existing functionality was not broken by the implementation of the change.

Version and Baseline

Version and Baseline — The final step of updating organizational documentation and configurations post-change. This includes updating master images, configuration baselines, and disaster recovery plans (DRP).