Appearance
SoD rule sets
Also known as
- SoD rules
- segregation of duties
- conflict matrix
- SoD matrix
- ruleset
- conflicting permissions
- enforcement
- block
- warn
- permission pair
Rule sets hold the segregation-of-duties rules: pairs of permissions that one person should not hold together, each with a risk level. The rule set decides whether a conflicting role assignment is only flagged or refused.
See a rule set and its rules
- Open ComplianceSegregation of duties and select the Rule sets tab.
- Select a rule set on the left. Each shows its code, number of rules and open violations, and its enforcement.
- On the right you see Enforcement, Active and Open violations, and the Rules table with each rule's code, name, conflicting permissions, risk, open violations and whether it is active.
A permission marked (not in catalogue) does not exist in this installation, for example because its module is not enabled. The rule then never matches.
Create a rule set
- Select New rule set.
- Fill in the fields and select Save rule set. You see "Rule set P2P saved".
| Field | What to enter | Required |
|---|---|---|
| Code | A short code, up to 40 characters, such as P2P. Stored in capitals. | Yes |
| Enforcement on role assignment | Off, Warn or Block. Block refuses unmitigated conflicts; warn logs and notifies. | Yes (default Warn) |
| Name | Such as "Procure to pay". | Yes |
| Description | What the set covers. | No |
| Active | Off to stop using the set's rules. | Default on |
Add a rule
- Select the rule set, then Add rule.
- Fill in the fields and select Save rule.
| Field | What to enter | Required |
|---|---|---|
| Code | Such as P2P-01. | Yes |
| Risk | Low, Medium, High or Critical. | Yes |
| Name | Such as "Maintain vendors and pay them". | Yes |
| Permission A | A permission key such as procurement.vendor.manage, or a wildcard such as finance.payment.*. | Yes |
| Permission B | The conflicting permission. Must differ from permission A. | Yes |
| Description | Why the two duties conflict. | No |
| Active | Off to pause the rule. | Default on |
A user or role holding both permissions, directly or through wildcards such as finance.*, violates the rule. If a key is not valid you see "A permission key such as finance.payment.create or finance.payment.*".
Edit or delete
- Select Edit on the rule set, or the pencil icon (Edit rule) on a rule.
- Select Delete on the rule set, or the bin icon (Delete rule), and confirm. Deleting a rule removes its mitigations and violations; deleting a rule set removes all its rules, mitigations and violations.
Run the analysis after you change rules: see Segregation of duties.
Differences by role
- You need Permission:
compliance.sod.manageto create, edit and delete rule sets and rules.
