Row Security can be a necessity for many JDE implementations but, very detailed row security can result in excessive effort put into maintaining security records as well as system performance issues.
Really achieving compliance in system security includes managing access to confidential or critical information, ensuring only appropriate access is in place for all users, that changes are authorized.
How does The Board and your top management assess the value of Security Audit reports to support their risk assurance? What do you have to report on and what should you give them?
The concept of internal controls which attempt to ensure that no single individual has the authority to execute two or more conflicting, sensitive transactions with the potential to impact financials.
Auditing changes within E1 can seem daunting! But you can easily audit your History Table for User, Role or Menu changes and identify what was done, when, by whom. Your auditors and going to love this!
While Exclusive can be used to “Manage Exceptions” and the E1 installation defaults to this setting, Inclusive is considered the stronger method for effectively managing data security.
Over time there are frequently Users or Roles in your system that are no longer used, but they still have records associated with them. Time for a clean up and maintenance schedule!
... or perhaps you will?! "How is this going to be beneficial to me?" "Here we go again, advice from people who don't know our business like me" "This is going to be so time consuming"
Whilst 'Cloud' is the on point buzzword of today, are you looking at something simply available online/via the Web, or is it Oracle's cloud computing service itself?
Discover out how to set up Row Security on your install. Read our full Case Study based on an international company, restricting access to country specific data.
Why not ask us how to run your own internal audit to ensure you are ready BEFORE the auditors arrive? It may not even cost you a penny!