Notifications
Clear all
Topic starter
25/06/2026 1:36 pm
TL;DR: Identity security is moving from back-end infrastructure to a business-facing control layer that affects compliance, efficiency, and secure access, according to SailPoint’s discussion with Salesforce and Keurig Dr Pepper leaders. The programme lesson is that identity work must be treated as an ongoing operating model, not a one-time project, because fragmented patterns create inconsistency and risk.
NHIMG editorial — based on content published by SailPoint: Keurig Dr Pepper and Salesforce discuss transforming their businesses with identity security
Questions worth separating out
Q: How should organisations govern identity security as a business enabler?
A: Treat identity security as an operating control that supports productivity, auditability, and secure change.
Q: Why do inconsistent identity integrations create governance risk?
A: Inconsistent integrations create governance risk because each application can end up with different provisioning, review, and revocation behaviours.
Q: How do non-human identities fit into zero trust programmes?
A: Non-human identities belong in zero trust because service accounts, machines, and tokens also make access decisions possible.
Practitioner guidance
- Standardise IGA integration patterns early Define a consistent identity pattern for onboarding, provisioning, certification, and deprovisioning before application migration begins.
- Extend zero trust to service accounts and machines Inventory non-human identities alongside human accounts and apply the same verification, access scoping, and monitoring expectations to each identity class.
- Treat identity data quality as a control requirement Map duplicate identity sources, reconcile conflicting attributes, and establish one authoritative data layer for access decisions and governance reporting.
What's in the full article
SailPoint's full post covers the operational detail this post intentionally leaves for the source:
- The customer panel discussion with Salesforce and Keurig Dr Pepper leaders on how identity security supports business priorities.
- The specific operating lessons on access recertification, user enablement, and secure access design that practitioners can adapt.
- The practical examples of how AI and ML are being introduced into identity workflows and user experiences.
- The panel's direct guidance on building a long-term identity security programme across cloud and enterprise environments.
👉 Read SailPoint's customer panel discussion on identity security and business enablement →
Identity security as a business enabler: what IAM teams should learn?
Explore further
25/06/2026 3:37 pm
Identity security has become an operating model, not a project. The article is right to frame identity as something that now affects business enablement as much as compliance. That is the real shift for governance teams: access quality, workflow speed, and auditability are now intertwined. Practitioners should treat identity security as a continuing operating discipline rather than a discrete deployment exercise.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, with 38% reporting no or low visibility and 47% only partial visibility, according to The State of Non-Human Identity Security.
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should security teams prioritise before scaling identity security?
A: Security teams should prioritise identity data quality, standard access patterns, and clear ownership for lifecycle decisions. If identity records are fragmented, every downstream control becomes harder to trust. A clean data layer and consistent governance model make scale possible without multiplying exceptions.
👉 Read our full editorial: Identity security is becoming a business enabler, not a back-end tool
