Permission creep and segregation of duties
ERP risk starts when one user can perform two tasks that are meant to check each other: when whoever raises a record also approves it, the control disappears. Roles are rebuilt around duties rather than around individuals.
- Conflicting duty pairs are governed by rule, not case by case
- Old permissions must close when a role changes hands
- Privileged accounts are granted with an expiry
- Exceptions are recorded with a reason and a date
Cloud configuration security
Most cloud incidents come from a setting left open rather than an exploit: public storage, a broad network rule, management access never closed. Configuration is not fixed once — it is measured continuously.
- The benchmark set is chosen against your risk appetite
- Drift is recorded the moment it appears
- Remediation advice arrives with its impact stated
- New accounts and subscriptions enter scope automatically
Integration and interface surface
ERP never stands alone; it talks to payroll, banking, e-invoicing and supplier systems. Those interfaces usually run on service accounts — the longest-lived and most broadly privileged accounts in the estate.
- Every service account has an owner and a lifetime
- Key and credential rotation is put on a calendar
- Interface traffic is watched as a pattern, not as content
- Unused integrations are closed, not left dormant
Evidence and audit trail
Security work is measured by what can be shown during an audit. Who accessed what, when and on what grounds must be traceable; an authorization with no record counts as one that never happened.
- Permission changes reconcile against approval records
- Logs are retained in a tamper-evident form
- A ready query set answers common audit questions
- Findings are tracked to a closing date