Types of authorization workflow

Two types of authorization are available within Bravura Security Fabric ’s workflow engine:

Static authorization is simple to configure, but requires manual maintenance. In Bravura Identity implementations, it is usually sufficient for small to medium-size organizations, where a small number of employees are responsible for reviewing and authorizing requests to access a resource. In Bravura Privilege implementations, Bravura Privilege Pattern makes it easier to use team management (which uses dynamic workflow).

In large enterprise environments, the selection of resource authorizers is more complex. Static authorization is not feasible; the maintenance required would make it impractical. Dynamic authorization addresses this challenge and also offers more flexibility in how the workflow is configured. Many businesses implement a combination of both static and dynamic authorization. You can apply relational user classes and security rules so that the authorizer is determined by the type of request, the resources associated with the request as well as who is making the request (and for whom).

You can also use plugins to dynamically assign authorizers instead of, or in addition to, static authorizers. In some enterprise environments, the authorization process is serial; for example, the request is first reviewed by the employee’s manager, followed by a security group member or resource owner. The authorization engine is flexible enough to accommodate most authorization scenarios.