IAM
Joiner-mover-leaver, SSO / MFA, access reviews, and the operating model between the IdP and the rest of the estate. For IAM engineers, helpdesk, and the owners of the directory.
Joiner-mover-leaver, SSO / MFA, access reviews, and the operating model between the IdP and the rest of the estate. For IAM engineers, helpdesk, and the owners of the directory.
Vault operations after go-live: onboarding, sessions, dual control, break-glass, and the cadence that keeps standing privilege from coming back. For vault admins, SOC, and platform owners.
Customer and partner identity: federation, consent, and the join between the customer IdP and the apps they actually use. For product, IAM, and digital-channel teams.
Non-human identity: service accounts, keys, workloads, and machines treated as privileged from day one. For IAM, platform, and DevOps — not a subtitle under PAM.
SaaS as a data path: discovery, shadow IT, and controls on what leaves through cloud apps. For security architecture and the owners of sanctioned SaaS.
Secure service edge as one fabric: web, cloud, and private access without three operating models. For network and security operations that have to run it together.
Private applications without a fat VPN: who may reach what, from where, and how sessions are logged. For network, IAM, and the application owners.
How data actually leaves — including privileged export. Policy that matches the path, not a default template. For DLP admins, SOC, and data owners. DPDP when the question is personal data in India.
Who the agent is, what data it may touch, and who may prompt it. Guardrails, access reviews, and incident paths for AI estates. For security, platform, and the teams shipping models into production.
Models and agents as identities: credentials, tool access, and the join to IAM / PAM / NHI so an agent is not an ungoverned service account. For IAM and AI platform owners in the same room.