Identity Governance & Administration
sara.next

Identity Governance & Administration

An IGA system in which every access has an owner and a history

sara.next is an IGA (Identity Governance and Administration) platform that puts identity and access management in order across the whole organisation: from the request and approval, through automatic execution of the change in the target system, to the review and the audit trail.

  • Active Directory
  • LDAP
  • REST
  • Graph API
  • SCIM
  • SQL
Access requestlifecycle
Request
access grant · project team
submitted
Resource
Microsoft Teams › project group
group
Approval
manager · application owner
2 / 2
Execution
auto-implementation · REST
executed
Verification
state in the system = decision
consistent
Timing
time-bound access · automatic revocation
90 days
Trail
request → decision → execution → result
recorded
Illustrative diagram of the request flow. This is not a product screenshot.
  • Process

    From request to verification

    One workflow for granting, changing, swapping the user of and revoking access.

  • Integrations

    Six integration models

    From manual handling to full auto-implementation — separately for each application.

  • Governance

    Access reviews

    Periodic confirmation of permissions by the people responsible for them.

  • Audit

    A full audit trail

    The request, decision, execution and operation result recorded in the history.

Who it is for

Find the path for your organisation

A company with two hundred employees and a public office with several dozen systems start differently from a global group. Answer three questions — we will show you where to start.

All paths
1. Type of organisation
2. Number of identities
3. Number of systems

Commercial company · 500 – 5,000 identities

Put roles and application owners in order

With several thousand identities the problem is no longer the lack of a tool, but scattered responsibility. The key is to designate application owners and the rules by which the system itself finds the decision-maker.

  1. Define roles and scope attributes for the main applications
  2. Calculate approvers from rules instead of entering them manually
  3. Automate access in the systems with the most traffic

The most common reasons: an external audit, SOX or NIS2, the cost of unused licences and the speed of onboarding new employees.

With several dozen systems, divide them into groups: automation for the most frequently changed ones, import and reviews for the rest.

The numerical thresholds are indicative — they help choose a starting point and do not define the limits of the product.

Scale

Proven in global organisations

sara.next is used by employees of global companies subject to SOX controls. The platform itself successfully passes audits by "Big Four" audit firms.

See our implementations
ABB Ltd
140k

identities

Hitachi Energy
60k

identities

How it works

Three steps to order in access

  1. Connect data sources

    Connect sara.next with Active Directory, LDAP and business applications. Data about users, roles and access goes into one register.

  2. Configure rules and policies

    Specify who should have access to what and on what terms — by role, department, location or position.

  3. Manage and monitor

    Approve requests, view reports and run reviews from one place. You can see who has access, when and why.

Solutions

For everyone responsible for access

Security, IT, audit and the business work on the same data, each within their own scope.

For technical teams

Integration matched to the capabilities of each application

Not every system has an API for managing permissions. That is why sara.next works in six models — you can start with records and import, and automate gradually.

  • A queue of auto-implementation tasks once approval is complete
  • Verification that the state in the system matches the decision
  • Handover to manual handling when an operation fails
  • Integration accounts with a minimum scope of permissions
sara.next integration levels
LevelModelScope
L0Manual handlingThe process, approvals, history and reviews in sara.next; the change is made manually.
L1Initial importLoading the current state of an application's access.
L2Dictionary synchronisationRoles, departments, locations, projects from source systems.
L3REST auto-implementationREST, Graph API, SCIM.
L4SQL auto-implementationSQL, procedures, permission tables.
L5Adapter / middlewareA REST adapter for non-standard systems.

Partners

We implement together with integrators

sara.next is available through a network of cybersecurity partners.

Meet our partners
  • Apius Technologies
  • xSecures
  • VIDA
  • Perceptus

See sara.next on your own scenarios

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