What is secure configuration management and why is baseline configuration important?

What is secure configuration management and why is baseline configuration important?

• A. Keeping systems configured securely; baseline ensures consistent secure settings and reduces drift.
• B. Keeping systems configured securely; baseline ensures consistent secure settings and reduces drift.
• C. Randomly changing system settings to test responses.
• D. Baseline configuration is optional and not needed.

Answer: (B)

Secure configuration management is about keeping systems configured in a secure, consistently approved state. The baseline configuration is the officially documented and hardened set of settings that define how every system should be configured. Why this matters: using a baseline gives you a known good reference to compare against, so you can quickly spot and correct deviations that creep in over time. This reduces configuration drift, ensures uniform security controls across all assets, and makes automated deployment and compliance checks reliable. When changes happen—patches, software installs, or admin edits—the baseline provides a stable point to measure against and remediate back to a secure state. The other ideas don’t fit this approach: randomly changing settings to test responses isn’t a manages-security practice and would increase risk, while treating baseline configuration as optional misses the fundamental goal of maintaining a secure, predictable environment.

Secure configuration management is about keeping systems configured in a secure, consistently approved state. The baseline configuration is the officially documented and hardened set of settings that define how every system should be configured. Why this matters: using a baseline gives you a known good reference to compare against, so you can quickly spot and correct deviations that creep in over time. This reduces configuration drift, ensures uniform security controls across all assets, and makes automated deployment and compliance checks reliable. When changes happen—patches, software installs, or admin edits—the baseline provides a stable point to measure against and remediate back to a secure state.

The other ideas don’t fit this approach: randomly changing settings to test responses isn’t a manages-security practice and would increase risk, while treating baseline configuration as optional misses the fundamental goal of maintaining a secure, predictable environment.