Skip to main content

Overview — Audit synthesis

Overview, the first entry of the Nomasx-1 menu, opens the Audit synthesis: on one page, the accounts, the segregation-of-duties conflicts and the licence position of every connected application, what needs a decision, and how fresh the data is. It is the page to open before an internal review, and the one to export for a steering committee.


At a glance​

Audit synthesisAccounts, SoD conflicts and licence position at a glancePERIODLast 12 months ▾APPLICATIONAll ▾ExcelPDF↻UsersDeclared accounts412380 enabled · 32 disabledRolesDefined and assigned9681 assigned · 15 orphanSegregation of dutiesUsers carrying a conflict371,204 lines · 3 privilegedLicence exposureBeyond the subscription€84,5004 of 22 componentsConflicts per refreshBy business process● Procure to pay ● Order to cash ● FinanceWhat needs a decisionFindings of the assessment reportActive SoD violations12 of 140 rules triggered37Self-conflicting rolesfix the role, every holder is resolved2Components over subscriptionbuy, or remove rights€84,500Generic / shared accounts0Data freshnessLast collection per moduleSECURITY2026-10-28Per licence componentGeneral Accounting50 subscribed64Application filterAll = the totalsFour figuresusers, roles, SoD, licencesTrendstacked by processFreshnessgreen < 2 days, red > 8ExportExcel or PDF synthesisDecision listby severity, with the figureUsers vs subscribedper component

The bar​

ControlEffect
PeriodOpens on Last 12 months. It applies to the two time charts: the conflicts per refresh and the transacting users per month.
ApplicationAll shows the totals across the applications; picking one narrows every widget to it.
Excel, PDFExport the page as it stands — the application picked and the period. The PDF is a synthesis: a cover naming the period and the filter, the four figures as cards, the charts drawn, the lists as tables.
↻Reloads every widget; Updated at gives the time of the data.

The four figures​

CardFigureDetail line
Users — declared accountsThe accounts collected.Enabled · disabled · dormant: enabled without a login in the last 90 days.
Roles — defined roles and their assignmentThe roles defined.Assigned · orphan (assigned to no user) · users holding more than 10 roles, with the maximum.
Segregation of duties — users carrying a conflictThe users with at least one conflict.Conflict lines · privileged users in conflict · business processes concerned.
Licence exposure — components deployed beyond the subscriptionThe value of the users over the subscribed quantities: list price plus three years of support per user over.Components over the subscription out of all components · users over.

The exposure reads the Subscribed Licenses and the pricing catalogue: a component without a price counts zero.


What needs a decision​

The findings of the Security & SoD assessment report, one line each, with a coloured dot — red to act on, orange to review, blue for information, green when nothing is found — and the count or the amount on the right:

FindingWhat to do
Active SoD violations — or No SoD violation, or No SoD matrix definedThe matrix rules triggered out of all rules, and the privileged pairings. Red when a privileged user is concerned. Without a matrix, define it under Settings → SoD.
Self-conflicting rolesA role grants both sides of an incompatible pair on its own: fix the role, and every holder is resolved.
Conflicting role combinationsPairs of roles that breach SoD only when held together: split the duties or revise the assignments.
Components over subscriptionMore users with rights than licences: buy, or remove rights. The amount is the exposure; red from 250,000, orange from 25,000.
Privileged accountsSuper-user access: confirm each one is owned, justified and reviewed quarterly.
Dormant enabled accountsNo login within 90 days, with those that never logged in: disable or re-certify.
Generic / shared accountsActions cannot be attributed to a person: replace them with nominative accounts.
*PUBLIC object grantsObjects open to every user by default: confirm none is a sensitive transaction.
Enabled accounts without rolesIncomplete provisioning, or accounts to disable.
Direct user-level grantsRights granted to a user instead of a role, outside role-based access control.
Users with more than 10 rolesBroad role accumulation: right-size, then run the detection again.
Orphan rolesRoles assigned to no user: remove or repurpose.

Trend and detail​

WidgetShows
Conflicts per refreshThe conflict lines at each SoD refresh over the period, stacked by business process — the trend of the remediation.
Per processUsers in conflict per business process, with the number of conflict lines; red when privileged users are among them.
Per licence componentUsers with rights per component, against the subscribed quantity. Technical and linked accounts are excluded; active users are those with a login in the last 90 days.
Data freshnessThe last collection per module, with its age: green under 2 days, orange under 8, red beyond. A red line means the figures above it are old.
Transacting users per monthThe distinct users with transactions each month, the applications added up.
Users with the most conflictsThe users carrying the most conflict lines, with the number of processes; privileged accounts are tagged.

The detail behind each widget is in the screens: Conflicts, Users, Roles, Usage Report, Financial Report.


Who sees it​

Each widget shows only when the user may run its query: a user without access to the segregation-of-duties data sees the page without those widgets. The row-level scope of the user's roles applies to every figure and to the export.