A systems technician is tasked with re-hardening a company laptop that was recently returned from a high-risk remote assignment before allowing it back onto the internal corporate network. Arrange the following workstation hardening and remediation steps in the correct procedural sequence from first to last.
- 1Disconnect all physical and wireless network interfaces to isolate the device.
- 2Boot the system using a trusted external rescue disk to perform an offline malware scan.
- 3Disable the built-in Guest account and unbind non-essential network protocol bindings and services.
- 4Configure Local Security Policy to enforce password-protected screen saver locks and disable AutoPlay/AutoRun.
- 5Connect the workstation to a restricted remediation VLAN to apply system updates and patch definitions.
Cevap
The correct sequence for re-hardening the remote workstation is: 1) Disconnect all physical and wireless network interfaces to isolate the device, 2) Boot the system using a trusted external rescue disk to perform an offline malware scan, 3) Disable the built-in Guest account and unbind non-essential network protocol bindings and services, 4) Configure Local Security Policy to enforce password-protected screen saver locks and disable AutoPlay/AutoRun, and 5) Connect the workstation to a restricted remediation VLAN to apply system updates and patch definitions.
Hardening a returning untrusted endpoint must always follow a defense-in-depth sequence: Isolation → Verification/Cleaning → OS Baseline Reduction → Policy Enforcement → Segregated Updating. Isolating network access first prevents threat proliferation. Offline scanning verifies system integrity. Disabling unused accounts and services reduces attack surface. Enforcing Local Security Policy ensures endpoint operational security, and using a segregated remediation VLAN allows patching without exposing production assets.
Adım Adım Çözüm
Anahtar Kavram
Workstation Hardening and Incident Remediation Lifecycle