An authorization within a corporate system may seem like an exclusively technical task. A user needs to carry out an activity, requests access, and, once certain requirements are met, receives the corresponding permissions.

From an operational standpoint, the process might be considered complete at that point. However, behind an authorization are questions that technology alone can hardly answer.

Why does the user need that access? Who has the authority to approve it? What risks arise if that access is granted? What responsibilities does the organization assume by granting it?

Beyond granting access, these questions point to a broader issue: technological decisions can have organizational, legal, and regulatory compliance implications.

My experience in SAP system security and my academic background in Law and Information Technology Management Engineering have led me to take a particular interest in this relationship.

I believe an authorization should be understood not merely as a permission that allows a user to perform certain duties, but as the technical expression of an organizational decision that requires justification, accountability, and control.

1. Technology Executes Decisions, but Does Not Always Determine Their Justification.

Enterprise systems and identity management tools make it possible to administer users, assign roles, restrict operations, and record activities. These mechanisms are essential to protect information and keep business processes operating.

Nevertheless, there is a difference between determining whether a system allows an action and assessing whether that action is consistent with a person’s responsibilities.

A user may hold a technically valid authorization while still having permissions that do not match their current duties.

This may happen for different reasons: changes in position, temporary authorizations that remain active, modifications to processes, or access decisions that were not reviewed in a timely manner.

From my perspective, this distinction represents one of the central dimensions of access governance.

Technical administration answers how permissions are granted, modified, or revoked. Access governance adds questions about who should decide, on what criteria, which risks must be assessed, and how outcomes are monitored.

The importance of this approach is also reflected in the NIST Cybersecurity Framework (CSF) 2.0, which includes the Govern function to address organizational context, risk management strategy, roles and responsibilities, policies, and oversight (National Institute of Standards and Technology [NIST], 2024).

The inclusion of this function highlights that cybersecurity management is not limited to implementing technical mechanisms.

2. Law, Technology, and Compliance: Three Perspectives on the Same Decision.

Although these disciplines have different objectives and methodologies, they can converge when examining the same organizational problem.

From a technology perspective, the focus is on understanding what a user can do within a system, how authorizations are implemented, and which mechanisms can control or record activity.

From a legal perspective, the task is to identify the applicable legal obligations and responsibilities, considering the nature of the information, the activities to be performed, the parties involved, and the relevant legal framework.

From a compliance perspective, the analysis focuses on how an organization identifies and meets its obligations and commitments through policies, procedures, accountable parties, and oversight mechanisms.

These perspectives should be kept in mind when making decisions about access to an organization’s systems.

Not every technical deficiency constitutes a legal violation. Nor does every internal policy, by itself, represent an obligation established by law. The legal significance of a situation requires examining its circumstances and the applicable provisions.

In this regard, ISO 37301:2021 provides a reference for establishing, implementing, evaluating, and improving compliance management systems. Its approach includes integrating responsibilities and processes within the organization (International Organization for Standardization [ISO], 2021).

The point is not to turn every technological decision into a legal issue, but to recognize when a broader assessment is necessary.

3. An Example: The Risk Behind a Combination of Authorizations.

Consider a hypothetical situation.

An organization uses SAP to manage financial processes. An employee requests new authorizations because their operational responsibilities have changed.

The requested permissions would allow the employee to perform additional activities related to vendor management and payment execution.

From a strictly technical perspective, it would be possible to identify the necessary roles and assign them according to the system configuration.

However, the assessment should not end there.

If the same person can participate in activities the organization has defined as incompatible, a segregation of duties (SoD) conflict may arise.

The question then changes. It is no longer enough to determine whether the user needs a transaction or a particular access permission; it is necessary to understand how that authorization relates to the entire process.

Is there an actual conflict given the assigned responsibilities? Can the risk be eliminated through a different distribution of duties? Are there operational reasons to retain the access? Which compensating controls might be appropriate?

SAP Access Control documentation addresses the identification and analysis of access risks, as well as their treatment through remediation or mitigation, as appropriate (SAP SE, n.d.).

It is important to clarify that a conflict detected during a risk analysis does not, by itself, constitute evidence of fraud, a legal violation, or misconduct.

An alert identifies a situation that needs assessment; it does not replace an analysis of the context or a decision by the responsible parties.

This distinction is essential to me. An organization does not necessarily demonstrate better governance by presenting fewer alerts, but rather by its ability to understand risks, justify decisions, and verify that controls actually work.

The example above is illustrative and does not refer to any specific incident or internal process.

4. Accountability Begins Where Configuration Ends.

Access control tools can automate checks, manage approvals, record decisions, and facilitate subsequent reviews.

