Question

Difficulty: EasyPatch and Configuration Management

A security administrator needs to apply a critical security update to enterprise web servers. What is the correct sequence of steps the administrator should follow to complete the patch management workflow?

  1. 1Identify and acquire the security patch from a verified vendor source.
  2. 2Validate and test the security patch in a non-production staging environment.
  3. 3Submit a change request for review and approval by the Change Advisory Board (CAB).
  4. 4Deploy the patch to production servers during an authorized maintenance window.

Answer

The correct sequence for the patch management process is: 1) Identify and acquire the security patch, 2) Validate and test the patch in a non-production staging environment, 3) Submit a change request for approval by the Change Advisory Board, and 4) Deploy the patch to production servers.
The standard enterprise patch management lifecycle progresses logically from patch discovery and acquisition, to non-production staging validation, followed by formal governance approval from the Change Advisory Board, and concluding with scheduled deployment to production systems.

Step-by-Step Solution

1
Identify and acquire the security patch from a verified vendor source.
The authentic security update is retrieved and verified.
You must obtain and verify the update before testing or scheduling deployment.
2
Validate and test the security patch in a non-production staging environment.
Patch stability, performance impact, and compatibility are verified.
Staging validation detects software conflicts without jeopardizing live production services.
3
Submit a change request for review and approval by the Change Advisory Board (CAB).
Formal authorization and back-out plans are officially documented and approved.
Enterprise change governance requires technical test evidence before approving live modifications.
4
Deploy the patch to production servers during an authorized maintenance window.
Production systems are updated with minimal disruption to users.
Deployment occurs only after validation and governance requirements are fully satisfied.

Key Concept

Standard Enterprise Patch Management Lifecycle
Rate this question