Skip to main content

Segregation of duties

Segregation of duties, right under Overview in the Nomasx-1 menu, follows the conflicts the SoD matrix finds in the access of every connected application: how many, which risks, which roles cause them, which conflicts were actually exercised, and how it evolves from one refresh to the next.


At a glance​

Segregation-of-duties monitoringPERIODLast 12 months ▾APPLICATIONAll ▾Users in conflictAt the latest refresh373 privileged · refreshed 2026-10-28Conflict linesUser × risk × activity pair1,20418 risks hit in 4 processesProven by activityBoth activities actually used941 proven conflict linesRoles involvedOne side of a conflict2631 role pairsConflicts per refreshBy risk levelRisks hitMost users first; the dot is the risk levelCreate a supplier and pay itProcure to pay14 usersPost and approve journal entriesFinance9 usersChange prices and invoiceOrder to cash6 usersReceive and adjust stockInventory3 usersApplication filterAll = the totalsProvenboth activities usedTrendby risk levelRisks hitthe dot is the level

The bar​

The Period — Last 12 months when the page opens — applies to the trend chart. Application: All gives the totals across the applications; picking one narrows every widget to it. Excel and PDF export the page as it stands.


The four figures​

CardFigureDetail line
Users in conflict — at the latest refreshThe users carrying at least one conflict.The privileged ones, and the date of the latest refresh.
Conflict lines — user × risk × activity pairEvery conflict found.The risks hit and the processes concerned.
Proven by activity — both conflicting activities actually usedThe users who used both sides of a conflict, according to the activity log.The proven conflict lines.
Roles involved — roles carrying one side of a conflictThe roles involved.The role pairs behind the conflicts.

A conflict is proven when the user's activity log shows transactions on the objects of both incompatible activities: the risk is not theoretical. It needs the activity log to be collected.


Trend and detail​

WidgetShows
Conflicts per refreshThe conflict lines at each refresh of the period, stacked by risk level — the trend of the remediation.
Risks hitThe risks with the most users first; the dot gives the risk level — red for high or critical, orange for medium, blue otherwise.
Role pairsThe pairs of roles that create the most conflicts, with the users concerned: red for a conflict inside a single role — fix the role and every holder is resolved —, orange for two roles held together.
Users with the most conflictsThe users carrying the most conflict lines, with the number of processes; privileged accounts are flagged.
Per processThe users in conflict per business process.
InvestigateLinks to the conflict screens — Summary, Details, Proven, Users, Roles — and to the Data Explorer, where the Segregation of duties model goes further.

Who sees it​

Each widget shows only when the user may run its query, and the row-level scope of the user's roles applies to every figure and to the export.