Topic starter
24/06/2026 7:20 pm
TL;DR: Identity security must move from predefined access and periodic review to real-time decisioning and inline enforcement as AI agents, non-human identities, and millisecond-scale risk outgrow static IAM models, according to Fabrix Security. The acquisition underscores how access governance now hinges on runtime context, not admin-time policy alone.
Editorial analysis by NHI Mgmt Group, based on content published by Fabrix Security: “Fabrix is Joining Silverfort to Build the Runtime Identity Security Platform”.
Key questions
Q: What breaks when identity reviews assume access will stay stable long enough to assess?
A: The review process breaks when access can be abused, chained, or abandoned faster than the governance cycle can inspect it.
Q: Why do AI agents increase non-human identity risk?
A: AI agents increase non-human identity risk because they can execute many actions quickly once they inherit a credential or tool permission.
Q: How should security teams evaluate runtime enforcement versus advisory analytics?
A: Security teams should ask whether a control can actually stop or constrain access in the same path where the request occurs.
Practitioner guidance
- Rebuild approval logic around runtime context Map which access decisions still depend on admin-time policy and identify where current context, not stored role data, should drive the decision.
- Place enforcement in the access path Prioritise controls that can block or constrain access at the point of authentication or session establishment, especially for high-risk workloads and AI-driven actions.
- Separate reviewable access from ephemeral access Determine where periodic access reviews still add value and where short-lived, fast-moving access requires issuance-time controls instead of recertification.
Bottom line: Identity security is shifting because preapproved access and delayed review no longer match the speed of machine and AI-driven activity.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 4:34 am
Static authorization is no longer a complete security model: Access that is defined once and reviewed later assumes identities behave within predictable windows. That assumption weakens when human, machine, and AI-driven identities can change risk posture in the middle of a session. The practical conclusion is that governance has to move closer to the moment of use.
A question worth separating out:
Q: What is the difference between static authorization and runtime decisioning?
A: Static authorization assigns access in advance based on roles or entitlements, while runtime decisioning re-evaluates the request using current context at the moment of access. The latter is better suited to volatile identities, changing risk, and AI-driven activity because it reflects what the identity is trying to do now, not what it was allowed to do earlier.
👉 Read our full editorial: Silverfort acquires Fabrix: identity security shifts to runtime