AcademyLabs

Labs

Work the incident yourself.

Staged Azure, Microsoft 365, AWS and Google Cloud incidents. Follow the evidence, contain the attack and see how long it took you.

Clouds in the catalogue

Every run is timed · Every run leaves a sealed case

invictus.academy/labs
LabsSearch ⌘K

Labs

Real cloud incidents, staged and waiting. Pick one and start investigating.

TrackAllCloud DFIRSOC & DetectionThreat Intel
KindAllShared cloud rangeChallengesInvestigationCloud rangeLab shell
CloudAllAzure & Entra IDMicrosoft 365AWSGoogle Cloud

Azure & Entra ID

Foothold via OAuth

A consented OAuth application, holding access that no stolen password would have given

Cloud DFIRBasicShared cloud range

  • OAuth applications and their granted permissions in KQL
  • A published indicator checked against your own tenant

About 20 minutesStart lab

Google Cloud

GCP service-account key leak

Whoever found a service-account key that was published to a public repository

Cloud DFIRBasicInvestigation

  • Service-account key use in Google Cloud audit logs
  • Separating the owner’s use from the finder’s

About 35 minutesStart lab

AWS

Bucket Reaper

Whoever found a writable marketing bucket, and the credentials somebody left inside it

Cloud DFIRIntermediateChallenges

  • Website defacement traced back to a bucket policy
  • Credentials found in storage, and what they unlocked

About 1 hourStart lab

The Labs catalogue, in the new design · lab titles from the live catalogue

Why practise

Meet the evidence before the incident.

A real incident gives you one attempt, under pressure. A lab gives you the same kind of evidence and a clock, and you can run it again.

Know where to look

Read the evidence before you need it

Sign-in records, audit events, mailbox rules and storage logs, from a real cloud incident. You learn what they record, and what they leave out.

Act, then check

Practise the response too

Labs ask you to contain as well as detect. Live labs grade the state you leave behind, such as a revoked session, so the response has to work.

See the change

Your times, over many runs

Time to detect and time to respond are measured from your own start, on actions the platform can confirm. The KPIs page shows the trend as you practise.

What you work on

How you work a lab

Three tracks: DFIR, SOC (detection and triage from a defender’s console) and threat intelligence, each by difficulty.

Three ways to run them: self-paced labs on your own schedule, team purple-team exercises on a shared live range, and public CTF events on frozen artefact sets.

The catalogue

Every lab, by cloud

Staged cloud incidents across Microsoft 365, Azure, AWS and Google Cloud.

A goblin dragging sacks of records out of an open vault

Google Cloud / Workspace

DataGoblin Hunt: The VitalHealth Bucket Heist

Google Cloud / Workspace · Intermediate · 90 min

Included in every plan →
A pale phantom stepping out of a giant browser window frame

Google Cloud / Workspace

Workspace Ghost: Session Theft via Browser-in-the-Middle

Google Cloud / Workspace · Basic · 60 min

Included in every plan →

In the app

Every run leaves a case.

The timeline, the evidence you tagged and your findings stay together for each run, beside your detect and respond times.

Illustrative run · times and events are sample data

invictus.academy/runs/bucket-reaper
Runs · Bucket ReaperSearch ⌘K

AWS · Challenges · Intermediate

Bucket Reaper: Static Site Hijack and AWS Backdoor

Detect00:18:42Identified
Respond00:31:05Running

Case timeline

  1. PutBucketPolicy on the marketing bucketTagged
  2. index.html replaced from an unknown address
  3. GetObject on a credentials file in storageTagged
  4. CreateUser and AttachUserPolicy

Case sealed on submit · hash-chained custody log

Question 3 of 6

Which policy change made the bucket publicly writable?

Your answer

Submit flagPass

Every plan includes Labs.

Pick a plan, or tell us about your team.

Team Training →