How should patch management be conducted in AFCOMAC networks to balance security with mission continuity?

How should patch management be conducted in AFCOMAC networks to balance security with mission continuity?

• A. Patch immediately on every system without testing.
• B. Patch only on weekend maintenance windows.
• C. Avoid patching altogether.
• D. Establish a risk-based patching schedule, test patches in a lab, maintain rollback plans, and coordinate with operators to minimize downtime during critical missions.

Answer: (D)

In AFCOMAC networks, patch management should balance security with mission continuity by applying patches in a controlled, risk-aware process. A risk-based schedule focuses on the most vulnerable and mission-critical systems first, so security improvements happen where they matter most without unnecessary disruption. Testing patches in a lab environment helps verify compatibility with mission-critical applications and configurations, reducing the chance a patch causes unintended failures in live operations. Having rollback plans in place means you can quickly revert if a patch creates issues, keeping downtime to a minimum. Coordinating with operators to schedule updates during appropriate maintenance windows minimizes impact on critical missions, preserving operational readiness while closing security gaps. Patching without testing can cause outages, patching only on weekends may miss urgent vulnerabilities, and avoiding patches altogether leaves systems exposed.

In AFCOMAC networks, patch management should balance security with mission continuity by applying patches in a controlled, risk-aware process. A risk-based schedule focuses on the most vulnerable and mission-critical systems first, so security improvements happen where they matter most without unnecessary disruption. Testing patches in a lab environment helps verify compatibility with mission-critical applications and configurations, reducing the chance a patch causes unintended failures in live operations. Having rollback plans in place means you can quickly revert if a patch creates issues, keeping downtime to a minimum. Coordinating with operators to schedule updates during appropriate maintenance windows minimizes impact on critical missions, preserving operational readiness while closing security gaps. Patching without testing can cause outages, patching only on weekends may miss urgent vulnerabilities, and avoiding patches altogether leaves systems exposed.