Audit of privileged access in ERP: risks and control tests

Table of contents

An audit of privileged access in ERP systems verifies whether identities with the ability to manage, configure, or execute critical processes have authorized, limited, traceable, and reviewed permissions. The assessment compares the design of the controls with evidence of their operation; it is not technical support or a test of exploitation.

What does a privileged access audit in an ERP system include?

Privileged access is not solely determined by an account being named "administrator." It can also stem from a role or a combination of permissions that allows the creation of users, assignment of profiles, modification of settings, approval of sensitive operations, or access to restricted information. Therefore, the review must consider the actual capabilities of each identity, not just its name or the title of the user.

The universe may include personal administrator accounts, users with elevated permissions in financial or operational processes, service accounts, and emergency access. It may also encompass temporarily assigned roles or permissions inherited from other profiles. The inclusion of the database, infrastructure, identity directories, or interfaces with other systems depends on the objective and agreed-upon limits of the audit; these should not be assumed to be part of the ERP scope by default.

In SAP or any other ERP platform, the names of roles, modules, and permissions vary. The analysis should translate these into capabilities that are understandable to the business: what actions they enable, on what data or processes, and in what environment. A profile with a seemingly limited name can accumulate relevant powers when combined with others, while a role called "administrator" may have a restricted scope. Evidence of actual permissions allows you to distinguish between these two cases.

This assessment relates to a broader view of IT audit and compliance, This applies when the scope includes technological controls, IT governance, or digital risks. The purpose is to evaluate controls and evidence, not to interfere with the configuration or replace the internal platform managers.

Risks that should be assessed

Privileged access concentrates capabilities that can affect relevant data, configurations, or transactions. The existence of high-level permissions does not, in itself, prove that an incident has occurred; it does, however, necessitate assessing whether the access is justified, limited, and subject to controls proportionate to its scope.

  • Excessive permissions: An account may retain capabilities that are not relevant to its current functions. The broader the scope of the permission, the more important it is to verify its authorization, purpose, and validity.
  • Insufficient segregation of duties: An individual could accumulate incompatible responsibilities within a process. For example, maintaining vendor data and approving payments may require joint review; the incompatibility depends on the process design and existing compensating controls.
  • Accounts without an owner or outdated: Users who have changed roles, left the organization, or no longer require access may remain enabled if role changes and departures are not reflected in the ERP in a timely manner.
  • Shared or poorly controlled service accounts: If multiple people use the same identity or there is no defined person responsible for a technical account, it can be difficult to attribute activity and confirm that permissions are still necessary.
  • Limited traceability: Incomplete, inaccessible, or unreviewed records can hinder the reconstruction of relevant actions and the identification of exceptions.

These risks are assessed based on the affected process, the sensitivity of the information, the actual scope of permissions, and the ability to detect or review activities. A privilege review should also consider how exceptions are documented: an operational need may explain access, but it does not eliminate the need to justify and monitor it.

To expand on the context of technological control, you can consult the content on security systems audit. The specific evaluation of an ERP, however, must be tailored to its processes, roles, and available evidence.

How to define the scope and gather evidence

Before running tests, it's advisable to define what you're trying to evaluate, which processes and environments are included, what period the review covers, and who is responsible for validating the information. This delimitation prevents confusing application privileges with access to related components that haven't been formally included.

The inventory should identify, to the extent relevant to the scope, individual users, administrators, service accounts, emergency access, and elevated roles. It is also helpful to understand how profiles are assigned, who approves changes, and what process records personnel movements or role modifications. If the company uses separate environments, the review should clarify which ones are included and how their permissions compare.

The evidence may include, among other things:

  • Lists of users, roles and effective permissions, with extraction date and identifiable scope.
  • Requests, approvals, and change logs for access assignments or modifications.
  • Current documentation on profiles, responsibilities and internal rules for segregation of duties.
  • Records of periodic reviews, the people responsible for carrying them out, and decisions made about the observed access.
  • Inventories of technical accounts, their purpose, internal owner, and associated permissions.
  • Activity logs and evidence of how exceptions are reviewed, according to the controls and policies applicable to the organization.

For evidence to be useful, it must be possible to establish its source, the time period it covers, and whether it represents the entire population or a select group. An isolated list or a screenshot can serve as supporting evidence, but it doesn't always allow for confirmation of the population's integrity or the history of changes. When using a sample, it must be documented how it was selected and what conclusion it allows us to draw, without extrapolating beyond its scope.

User and activity information may be sensitive. Its collection, storage, and circulation must follow applicable internal controls, limiting access to those involved in the review and avoiding the inclusion of unnecessary data.

Control tests for privileged access

