The end of year IT checklist has one job: make sure the systems holding your business together can survive two or three weeks of Christmas shutdown with almost nobody watching them. Confirm backups, patch and reboot, lock down identities, and decide who answers the phone if something breaks.
Why the shutdown is a target, not a holiday
The Christmas-to-January window is one of the worst times of the year to get hit, and attackers know it. Offices are empty, the rostered skeleton crew is stretched thin, and the people who would normally spot something odd are at the beach. A ransomware crew that gets in on the 24th of December has a clear run until staff trickle back, and by the time anyone notices the encrypted files, the response is days late.
The Australian Cyber Security Centre (ACSC) has flagged this pattern: incident volumes climb around public holidays because response is slow. Attacks are no more sophisticated in December, the gap between compromise and detection just stretches from hours to weeks. A breach contained in an afternoon during business-as-usual becomes a disaster when the alert sits unread for a fortnight.
This collides with the right to disconnect, now in force under the Fair Work Act for businesses of every size. You cannot assume staff will check work email “just in case” over their leave. If you want someone reachable, that has to be a defined, paid on-call arrangement, not a vague hope. Plan around a genuine skeleton crew, where most of your people are legitimately off.
The pre-shutdown checklist
Work through this in the last week before everyone downs tools. Most of it is an hour or two of effort, and the difference between a quiet break and a January spent rebuilding.
Confirm backups and run a restore test
A backup that has never been restored is a hope, not a safeguard. Before the shutdown, check every critical system is backing up successfully, then prove it by restoring something, a folder, a mailbox, a VM, to confirm the data comes back clean. Plenty of businesses discover their backups have been silently failing only when they finally need them.
If you run Microsoft 365, remember Microsoft does not back it up for you, you need a third-party backup of Exchange, SharePoint and OneDrive. Confirm that is running too. A holiday outage tests both halves of your recovery objectives at once, how much data you can lose, and how long you can survive without systems. If you have never set your RTO and RPO, now is the prompt.
Patch, then reboot
Apply outstanding updates to servers, workstations and network gear before the break, then reboot so the patches take effect, half-applied updates waiting on a restart are a common cause of machines coming back wrong in January. Pay particular attention to firewalls, VPN appliances and anything internet-facing: an unpatched edge device is the most common way in during a quiet period.
Lock down identity with MFA and conditional access
Identity is the front door, and over the shutdown it should be bolted. Confirm multi-factor authentication is enforced on every account, with no exceptions sitting in a “we’ll fix it later” pile. Then tighten conditional access policies so sign-ins from unexpected countries, unmanaged devices or impossible-travel scenarios are blocked or challenged. With your team in Melbourne and on leave, a login from overseas at 3am is exactly what you want to catch.
Secure the accounts of departing staff
End of year is when a lot of people finish up. Any account belonging to someone who has left should be disabled, its sessions revoked and its access removed before the office closes. A live account with no human attached is pure risk over a three-week shutdown nobody is watching. Do the same for departing contractors and temporary staff.
Review remote access
If people will work remotely during the quieter weeks, make sure that access is secured, MFA on the VPN, or better, modern access without a legacy VPN at all. Just as importantly, switch off access that is not needed: every open door is one more thing to monitor when almost no one is. Disable old RDP exposure, retire unused VPN accounts, and cut the attack surface to what is genuinely required.
Brief staff on holiday-season scams
The festive season is prime time for phishing, gift-card scams and business email compromise (BEC). The classic play lands hardest now: a fake message “from the boss”, conveniently unreachable on leave, asking an employee to urgently buy gift cards or redirect a supplier’s bank details before everyone clocks off. With managers away, these attacks have a far higher hit rate.
A short reminder before the break works: no legitimate request to buy gift cards or redirect a payment comes by email alone, and any bank-detail change must be verified by phoning a known number, never the one in the email. We cover this in our guide to phishing and BEC.
Physical security and the building itself
Cyber is not the whole story, an empty office is a physical target too. Before you lock up:
- Server room and comms cabinets, locked, not propped open “for ventilation”, with cooling confirmed to keep running.
- UPS units, test that the battery backup holds, so a holiday power cut doesn’t drop your servers hard. Replace tired batteries before, not after.
- Doors, alarms and cameras, armed, working, and with someone nominated to respond to an alarm callout.
- Loose hardware, laptops and portable devices secured away, not left on desks in view of a window.
Confirm alerting and monitoring still reach a human
This is the one people forget. Your monitoring tools keep generating alerts over the shutdown, but if they land in the inbox of someone on leave, they may as well not exist. Confirm critical alerts route to whoever is on call, and that the person knows it and has the access to act. A SIEM that detects an intrusion on Boxing Day is worthless if the alert sits unread until January, the gap a managed security operations centre exists to close, because a 24/7 SOC does not take Christmas off.
Power down or leave running?
The last decision is what to physically switch off. Shutting everything down to save power is fine for some equipment and dangerous for others:
| Equipment | Decision | Why |
|---|---|---|
| Servers, NAS, domain controllers | Leave running | Backups, sync and remote access depend on them; cold-starting old hardware is when disks fail. |
| Firewall, switches, Wi-Fi, modem | Leave running | Needed for monitoring, alerting and any remote work over the break. |
| Individual workstations and monitors | Power down | No reason to run; saves power and removes idle endpoints from the network. |
| Desk phones, printers, peripherals | Power down | Not needed while the office is empty. |
Leave the infrastructure that keeps you protected and recoverable running; switch off the user-facing kit that sits idle. If you are unsure whether a machine is load-bearing, ask your IT provider first.
How a shutdown goes wrong: an illustrative example
Picture a mid-sized logistics firm that locks up on the 23rd with backups it assumes are fine and alerts routing to a manager who is, sensibly, off the grid for a fortnight. A workstation left on is compromised through an unpatched application, generating alerts into an inbox nobody opens until January. By then the attacker has been moving through the network for over a week. This is the pattern in most of the holiday-period incidents reported publicly, and it is entirely avoidable.
The fix afterwards is unremarkable: MFA everywhere, alerts routed to a desk that is actually monitored, idle endpoints powered down, and a verified restore test before any future shutdown. The lesson is that an empty office without monitoring is not “closed”. It is unguarded.
The January re-opening checklist
Coming back is shorter, but skipping it causes its own mess:
- Apply and reboot, install updates that landed over the break and restart machines that were powered down.
- Review the logs, check sign-in logs, alerts and security events from across the shutdown for anything that slipped through.
- Confirm backups ran, verify the jobs kept running over the whole break, not just up to the day you left.
- Re-enable what you switched off, bring remote access and disabled services back only where genuinely needed.
- Re-brief on scams, January is still high season for BEC.
Frequently asked questions
Should we shut down our servers over the Christmas break?
Generally no. Servers, network gear and anything your backups, monitoring or remote access depend on should stay running. Powering them down removes the protection you need most while the office is empty, and cold-starting older hardware after weeks off is a common failure point. Power down idle workstations instead.
Why is the holiday period higher risk for cyber attacks?
Because detection and response slow to a crawl. An empty office means alerts go unread, the skeleton crew is stretched, and an intruder can move through your network for weeks before anyone notices. The attack is no cleverer in December, the danger is the time it takes you to spot it.
Do we need someone on call during the shutdown?
If you have systems that must keep running, yes, but make it a defined, paid on-call arrangement, not an assumption that staff will check email on leave. The right to disconnect now applies to all businesses. For many, the cleaner option is routing critical alerts to a managed SOC.
Where TechAssist fits
We are a Melbourne MSP, founded in 2014, with 13 Melbourne-employed staff and no offshore call centre. Our NOC runs from Tecoma and our 24/7 on-call and emergency support does not close for the holidays. That matters in late December, when an attacker is counting on no one being there to read the alert.
If you want your shutdown handled properly this year, with backups verified, identity locked down and monitoring routed to a desk that is actually staffed, that is core managed IT and cyber security work for us. Get in touch before the office empties out, and take your own break knowing the lights are still on where they count.