Notifications
Clear all
Topic starter
24/06/2026 11:21 pm
TL;DR: CrowdStrike’s acquisition of SGNL reflects a broader consolidation trend as security platforms move to close identity and access gaps for cloud and AI systems, while Apono argues that static roles and periodic reviews no longer scale. The real issue is that access decisions must now adapt continuously across humans, NHIs, and AI-driven actors.
NHIMG editorial — based on content published by Apono: Why Did CrowdStrike Buy SGNL? It’s all about AI
Questions worth separating out
Q: How should teams govern access when cloud and AI workloads change too fast for static roles?
A: Teams should move from assignment-time thinking to runtime authorization.
Q: Why do non-human identities create more governance pressure than human accounts?
A: Non-human identities scale faster, change more frequently, and are often distributed across tools that sit outside the main identity provider.
Q: What breaks when access reviews are still tied to periodic certification cycles?
A: Periodic reviews miss access that is granted, used, and retired between review windows.
Practitioner guidance
- Re-baseline access models around runtime decisions Review whether your current roles, entitlements, and approvals still assume a slow-moving environment.
- Pull NHIs into a single governance inventory Consolidate service accounts, API tokens, workload identities, and automation into one inventory with owners, expiry rules, and review cadence.
- Define control points for AI-driven access paths Map where agentic systems can choose tools, access data, and continue execution without human approval.
What's in the full analysis
Apono's full analysis covers the operational detail this post intentionally leaves for the source:
- A closer breakdown of the dynamic authorization model and how it differs from static entitlement reviews.
- Specific examples of how Just-in-Time access is positioned for humans, NHIs, and AI-driven workflows.
- The consolidation pattern across privileged access vendors and what it implies for platform selection.
- The practical access governance principles Apono says guide its approach in cloud environments.
👉 Read Apono's analysis of the CrowdStrike and SGNL acquisition context →
CrowdStrike buys SGNL: what changes for IAM and AI governance?
Explore further
25/06/2026 8:10 am
Dynamic authorization is now an identity governance requirement, not an optimization. Static roles and periodic access reviews were designed for systems where privilege changed slowly enough to be certified after the fact. That assumption no longer holds in cloud environments where access paths shift continuously. The implication is that identity governance must be evaluated by how well it follows runtime usage, not by how neatly it documents old entitlements.
A few things that frame the scale:
- The ratio of non-human identities to humans is now estimated at roughly 150:1, according to Ultimate Guide to NHIs.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: Who is accountable when AI or machine identities act outside intended scope?
A: Accountability stays with the organisation that owns the identity, the policy, and the data path. Vendors may provide infrastructure or models, but the enterprise still controls authorisation boundaries and operational guardrails. If those are missing, the programme owner cannot treat AI or machine behaviour as an external problem.
👉 Read our full editorial: CrowdStrike’s SGNL acquisition signals a new identity control plane