However, their usefulness depends on the quality of the criteria and responsibilities defined by the organization.

A system can identify a potentially risky combination of permissions. What it cannot always determine is whether an exception serves a legitimate need, who should be accountable for accepting it, or whether mitigation measures are adequate.

These assessments require human involvement and knowledge of the operational context.

For this reason, I believe an authorization should be assessed through four questions:

  • Need: Which responsibility or activity justifies the access?

  • Risk: What consequences could arise from granting or using it?

  • Decision: Who is authorized to approve it, and according to which criteria?

  • Follow-up: How will the organization verify that the access remains appropriate?

The answers should be consistent with the classification of information, the user’s responsibilities, internal policies, and applicable obligations.

This way of approaching the issue is aligned with the risk management approach of the NIST CSF 2.0 (NIST, 2024), in which cybersecurity decisions are considered within the organization’s broader context and objectives.

In other words, the system implements an authorization, but the organization retains responsibility for its justification and oversight.

5. Security and Compliance Are Not the Same Thing.

Another distinction I consider relevant is the relationship between security and regulatory compliance.

Information security seeks to manage risks that may affect the confidentiality, integrity, and availability of information and systems.

Compliance, in turn, involves identifying and meeting applicable obligations and commitments, as well as establishing mechanisms to monitor adherence to them.

The two areas may overlap, but they are not equivalent.

An organization could meet certain documentation requirements and still face significant technological risks. Similarly, it could have technically robust security mechanisms and still need adjustments to address specific obligations.

This is why I consider it insufficient to assess controls solely on the basis of their existence.

A documented control is not necessarily an effective control. To assess its value, it is necessary to understand which risk it is intended to manage, how it operates, who is responsible, and what evidence can be used to evaluate its results.

Frameworks provide tools for conducting these assessments, but they do not eliminate the need to interpret the particular context of each organization.

Likewise, frameworks and standards such as the NIST CSF and ISO 37301 should not automatically be treated as generally applicable legal obligations. Whether they are binding depends, among other factors, on applicable provisions and on commitments the organization has undertaken.

6. A Professional Perspective That Connects Disciplines.

My career has developed primarily in information technology, with a particular focus on SAP security, access governance, and internal controls.

My legal education broadens my perspective on how these activities relate to organizational accountability and the fulfillment of obligations.

I do not believe that integrating different disciplines means replacing the specialized expertise each requires.

On the contrary, recognizing their boundaries makes it possible to understand problems more clearly and ask questions that might otherwise be overlooked.

When I examine an authorization process, I want to understand both its technical implementation and the reasons that justify it, along with the mechanisms used to oversee it.

When I think about a control, I am interested not only in verifying that it exists, but also in identifying the problem it is intended to address and the consequences if it proves ineffective.

And when I examine the relationship between technology and law, I consider it essential to distinguish an operational decision from a legal obligation and a governance practice.

These differences do not necessarily separate the disciplines. Properly understood, they allow us to connect them with greater precision.

7. Conclusion: The Value Lies in Understanding the Decision.

Digital transformation presents challenges that can rarely be resolved from a single area of expertise.

Enterprise systems make it possible to execute complex processes, but their operation depends on human decisions concerning responsibilities, risks, and organizational objectives.

Access governance provides a concrete example of this relationship. An authorization can be configured through a technical operation. Its justification, however, requires understanding the user’s duties, the risks involved, and the relevant policies and obligations.

My perspective is that the true value of connecting law, technology, and compliance does not lie in bringing three disciplines together under a single concept, but in using their different approaches to make better-informed decisions.

That is also the purpose of this space: to examine technological challenges from a multidisciplinary perspective, distinguish facts from interpretations, and develop arguments that contribute to a more complete understanding of the digital environment.

Because behind every technological decision there may be an organizational question worth examining.

References

International Organization for Standardization. (2021). Compliance management systems — Requirements with guidance for use (ISO Standard No. 37301:2021). https://www.iso.org/standard/75080.html

National Institute of Standards and Technology. (2024). The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29). https://doi.org/10.6028/NIST.CSWP.29

SAP SE. (n.d.). SAP Access Control 12.0: Managing access risks. SAP Help Portal. https://help.sap.com/docs/SAP_ACCESS_CONTROL/5cae1bc9a72348389e91183714220e30/bd18cb07c2ba40ee8c6ab632539f2802.html

Professional analysis and opinion article. The references support the technical and management concepts presented; interpretations and conclusions reflect the author’s perspective. This content does not constitute legal advice or replace an assessment of the obligations applicable to a particular organization.