Recommended
Recommended
More Related Content
Similar to Threat Modeling in the Cloud
Similar to Threat Modeling in the Cloud (20)
More from Paige Cruz
More from Paige Cruz (14)
Recently uploaded
Recently uploaded (20)
Threat Modeling in the Cloud
- 1. Threat Modeling in the ☁ Paige Cruz @paigerduty
- 2. What threats are likely for a vending machine?
- 3. Your threat model is not my threat model: Hospital edition 🏥
- 4. 4
- 5. 5 Warning Do not use endoscopy equipment to steal chocolate from this vending machine.
- 7. A structured process to identify security requirements, pinpoint threats and potential vulnerabilities, quantify threat and vulnerability criticality and prioritize remediation methods. The Official ™ Definition 7
- 8. “ Threat modeling is a conversation. - Matthew Coles Sr Principal Product Security Eng @ Dell 8 Real World Definition
- 9. Guiding Questions 9 What are we working on?
- 10. Guiding Questions 10 What are we working on? What can go wrong?
- 11. Guiding Questions 11 What are we working on? What can go wrong? What are we going to do about it?
- 12. Guiding Questions 12 What are we working on? What can go wrong? What are we going to do about it? Did we do a good enough job?
- 13. 13 ✨ ✨
- 14. 14 Architect
- 19. 19
- 20. Threat Modeling in the Cloud ☁
- 21. Which make up the top 3 cloud threats? ⬡ Weak Control Plane ⬡ Account Hijacking ⬡ Data Breaches ⬡ Insufficient IAM and Key Management ⬡ Metastructure + Applistructure Failures ⬡ Abuse + Nefarious Use of Cloud Services 21 ⬡ Insecure Interfaces + APIs ⬡ Insider Threat ⬡ Misconfiguration and Inadequate Change Control ⬡ Lack of Cloud Security Architecture + Strategy ⬡ Limited Cloud Usage Visibility
- 22. Which make up the top 3 cloud threats? ⬡ Weak Control Plane ⬡ Account Hijacking ⬡ Data Breaches ⬡ Insufficient IAM and Key Management ⬡ Metastructure + Applistructure Failures ⬡ Abuse + Nefarious Use of Cloud Services 22 ⬡ Insecure Interfaces + APIs ⬡ Insider Threat ⬡ Misconfiguration and Inadequate Change Control ⬡ Lack of Cloud Security Architecture + Strategy ⬡ Limited Cloud Usage Visibility
- 23. Which make up the top 3 cloud threats? ⬡ Weak Control Plane ⬡ Account Hijacking ⬡ Data Breaches ⬡ Insufficient IAM and Key Management ⬡ Metastructure + Applistructure Failures ⬡ Abuse + Nefarious Use of Cloud Services 23 ⬡ Insecure Interfaces + APIs ⬡ Insider Threat ⬡ Misconfiguration and Inadequate Change Control ⬡ Lack of Cloud Security Architecture + Strategy ⬡ Limited Cloud Usage Visibility
- 24. Which make up the top 3 cloud threats? ⬡ Weak Control Plane ⬡ Account Hijacking ⬡ Data Breaches ⬡ Insufficient IAM and Key Management ⬡ Metastructure + Applistructure Failures ⬡ Abuse + Nefarious Use of Cloud Services 24 ⬡ Insecure Interfaces + APIs ⬡ Insider Threat ⬡ Misconfiguration and Inadequate Change Control ⬡ Lack of Cloud Security Architecture + Strategy ⬡ Limited Cloud Usage Visibility
- 25. 25
- 26. 26
- 27. 27 🙃 🤨 😬
- 28. 28 “If Defendant had disclosed the full extent of the breach in August instead of waiting months, Plaintiff/Class would have been on heightened alert and changed passwords to avoid theft that ensued.”
- 29. 29
- 30. 30
- 31. 31
- 32. 32 👀 👀 👀 👀 👀
- 33. 33
- 34. Case Study
- 35. “While Argo services often support various risk or threat prevention methods, these are frequently under-documented or are provided on an opt-in basis rather than default - Argo Project Threat Model 35
- 36. 36
- 37. 37
- 38. Minimal Service Documentation: Argo 38
- 39. Threat Modeling and You ✨
- 40. 40 1 Identify 1 feature or service to begin threat modeling
- 41. 41 1 2 Identify 1 feature or service to begin threat modeling Schedule a meeting. Agenda: The 4 Guiding Questions
- 42. 42 1 3 2 Identify 1 feature or service to begin threat modeling Send pre-read of the Threat Modeling Manifesto Schedule a meeting. Agenda: The 4 Guiding Questions
- 43. 43 1 3 4 2 Identify 1 feature or service to begin threat modeling Send pre-read of the Threat Modeling Manifesto Schedule a meeting. Agenda: The 4 Guiding Questions Ensure minimal service documentation
- 44. 44 1 3 5 4 2 Identify 1 feature or service to begin threat modeling Send pre-read of the Threat Modeling Manifesto Assign a scribe and facilitator for the meeting Schedule a meeting. Agenda: The 4 Guiding Questions Ensure minimal service documentation
- 45. 45 1 3 5 6 4 2 Identify 1 feature or service to begin threat modeling Send pre-read of the Threat Modeling Manifesto Assign a scribe and facilitator for the meeting Schedule a meeting. Agenda: The 4 Guiding Questions Ensure minimal service documentation Rinse and repeat
- 46. Case Study
- 48. Threat Modeling is a conversation
- 49. Further Resources ⬡ Threat Modeling Manifesto ⬡ OWASP Top Ten Web App Security Risks ⬡ Hiding Malware in Docker Desktop <- srsly a hilarious and informative read ⬡ MITRE ATT&CK adversarial knowledge base 101 blog post 49
- 50. Minimal Service Documentation ⬡ How does the service work? ⬡ Are there any subcomponents or shared boundaries? ⬡ What communication protocols does it use? ⬡ Where does it store data? ⬡ What is the most sensitive data it stores? 50
- 51. 1. Data Breaches 2. Misconfiguration and Inadequate Change Control 3. Lack of Cloud Security Architecture + Strategy 4. Insufficient IAM and Key Management 5. Account Hijacking 6. Insider Threat 7. Insecure Interfaces + APIs 8. Weak Control Plane 9. Metastructure + Applistructure Failures 10. Limited Cloud Usage Visibility 11. Abuse + Nefarious Use of Cloud Services 51
- 52. 52 Let’s Chat @ CNCF Booth G3 Friday, 2:20 - 3:20 paigerduty.com ★ @chronosphere.io ★ @hachyderm.io