Topics
Start from the question in front of you. Each group is a few hubs and labs that already exist. Nothing here is permission to test a system you do not own.
I saw a weird email
6 links
A reported message is a header and a sender, not a verdict. Read the Received chain and the authentication results before you tell anyone it is phishing. Then look at domains that resemble yours, and at the report that says who is sending as you.
I need to read a packet
5 links
A capture is a list of conversations, not a pile of hex. Start with who talked, which protocol carried it, and whether the payload is still readable. The packet lab asks you to put one page load in order. You are not sending traffic.
Something logged into an account
6 links
A logon is an account, a type, and a source. The Active Directory and identity lessons name which record shows that a password was used, and which record does not. The labs hand you a push-bombing queue and a token so you can say what you would trust.
A scanner or an exposed port
2 links
A scan report is a list of what answered. Read it from the side that was scanned, on a host you are allowed to look at. Then decide which of those answers should have been reachable, and which firewall rule should have stopped the rest.
A laptop or a disk
5 links
A disk and a memory image are evidence with a clock. The forensics workbench is how you read them. Triage is how you collect and order what you found. The timeline lab is five events you have to put in one sequence.
I have one alert
4 links
An alert is a claim with a clock. Read the title, who it names, when it fired, what the rule was written to catch, and what ordinary work would look the same. Then write the note.
I have an interview or a cert
3 links
One exam is enough vocabulary. After that, you need a lab you can describe without the hint open. The certification lessons are the names. The career paths are the short lists that end in that lab.