Secure System Integrations
summary
Recommends a concrete baseline: enforce network segmentation, use TLS 1.3 only (or a hardened 1.2) and verify with SSL Labs scanning, and move client auth from shared secrets to asymmetric methods like mutual TLS + cnf claim or Private Key JWT/DPoP via OAuth2 client‑credentials so tokens are sender‑constrained. Warns S3 presigned links and message bus keys create bearer shortcuts, so either proxy through the API, tighten scope/rotation, and add automated negative tests (forbidden on missing scope) and OWASP/OASV checks.
AI-written summary · about
chapters (20)
- 0:00Secure system integrations
- 1:57Infrastructure security basics
- 3:21Transport layer hardening
- 7:38Client authentication methods
- 9:50OAuth 2.0 client credentials
- 13:47Bearer token limitations
- 17:48Proof of possession tokens
- 23:10Sender-constrained tokens
- 24:37HTTP API integration summary
- 26:43File transfer security
- 29:56Legacy protocol security
- 31:02Message bus security
- 31:47Complexity vs security
- 33:36Threat modeling integrations
- 35:50Zero trust applications
- 37:57Trust boundaries refactoring
- 41:14Verifying implementations
- 43:41Security frameworks
- 45:33Performance and availability in security
- 45:56Integration security baseline
related talks
50mCommon API security pitfalls
01h 02mLock That Sh*t Down! Auth Security Patterns for Apps, APIs, and Infra
32mREST security essentials
30mInsecurity protocols: an overview of modern authentication
56mLock That Sh*t Down!
53mCommon API Security Pitfalls
59mInsecure Transit - Microservice Security
37mAdd security to architecture one step at a time