1.3 : Change Management

Question 1

Approval Process

Answer 1

The formal procedure to obtain authorization before implementing changes, ensuring that all changes are reviewed and approved by the appropriate parties.

Question 2

Ownership

Answer 2

Responsibility assigned to an individual or group to manage and oversee changes, ensuring accountability and proper implementation.

Question 3

Stakeholders

Answer 3

Individuals or groups who are affected by or have an interest in the change. They provide input and approval, ensuring that the change meets the needs of the organization.

Question 4

Impact Analysis

Answer 4

Assessing the potential effects of a change on systems, processes, and business operations. This helps in identifying risks and planning mitigations.

Question 5

Test Results

Answer 5

The outcomes of testing a change in a controlled environment to ensure it works as intended and does not introduce new issues.

Question 6

Backout Plan

Answer 6

A strategy for reverting a change if it causes unexpected problems, allowing systems to be restored to their original state.

Question 7

Maintenance Window

Answer 7

A scheduled time period during which systems can be taken offline or modified with minimal impact on business operations.

Question 8

Standard Operating Procedure (SOP)

Answer 8

A set of written instructions that describe the routine processes to be followed during change management, ensuring consistency and compliance.

Question 9

Allow Lists/Deny Lists

Answer 9

Lists that specify which entities (e.g., IP addresses, applications) are permitted or denied access to a resource, helping control security and traffic.

Question 10

Restricted Activities

Answer 10

Actions that are limited or prohibited during certain operations or times to reduce risk and maintain security.

Question 11

Downtime

Answer 11

The period when a system is unavailable, often due to maintenance or unexpected outages. Planning and minimizing downtime is crucial for maintaining service continuity.

Question 12

Service Restart

Answer 12

Rebooting or restarting a service as part of maintenance or after changes, ensuring that updates take effect or issues are resolved.

Question 13

Application Restart

Answer 13

Restarting an application to apply changes or updates, ensuring that new configurations are loaded and operational.

Question 14

Legacy Applications

Answer 14

Older software systems that may not be fully supported or compatible with newer technologies, requiring special considerations during changes.

Question 15

Dependencies

Answer 15

Interdependencies between systems or applications that must be considered during changes to prevent disruptions or failures.

Question 16

Updating Diagrams

Answer 16

Modifying network or system diagrams to reflect changes, ensuring that documentation is accurate and up to date.

Question 17

Updating Policies/Procedures

Answer 17

Revising organizational policies and procedures to incorporate changes, ensuring ongoing compliance and effective operation.

Question 18

Version Control

Answer 18

The process of managing changes to documents, configurations, and software, allowing for tracking of revisions and rollback if necessary.

Question 19

Change Management

Answer 19

Plans, implements, and monitors changes to protect organizations from unforseen consequences

Question 20

Technical Implications of Change Management

(List all)

Answer 20

• Allow lists/deny lists
• Restricted activities
• Downtime
• Service restart
• Application restart
• Legacy applications
• Dependencies