STRIDE, data flow diagrams, risk rating, mitigations
Practise these as flashcards. One or two lines each; the ones you miss come back first.
Start freeThreat modeling is a process for identifying and addressing potential security threats in a system, usually before development begins. It's important because it helps teams proactively find and fix vulnerabilities, reducing the risk of security breaches.
Threat modeling should be done early, ideally during the design phase, and repeated whenever there are significant changes to the system architecture or new features are added.
A DFD is a visual representation of how data moves through a system, showing processes, data stores, and external entities. In threat modeling, it's used to map out the system and identify trust boundaries where threats are more likely.
STRIDE stands for Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. These are categories of security threats to consider during threat modeling.
A common trust boundary in a web app is between the user's browser and the backend server. Data crossing this boundary needs validation because the server can't trust input from the client.
I'd check for spoofing (can someone pretend to be another user?), tampering (can login requests be altered?), repudiation (can users deny actions?), information disclosure (are credentials leaked?), denial of service (can logins be abused?), and elevation of privilege (can users gain admin access?).
Risk rating helps prioritize which threats to address first by evaluating their potential impact and likelihood. This ensures resources are focused on the most critical vulnerabilities.
DREAD stands for Damage, Reproducibility, Exploitability, Affected Users, and Discoverability. Each factor is scored, and the total helps rank threats by risk level.
I log each mitigation as a ticket or task in our project management tool, link it to the specific threat, and ensure it's assigned and verified before closing.
To mitigate information disclosure, I would enforce HTTPS to encrypt data in transit and ensure sensitive data is not logged or exposed in error messages.
CVSS, or Common Vulnerability Scoring System, is a standardized way to assess the severity of security vulnerabilities. It assigns a numerical score based on factors like impact and exploitability, helping prioritize remediation.
Technical mitigations involve changes to code or infrastructure, like input validation or encryption. Process-based mitigations are changes to how work is done, such as code reviews or security training.