Patching, Configuration, and Least Privilege
- Explain vulnerability reduction through secure configuration
- Apply the idea to evidence from a realistic technology scenario
- Justify a decision using security, reliability, cost, and user impact
Patching, Configuration, and Least Privilege
Hardening reduces opportunities for misuse: patch known flaws, disable unnecessary services, remove default credentials, enforce secure configuration, and grant only the privileges required. Least privilege limits both accidental damage and what malware can do after compromise.
Decision lens
Strong technical decisions connect evidence → mechanism → impact → response. Identify what the evidence shows, explain the system behavior that produced it, state the likely effect on people or data, and choose a response that addresses the cause without creating unnecessary disruption.
A kiosk application runs under a local administrator account and the operating system is six months behind on security updates.
- 1.The excessive privilege increases the impact of any exploit.
- 2.Missing patches increase likelihood when known vulnerabilities exist.
- 3.Run the kiosk with a restricted account and an allowlist.
- 4.Test and deploy updates through a managed patch process.
Which is an example of least privilege?
Which response best demonstrates complete reasoning about vulnerability reduction through secure configuration?
For a scenario about vulnerability reduction through secure configuration, identify the decisive evidence before naming a response. A defensible conclusion here is: Reduce privilege and patch exposure; either control alone leaves a major part of the risk untreated.
Answer the 2 checkpoints as you read.
Sign in to save your progress