Cloud Threat Model
I attended a cybersecurity event πcontainer security village. I learn this topic Threat Modelling in Cloud so i want to apply this theory. Some memories :)
My experiment a static website in an AWS S3 bucket, served via a Content Delivery Network (CDN), with an AWS Lambda backend API. I want to apply threat modeling: shifting security left by finding flaws in the design phase rather than in production.

Diagram showing Components (Data Flows) β΄οΈ
- Where does secure private data start?
|
|
Phase 2: Identify Threats (Using STRIDE) π§
| Component | STRIDE Category | Threat Description |
|---|---|---|
| S3 Bucket | Information Disclosure | Misconfigured permissions allow unauthorized public read access. |
| CDN (CloudFront) | Spoofing / Tampering | Attackers bypass the CDN to target the S3 origin directly. |
| API Gateway / Lambda | Elevation of Privilege | Lack of authentication allows unauthorized code execution. |
STRIDE methodology (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) to identify threats at each component.
Mitigation Plan: Cloud configuration fixes.
- S3: Block direct public access and apply CloudFront restriction.
- Lambda: Use IAM roles for S3 and Cloudfront access.
- API Gateway: Enable a firewall to block IPs that exceed request limits.
- CloudFront: Apply Amazon CloudFront Origin Access Control (OAC).
πMy code:π Results
Recommended Tools
- OWASP Threat Dragon (Free, open-source tool)
Offtopic
Love your dogs by giving them a quality life. Donβt forget to neuter!