Entitlements

The concept of data ownership is a concept that can be defined as follows: The data should only be shown to users authorized to view it. Examples would be a data policy that keeps Client and Advisor information segregated and confidential as a default security setting.

Permission management is a set of practices that provides, resolves, enforces, revokes, and manages detailed access rights. These rights are also called authorizations, privileges, access rights, permissions, or rules. Its purpose is to execute data access policies in a structured and unstructured way. Rights management can be done using different methods and is generally different between platforms, applications, network components, and devices. Some sources of rights are:

  • Delimited local context data
  • Shared monolith data context
  • Business domain data
  • Centralized access rights service

The concepts of authorization and rights are closely related and with access control. They both have characteristics that can overlap. That is, authorization and entitlement can have some matching properties. The authorization can be understood as a restriction or prescription formula for access control, while the right is an explicit list of the user’s right to access.

In general, the applications are mainly focused on rights. However, there are several reasons for a division between authorization and entitlement. It is more efficient to manage rights by applying authorizations because it is simpler to modify formulas than explicit lists.

Authorization vs. Entitlement: The main differences

  • Authorizations are easier to apply.
  • Generally, the rights can be determined in the context of the application.
  • Authorization is less dependent on business context than law.
  • Authorizations and rights may have a limited and different time.
  • Authorizations and rights require other data structures and abstraction models.
  • Authorization and entitlement designs are evolving in different directions.
  • The common use of authorizations and rights in a single application often results in a difficult-to-manage system with poor performance and a limited interface, such as inherited permissions.
  • The separation between the two types allows us to benefit from isolation, autonomy, sole responsibility, exclusive status, and mobility.

A rights service is a service specially designed to provide rights. Provide only the data necessary for the rights and nothing else. The same entitlement service can provide different types of entitlements. The entitlement service always allows entry with authorization prescription, while the enterprise domain service can optionally accept authorization filters or allow clients to perform authorization post-filtering. The factors that drive entitlement service are the possibility of policy reuse by multiple applications, which provides the ability to deliver a sufficient volume of data without any other suitable solution. The entitlement service may or may not own the DevSecOps platform or group as part of the core security solution.

 

Satori logo2 white