Run a team session.
Choose three drills, let people practise, then decide what to do differently at work. Everyone plays in their own browser for free. No sign-up needed.
- Choose the team’s role and the habit they want to practise.
- Select three existing drills.
- Share the drill links and a short facilitator brief.
- Discuss what happened using the result timeline, a replay, or an export a participant chooses to share.
- Agree one workplace action, who will follow up, and when the team will practise again.
See a checked result export
This sample was downloaded with Export my result after a completed test run using fictional data. It is a participant result, separate from the facilitator brief.
Scenario: The vendor bank change. Mode: Guided training (training). The preview below contains the complete downloaded JSON, including its score and timeline.
This was an automated completed test run, so its recorded duration of 2 seconds is not a participant play-time estimate.
Download the fictional samplePreview the downloaded sample
{
"schemaVersion": 1,
"product": "Hamcodes Labs",
"mode": {
"id": "training",
"label": "Guided training"
},
"seed": "willow-moss-18",
"durationSeconds": 2,
"totals": {
"points": 95,
"max": 105,
"stars": 3,
"maxStars": 3
},
"scenarios": [
{
"id": "vendor-bank-change",
"title": "The vendor bank change",
"kind": "Business email compromise",
"points": 95,
"max": 105,
"stars": 3,
"rewinds": 0,
"overReports": 0,
"events": [
{
"points": 10,
"label": "Took out the vendor master file",
"verdict": "careful",
"detail": "The verified number for Ferrum Steel is 0114 496 0213. That is the number to call, not the one in the email.",
"ideal": "checks the request against the independent record before acting."
},
{
"points": 6,
"label": "Checked Ferrum Steel’s record in the ERP",
"verdict": "careful",
"detail": "The record shows the account on file and the verified phone number.",
"ideal": "compares the request with the record on file."
},
{
"points": 12,
"label": "Read the full email headers",
"verdict": "careful",
"detail": "The checks pass because the attacker owns the lookalike domain. The headers show the message came from the lookalike, not from Ferrum Steel.",
"ideal": "reads the headers and, more importantly, the sender domain, not just the display name."
},
{
"points": 22,
"label": "Called Ferrum Steel back on the number on file",
"verdict": "safe",
"detail": "Gary confirms Ferrum Steel sent nothing and their account has not changed. That call is what breaks the fraud.",
"ideal": "verifies a payment change by calling the number they already hold, never the number in the request."
},
{
"points": 45,
"label": "Rejected the change",
"verdict": "safe",
"detail": "The change is refused. Tonight’s payment goes to Ferrum Steel’s real account, the one already on file.",
"ideal": "rejects an unverified change and keeps paying the account on file."
}
]
}
],
"timeline": [
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "scenario-start",
"label": "The vendor bank change begins"
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "decision",
"label": "Took out the vendor master file",
"verdict": "careful",
"points": 10
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "decision",
"label": "Checked Ferrum Steel’s record in the ERP",
"verdict": "careful",
"points": 6
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "decision",
"label": "Read the full email headers",
"verdict": "careful",
"points": 12
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "decision",
"label": "Called Ferrum Steel back on the number on file",
"verdict": "safe",
"points": 22
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "decision",
"label": "Rejected the change",
"verdict": "safe",
"points": 45
},
{
"scenario": "vendor-bank-change",
"storyTime": "16:30",
"kind": "scenario-end",
"label": "The vendor bank change finished",
"verdict": "neutral"
}
]
}Start with the workplace habit.
A pack can be discussed around the people you are training and the decisions they face. Here is a representative example using existing drills.
Example: payment and account requests
Audience: Finance and service desk colleagues.
Three drills: The bank-detail switch; The MFA prompt that will not stop; Account recovery, the back door.
Intended habit: Pause under pressure, independently verify payment or account requests, and use the right escalation route.
Follow-up action: Confirm the trusted contact route for payment and account requests, and name the escalation owner. Agree an owner and a date for the next practice.
Bring this to the enquiry
Tell us who the training is for, the habit you want to practise, and the kinds of requests the team handles. Share a high-level description of your approved process, policy, tool or reporting route.
You can discuss drill selection, the audience and wording, workplace guidance in the facilitator brief, and the follow-up action. Use the existing enquiry form to send that outline; the next conversation can clarify the fit and scope before any custom work is agreed.
Example facilitator brief
Manual copy: select the text above and use Ctrl+C or Command+C, or touch and hold to copy.
Official sources for the featured drills’ framework tags
Training references
These references help a facilitator describe what participants practise. They are not a certification or evidence that an organization complies with a framework. Existing catalogue mappings are retained; limitations are identified below.
- ATT&CK T1566.001: ATT&CK T1566.001
Enterprise ATT&CK · Spearphishing Attachment · T1566.001
Practise inspecting a suspicious message and reporting it before trusting its request.
Existing catalogue mapping retained. The linked shared-document drill practises link checks; it does not demonstrate the specific attachment technique described by T1566.001.
- NIST PR.AT: NIST PR.AT
NIST CSF 2.0 (2024) · PR.AT
Practise recognizing suspicious requests and choosing a safe next step in everyday work.
- OWASP LLM06: OWASP LLM06
OWASP LLM Top 10 (2023-24) · LLM06
Practise keeping sensitive work information out of an unapproved chatbot.
The existing LLM06 tag uses the 2023-24 Sensitive Information Disclosure numbering; later editions use different numbers.
- GDPR Art.5: GDPR Art.5
Regulation (EU) 2016/679 · Article 5
Practise limiting personal information shared with a tool and protecting its confidentiality.
- NIST RS.CO: NIST RS.CO
NIST CSF 2.0 (2024) · RS.CO
Practise promptly passing useful facts to the designated reporting channel.
- ISO A.6.8: ISO A.6.8
ISO/IEC 27001:2022 · existing A.6.8 tag (control unverified)
The drill practises reporting a concern quickly through the appropriate work channel.
Existing catalogue mapping retained. ISO confirms the publication edition, but the exact control mapping could not be confirmed from an accessible official public preview.
- ATT&CK T1566.002: ATT&CK T1566.002
Enterprise ATT&CK · Spearphishing Link · T1566.002
Practise questioning a payment-change message and verifying the request independently.
- ISO A.5.14: ISO A.5.14
ISO/IEC 27001:2022 · existing A.5.14 tag (control unverified)
The drill practises verifying payment-change information through a trusted route.
Existing catalogue mapping retained. ISO confirms the publication edition, but the exact control mapping could not be confirmed from an accessible official public preview.
- ATT&CK T1621: ATT&CK T1621
Enterprise ATT&CK · MFA Request Generation · T1621
Practise rejecting unexpected sign-in prompts and reporting repeated requests.
- NIST PR.AA: NIST PR.AA
NIST CSF 2.0 (2024) · PR.AA
Practise protecting sign-in and recovery routes so access stays with the intended person.
- CIS 6: CIS 6
CIS Controls v8 · Control 6
Practise keeping MFA approvals under your control and escalating unexpected access attempts.
- ATT&CK T1098: ATT&CK T1098
Enterprise ATT&CK · Account Manipulation · T1098
Practise reviewing recovery settings and removing stale routes that could give someone access.
- OWASP A03: OWASP A03
OWASP Top 10:2021 · A03 Injection
Practise reproducing SQL injection or stored XSS, choosing a fix, and retesting normal use.
- CWE-89: CWE-89
MITRE CWE · CWE-89 (SQL injection)
Practise separating SQL commands from supplied data and proving the original attack is blocked.
- CWE-79: CWE-79
MITRE CWE · CWE-79 (cross-site scripting)
Practise preventing stored input from running as script while keeping legitimate content usable.
- OWASP A01: OWASP A01
OWASP Top 10:2021 · A01 Broken Access Control
Practise enforcing permissions on the server and retesting both allowed and forbidden access.
- CWE-284: CWE-284
MITRE CWE · CWE-284 (Improper Access Control)
Practise checking that a person can reach only the resources their role permits.
A broad training reference. MITRE discourages using this high-level identifier to classify a real vulnerability.