Threat Modeling for OpenSearch: Identifying and Mitigating Security Risks
summary
Covers practical threat modeling using STRIDE and concrete OpenSearch defenses: identify assets (indices, cluster metadata, credentials), protect ports 9200/9300 with per-node TLS certificates and perfect forward secrecy, enable the OpenSearch Security plugin for RBAC, field/attribute-level controls, TLS, and audit logs. Notes common failures—default creds, publicly exposed clusters—and operational controls: query allowlists, circuit breakers, rate limits, backups, incident runbooks, and penetration testing; cites typical breach costs (~$5M) and global losses (~$10B).
AI-written summary · about
chapters (16)
- 0:00Threat modeling for OpenSearch
- 1:02Security in OpenSearch deployments
- 2:25What is threat modeling
- 3:28STRIDE framework overview
- 5:55OpenSearch architecture protection
- 7:19Assets and entry points
- 9:03Trust boundaries in security
- 11:28Security threats in OpenSearch
- 13:55Mitigating threats with plugin
- 17:02Encryption strategies
- 19:07Defense in depth
- 20:34Application security best practices
- 22:59Monitoring and incident response
- 24:45Security checklist
- 26:30Key takeaways
- 26:57Q&A
related talks
41mSecuring OpenSearch: Hints for avoiding common hassles
13mSecuring the Data Frontier: Real-World Strategies With OpenSearch
14mThreat Modeling for O11y: From Blind Spots to Actionable Insight
37mSecuring Open Source Through Threat Modeling
11mLightning Talk: A Supply Chain Security View of OpenSearch
53mThreat Modeling: uncover vulnerabilities without looking at code
57mUnlocking Threat Modeling
55mFirewall Reversed: How Open Source Became Asia's Best Defense
