Identity Governance & Administration
sara.next
  1. sara.next
  2. Platform

Platform

Identities, access and evidence in one system

sara.next covers the entire access lifecycle: who requested it, who approved it, whether it was actually granted and when it was last confirmed as needed.

The access lifecycle

Five stages, one record

Every stage leaves a trace linked to the same request. As a result the history of access can be reconstructed without searching through mailboxes and spreadsheets.

  1. Request

    A user or an authorised person files a request to grant, change, swap the user of or revoke access.

  2. Approval

    The request goes through an approval workflow in line with the requirements of the organisation and the application owner.

  3. Execution

    The approved change goes into the queue and is executed in the target system — automatically or manually.

  4. Verification

    sara.next checks whether the expected state has been reached, e.g. whether the user has been added to the group.

  5. Review

    Access periodically comes back for confirmation. A negative decision triggers revocation.

Area 01

Identity management

IGA-11

Identity lifecycle

Joining, changing position, leaving.

IGA-12

Identity sources

Active Directory, LDAP, HR systems.

IGA-13

External identities

Contractors, suppliers, partners.

scope to be confirmedin progress
IGA-14

Technical and service accounts

The owner and purpose of every account.

scope to be confirmedin progress

Area 03

Governance and compliance

Scope

Not just applications

The same process — request, approval, review — can cover any resource to which access should have an owner and a history.

Applications

Company systems

Finance, HR, warehouse, sales, project systems.

Data

Drives and shared spaces

SharePoint, Dropbox, Google Drive and similar.

Services

Accounts and subscriptions

Bank accounts, web applications, subscriptions to portals and services.

Physical access

Buildings and zones

Rooms, server rooms, warehouses — after the configuration is adapted.

What sets sara.next apart

A decision is not the same as execution

In many organisations the access process ends when the request is approved. Between approval and the change in the application there remains manual administrator work, delays and no confirmation that the state in the system matches the decision.

How auto-implementation works

Less manual work

Repetitive granting and revoking of access is carried out by the integration.

Fewer errors

Decisions don't have to be retyped manually into many systems.

Greater control

The change is linked to the request, the decision and the approver.

Better auditability

The history of decisions, execution and verification serves as control evidence.

See sara.next modules in action

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.