Building Neo-security Platforms: Securing APIs using modern standards
summary
Argues a concrete “neo-security” stack using SAML, OpenID Connect, OAuth 2, plus SCIM, JSON token formats and XACML for authorization; recommends placing a security token service (STS) centrally like DHCP/DNS and running a federation server and identity repository for SSO and JIT provisioning. Says SCIM supports bulk ingest, OpenID Connect targets mobile/IoT, OAuth 2 enables delegated access, and policy enforcement uses a PDP/PAP model; platforms are usually custom but can integrate MFA via resellers.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:00Agenda
- 2:16The Big Picture
- 3:10Identity
- 3:40Identity technologies
- 7:35Single signon
- 10:10OpenID Connect
- 11:35Simple Clouded Identity
- 12:25OAuth
- 13:40Identity Protocol Suite
- 14:10Neosecurity Platform
- 18:00Policy Decision Point
related talks
32mPlatform Security that will Last for Decades
20mBuilding a secure API: Overview of techniques and technologies needed to launch a secure API
24mTransforming into a Platform for Innovation and Agility
44mPresentation on Security Standards and Protocols
29mAPI Security in 2017
32mSecuring Value in API Ecosystems
27mIntegrating API Security Into A Comprehensive Identity Platform
32mModern And Secure IAM For Modern Applications