1. Keep encrypted backups and test them.
Keep multiple copies of critical data, with at least one offline or logically isolated. Encrypt them, limit who can delete them, and run restore tests on a schedule. Quick vocabulary: offline means disconnected, isolated means separated from production networks and credentials, and immutable means it can’t be changed for a set period. Each helps. None replaces testing.
2. Patch internet-facing systems first.
Unpatched VPNs, firewalls, and remote access tools stay on attacker wish lists for a reason. Prioritize known exploited vulnerabilities, then work down the list. Patching is essential, but it isn’t a complete defense.
3. Lock down RDP and remote access.
Don’t expose RDP to the public internet. If you need remote access, put it behind a VPN or zero-trust gateway, require multifactor authentication (MFA), restrict who can connect from where, and monitor authentication logs. Turn off what you don’t use.
4. Train employees to spot phishing and social engineering.
Phishing is one of the most common ways in. Security awareness training (SAT) helps people catch suspicious links, fake urgency, and impersonation before they become an attacker’s foothold.
5. Use application allowlisting.
If unapproved tools can’t run, attackers have fewer ways to drop payloads and abuse legitimate software. It’s especially useful against loaders, rogue binaries, and unauthorized remote access tools.
6. Segment your network.
Flat networks make attackers faster. Segmentation helps keep one compromised system from becoming an organization-wide outage.
7. Require phishing-resistant MFA.
Prioritize email, VPN, remote access, and privileged accounts. Standard MFA isn’t enough: in the EvilTokens campaign, victims completed MFA correctly and still gave attackers a valid session. If a system can’t support phishing-resistant MFA yet, document the workaround and plan the migration.
8. Watch for suspicious PowerShell, WMI, and script activity.
Attackers often live off the land, which means they use tools already on your systems, like PowerShell and Windows Management Instrumentation (WMI). That makes malicious activity look like routine admin work. Monitoring for unusual scripting and native tool use helps you catch attackers sooner.
9. Add behavioral endpoint detection with 24/7 monitoring.
Endpoint detection and response (EDR) shows you what’s happening on your endpoints, and behavioral detection flags suspicious patterns as they unfold. But round-the-clock monitoring only helps if someone’s there to act at 2am. Look for managed EDR that pairs detection with SOC analysts who investigate and respond, and ask exactly what coverage and response you get.
10. Build and test an incident response (IR) plan.
Define isolation steps, owners, recovery decisions, communications, and escalation paths before a real incident forces the issue. Then run it. A plan that’s never been tested has gaps you’ll only find at the worst moment. Gather the people who’d actually be in the room for a tabletop exercise, and turn every hesitation or disagreement into a fix. Our Incident Response Tabletop-in-a-Box gives you a ready-to-run scenario, facilitator notes, and defined roles and decision points, no outside consultant needed.