CC ยท Asset protection and security testing
Configuration and change management
Baselines, hardening, patching and the request, approve, test, implement, document change process.
Key points
- A baseline is an agreed, reviewed set of settings for a system, and it changes only through change control.
- Hardening removes unneeded services and weak defaults.
- Patching fixes known flaws.
- Every change follows a process: request, approval, testing, implementation, documentation, so that nothing unreviewed reaches production.
Source: https://csrc.nist.gov/glossary/term/baseline_configuration
Practice questions
What is a security baseline?
- An approved reference configuration systems are built and checked against
- The output of the last vulnerability scan
- A log of every past security incident
- The maximum budget for security tools
Show answer
Answer: A. An approved reference configuration systems are built and checked against
A baseline is the approved reference configuration against which systems are built and checked. It is not a one-time scan result, an incident log or a price list.
Which actions are typical system hardening steps?
- Disable unused services and ports
- Change default credentials
- Share one admin password across all servers
- Leave sample accounts enabled for convenience
- Remove unneeded software
Show answer
Answer: A. Disable unused services and ports, B. Change default credentials, E. Remove unneeded software
Hardening shrinks the attack surface: disable what is not needed and replace weak defaults. Sharing admin passwords and leaving defaults on do the opposite.
True or false: a patch should be rolled out straight to all production systems because vendors already tested it.
Show answer
Answer: False
False. Vendor testing cannot cover your environment, so patches are tested first (and rolled out in stages) to catch breakage.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
