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
The bar
| Control | Effect |
|---|---|
| Period | Opens on Last 12 months. It applies to the two time charts: the conflicts per refresh and the transacting users per month. |
| Application | All shows the totals across the applications; picking one narrows every widget to it. |
| Excel, PDF | Export 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
| Card | Figure | Detail line |
|---|---|---|
| Users — declared accounts | The accounts collected. | Enabled · disabled · dormant: enabled without a login in the last 90 days. |
| Roles — defined roles and their assignment | The roles defined. | Assigned · orphan (assigned to no user) · users holding more than 10 roles, with the maximum. |
| Segregation of duties — users carrying a conflict | The users with at least one conflict. | Conflict lines · privileged users in conflict · business processes concerned. |
| Licence exposure — components deployed beyond the subscription | The 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:
| Finding | What to do |
|---|---|
| Active SoD violations — or No SoD violation, or No SoD matrix defined | The 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 roles | A role grants both sides of an incompatible pair on its own: fix the role, and every holder is resolved. |
| Conflicting role combinations | Pairs of roles that breach SoD only when held together: split the duties or revise the assignments. |
| Components over subscription | More users with rights than licences: buy, or remove rights. The amount is the exposure; red from 250,000, orange from 25,000. |
| Privileged accounts | Super-user access: confirm each one is owned, justified and reviewed quarterly. |
| Dormant enabled accounts | No login within 90 days, with those that never logged in: disable or re-certify. |
| Generic / shared accounts | Actions cannot be attributed to a person: replace them with nominative accounts. |
| *PUBLIC object grants | Objects open to every user by default: confirm none is a sensitive transaction. |
| Enabled accounts without roles | Incomplete provisioning, or accounts to disable. |
| Direct user-level grants | Rights granted to a user instead of a role, outside role-based access control. |
| Users with more than 10 roles | Broad role accumulation: right-size, then run the detection again. |
| Orphan roles | Roles assigned to no user: remove or repurpose. |
Trend and detail
| Widget | Shows |
|---|---|
| Conflicts per refresh | The conflict lines at each SoD refresh over the period, stacked by business process — the trend of the remediation. |
| Per process | Users in conflict per business process, with the number of conflict lines; red when privileged users are among them. |
| Per licence component | Users 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 freshness | The 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 month | The distinct users with transactions each month, the applications added up. |
| Users with the most conflicts | The 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.
Related
- Data Explorer — to go beyond the synthesis, by any field.
- Security & SoD assessment — the full report behind the decision list.