Who has access to what?

Here’s a simple SAP security question:

๐—ช๐—ต๐—ผ ๐—ต๐—ฎ๐˜€ ๐—ฎ๐—ฐ๐—ฐ๐—ฒ๐˜€๐˜€ ๐˜๐—ผ ๐˜„๐—ต๐—ฎ๐˜?

It sounds almost too basic.

But there is a second part that makes it more interesting:

๐—–๐—ฎ๐—ป ๐˜†๐—ผ๐˜‚ ๐—ฎ๐—ป๐˜€๐˜„๐—ฒ๐—ฟ ๐—ถ๐˜ ๐—ป๐—ผ๐˜„?

Not:

โŒ After exporting three reports
โŒ After someone builds a spreadsheet
โŒ After asking an analyst to investigate it next week

I mean now.

And then:
โ†’ Why does that person have the access?
โ†’ Which role provides it?
โ†’ Which authorization object provides it?
โ†’ What value creates the access?
โ†’ Is the access being used?
โ†’ Is it sensitive?
โ†’ Does it create an SoD conflict?
โ†’ Would removing it from the assigned role affect other users?

That is where โ€œvisibilityโ€ becomes very different from simply having data.

Most large SAP environments contain the information required to answer these questions.

The challenge is connecting it quickly enough to make the information useful.

For me, that distinction is important.

๐—›๐—ฎ๐˜ƒ๐—ถ๐—ป๐—ด ๐—ฆ๐—”๐—ฃ ๐˜€๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† ๐—ฑ๐—ฎ๐˜๐—ฎ ๐—ถ๐˜€ ๐—ป๐—ผ๐˜ ๐˜๐—ต๐—ฒ ๐˜€๐—ฎ๐—บ๐—ฒ ๐˜๐—ต๐—ถ๐—ป๐—ด ๐—ฎ๐˜€ ๐˜‚๐—ป๐—ฑ๐—ฒ๐—ฟ๐˜€๐˜๐—ฎ๐—ป๐—ฑ๐—ถ๐—ป๐—ด ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฆ๐—”๐—ฃ ๐—ฎ๐—ฐ๐—ฐ๐—ฒ๐˜€๐˜€ ๐—ฝ๐—ผ๐˜€๐˜๐˜‚๐—ฟ๐—ฒ.

And when a CISO, auditor, or project team asks a question, speed matters.

You shouldn’t need to start a small consulting project every time someone asks:

โ€œ๐—ช๐—ต๐—ผ ๐—ฐ๐—ฎ๐—ป ๐—ฑ๐—ผ ๐˜๐—ต๐—ถ๐˜€?โ€

Written by Cyril Hauppert

Helping protect companies by providing unparalleled visibility over user authorizations and the timely identification of incorrect and excessive access to critical IT systems

October 16, 2026

Tags: Audit | Compliance | SAP | SOD

You may also like…

5 000 SOD conflicts. Now what?

5 000 SOD conflicts. Now what?

I've seen SoD exercises generate enormous numbers of findings. Hundreds. Thousands. Sometimes far more. And...

Loading...