Examkin

Question

Difficulty: Very hardChange Management and Security Impacts

An enterprise organization is migrating a monolithic legacy application to a cloud-native microservices architecture. To maintain security governance during continuous integration and continuous deployment (CI/CD) updates, the Security Advisory Board is revising the organization's change control procedures. Which of the following technical and procedural requirements must be integrated into the change management workflow to evaluate and mitigate security impacts effectively? (Select TWO.)

  1. Embedding automated static and dynamic security testing gates into the build pipeline to evaluate code changes before deployment approvalAnswer
  2. Establishing immutable baseline configuration repositories paired with automated drift detection to identify unauthorized system modificationsAnswer
  3. C
    Delegating emergency hotfix approval and implementation exclusively to software leads without requiring retrospective change advisory board documentation
  4. D
    Substituting pre-deployment vulnerability testing and change reviews with inline Web Application Firewall rule adjustments

Answer

The correct requirements are embedding automated static and dynamic security testing gates into the build pipeline and establishing immutable baseline configuration repositories paired with automated drift detection.
Integrating automated security testing gates directly into deployment pipelines ensures code changes undergo rigorous vulnerability evaluation prior to deployment, while maintaining immutable configuration baselines with automated drift detection guarantees that any unauthorized operational changes are identified and remediated promptly.

Step-by-Step Solution

1
Evaluate pre-implementation change validation controls for modern CI/CD software pipelines.
Integrating automated static (SAST) and dynamic (DAST) testing into pipeline build stages enforces mandatory security impact analysis prior to production promotion.
Pre-deployment automated testing prevents vulnerable or non-compliant code from reaching live environments without proper security assessment.
2
Evaluate post-implementation integrity controls and baseline maintenance requirements.
Configuring baseline repositories with automated drift detection continuously cross-checks active infrastructure state against approved change records.
Drift detection ensures all systems remain within authorized security postures and alerts administrators to out-of-band or malicious modifications.
3
Analyze incorrect procedural and technical shortcuts against change management principles.
Emergency changes still require retrospective Change Advisory Board (CAB) validation, and perimeter firewall rules cannot replace proper application patch and change testing.
Governance frameworks mandate full documentation of emergency workflows, while control selection must address root causes rather than applying external workarounds.

Key Concept

Change Management and Security Impacts
Rate this question

Topics

Change Management and Security Impacts

More questions from this topic