5 000 SOD conflicts. Now what?

I’ve seen SoD exercises generate enormous numbers of findings.

Hundreds.

Thousands.

Sometimes far more.

And technically, the report may be correct.

But it leaves the security team with another problem:

๐—ช๐—ต๐—ฒ๐—ฟ๐—ฒ ๐—ฑ๐—ผ ๐˜†๐—ผ๐˜‚ ๐˜€๐˜๐—ฎ๐—ฟ๐˜?

Not every conflict carries the same level of risk.

Not every combination is actually being used.

Not every issue deserves the same urgency.

That means the useful questions become:

โ†’ Which conflicts involve truly sensitive activities?
โ†’ Which users can actually execute both sides of the conflict?
โ†’ Which combinations represent meaningful business exposure?
โ†’ Which issues are inherited from old roles or outdated assignments?
โ†’ Which conflicts can be remediated safely without disrupting operations?

This is where I think many compliance exercises lose value.

They focus heavily on ๐—ณ๐—ถ๐—ป๐—ฑ๐—ถ๐—ป๐—ด ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜†๐˜๐—ต๐—ถ๐—ป๐—ด.

But very little on ๐—ฑ๐—ฒ๐—ฐ๐—ถ๐—ฑ๐—ถ๐—ป๐—ด ๐˜„๐—ต๐—ฎ๐˜ ๐—บ๐—ฎ๐˜๐˜๐—ฒ๐—ฟ๐˜€ ๐—บ๐—ผ๐˜€๐˜.

For a CISO or SAP security lead, 5,000 findings are not necessarily better than 50.

And 50 may not be better than 5.

If the 5 are the ones that actually matter.

๐—” ๐˜‚๐˜€๐—ฒ๐—ณ๐˜‚๐—น ๐—ฎ๐˜€๐˜€๐—ฒ๐˜€๐˜€๐—บ๐—ฒ๐—ป๐˜ ๐˜€๐—ต๐—ผ๐˜‚๐—น๐—ฑ ๐—ต๐—ฒ๐—น๐—ฝ ๐—ฝ๐—ฟ๐—ถ๐—ผ๐—ฟ๐—ถ๐˜๐—ถ๐˜‡๐—ฒ ๐—ฟ๐—ถ๐˜€๐—ธ, ๐—ป๐—ผ๐˜ ๐—ท๐˜‚๐˜€๐˜ ๐—ฐ๐—ผ๐˜‚๐—ป๐˜ ๐—ถ๐˜.

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 30, 2026

Tags: Audit | Compliance | SAP | SOD

You may also like…

Loading...