Plan
Six stages of implementation
- Stage 1Process audit
- Stage 2Application requirements
- Stage 3Process design
- Stage 4Platform configuration
- Stage 5Training
- OngoingService and support
Expert view
Why we start with the process, not with installation
Installing sara.next takes little time. What determines the success of an implementation happens earlier and is not technical: establishing who in the organisation is responsible for which applications, what roles exist in them and who has the right to decide on access.
That is why the first stage is a review of the current process. If a process exists, we describe it and point out where it leaves no trace. If it does not exist, we design it from scratch. braf.tech works in an advisory and technology model: we supply the tool, but we also help adapt it to the specifics of the organisation.
The role of application owners
The most important participants in the project are not IT staff but the people responsible for applications on the business side. They know which roles make sense and who should approve access. Gathering these requirements — and documenting them — is a separate stage that should not be cut short.
After go-live we stay: service, support lines and help during external audits are part of the offering, not an add-on.
Stages
From a process audit to support during audits
Process audit
A review of current access management and recommendations for improvement. Where there is no process, we design it from scratch.
Application requirements
Gathering requirements from the owners of the applications that are to be covered by sara.next.
Process implementation
Defining roles, approvers and review rules.
Platform configuration
Tailoring sara.next: applications, roles, workflows, notifications, reports.
Training
For users, administrators and people responsible for compliance.
Service and support
L2, L3 and L4 support lines and help during external audits.
Integrations
Automation at your own pace
You do not have to automate everything at once. Applications can be covered by records and reviews, and integrations switched on gradually.
Integration modelsTypical order
- Choosing 2–3 pilot applications
- Analysing the permission model and confirming interfaces
- Importing the initial state and cleaning up dictionaries
- Configuring auto-implementation, testing and a pilot
- Extending the scope to further applications
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.