AttackGraph.org

Course › Lesson 3 of 7

Delivery

Delivery is the moment the attack reaches the target and someone acts on it. In MITRE ATT&CK this is the Initial Access tactic. It's the first stage where the defender's controls can really bite. In the Westfield case study, it's the phishing wave of 3 May 2025.

The case study. This lesson uses the University of Westfield master case study from Cyber Security Fundamentals. If you've followed the earlier lessons you'll recognise the attack; each lesson looks at one stage of it.

What delivery is

Delivery is transmitting the attack to the target and getting the first action: a click, an opened attachment, a login on a fake page. It's the third stage of the Cyber Kill Chain and maps to ATT&CK's Initial Access tactic.

Unlike reconnaissance and weaponisation, delivery reaches the target's environment, so mail filtering, web-content controls, user training and monitoring all have something to catch.

In the Westfield attack

On 3 May 2025, LedgerWraith emailed staff claiming that, after a cyber attack, everyone had to reset their SAP ERP credentials, with a link to the fake reset page. Staff who believed it clicked and reached the fake login page. The story was believable partly because the real portal had no MFA, so a forced reset sounded plausible.

This stage in ATT&CK

CodeTechniqueIn this case study
T1566.002Phishing: Spearphishing LinkThe mass reset email with a link
T1204.001User Execution: Malicious LinkA staff member clicking the link
T1133External Remote Services(Task B) logging in to remote access
T1190Exploit Public-Facing Application(Task B) hitting the legacy OpenVPN gateway
T1199Trusted Relationship(Task B) using a partner's access

Hover over any code in the builder to see ATT&CK's own description.

Defending against this stage

Delivery is where defence starts to work. For spearphishing links, ATT&CK lists M1017 User Training, M1021 Restrict Web-Based Content and M1031 Network Intrusion Prevention, among others. Mail filtering blocks many messages before they arrive; user training helps staff spot the ones that get through; blocking the link stops the click from mattering. The broader lesson: an organisation's weakest way in sets its risk, so every route has to be covered.

Worked example

Attack graph: two preconditions feeding a phishing email event, then a click event, ending in the goal 'Fake login page opened'.
The click depends on the email being delivered, so it needs the sending event's result.Try it in the builder

Your tasks

Each task opens in the builder with the scenario beside your graph. Build your graph, press Check my graph for feedback as often as you like, then compare with the model answer. Your work on each task is saved in your browser.

Task A · what happened

The phishing wave

Model the sending of the email and the click that followed.

Task B · what are the options

Ways in

Map the different ways an attacker could get a first foothold at Westfield.

When you've finished, you can send your graph and its activity log to your tutor with Email to tutor in the builder.

← Back to the course