Checking controls against six cyber attack paths
Check evidence for phishing, service disruption, intercepted sign-in, malware, browser exploitation and password attacks with your IT provider.

A list of cyber threats is useful when it leads to checks you can complete. Ask IT which controls address each attack path, where those controls apply and what evidence shows they’re working.
These six categories overlap. They aren’t a ranking of current threats or a complete security assessment. Use them to find gaps in the systems your business depends on.
1. Deceptive messages and requests
Check message filtering, supported sign-in protection and staff verification for sensitive requests. Include a payment-detail change sent from a familiar but compromised account in a harmless exercise.
Verify that staff know how to report the request without replying to the suspected sender. Filtering reduces unwanted messages, but some will still get through.
2. Denial of service
Ask your internet and hosting providers what protection is enabled, what it covers and how to reach them during an outage. Record dependencies and an alternative contact route.
The Cyber Centre’s DDoS guidance addresses prevention and preparation. Local rate limits alone can’t resolve every upstream capacity problem.
Test the escalation plan without generating attack traffic. An outage can have plenty of causes besides a DDoS attack.
3. Intercepted or relayed sign-in
Verify the use of supported phishing-resistant MFA for important accounts and check permitted remote-access routes. Cyber Centre guidance on adversary-in-the-middle attacks explains why some MFA methods can still be relayed.
A VPN protects traffic across its particular tunnel. It can’t tell you whether the site at the other end is genuine, and it won’t stop someone typing their password into a fake page.
4. Malicious software
Check how software gets installed, endpoint protection, patch coverage and restrictions on ordinary users’ privileges. Verify that each managed device is reporting its current status.
Include recoverability and a known incident contact. Backups help with some recovery needs, but they don’t prevent infection or undo disclosure. Don’t use live malware to test these controls.
5. Browser exploitation and unwanted downloads
Check browser updates, extension controls and web filtering on supported devices. Confirm who investigates warnings and blocked downloads.
The Cyber Centre’s search-poisoning guide covers one route to harmful content. Visiting a page, entering credentials and running a download can have different consequences; the report should say exactly what the person did.
A control that blocks known destinations may miss a new one. No warning doesn’t mean a site is safe.
6. Password guessing and reuse
Check unique credentials, supported MFA, detection of unusual attempts and account recovery. Confirm that controls cover administrator and supplier accounts as well as staff.
Review lockout behaviour with IT. It can limit some attempts while also disrupting legitimate access. It doesn’t stop every password-spraying or stolen-credential attack.
Turn gaps into assigned work
For each check, record coverage, evidence, limitations and the next action. Assign an owner and verification step. Prioritize according to reachable systems and business consequences.
Recheck after a major configuration change or supplier handover. Keep the working evidence alongside the plan so a new person can see what was verified.


