Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.3.1.14. Threat Modeling and Risk Assessment

3.3.1.14. Threat Modeling and Risk Assessment

💡 First Principle: Scanners find known weaknesses in what is already built; threat modeling finds design flaws before they are built. Risk assessment then decides, with evidence, which threats to fix first and which to accept.

Threat modeling in practice (AWS's four questions):
  1. What are we working on? Draw the data flows, components and trust boundaries (internet to API, service to service, account to account, third-party callbacks).
  2. What can go wrong? Walk each element and flow with a framework such as STRIDE and write specific threat statements (source, prerequisite, action, impact, asset). AWS's open-source Threat Composer tool (also in the AWS Toolkit for VS Code) structures this.
  3. What are we going to do about it? Choose a response per threat: mitigate, accept (with a named owner), transfer or avoid.
  4. Did we do a good enough job? Review the model and update it whenever the design changes; it is a living artifact kept with the code.
STRIDE threatProperty violatedExample AWS mitigations
SpoofingAuthenticationCognito or IAM Identity Center with MFA, mutual TLS with Private CA, SigV4 with short-lived role credentials
TamperingIntegrityTLS, S3 Object Lock, CloudTrail log file validation, KMS or ML-DSA signatures
RepudiationNon-repudiationOrganization trail, database activity streams, immutable log archive
Information disclosureConfidentialityKMS encryption, data perimeters, least privilege, Macie discovery
Denial of serviceAvailabilityShield, WAF rate-based rules, API throttling, Multi-AZ
Elevation of privilegeAuthorizationLeast-privilege roles, permissions boundaries, SCPs, ABAC

Prioritizing: score each threat by likelihood and impact, treat the highest risks first, and record the decision for every remaining threat (owner, accept/transfer/defer, review date) in a risk register. Fixing the cheapest threats first or ignoring unlikely-but-catastrophic ones are both indefensible. Mitigations that limit blast radius, such as separate accounts, tenant-scoped roles with ABAC and permissions boundaries, reduce the impact of a whole class of threats at once.

Continuous risk assessment of running systems:
  • Amazon Inspector scores vulnerabilities in EC2, ECR images and Lambda, adjusting for context such as network reachability. Security Hub CSPM checks configurations against standards.
  • The new AWS Security Hub correlates CSPM, Inspector, Macie and GuardDuty signals into exposure findings, so "vulnerable, reachable from the internet, with a permissive role and sensitive data" ranks above thousands of isolated CVEs. GuardDuty Extended Threat Detection links related signals into attack-sequence findings.
  • IAM Access Analyzer shows external, internal and unused access. Validate that mitigations work with AWS Fault Injection Service experiments and game days, and use Well-Architected security pillar reviews to track risk over time.

⚠️ Exam Trap: "Run Inspector" or "enable GuardDuty and Security Hub" does not answer a question about finding design flaws before code exists. That is a threat-modeling question, and the tools come later to assess the built system.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned