ORACLE seeded controls creating their own segregation of duties conflicts!?!
hi again
As above, throughout multiple Controls ran, they contain seeded ORACLE roles creating 100s of conflicts:
why aren't ORACLE using their own role creation steps to avoid these? ..or is it a case of, "do as I say, not as I do" !??! 😆
am I missing something?
0