Notifications
Clear all
Topic starter
25/06/2026 1:36 pm
TL;DR: Identity programmes now depend as much on implementation capacity and lifecycle support as on product features alone, according to SailPoint. Its Partner Fleet program is designed to clarify partner roles, strengthen delivery services and managed services, and speed customer deployment across its identity security business.
NHIMG editorial — based on content published by SailPoint: Introducing the SailPoint Partner Fleet program
Questions worth separating out
Q: How should IAM teams evaluate partner-managed identity services?
A: Treat partner-managed identity services as a governance extension, not a procurement checkbox.
Q: What breaks when identity delivery partners are poorly defined?
A: Programme ownership becomes fragmented, and identity controls are implemented inconsistently across deployments.
Q: When should organisations use managed services in identity security?
A: Use managed services when internal teams need repeatable operational support and the work can be measured, audited, and governed.
Practitioner guidance
- Define partner control boundaries Map each partner role to a specific identity lifecycle outcome such as deployment, access review support, or managed operations.
- Tie certification to measurable delivery quality Use partner certification as one input, not the only one.
- Keep decision rights inside the programme Require that approval, exception handling, and policy ownership remain visible to the identity team even when operational work is delegated.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- Role definitions for delivery services, solutions advisory, and growth partners
- Competency structure for managed services and delivery recognition
- Partner portal resources planned for training, certification, and lifecycle tracking
- Program positioning for scaling identity security delivery across enterprise customers
👉 Read SailPoint's Partner Fleet blog on identity delivery and managed services →
SailPoint Partner Fleet: what it means for IAM delivery teams?
Explore further
25/06/2026 3:37 pm
Partner ecosystems are now part of identity governance, not just go-to-market motion. Identity security deployments depend on implementation quality, support quality, and lifecycle follow-through. When a vendor’s partners act as an extension of the platform, the partner layer becomes part of the operational control surface. The implication is that IAM leaders should evaluate ecosystem maturity as seriously as product feature fit.
A few things that frame the scale:
- Companies are dedicating an average of 32.4% of their security budgets to secrets management and code security, with US organisations leading at 40.8%, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the same report.
A question worth separating out:
Q: Who remains accountable when identity operations are outsourced to partners?
A: The enterprise remains accountable. Partners can execute tasks, but the identity team still owns approval, policy intent, and risk acceptance. If accountability is not explicitly retained, outsourcing becomes a visibility problem as well as an operational one, especially during audits or incidents.
👉 Read our full editorial: SailPoint Partner Fleet reframes partner delivery for identity security
