GOVERNATLAS / PRODUCT DOSSIER

SailPoint Identity Security Cloud

SailPoint presents Identity Security Cloud as a suite on SailPoint Atlas, with access recommendations, workflows, role modeling and activity insights. SailPoint certification documentation describes campaign scoping, certifier approval or revocation, remediation and administrator completion; it distinguishes legacy campaigns from a migrating certification engine.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

Where it fits

Ask which suite and certification engine the proposal actually supplies.

The decision to make

Ask which suite and certification engine the proposal actually supplies. The current certification documentation uses Human Fabric branding and describes phased availability, while the Identity Security Cloud page retains its suite description. Those labels should not be treated as a promise of feature parity. Establish the source types and access objects that are certifiable before interpreting a completed campaign as complete coverage.

What this record does not establish

Suite descriptions and the current certification guide are documentary evidence only. Phased functionality, legacy campaign handling and connector-specific remediation require confirmation for the tenant. No universal module entitlement, migration equivalence or compliance outcome is asserted.

2 current sources · 2 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Use a small synthetic source with a direct entitlement, a role-derived grant and an item intentionally excluded from certification. Show the campaign filter, reviewer decisions and resulting target changes. Preserve a legacy campaign report, then ask how that history is accessed under the proposed engine. Include a rejected revocation so campaign completion and remediation completion can be compared explicitly.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. The quoted suite, tenant engine and certifiable-object boundary recorded together.
  2. A reproducible filter-to-decision-to-remediation trace, including excluded access and legacy history.

THE OPERATING DETAIL

Follow the decision into the enforcing system.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Set the operating boundary

The current certification documentation uses Human Fabric branding and describes phased availability, while the Identity Security Cloud page retains its suite description. Those labels should not be treated as a promise of feature parity. Establish the source types and access objects that are certifiable before interpreting a completed campaign as complete coverage.

A proposed buyer demonstration

Use a small synthetic source with a direct entitlement, a role-derived grant and an item intentionally excluded from certification. Show the campaign filter, reviewer decisions and resulting target changes. Preserve a legacy campaign report, then ask how that history is accessed under the proposed engine. Include a rejected revocation so campaign completion and remediation completion can be compared explicitly.

What the evidence does not establish

Suite descriptions and the current certification guide are documentary evidence only. Phased functionality, legacy campaign handling and connector-specific remediation require confirmation for the tenant. No universal module entitlement, migration equivalence or compliance outcome is asserted.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

SailPoint certification documentation describes campaign scoping, certifier approval or revocation, remediation and administrator completion; it distinguishes legacy campaigns from a migrating certification engine.

Source, dates & preserved provenanceSailPoint Identity Security Cloud — current primary scope ↗

Authority: vendor owned
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 50177d2c4bec80657660d2ae2b27f383891a25abcf47218c79438e2c3650b760

The hash identifies the preserved capture. The live source may have changed.

02
vendor asserted

SailPoint presents Identity Security Cloud as a suite on SailPoint Atlas, with access recommendations, workflows, role modeling and activity insights.

Source, dates & preserved provenanceSailPoint Identity Security Cloud — identity or current documentation follow-up ↗

Authority: vendor owned
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 2089eba6e2931c9879f49667dfb9e818c0c89cfac49b22cac394e3b1571c4425

The hash identifies the preserved capture. The live source may have changed.

Source register

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Can you demonstrate and export: The quoted suite, tenant engine and certifiable-object boundary recorded together.

02

Can you demonstrate and export: A reproducible filter-to-decision-to-remediation trace, including excluded access and legacy history.

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