Section: INCIDENT MANAGEMENT AND RESPONSE

Explanation
Security procedures often have to change frequently to keep up with changes in software. Since a procedure is a how-to document, it must be kept up-to-date with frequent changes in software. A security standard such as platform baselines - defines behavioral limits, not the how-to process; it should not change frequently.
High-level objectives of an organization, such as security governance, would normally be addressed in a security policy.

Section: INFORMATION SECURITY PROGRAM DEVELOPMENT
Explanation:
Since the operating system (OS) patch will adversely impact a critical application, a mitigating control should be identified that will provide an equivalent level of security. Since the application is critical, the patch should not be applied without regard for the application; business requirements must be considered.
Altering the OS patch to allow the application to run in a privileged state may create new security weaknesses. Finally, running a production application on a test platform is not an acceptable alternative since it will mean running a critical production application on a platform not subject to the same level of security controls.

Section: INFORMATION SECURITY PROGRAM MANAGEMENT