Testing must link each control objective to a source of evidence and a verifiable criterion. The selection of accounts and events is determined by considering scope, risk, and time period; there is no universal number of cases that can replace professional judgment. The following matrix presents examples of possible tests, not uniform requirements for all organizations.

Examples of tests in a privileged access review

Control objective Possible test Related evidence
Authorization and allocation Select accounts with elevated permissions and compare the actual access with the request, justification, approval, and assigned role. Requests, approvals, change history, and permission list.
Minimum privilege Compare the assigned capabilities with the person's functions or the documented need of the technical account. Roles, responsibilities, inventory of accounts and validation of the person responsible for the process.
ERP segregation of duties Compare permission combinations with the incompatibility rules defined for the included processes and examine exceptions. Matrix of functions, assigned roles, approvals, and documented compensating controls.
Service accounts Verify that there is an identifiable purpose and responsible party, and that the permissions and use of the account are consistent with that need. Inventory, justification, permits and available reviews.
Periodic reviews Check if the review covered the defined population, who approved it, and how the indicated accesses were managed. Review record, validations of responsible parties and follow-up evidence.
Traceability Examine whether the available records allow relevant activities to be associated with an identity and whether they are reviewed according to the applicable policy. Activity logs, log access controls, and review evidence.
Emergency access Review the reason, the authorization, the period of use, and the subsequent examination of the activities carried out with those accounts. Usage record, approvals and subsequent review.

A segregation test is not about assuming two roles are incompatible because their names sound different. It assesses what actions enable and whether a combination allows for the consolidation of stages that the process design seeks to separate. If an exception exists due to operational necessity, it's advisable to verify who approved it and what alternative supervision is documented.

The review of service accounts should consider their non-personal nature: identifying an internal owner and purpose helps assess whether access is still necessary. It can also be verified whether their use aligns with internal policies, including, where relevant, restrictions on interactive logins. The audit records and evaluates the evidence; it does not require performing operational actions or modifying production transactions to test these controls.

To maintain a secure and verifiable evaluation, consultations and validations must be authorized and coordinated with system owners. When a test requires technical interaction, its method and environment must be defined within the approved scope, preventing unauthorized changes or disruptions to operations.

How to interpret the results and follow up

The results may relate to the design of the control or its operation during the period under review. A control may be described in a policy but lack sufficient evidence of its application; it may also be implemented even though its design does not cover all relevant permission combinations. Differentiating between these situations facilitates the formulation of accurate and proportionate observations.

A well-supported observation identifies the criterion used—for example, an internal policy or an approved rule for the process—the observed condition, and the supporting evidence. When information allows, it can explain the cause and potential effect without presenting a possibility as a confirmed incident. If an obligation depends on existing regulation, it must be validated for the relevant organization and period before being presented as a normative criterion.

The priority for follow-up can consider the scope of access, the criticality of the process, the sensitivity of the data, the duration of the situation, and the available compensating controls. This assessment helps ensure that the company's response is consistent with its context. Not all observations require the same action: some may require adjusting permissions; others, documenting an exception, improving approval processes, or strengthening activity reviews.

Management must also define responsibilities and maintain evidence of agreed-upon decisions and actions. Changes in job positions, reorganizations, the addition of modules, significant ERP modifications, or incidents may warrant an additional review, beyond the frequency established by the organization based on its risks, policies, and applicable obligations. The audit provides an assessment limited to the scope, period, and evidence examined; it does not eliminate risks nor replace ongoing access management.

Frequently Asked Questions

What is considered privileged access in an ERP system?

It is an access level that allows you to manage users or roles, change settings, perform high-impact actions, or access restricted information. The classification depends on the actual capabilities and their combination, not solely on the account name or the account holder's title.

Should the audit include service accounts?

If they are within the scope of the review and have access to the ERP system, they should be included. The review can verify their purpose, internal responsible party, permissions, and evidence of use or review. Their evaluation should consider organizational policies and the technical function they fulfill.

How is segregation of duties proven?

Effective permission combinations are compared with the incompatibility rules defined for company processes. Exceptions and compensating controls are also reviewed. A role label alone does not confirm a conflict.

What evidence is useful for reviewing access?

Useful evidence includes user and permission lists, requests and approvals, change logs, reviews by responsible parties, technical account documentation, and relevant activity logs. These must have an identifiable origin, date, and scope.

How often should privileges be reviewed?

There is no single frequency applicable to every company and platform. The organization can define it by considering risk, the criticality of processes, its policies, and its corresponding obligations. Changes in roles, significant ERP modifications, and incidents can also trigger a review outside the usual cycle.

This article has been verified by
Humberto González,
Public accountant
Recent Publications
Categories

Search