Getting started
Methodology
Deciding what to look at first, and why.
0 of 6 completed
- 1Knowing the application
Four questions a reviewer answers about an application before reading the code.
Open the lesson
Listen to an AI summary of Knowing the application
0:00 / 0:28 - 2Risk based review
A change that could cause more harm gets a closer review. A team judges each change by who can reach the code and what could be lost.
Open the lesson
Listen to an AI summary of Risk based review
0:00 / 0:30 - 3Threat modelling
A threat model lists what an attacker wants, where the attacker can get in and what stops the attacker. A reviewer uses the list to decide which code needs the most care.
Open the lesson
Listen to an AI summary of Threat modelling
0:00 / 0:31 - 4Static code analysis
A static analysis tool reads the code without running the software and reports the lines that look risky. The tool does not know what the software is for.
Open the lesson
Listen to an AI summary of Static code analysis
0:00 / 0:33 - 5Sources and sinks
A source is where data from outside comes into the code. A sink is where the code passes the data to a program that acts on the data.
Open the lesson
Listen to an AI summary of Sources and sinks
0:00 / 0:33 - 6Searching the code
A search finds the lines where data from outside comes in and where the data is used. Each result is a place to start reading.
Open the lesson
Listen to an AI summary of Searching the code
0:00 / 0:32