- sara.next
- Technology
- Version support cycle
Technology · Documentation
Version support cycle
For an IGA system, version support is part of operational risk management: it affects the security of the access process and the ability to maintain continuity of control.
- maintenance
- security fixes
- migration planning
- from working documentation — to be approved
Context
What a supported version means
An access management system operates in an ecosystem of dependencies — the browser, the database, the runtime environment, the SSO provider and the target systems. A new release does not in itself guarantee compatibility with each of these elements. An organisation needs to know which versions are supported, how it receives critical fixes and when it should plan an update.
The model below presents a recommended support policy. braf.tech provides maintenance and support for sara.next.
NoteThis page does not set public, binding support periods, an EOL calendar or a guaranteed time for delivering fixes. The SLA scope and response times follow from the offer and the contract with the client.
Phases
Proposed lifecycle phases
| Phase | What it means operationally | What needs to be agreed |
|---|---|---|
| Current / active | The main line of development, fixes and functional changes | The scope of support and how changes are qualified |
| Maintenance / maintained | Stabilisation and qualified bug and security fixes | Which fixes are backported |
| End of Support | End of standard support for the version | The communication deadline and the migration path |
| Extended Support, if offered | Individual support after the standard phase ends | Scope, exclusions, period, cost — by contract only |
A proposed model. The phases do not constitute a binding product support policy.
Agreements
Agreements relevant to IT and cybersecurity
Security support
How vulnerabilities are assessed, the availability of fixes and communication procedures in the event of a critical issue.
Environment compatibility
The matrix of supported DB, Java/runtime, IdP and browser versions should be based on the current release, not on historical descriptions of the stack.
Configuration migration
The impact of the update on roles, dictionaries, workflows, review schedules, reports and Groovy scripts.
Client integrations
Responsibility for adapting dedicated connections if the APIs of the target systems change.
Deployments with elevated criticality
Maintenance windows, UAT, a recovery scenario and a rollback plan.
Incident handling
How escalation, classification and the handover of workarounds work, depending on the maintenance contract.
Example
Planning an update in a financial institution
The institution plans the update between quarterly review cycles. First it identifies application-specific configurations and tests all critical paths: creating a request, approval, auto-implementation and state checking, carrying out a recertification and generating audit evidence. The implementation team documents the test results and the recovery plan before deciding on the production change.
- TimingBetween review cycles
- Step 1Application configurationsIdentifying specific settings.
- Step 2Testing critical pathsFrom the request to the audit evidence.
- Step 3Test results and recovery planDocumented by the implementation team.
- Step 4Decision on the production change
An implementation expert's view
A security fix is not the same as a functional update
In an IGA project I would not recommend automatically updating production just because a new version is available. The key is to separate a security fix that requires urgent action from a functional update that can wait until the review campaign is over.
In both cases responsibility for integration testing must be clearly assigned.
Plan the maintenance and updating of sara.next
Based on your organisation's architecture, risk and control calendar.