Level 6 · In practice

6.4Toolbox

Goal: have operational checklists reusable in daily work.

Estimated time: 10 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

Install clean: back up, install the OS, drivers and updates, standard account, licensed software, antivirus, encryption, verified restore.
Audit: tested backups, updates, MFA, unique passwords, least privilege, shares by need, up-to-date documentation.
Rule: a checklist ticked every time beats a method known by heart — on the day, you execute.

Sofiane’s thread — the sheets near the workstation

After a quarter, the sheets below stay near Sofiane’s workstation: the installation one displayed next to the screen, the audit one in his notebook. “What saves me,” he says in substance, “isn’t knowing the points, it’s ticking them every time — especially the day before an intervention at the client’s.”

Adapt the wording to your context, keep the structure: it’s what prevents oversights and incidents.

Ready-to-use references

A good checklist makes a task fast, repeatable and complete. Adapt it to your context, but keep the structure: it’s what protects.

Three key moments

An intervention plays out at three moments: install a clean workstation, audit the existing security, and handle an incident without improvising. Three sheets, three must-dos.

Tick, don’t recite

You no longer think under pressure: you execute the sheet near the workstation. What is ticked is done; what is assumed done isn’t.

Set up a workstation

Back up existing data
Install the OS (up-to-date media)
Drivers + full Windows Update
STANDARD user account (not admin)
Software with valid licenses; antivirus + firewall active
Disk encryption (laptops); restore the data and verify

Express security audit

Backups recent AND tested?
Updates current (OS + software)?
MFA active on all accounts?
Unique passwords (manager)?
Accounts on least privilege, admins separate?
Antivirus/firewall active; shares by need; documentation up to date?

Handle an incident end to end

Qualify: exact symptom, workstation/user, since when
Isolate if necessary (ransomware, compromised workstation) without shutting down
Diagnose from simple to complex, one change at a time
Fix and prove (retest, confirm with the user)
Restore if needed from a clean, disconnected backup
Log in the ticket + document the solution (knowledge base)

Common misinterpretation: “collecting checklists.” No. A checklist is useful only when ticked and used: take the one for your next intervention, the others will wait.

Text version of the diagram (SEO / screen readers / translation): 1) Set up a workstation — backup, up-to-date OS, drivers and updates, standard account, licensed software, antivirus/firewall, encryption, verified restore. 2) Audit security — tested backups, updates, MFA, unique passwords, least privilege, shares by need, documentation. 3) Handle an incident — qualify, isolate if needed, diagnose from simple to complex, prove, restore, log and document. Lesson: you no longer think under pressure, you execute the sheet.

Script ready to say — set up a clean workstation (30 s)

“Data backed up? Up-to-date OS? Drivers and updates? Standard account? Licensed software? Antivirus/firewall? Encryption? Data restored and verified? If any no, I fix it before returning the workstation.”

Keep this near the next workstation to prepare.

Script ready to say — handle an incident (30 s)

“I qualify, I isolate if needed without shutting down, I diagnose from simple to complex, one change at a time, I prove, I restore if necessary and I document.”

The last safety net before closing a ticket.

Copy-paste template — my checklists

[ ] Data backed up
[ ] OS + drivers + updates
[ ] STANDARD account (not admin)
[ ] Licensed software + antivirus/firewall
[ ] Encryption (laptops)
[ ] Data restored + verified
[ ] Security audit (MFA, privileges, shares)
[ ] Incident logged + documented

Copy-paste template — Windows workstation commands

systeminfo            -- system version and state
winget upgrade --all  -- update the software
manage-bde -status    -- BitLocker encryption
getmac                -- MAC address (DHCP reservation)

Very small business / small budget

Sheets on one page displayed on the wall: the essentials (clean workstation, tested backup, MFA, docs) are enough.

Algiers SME

Build the local realities into the sheets: network outages, a single Internet link, heterogeneous hardware, a known point of contact.

Remote / hybrid

Add a written-validation line to the follow-up: at a distance, a dated, ticked intervention avoids misunderstandings.

Intercultural

Make labels explicit in writing: what seems obvious (who validates, which format) isn’t for everyone.

Caution: Generic reminder: speed and confidence commit your reliability — tick every time “tested backup, standard account, MFA active, incident logged and documented”; keep no unnecessary data on the workstation.

48h challenge — apply it tomorrow

Take 1 real workstation, run the “Set up a workstation” checklist, then the “Express security audit,” and tick where it stands.

Section exit checklist

I ticked a checklist on a real workstation.
I can draw the installation sheet and the express audit.
I did the 48h challenge or scheduled its date.

Self-assessment 1-5: tooling of my interventions?dated use of the checklists?

← Previous : Best practices & pitfalls (V3)Next : Field feedback (V3) →

Check your understanding

Sofiane is setting up a workstation for a user. What must he tick as a priority?

💡

Tip: keep these checklists near the guide’s capstone project (the fleet of Sofiane’s SME).