Identity Governance & Administration
sara.next
  1. sara.next
  2. Solutions
  3. The principle of least privilege in practice

Solutions · By need

The principle of least privilege in practice

How to limit excessive roles through parameterisation, approval and recurring reviews.

  • least privilege
  • roles with dimensions
  • validators and limits

Context

Least privilege requires a detailed permission model

The principle of least privilege means granting only the access needed to perform a specific task. The problem arises when an application offers a few broad roles and the organisation does not control their actual scope.

sara.next lets you define roles with additional dimensions, such as organisational unit, region, resource or level of operation. Dictionaries, dependencies and validators make it possible to limit invalid combinations of values, and the approval process introduces business control.

Example

Database access

Instead of being granted a general administrator role, the user requests a permission for a specific database and a selected set of operations. The dimensions can be the database name and the permission level. For SQL systems, automatic implementation and verification of the target state can be prepared.

01 · Instead of

  • A general administrator rolebroad scope, hard to justify

02 · A role with dimensions

  • Dimension: database namea specific database
  • Dimension: permission levela selected set of operations

03 · SQL systems

  • Automatic implementationprepared scripts
  • Verificationtarget state

requires preparation and testing

Illustrative diagram. Designing the scripts requires rigorous validation of parameters and of the permissions of the technical integration account.

An implementation expert's view

Fewer roles, better-designed dimensions

Least privilege is not about multiplying thousands of micro-roles. In practice a limited number of understandable business roles with controlled parameters works better.

Well-designed dimensions limit the growth of the role catalogue while preserving the granularity of permissions.

Scope

Limits of the solution

Notesara.next supports enforcing least-privilege principles, but it is not automatically a PAM system, JIT access or an engine for full analytics of effective permissions in every system.

Automatically detecting all SoD conflicts and excessive permissions requires the rules and the scope of data and integration to be confirmed.

See how to design a role catalogue without uncontrolled growth

During a technical consultation we will go through your applications, roles and the scope of the first implementation stage.