Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. Platform security

Technology · Security

Platform security

A system that manages access to other systems must itself be controllable. Below are the mechanisms built into the architecture.

  • from working documentation — to be approved

Security model

Four pillars

01

Federated authentication

Sign-in through an external identity provider; the application does not store passwords.

02

Authorisation

Roles, role permissions and rules for access to application resources.

03

Communication protection

HTTPS in production environments: confidentiality and integrity of data.

04

Data access control

Data visible according to role: user, manager, compliance, administrator.

Expert view

Who watches the system that watches access

An IGA system is an attractive target: it holds a complete map of the organisation's entitlements and can change them. Security teams rightly ask not only what the platform controls, but also how it is itself controlled.

The answer has three layers. The first is access to the application itself: sign-in via the identity provider and role-based authorisation. The second is integrations: all connections to target systems originate from the backend, each application has its own token, and technical accounts should have only the scope needed for the defined operations.

The third layer: administrator accountability

The hardest question is: what can the platform administrator do and how will we know about it? In sara.next configuration changes require a ticket number, record changes are versioned, and application events go to logs that can be forwarded to the organisation's monitoring systems.

We also recommend a simple organisational practice: administrative permissions in sara.next should be subject to the same periodic review as all other access.

Integrations

Integration credentials under control

Integration models

Principles

  • All integrations are handled by the backend — the browser does not connect to target systems
  • Each application using auto-implementation has its own token, which can be renewed or deleted
  • Configuration parameters can be stored in encrypted form
  • Sensitive configuration data — in the environment's secrets management mechanism
  • Technical integration accounts with the minimum scope of permissions

Accountability

Changes in the system leave a trace

Data change history

Record modifications are versioned, which makes it possible to restore an earlier state.

Ticket number

Changes in the administration panel require a ticket number.

Notification log

Sending time, recipients and content of every message.

Maintenance

Monitoring and diagnostics

Application health

Technical endpoints for monitoring systems to check operation.

Performance

Request and database query times, memory usage, active sessions.

Logs

Application events with logging levels — for diagnostics and security event analysis.

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.