Technical Anshu
Tutorials Blog
Monthly Routine

Monthly IT Security Checklist for Small Office Owners One Hour Routine

Security that depends on remembering everything fails. Security on a calendar works. This one-hour monthly routine keeps all four layers honest - and produces the proof that you checked.

By Technical AnshuWindows 10 / 11Small Office IT
Watch the complete IT security setup in the video - all four layers shown step by step

The four-layer setup is not finished when it is installed; it is finished when it is checked on a schedule. Firewalls get new rules, PCs stop reporting, backup jobs silently fail, staff leave and take their accounts with them - unless someone looks. This page is that look: a one-hour monthly routine an office owner or IT person can run end to end, in order, with a one-page record each month. Print it. Use it. File it.

MONTHLY SECURITY CHECK - ONE PAGE RECORD
Month: __________ Checked by: ____________ [ ] Firewall firmware current, rules reviewed, no new forwards [ ] Patch report: every PC reported within 7 days, none critical-missing [ ] Antivirus: all PCs green, definitions current, no expired trials [ ] Backup: jobs succeeded all month Last restore test: files opened OK [ ] Accounts: leavers disabled, MFA still on for email/VPN/backup [ ] Passwords: no new shared notes, password manager in use [ ] One thing to fix next month: ______________________________ Time taken: ~55 minutes Signature: ____________
Example record page - tick, note, sign, file. Twelve of these a year is your evidence the system is alive, and your early warning when something starts slipping.
1

First 15 Minutes - The Door and the Fleet

Start at the perimeter. Log in to the firewall: confirm the firmware is current, scan the rule list for anything added since last month, and verify no port forwarding appeared (a well-meaning staff member enabling remote access is a classic). Then open the endpoint console and sort by last-report date. Any PC silent over 7 days is this month's first fix. Confirm the patch summary shows no machine missing critical updates.

  1. Firewall firmware updated or confirmed current
  2. Port-forward and remote-access rules match your written list - no surprises
  3. Every PC reported to the console within the last 7 days
  4. Critical patches applied fleet-wide; stragglers named and scheduled
2

Next 15 Minutes - Antivirus and Backup Jobs

Open the antivirus console (or spot-check PCs if you run Defender without one): every machine green, definitions dated this week, no expired trial products sitting registered. Then the backup console: every scheduled job showing success for the full month - and read the actual log, not just the green icon, at least once. A month of quiet failures discovered today is a save; discovered during ransomware is a loss.

  1. Antivirus status green on every PC; alerts from the month reviewed
  2. Backup jobs succeeded; failures investigated, not just acknowledged
  3. Offline drive rotation actually happened - check the label dates
3

Next 20 Minutes - The Restore Test

The heart of the routine, and the step that must never be skipped two months in a row. Restore real data and open it: a recent accounts file, a folder of documents, one application dataset. Restore to a test location, open the files, confirm the data is recent and complete, then note the result on the record page. Once or twice a year, extend this to a full server-image restore onto spare hardware or a virtual machine.

  1. Pick files at random - not the same sample every month
  2. Confirm restored files open and contain this month's data
  3. Record the result and the time the restore took - that number is your recovery estimate
4

Final 10 Minutes - Accounts and the Fix List

Close with people. Compare the staff list with active accounts: anyone who left is disabled everywhere - Windows, email, VPN, applications. Confirm MFA is still enforced on email, VPN, backup and firewall logins; settings drift too. Then write the single most important fix for next month at the bottom of the page. One fix a month, every month, is twelve real improvements a year - that is how small offices quietly become hard targets.

Honest line: a month will come when the routine slips - a festival rush, a busy season. Do not fake the ticks. A skipped month recorded honestly still protects you; a forged checklist discovered after an incident protects no one and fools exactly one person - you.

Watch the Full Video

See the complete security setup live - firewall, endpoint, antivirus and backup, all in one video.

Watch Full Video
Common Questions (FAQ)

Who should run this checklist - the owner or the IT person?

Either works; what matters is that it is one named person and a backup person who can cover absence. In many small offices the owner reviews the one-page record while the IT person performs the checks.

One hour seems short for all this. Is it realistic?

Yes, once the four layers are set up - the routine is verification, not installation. Most items are a console glance. The restore test is the longest part, and it is also the one that proves the whole system.

What should we do with the completed checklists?

File them by month. They are your trend record (which PC keeps failing, how restore times change) and, if an incident ever reaches insurance or a client audit, they are evidence of due care.

This guide is based on the Complete IT Security Setup video by Technical Anshu - stuck on any step, ask in the video comments and you will get a reply.