How is patch management handled in FOSSE to minimize risk?

• A. Patch during production hours only
• B. Timely patching after change window, test in non-prod, backout plan, rollback, verification
• C. Never patch
• D. Patch immediately with no testing

Answer: (B)

A controlled, risk-aware patch management process is essential. The best approach combines timely patching within a planned change window with thorough testing in a non-production environment, followed by a backout or rollback plan and post-deployment verification. Patching after a scheduled window minimizes disruption to users, while testing in non-prod helps catch compatibility or performance issues before they reach production. A backout or rollback plan provides a safe exit if the patch creates problems, preserving service continuity. Verification after deployment confirms that the patch is applied correctly and that systems continue to operate as expected.

Disrupting production hours can cause user impact and makes immediate rollback harder. Patching without testing leaves unknown risks that could destabilize services. And never patching leaves known vulnerabilities unaddressed.