Identity Governance & Administration
sara.next
  1. sara.next
  2. Platform
  3. Reporting and audit

Platform · Oversight and compliance

Reporting and audit

A single source of truth about access, roles and decisions — for internal controls, external audits and SOX.

Reports

A report for the auditor's question

Configurable reports

The administrator defines a report and its parameters, e.g. application, quarter and year.

Role-based access

Reports can only be downloaded by people with access to the manager panel or the compliance panel.

Applications under control

List of applications taking part in reviews, including those flagged as SOX.

Requests and their status

Current and completed access requests for the selected application.

Readable layout

Access attributes split into separate columns, with their own names and order.

Moving between environments

Report definitions can be exported and imported.

Expert view

A report should answer a question, not dump data

A typical auditor's request reads: "please provide a list of people with access to system X as of date Y, with information on who approved the access". A typical organisation's answer is three files from three sources that have to be combined by hand. This takes days, and the result still raises doubts because its completeness cannot be demonstrated.

The value of reporting in an IGA system comes from the fact that data on access, decisions and reviews sits in one place and is linked together. A report is then not a compilation — it is a view of the records.

Who can download a report

This question is asked too rarely. A list of all entitlements in an organisation is itself sensitive information. In sara.next reports are available only to designated roles, and the download history shows who downloaded what and when.

A practical tip: before you define your own reports, ask the auditor what they will need a year from now. Most needs come down to a few recurring reports — it is worth having them ready before the audit, not during it.

Audit trail

Who, what, when and on what basis

What stays in the history

  • The request, the approvers' decisions and the implementation result
  • Review actions — with date and time
  • Configuration changes — each with a ticket number from the ticketing system
  • Access created by import — flagged as imported
  • Notifications sent: time, recipients and content
  • History of data modifications in the database

Who it is for

Three perspectives on the same data

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.