During a routine vulnerability audit, a security analyst discovers that multiple cloud virtual machines provisioned via Infrastructure as Code (IaC) templates are running outdated OS software packages vulnerable to remote code execution. Manually logging into each running instance to apply software patches resolves the vulnerability temporarily, but subsequent automated orchestration runs overwrite the manual patches, reverting systems to the vulnerable state. Which of the following operational procedures should the analyst implement to permanently remediate the vulnerability without introducing configuration drift?
- Update the baseline golden image and IaC repository templates with the patched package versions, then redeploy the virtual machine instances through the CI/CD pipeline.Answer
- BDeploy network-level intrusion prevention system (IPS) rules to block traffic targeting the vulnerable package while leaving running host configurations untouched.
- CDisable automated configuration state reconciliation on the orchestration server for the affected instances after manually applying the patch.
- DReclassify the vulnerability severity level in the centralized SIEM log management platform to exclude automated patch alerts.
Answer
Update the baseline golden image and Infrastructure as Code (IaC) repository templates, followed by redeploying the instances using the automated CI/CD pipeline.
In automated and Infrastructure as Code (IaC) environments, system configurations are driven by centralized baselines and golden images. Updating the underlying IaC code and base images ensures that patches are built into the source of truth, allowing automated CI/CD pipelines to deploy compliant, non-drifting instances.
Step-by-Step Solution
Key Concept
Configuration Drift and Immutable Infrastructure Patch Management
Estimated Time:2m 0s