Approval workflow before publishing a business rule
J
Jeroen Smit
Problem
Business rules in HelloID Provisioning determine who gets which accounts and permissions, but they are reviewed and approved outside HelloID (email, meetings, tickets). HelloID does not record who approved a rule, when, or which version. An administrator can also create or change a rule and publish it without a second check.
Desired behavior
When a business rule is created or changed, HelloID starts an approval workflow. The rule is only published after a designated approver, such as the application owner, has approved it. The approver can see what has changed and which persons fall within the scope of the rule, so they can decide whether these persons may receive the entitlement. The approval or rejection is recorded in the audit log, including who approved, when, and which version.
The person who created or changed the rule should not be able to approve it. Organizations should be able to choose where this approval is required.
Why
Frameworks such as ISO 27001, NEN 7510, BIO and NIS2 require access to be granted under an approved policy, with segregation of duties and traceable changes. Business rules are that policy in HelloID, so the approval should take place and be logged in HelloID itself. This gives auditors direct evidence, involves the business owner in access decisions and reduces the risk of unauthorized or incorrect changes.