Lesson 4: Security, Recovery, and Verification

Core path: 42 minutes

A system is not finished because the seeded faults are gone.

Today you prove the Harborview environment meets the client requirements after your changes.

Part 1: account and access review

Verify the target state for:

• standard-user daily accounts;
• approved administrative support path;
• MFA on staff/cloud identities;
• screen lock/session protection;
• no unnecessary guest/unused accounts;
• least-privilege access to shared resources.

Do not collect user passwords as evidence.

Part 2: endpoint and network security review

Check the supplied state for:

• host firewall enabled;
• endpoint protection enabled/current;
• OS/application updates current under the scenario;
• approved software sources;
• secure wireless configuration;
• appropriate network profile/sharing settings;
• approved remote-support path only;
• disk/data protection where required.

A security control is not successful if the technician had to permanently disable it to make the system work.

Part 3: printer, mobile, and data handling

Verify:

• correct printer queue/driver path;
• secure printer/scan configuration where required;
• managed mobile device remains under approved policy;
• mobile sync/app state meets client requirements;
• service records contain no passwords or unnecessary sensitive data;
• retired/replaced media would follow approved sanitization/disposal procedures.

Part 4: backup and recovery verification

Review the client backup plan.

A backup status of "successful" is not enough by itself.

Using the supplied recovery scenario, document:

asset/data protected:
backup method/destination:
latest successful backup evidence:
restore test performed:
restored item/state:
verification result:
remaining recovery risk:

If a snapshot exists only on the same failed storage device, do not call it an independent backup.

Part 5: functional verification

Create a final verification checklist covering the actual client workflows:

• all required workstations boot normally;
• required displays/input/peripherals work;
• wired desktops receive correct network configuration;
• staff/mobile Wi-Fi works as intended;
• DNS/name-based service access works;
• browser/cloud productivity access works;
• video meeting capability works on required seats;
• printer output works from the required workstation(s);
• scan workflow works as required;
• mobile sync works under approved policy;
• local practice VM behaves according to its intended network mode;
• endpoint/security controls remain enabled;
• backup/restore verification is complete.

Part 6: unresolved risk and escalation

Not every issue should be "fixed" by a student technician.

Record anything that requires:

• vendor support;
• administrator approval;
• hardware replacement;
• security escalation;
• policy decision;
• additional budget;
• future maintenance window.

Use this structure:

remaining issue/risk:
impact:
current evidence:
why not resolved here:
recommended next owner:
next action:

Student action

Submit the security, recovery, and final verification packet with before/after evidence where available.

Success criteria

You pass when the final environment is not merely "working" but verified against the client requirements, protected by the required controls, recoverable under the supplied test, and honest about anything still unresolved.