GOVERNATLAS / PRODUCT DOSSIER

Lumos Access Reviews

Lumos describes campaigns scoped by applications, owners and frameworks, using entitlement-level context and prior decisions. Lumos describes rejected-access revocation, guarded exceptions, ITSM tracking and evidence reports within its access-review workflow.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

Where it fits

Evaluate the campaign as a sequence of decisions and downstream changes, rather than a faster way to approve a list.

The decision to make

Evaluate the campaign as a sequence of decisions and downstream changes, rather than a faster way to approve a list. A useful reviewer needs the provenance and collection time of an entitlement, its business owner and the reason it remains necessary. Ask how account-level removal differs from removing one entitlement, and how the proposed integrations represent unmatched identities and non-human accounts.

What this record does not establish

The reviewed page supplies vendor assertions, including AI recommendations and automation. Its speed, saved-hours and audit-readiness statements are excluded as GovernAtlas findings. Current edition, integration permissions and retention need proposal-specific evidence.

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

Build a synthetic campaign with one employee, one service account and one account without a current owner. Retain one permission, reject another and record an exception with a named expiry. Interrupt the sandbox revocation workflow and compare the campaign status, ITSM handoff and connected-system permission. Restore the connector and check whether retries create duplicate actions or preserve the original decision.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A campaign manifest with snapshot time, entitlement provenance and reviewer ownership.
  2. Separate evidence for the review decision, queued action, effective removal and unresolved exception.

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

A useful reviewer needs the provenance and collection time of an entitlement, its business owner and the reason it remains necessary. Ask how account-level removal differs from removing one entitlement, and how the proposed integrations represent unmatched identities and non-human accounts.

A proposed buyer demonstration

Build a synthetic campaign with one employee, one service account and one account without a current owner. Retain one permission, reject another and record an exception with a named expiry. Interrupt the sandbox revocation workflow and compare the campaign status, ITSM handoff and connected-system permission. Restore the connector and check whether retries create duplicate actions or preserve the original decision.

What the evidence does not establish

The reviewed page supplies vendor assertions, including AI recommendations and automation. Its speed, saved-hours and audit-readiness statements are excluded as GovernAtlas findings. Current edition, integration permissions and retention need proposal-specific evidence.

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

Lumos describes rejected-access revocation, guarded exceptions, ITSM tracking and evidence reports within its access-review workflow.

Source, dates & preserved provenanceLumos Access Reviews — official access review scope ↗

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

Artifact SHA-256: c4437d3c767502e57047bf7a4d94ef7abbf31b910b0ff112fbc2c8305e62d087

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

02
vendor asserted

Lumos describes campaigns scoped by applications, owners and frameworks, using entitlement-level context and prior decisions.

Source, dates & preserved provenanceLumos Access Reviews — official access review scope ↗

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

Artifact SHA-256: c4437d3c767502e57047bf7a4d94ef7abbf31b910b0ff112fbc2c8305e62d087

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: A campaign manifest with snapshot time, entitlement provenance and reviewer ownership.

02

Can you demonstrate and export: Separate evidence for the review decision, queued action, effective removal and unresolved exception.

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 ↗