The Atlas take.
Atlas judgment: SailPoint Human Fabric, the current public destination for Identity Security Cloud, belongs in an identity-governance evaluation rather than a basic SSO comparison. Its value is connecting identity and entitlement information to lifecycle, requests and certification decisions. The decisive dependency is application integration: a manager approving or revoking access in a campaign is useful only when the underlying entitlement is accurately represented and the change reaches the target. Start with a few difficult applications and reconcile reality before scaling the program. Treat adjacent machine, agent and cloud entitlement capabilities as separately scoped additions to workforce governance.
02 / DEFINE THE BOUNDARY
What you are actually evaluating.
Current public naming also uses Human Fabric and describes its relationship to Identity Security Cloud. Existing customer editions and migration requirements still need contract-specific verification. This profile is identity governance, not workforce single sign-on.
Names you may encounter IdentityNow. Historical names do not establish current feature equivalence.
03 / THE CONTROL PATH
Where it sits. How it works.
Source integrations aggregate identity and access data, governance policy supports requests and reviews, and provisioning or fulfillment changes target access.
- 01
Sources and correlation
Application sources supply account and entitlement information that must map to the correct identity.
- 02
Governance decisions
Roles, access profiles and certification campaigns organize requests and review decisions.
- 03
Fulfillment and evidence
Supported provisioning or assigned remediation implements approved changes, with target-side verification closing the loop.
04 / WHAT EARNS ITS PLACE
Strengths, with the evidence attached.
Atlas analysis of documented capabilities; availability and behavior depend on the edition and environment.
Source management is explicit
The source guide documents managing application connections and the account/access data on which governance depends.
Certification has a defined workflow
Certification documentation provides a concrete review mechanism to test with managers and application owners.
Inspect the documented capability notes
- Lifecycle, certifications, and separation-of-duties rules review whether standing access to applications and entitlements is still justified.
- Discovery and governance modules examine entitlement sprawl; verify just-in-time access patterns against the selected connectors.
- Cloud infrastructure entitlement and non-employee modules exist as adjacent coverage; confirm which edition your tenant actually includes.
05 / KNOW THE COMPROMISES
The tradeoffs to take seriously.
Architectural implications and procurement questions from Atlas; these are not independently measured product failures.
Aggregation is not enforcement
Atlas would verify whether each connector can read, change or remove the required entitlement rather than infer write support from discovery.
Brand breadth can exceed the core program
Human Fabric positioning spans broader identity coverage; the quote should identify the capabilities actually required for workforce governance.
06 / FROM PURCHASE TO PRACTICE
Make it work in your environment.
A proposed implementation sequence. Confirm supported versions, permissions, and rollback with the current documentation.
- 01
Establish identity and entitlement ground truth
Reconcile authoritative people records and application accounts, including contractors, orphan accounts and shared identities.
- 02
Pilot a meaningful certification
Use one application with understandable access descriptions and reviewers who can justify each decision.
- 03
Prove fulfillment and failure ownership
Verify target-side removal, detect unsuccessful changes and assign remediation to application owners before expanding campaigns.
07 / THE OPERATING COMMITMENT
The bill is only part of the cost.
Commercial shape
Obtain an identity-and-module proposal tied to the application integration plan, including any virtual-appliance and implementation duties.
- Governed identity population and selected modules
- Application connectors and lifecycle/fulfillment scope
- Data cleanup, reviewer operations and integration services
08 / COMPARE THE JOB
Put these beside it.
Alternatives worth examining for the same problem. Check each offering’s scope before treating it as a substitute.
Saviynt Identity Cloud
Compare another cloud identity-governance program using the same account correlation and revocation tests.
OracleOracle OCI IAM / Identity Governance
Compare the governance portion of Oracle’s portfolio where Oracle application entitlements dominate the program.
09 / MAKE THE DECISION OBSERVABLE
Earn confidence through a real evaluation.
Suggested by Atlas. Agree acceptance criteria, use synthetic fixtures in an authorized environment, and capture both useful work and failed controls.
- TEST 01
Find an orphaned entitlement
Acceptance evidence: Seed a fictional unowned account and preserve source aggregation, correlation decision and reviewer-visible context.
- TEST 02
Close a revoked access loop
Acceptance evidence: Revoke an approved lab entitlement in a certification and retain target-side proof of removal plus failure handling.
- TEST 03
Test a mover without access accumulation
Acceptance evidence: Change a synthetic worker’s role and prove required new access arrives while obsolete access is removed or explicitly reviewed.
START WITH ONE EXERCISE
In a SailPoint lab tenant, import a synthetic employee with an extra finance entitlement, launch a certification, revoke the extra entitlement, and re-read the application.
Evidence to look for: The certification record shows the revoke decision, and the connected lab application no longer lists that entitlement for the synthetic user.
Questions to bring to the vendor
- Which current offering and edition does the proposal specify, and are any actual migration requirements documented?
- For each in-scope application, does the connector both read entitlements and revoke them, or only list accounts?
- How are just-in-time or zero standing privilege claims demonstrated on a real connector rather than a brochure?
10 / SHOW THE WORK
Evidence, and what is still unknown.
What this research cannot establish
- No independent connector-completeness, access-removal timing or reviewer-effort benchmark was performed.
- Confirm exact Human Fabric packaging, write capabilities and virtual-appliance requirements for the chosen sources.
Dossier research reviewed October 18, 2026. Earlier profile references are retained for traceability; products and commercial terms change.
- SailPoint Identity Security Cloud ↗Earlier profile reference
- SailPoint Human Fabric current product scope ↗Product information
- SailPoint source management ↗Documentation
- SailPoint certifications ↗Documentation
KEEP BUILDING YOUR JUDGMENT