GOVERNATLAS / PRODUCT DOSSIER

Clear Skye IGA

Clear Skye describes IGA on the ServiceNow platform with identity lifecycle, access requests, reviews and separation-of-duties capabilities. Clear Skye describes a connector framework using SCIM, LDAP and JDBC, alongside ServiceNow connections and credentials for access-related fulfillment.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

Where it fits

Assess the identity workflow within the actual ServiceNow operating model.

The decision to make

Assess the identity workflow within the actual ServiceNow operating model. Existing platform familiarity does not settle license boundaries, upgrade responsibility, privileged integration credentials or separation between requester, approver and fulfiller. Start with the relevant service data and identity ownership rather than assuming every existing ticket contains trustworthy access context.

What this record does not establish

The product page contains generic placeholder FAQ text, which is excluded. Only substantive product and connector descriptions support the assertions. No scale, implementation-speed or comprehensive audit finding is inferred.

1 current source · 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

Create a synthetic joiner and a role change, with one request needing a second approver. Follow the ServiceNow record through approval, connector execution and target observation. Rotate a sandbox integration credential and inspect the failed and retried actions. Ask an independent operator to export the evidence and distinguish a closed request from confirmed deprovisioning.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. The ServiceNow roles, required modules, connector credentials and ownership documented for the proposal.
  2. A request-to-fulfillment trace preserving credential failure, retry and observed target state.

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

Existing platform familiarity does not settle license boundaries, upgrade responsibility, privileged integration credentials or separation between requester, approver and fulfiller. Start with the relevant service data and identity ownership rather than assuming every existing ticket contains trustworthy access context.

A proposed buyer demonstration

Create a synthetic joiner and a role change, with one request needing a second approver. Follow the ServiceNow record through approval, connector execution and target observation. Rotate a sandbox integration credential and inspect the failed and retried actions. Ask an independent operator to export the evidence and distinguish a closed request from confirmed deprovisioning.

What the evidence does not establish

The product page contains generic placeholder FAQ text, which is excluded. Only substantive product and connector descriptions support the assertions. No scale, implementation-speed or comprehensive audit finding is inferred.

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

Clear Skye describes a connector framework using SCIM, LDAP and JDBC, alongside ServiceNow connections and credentials for access-related fulfillment.

Source, dates & preserved provenanceClear Skye IGA — current primary scope ↗

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

Artifact SHA-256: 499f962094aaa27c398e4de9afc57bcc1b3a2fd8f9d7901b213752439e70b346

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

02
vendor asserted

Clear Skye describes IGA on the ServiceNow platform with identity lifecycle, access requests, reviews and separation-of-duties capabilities.

Source, dates & preserved provenanceClear Skye IGA — current primary scope ↗

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

Artifact SHA-256: 499f962094aaa27c398e4de9afc57bcc1b3a2fd8f9d7901b213752439e70b346

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

Source register

Clear Skye IGA — current primary scope ↗vendor owned · captured 2026-10-18
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 ServiceNow roles, required modules, connector credentials and ownership documented for the proposal.

02

Can you demonstrate and export: A request-to-fulfillment trace preserving credential failure, retry and observed target state.

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 ↗