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 technically, the report may be correct. But it leaves the security team with another problem: ๐—ช๐—ต๐—ฒ๐—ฟ๐—ฒ ๐—ฑ๐—ผ ๐˜†๐—ผ๐˜‚ ๐˜€๐˜๐—ฎ๐—ฟ๐˜? Not every conflict carries the same...
Sensitive access is not automatically bad

Sensitive access is not automatically bad

I don’t believe the goal of SAP security should be to eliminate sensitive access. That wouldn’t be realistic. People need to perform critical activities. Someone has to: โ€ข Create or change master dataโ€ข Approve transactionsโ€ข Administer rolesโ€ข Maintain...
The role looks fine

The role looks fine

A role can look perfectly reasonable on paper. The name makes sense.The assignment was approved.The user clearly needs it. And yet the real issue may be sitting much deeper inside the role. One authorization object.One activity value.One unrestricted field.One range...
One Wildcard. Hundreds of users

One Wildcard. Hundreds of users

When reviewing SAP access, people naturally look at roles. Which roles does the user have? Are the roles approved? Does the role name make sense? All useful questions. But sometimes the interesting part isn’t the role. It’s what is sitting ๐—ถ๐—ป๐˜€๐—ถ๐—ฑ๐—ฒ it. โ€ข A...
Inactive account. Active access

Inactive account. Active access

Dormant accounts are easy to categorize as a cleanup problem. An account hasn’t been used. Someone should probably remove it. Put it on the backlog. Move on. But I think that misses the bigger question: ๐—ช๐—ต๐—ฎ๐˜ ๐—ฎ๐—ฐ๐—ฐ๐—ฒ๐˜€๐˜€ ๐—ฑ๐—ผ๐—ฒ๐˜€ ๐˜๐—ต๐—ฒ ๐—ฎ๐—ฐ๐—ฐ๐—ผ๐˜‚๐—ป๐˜ ๐˜€๐˜๐—ถ๐—น๐—น ๐—ต๐—ฎ๐˜ƒ๐—ฒ? An unused account...
Loading...