Study guide
3.3 Support and Implement the Change Management Lifecycle
ISC2 Systems Security Certified Practitioner SSCP
Track your progress as you read
Finished sections get a check mark.
1 Introduction and Exam Overview
1.1 Current Exam Facts 1.2 Computerized Adaptive Testing, Scoring, and Retakes 1.3 Eligibility, Associate Pathway, Endorsement, and Maintenance
2 Ethics and Security Concepts
2.1 Comply with Codes of Ethics 2.2 Understand Security Concepts 2.3 Identify and Implement Security Controls
3 Functional Controls, Assets, and Change Management
3.1 Document and Maintain Functional Security Controls 3.2 Support and Implement the Asset Management Lifecycle 3.3 Support and Implement the Change Management Lifecycle
4 Security Awareness and Physical Security Operations
4.1 Support and Implement Security Awareness and Training 4.2 Collaborate with Physical Security Operations
5 Authentication Methods and Trust Architectures
5.1 Implement and Maintain Authentication Methods 5.2 Federated Access with OAuth2, SAML, and OpenID Connect 5.3 Understand and Support Internetwork Trust Architectures
6 Identity Lifecycle and Access Control Models
6.1 Support and Implement the Identity Management Lifecycle 6.2 Mandatory, Discretionary, and Role-Based Access Control 6.3 Rule-Based, Attribute-Based, and Privileged Access Management
7 Risk Management, Visibility, and Legal Concerns
7.1 Risk Management Concepts and Treatment 7.2 Risk Visibility, Reporting, and Threat Intelligence 7.3 Legal and Regulatory Concerns
8 Assessments, Monitoring, and Analysis
8.1 Security Assessments and Vulnerability Management 8.2 Operate and Monitor Security Platforms 8.3 Analyze Monitoring Results
9 Incident Response and Forensic Investigations
9.1 Incident Response: Preparation, Detection, Analysis, and Escalation 9.2 Containment, Eradication, Recovery, and Lessons Learned 9.3 Understand and Support Forensic Investigations
10 Business Continuity and Disaster Recovery
10.1 Business Continuity and Emergency Response 10.2 Disaster Recovery and Restoration Metrics 10.3 Backup, Redundancy, Testing, and Drills
11 Cryptography Foundations
11.1 Reasons and Requirements for Cryptography 11.2 Hashing, Salting, Symmetric, Asymmetric, and ECC 11.3 Digital Signatures, HMAC, Algorithm Strength, and Cryptanalysis
12 Secure Protocols and Public Key Infrastructure
12.1 Understand and Implement Secure Protocols 12.2 Understand Public Key Infrastructure
13 Networking Fundamentals, Attacks, and Access Controls
13.1 Understand and Apply Fundamental Concepts of Networking 13.2 Understand Network Attacks and Countermeasures 13.3 Manage Network Access Controls
14 Network Security Operations, Wireless, and IoT
14.1 Manage Network Security 14.2 Operate and Configure Network-Based Security Appliances and Services 14.3 Secure Wireless Communications 14.4 Secure and Monitor Internet of Things
15 Malware, Malicious Activity, and Endpoint Security
15.1 Identify and Analyze Malicious Code 15.2 Malicious Activity, Social Engineering, and Behavior Analytics 15.3 Implement and Operate Endpoint Device Security
16 Mobile, Cloud, and Virtual Environments
16.1 Administer and Manage Mobile Devices 16.2 Cloud Security: Deployment, Service Models, and Shared Responsibility 16.3 Cloud Legal, Regulatory, and Third-Party Requirements 16.4 Operate and Maintain Secure Virtual Environments
3.3 Support and Implement the Change Management Lifecycle
Key Takeaways Explain This Topic AI
Standard changes are pre-approved and low risk; normal changes go through the change advisory board after security impact analysis; emergency changes use expedited authorization but are still documented and audited.
The SSCP's core change task is security impact analysis: how the change affects confidentiality, integrity, availability, authentication, logging, and exposure.
Configuration management maintains known-good baselines for configuration items; change management is the process that modifies those baselines.
Unauthorized change — production that differs from baseline with no request for change — is an event of interest and must be investigated.
Roles (requester, implementer, change manager, change advisory board, asset owner, security, audit) and communications must be defined, or emergency work becomes untraceable.
Last updated: August 2026
Support and Implement the Change Management Lifecycle
SSCP Knowledge Area 1.6 asks you to support and/or implement the change management lifecycle . In operations, an untracked change is one of the most common ways preventative controls silently die: someone opens a firewall port "for the weekend," a sysadmin disables a SIEM forwarder to quiet an alert, or a vendor tunes a cipher suite at 03:00. Domain 3 later treats unauthorized change as an event of interest . Domain 1 is where you learn the process that should have produced an authorized one.
Change management is the process that reviews, approves, communicates, implements, and audits modifications. Configuration management (CM) is the state : known-good baselines for configuration items (CIs) . You need both. A perfect asset register with no change process still drifts. A busy change advisory board (CAB) with no baseline cannot tell authorized work from tampering.
Roles, Responsibilities, Processes, Communications, and Audit
Write roles down before the 02:00 outage, not during it.
- Role Responsibility
- Change requester Submits the request for change (RFC) with business reason, affected CIs, and desired window
- Implementer (often the sysadmin) Builds, tests, executes, and is ready to back out
- Change manager Owns the process, calendar, and collision detection
CAB Reviews risk, scheduling conflicts, and security findings; includes security, operations, and business voices
- Asset owner Accepts residual risk if the change proceeds with findings
- Security practitioner (SSCP) Performs or reviews security impact analysis (SIA)
- Service desk / communications Tells users what will break and when
- Audit Samples completed RFCs against production and the baseline
The process is predictable: request, classify, analyze impact (including SIA), approve or reject, schedule and communicate, implement with a backout plan, verify, close, and audit. If your organization uses an Information Technology Infrastructure Library (ITIL)-style tool, the SSCP still cares about the same bones — the exam will not require a specific vendor workflow.
Communications are a control. A silent firewall change that blocks a hospital interface is an availability incident even if the packet-filter logic is "more secure." Notify stakeholders, record the window, and say how to escalate if the change fails.
Audit closes the loop: sample emergency changes, look for implementers who approve their own work, and compare the configuration baseline to reality. Segregation of duties still applies — the person who codes the firewall rule should not be the only person who marks the RFC approved.
Standard, Normal, and Emergency Changes
Classify by risk and predictability, not by how impatient the requester is.
Type When you use it Approval Example
Standard Low risk, well-known, already documented in a catalog Pre-approved; still logged Create a user mailbox from the approved template; restart a service on a published schedule
Normal Not pre-approved; medium or high risk; needs analysis CAB (or delegated change authority) after SIA Open a new inbound Transmission Control Protocol (TCP) port; change a production Transport Layer Security (TLS) cipher suite; deploy a new microservice
Emergency Immediate threat to confidentiality, integrity, or availability, or a major outage Expedited / emergency CAB; implement fast, document fully , review after Vendor hotfix on a downed payments database at 02:10; block a mass-exploit Internet Protocol (IP) address at the edge
Standard does not mean "small enough that we skip the ticket." It means the organization already assessed that this procedure is low risk and pre-authorized. Weekend vendor Remote Desktop from the internet is not a standard change just because it is temporary.
Emergency is not a free pass. The database administrator who applies an unlisted hotfix at 02:10 to restore service is in the emergency path: expedited authorization (even a recorded bridge approval), a backout idea, and an RFC filed when the smoke clears so SIA and audit can catch up. "We will mention it on Monday" is unauthorized change.
Normal is the default for anything that alters exposure, authentication, logging, or a production baseline.
Security Impact Analysis
Security impact analysis is the SSCP-specific heart of this knowledge area. For each proposed change, ask:
Does it weaken confidentiality, integrity, or availability ?
Does it add or remove authentication, multi-factor authentication (MFA) , encryption, or logging?
Does it change network exposure (new port, new peer, public object storage, flattened segment)?
Does it affect a regulated data set (protected health information, personally identifiable information, payment data)?
Are compensating controls needed if a preventative control will be temporarily removed?
What is the backout, and does backout itself have security impact?
Scenario. A product manager pings the sysadmin: "Open TCP 3389 from the internet to the jump host just for this weekend so a vendor can debug." SIA says you are exposing Remote Desktop to the world, punching a hole in a preventative firewall control, and creating an audit gap if the rule is forgotten. The SSCP's answer is an RFC (normal, or emergency only if production is already failing), compensating controls if the business insists (time-bound rule, virtual private network (VPN) instead of raw 3389, MFA, session recording, automatic expiry), and a backout that deletes the rule. Chat messages are not CAB approval.
SIA is required even when the change "only" updates a library. Dependency changes can introduce known exploited vulnerabilities or license conflict — that is why asset inventory and change management meet.
Configuration Management
CM identifies configuration items , records their attributes, and protects a baseline — the known-good state. Baselines include operating-system gold images, infrastructure as code, firewall policy revisions, and container manifests. Tools vary; the idea does not. Infrastructure as code (IaC) is simply a machine-readable baseline you can review in the same RFC as any other change.
When a change is approved and implemented, update the baseline . If you do not, the next drift report will flag a legitimate change as rogue, or worse, a rogue change will look legitimate.
Unauthorized change — production differs from baseline with no RFC — is an event of interest . Treat it like an anomaly in Domain 3: investigate, determine whether it was malicious, sloppy, or an undocumented emergency, and either roll back or ratify through the process.
Scenario. Security operations center (SOC) analysts see a production web server's TLS cipher suite change at 03:14 with no matching RFC. The baseline still lists the old suite. That is not nightly maintenance. It is unauthorized change. Pull change tickets, admin logs, and who had privileged access. If it was a vendor "optimization," it still needed a change record. If it was an attacker disabling strong ciphers, you are in incident response.
Putting the Lifecycle Together
A healthy operations team can answer four questions for any production delta: Who requested it? Who approved it after SIA? What baseline did it move from and to? Who verified it and told the users? If any answer is "we are not sure," the change-management lifecycle is not implemented — it is a slide in a policy deck.
SSCPs rarely chair the CAB, but they are the people who notice that a "standard" catalog item now includes a new internet port, that an emergency change from last week never received a post-implementation SIA, or that configuration drift on a jump host matches no ticket. That is Domain 1 work, and it is how preventative controls stay preventative after the change window closes.