Auditor's questions
Where the answer is in sara.next
| Question | Source of the answer |
|---|---|
| Who has access to this application? | Application user list report; searching active access by role and attributes. |
| Who approved this access? | The history of the request from which the access was created. |
| Is access verified periodically? | Review cycle configuration, reviewer decisions, questionnaires. |
| What happened to unconfirmed access? | Removal requests generated after the review ended. |
| Who changed the process configuration? | The ticket number assigned to changes in the administration panel. |
| What access did a person who left have? | Access archive and archived users. |
Expert view
An entitlement audit is won a year before the audit
Organisations usually prepare for an audit a few weeks before the date: they gather lists, ask managers for confirmations and clean up obvious irregularities. This approach has two flaws. First, evidence produced just before the audit is less credible to the auditor than evidence created in the course of work. Second, the whole effort has to be repeated a year later.
The alternative is a process in which evidence is a by-product of normal work. A request approved in the system is evidence of approval. A review completed with a questionnaire is evidence of a review. A removal request generated after the deadline is evidence of consequences.
Three things auditors ask about most often
- Completeness: how do you know that the list covers all access, not just what someone reported?
- Independence: was the person confirming the access different from the person using it?
- Timeliness: how much time passed between an employee leaving and their access being revoked?
Each of these questions is easier to answer when the records were created from an import approved by the application owner, reviewers are determined by rules, and events have dates.
Experience
A platform that passes audits itself
sara.next does not just help meet control requirements — it is itself successfully audited by Big Four audit firms, because it supports processes in the compliance units of finance departments.
- Types of controls
- SOX
- Review cycle
- quarterly
- Support
- L2–L4
as well as internal and external audits
for most applications; configurable
also during external audits
Next
The mechanisms the audit relies on
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.