Maximising Security with Threat Modelling in the Cloud
summary
Visma aggregates findings from cloud scanners (proof‑of‑concept with Aqua/Orca and others) and maps them to MITRE ATT&CK then to STRIDE to derive concrete threat‑modeling questions. Scans reveal many public VMs, exposed Kubernetes control planes, overly privileged IAM/service accounts, disabled logging, missing MFA and public storage — a high volume of real misconfigurations. A new Cloud Guardian service ingests those findings to drive automated, prioritized follow‑ups and interactive threat checks (drag‑and‑drop infra + questions); approach is working at Visma scale.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 2:43Visma security program
- 5:43Defining cloud threat modeling
- 10:22Threat modeling methodology
- 13:38Identifying actors and impacts
- 20:01Asset identification in cloud
- 23:05Mitre ATT&CK framework
- 27:43Analyzing cloud vulnerabilities
- 36:41STRIDE threat modeling method
- 45:54Follow-up and automation
- 48:34Q&A session
related talks
15mThe origin of security challenges & a revolutionary solution
40mCloud Threat Modeling - from Architecture Design to Application Development
21mMake threats visible in your cloud environment — Eric Jung
50mAvoiding cloud security anti-patterns the right way
14mThe origin of cloud security challenges and a revolutionary solution
47m3 steps to help mitigate cloud risks
32mIntro to Threat Modeling in the Cloud
45mProtecting you from you: Misconfiguration-caused breaches