The history of a single access entry
From the first request to revocation
- Event 1RequestWho requested it and with what justification.
- Event 2ApprovalWho approved it and when.
- Event 3ExecutionManual or automatic, with the result.
- Every cycleReviewThe reviewer's decision and the questionnaire.
- In case of changeModificationA new request linked to the access.
- At the endRevocationThe access moves to the archive.
Expert view
A history that can be told backwards
An auditor rarely starts with the process. They start with the result: they pick a dozen or so active access entries and ask for each one to be documented. Who requested it? Who approved it? When was it granted? When was it last confirmed? In an organisation without unified records, answering means searching the mailboxes of several people — provided they still work there.
The audit trail in sara.next is built around the access, not around events. From any active access entry you can go to the request it came from, and on to all the decisions, the execution, later changes and reviews. This makes it possible to answer the auditor's question in the order in which they ask it.
Two kinds of history
The first is the access history — described above. The second, often overlooked, is the configuration history: who changed the rule for determining approvers, who added an application, who started an import. In sara.next changes in the administration panel require a ticket number, and access created by import is flagged as imported, with the approver and justification.
Thanks to this, the answer to the question "where did this access come from" always exists — also for entitlements that were created before the system was implemented.
Scope
What is recorded
| Area | What stays in the history |
|---|---|
| Requests | Request history: statuses, assignments, decisions and comments. |
| Access | Which request the access came from, start and end dates. |
| Reviews | All actions within a review with date and time, changes of reviewers. |
| Import | Input file, result file with errors, approver and comment. |
| Configuration | A ticket number given when saving changes in the administration panel. |
| Notifications | Sending time, recipients and message content. |
| Reports | Who downloaded which report and when. |
Archive
Revoked access does not disappear from the records
Archived access
Searchable by application, role and attributes, with the end date.
Archived users
The access history of people who no longer work in the organisation.
Data versioning
Changes to database records are saved, which makes it possible to restore an earlier state.
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.