On this page
- 1. Turn on multi-factor authentication everywhere that matters
- 2. Patch internet-facing systems first, and fast
- 3. Know what you expose to the internet
- 4. Remove standing admin rights
- 5. Use a password manager and stop reuse
- 6. Back up, and test restores
- 7. Lock down email
- 8. Train people with realistic practice
- 9. Collect logs and make sure someone reviews them
- 10. Have an incident response plan, and rehearse it
- Where to start
Advanced attacks get the headlines, but most breaches we investigate begin with something ordinary: a reused password, an unpatched VPN, an over-privileged account or an employee tricked by a convincing email.
The good news is that a short list of fundamentals blocks a large share of those attacks. None of them require an expensive platform. All of them require consistency.
1. Turn on multi-factor authentication everywhere that matters
Start with email, remote access (VPN, RDP gateways), cloud consoles, finance systems and admin accounts. Prefer phishing-resistant methods such as passkeys, FIDO2 security keys or app-based number matching over SMS codes.
2. Patch internet-facing systems first, and fast
Firewalls, VPN appliances, email gateways and public web servers are the first things attackers scan. Track vendor advisories for these specifically and treat known-exploited vulnerabilities as emergencies, not routine maintenance. The CISA Known Exploited Vulnerabilities catalogue is a useful priority list.
3. Know what you expose to the internet
You cannot patch or protect an asset you do not know exists. Keep an up-to-date inventory of domains, subdomains, IPs and open services, ideally with continuous external attack surface monitoring so new exposure is caught quickly.
4. Remove standing admin rights
Day-to-day accounts should not be administrators. Use separate admin accounts, grant privileges only when needed and review who has access to critical systems at least quarterly.
5. Use a password manager and stop reuse
Credential stuffing works because people reuse passwords. A company password manager makes unique, strong passwords the easy option. Combine it with MFA and breached-password checks.
6. Back up, and test restores
Keep at least one backup copy offline or immutable so ransomware cannot encrypt or delete it. Then actually test restoring a critical system.
7. Lock down email
Configure SPF, DKIM and DMARC for your domains to make spoofing harder, and enable attachment and link scanning. Move DMARC towards an enforcement policy (quarantine or reject) once you are confident legitimate mail is aligned.
8. Train people with realistic practice
Annual slide decks do little. Short, regular training and realistic phishing simulations build the habit that matters most: pausing and reporting a suspicious message rather than clicking it. Make reporting easy and never punish people for honest mistakes.
9. Collect logs and make sure someone reviews them
Centralise logs from identity, endpoints, email and key servers. Logging only helps if someone reviews alerts, whether that is an internal team or a managed security provider.
10. Have an incident response plan, and rehearse it
Decide in advance who leads an incident, how to contact them out of hours, who talks to customers and regulators, and which external experts you will call. A one-hour tabletop exercise once a year will expose most gaps.
Where to start
If this list feels long, start with the top three: MFA, patching internet-facing systems and knowing your external attack surface. Then work down the list over the next quarter.
Want an outside view of where you stand? A focused vulnerability assessment or penetration test will show which of these gaps are real in your environment. Get in touch and we will help you prioritise.
Written by
Muhammad Fawad Mushtaq
Head of Compliance, FutaqSec