Foundation bridges

These ten lessons already exist. This page does not replace them. It tells you why the lesson matters, what you should be able to do, where to practise, and what to open next. Opening one of these lessons also shows the same bridge above the lesson text.

The CIA triad. People use these three words as labels. The useful version is being able to say which goal a control is for. Phishing. Most early incidents start with a message, not a novel exploit. You need to separate the display name from the sender. Passwords and hashing. A password that is stored so it can be read back is already a different problem from a password that is slow to guess. Incident response basics. A first note that overclaims is hard to walk back. Practice saying what a fact supports. Shared responsibility. “It is in the cloud” does not say who patches the application or who sets the role. Cloud identity and access. A role that can do everything is a standing incident. The practice is naming the action and the resource. SQL injection. The database cannot tell your query from the part a caller typed, unless you keep them separate. IDOR. A page that loads “your” invoice by a number will load someone else’s if the server never checks the owner. Cross-site scripting. A page that inserts a name into HTML will run script if that name was chosen by someone else. BOLA and BFLA. Authentication answers who is calling. Authorization answers which object and which action. Stopping after the first question is the bug.

Glossary terms you can ask the offline coach for: BOLA, BFLA, HTTP 401, HTTP 403, HTTP 200, SPF, DKIM, OAuth state, OIDC nonce, Least privilege, pull_request_target, Prompt injection, Image digest.

Open the coach · Open practice labs · Open the analyst shift