- sara.next
- Technology
- Integration accounts
Technology · Security
Integration accounts
The IGA technical account can grant and revoke access. It should therefore have a strictly defined scope of action that can be audited and limited.
- REST
- SQL
- least privilege
- credentials
Context
Why integration accounts need a separate policy
The identity of the user filing the request and the technical identity making the change in the target system serve different functions. The first is part of the business process. The second has permissions for administrative operations, so compromising it can have consequences for many accounts or resources.
The sara.next documentation describes the configuration of SQL connections (including the JDBC URL, login and password) and REST connections (base URL, authentication method and credentials). For REST the None, Basic, Bearer and API Key modes are listed. The auto-implementation mechanism uses the configured connection, runs the script and can verify the result.
Connections are defined in the administration panel (Administration → Configuration → SQL Connections and REST Connections) and then specified in the application's auto-implementation configuration.
The big picture
Two identities in one process
01 · Business process
- Requesteruser identity
- Approveraccess decision
02 · sara.next
- REST or SQL connectionconfigured credentials
- Implementation scriptexecutes the approved change
- Verificationoptional result check
03 · Target system
- Integration accountadministrative operations
- Operation logtrace of the change being executed
correlation with the request identifier
Pattern
A pattern for configuring a secure account
A dedicated identity per system and environment
Separate production accounts from test accounts; do not use a personal administrator account.
A minimum set of operations
When the API only allows managing membership of one group, do not give the account a global administrator role.
Network restrictions
Access to endpoints and ports only from the required segments and through agreed network channels.
Credentials
Decide where they are stored, how they are protected at rest, the rotation rules and the revocation procedure. Using a vault or secrets manager requires an analysis of the specific deployment — we do not claim this feature as built in.
Accountability
Correlate the request identifier with the operation log in sara.next and in the target system. Separate the approver from the account performing the operation.
Change management
Test the new account's permissions in a non-production environment and record the justification for granting the privileges.
Comparison
REST and SQL — different risk profiles
Scope limited to the API
REST usually makes it possible to limit permissions to a specific API scope. However, the authorisation scope depends on the target system; using a Bearer token alone does not prove security or automatic token rotation.
SQLFlexibility that calls for caution
SQL offers flexibility for integrating with applications that have no API, but requires particular caution. Restricted procedures or a dedicated database interface should be preferred over an account with broad DDL/DML permissions. Parameters coming from requests must be validated and handled safely before being inserted into SQL statements.
Controls
The control model for integration account permissions
| Control | Recommended evidence |
|---|---|
| Account owner | System name, technical and business owner |
| Entitlements | An approved list of operations, endpoints and tables |
| Secret rotation | Procedure, frequency, execution trace |
| Access restrictions | Network rules, TLS, connection policy |
| Monitoring | Alerts for authorisation errors and unusual activity |
| Emergency revocation of permissions | A tested revocation scenario that does not block the other integrations |
An implementation expert's view
The temptation of a single "super account"
With IGA integrations the most common temptation is to create a single "super account" that can do everything. It makes the pilot easier, but makes the later audit harder and increases the blast radius of an incident.
In the target design, the scope of permissions of the technical account should follow directly from the catalogue of script operations, not from the integrator's convenience.
Scope
What sara.next provides and what depends on the environment
Documented
- definitions of REST/SQL connections and the mechanism that invokes implementation,
- configuration of different REST authentication types.
To be agreed and verified during implementation
- native integration with a specific vault,
- automatic secret rotation,
- mTLS,
- isolation of secrets in logs,
- the scope of administrators' internal permissions,
- an exact audit trail of access to credentials.
Verify the permission model for integration accounts with us
We will choose the narrowest possible technical roles for your target systems.