Showing posts with label Oracle Security. Show all posts
Showing posts with label Oracle Security. Show all posts

Friday, March 10, 2017

Effective Governance over Profile Option Values in Oracle E-Business Suite


Effective Governance over Profile Option Values



“If only I knew back then what I know now…”  A famous phrase with applicability to many of life’s situations…

If you’ve implemented an ERP system and stuck around for a while, eventually you’ll say those words.  The implementation of a new ERP system for the first time is like drinking from a fire hose. 
If you’ve been live for a couple of years and were part of the implementation team, I challenge you to do just that.  Go back and visit your implementations configurations with the knowledge you now have.  No doubt some of the decisions you made during the implementation you’d make differently now.
Specifically, look at how you set your profile options and what profile option values you have set since you went live.  I am guessing that your governance process related to profile option values has been less than perfect.
Start with these questions to understand if you have in place proper governance relating to the approval and maintenance of profile option values:
1.      Which profile options should be set in Production?  Or… which profile options should NOT be set in Production? (yes this implies that some should not be set).
2.      Who is authorized to approve the setting of new profile options or changes to existing settings?
3.      At what level(s) should each profile option be set (Site, Application, Responsibility, User)
Each profile option has unique characteristics and abilities.  Following is a screen shot of the System Profile Values form where profile option values can be configured:


The above example shows a profile option that can only be set at the Site and User levels. 
The next example “Printer” can be set at any level.

The configuration of each Profile Option is set in the Profiles form.  The box “Hierarchy Type Access Level” defines at which level a Profile Option is Visible and Updatable.  The User Access box identifies whether it can be updated via the User Profile Values form.



Following is a screen shot of the User Profile Values form (aka Personal Profile Values):



Risks and Controls related to the Personal Profile Values form will be covered in another blog.'

You can download a template to use as a starting point for your risk assessment here: http://erpra.net/BookResources.html.   Your organization could used the outcome of the risk assessment as a basis for a desktop procedures for those that have the authority to make profile option value changes in Production.
If you want to know more about Profile Options and why you should care, I’d suggest watching the video for the full webinar we did on this topic at: https://www.youtube.com/watch?v=NGa_rGAetLc. 

One other topic of interest may be how to address the profile option "Utilities: Diagnostics" from a SOX audit perspective.  I covered that in an earlier blog that you can review at: http://jeffreythare.blogspot.com/2017/01/why-utilities-diagnostics-should-not-be.html.

Recommended Services from ERP Risk Advisors related to this topic

We are a free health check that includes reviewing how  your organization has set many of the high risk profile options.  See more about this free service at:  http://erpra.net/Services.html . 
If you are an auditor, keep in mind that we also do outsourced IT audit work.   We are thorough, risk-based, and will work with you to develop a scope that fits your budget.



Tuesday, February 7, 2017

Security Standards for Oracle E-Business Suite: DMZ Configuration Guide


Security Standards for Oracle E-Business Suite: DMZ Configuration Guide



In my last blog (see http://jeffreythare.blogspot.com/2017/01/security-standards-for-oracle-e.html) we discussed Oracle’s Secure Configuration Guide (MOS Note 403537.1).  Another critical document that Oracle publishes is their DMZ configuration document (MOS Note 380490.1).  Every step must be meticulously followed or your data could be exposed – especially for those with externally facing applications such as Employee Self Service, iStore, or iRecruitment. 

If you are running iStore and have NOT tokenized your credit card data, you could be exposing your organization to significant PCI risk since Oracle provides the ability to decrypt credit card data via a concurrent program.  Find out more about decryption risk at: http://erpra.net/files/Decryption_of_Credit_Card_and_Bank_Data_Risks_and_Controls_v3.pdf. 

Other good information related to the DMZ configuration and related risks can be found on our partner firm’s, Integrigy, website at: https://www.integrigy.com/tags/dmzexternal.  Integrigy is also hosting a webinar on 9-Feb on this topic.  Sign up at: https://www.integrigy.com/security-resources/common-mistakes-when-deploying-oracle-e-business-suite-internet-webinar. 


Recommended Services from ERP Risk Advisors


We offer assessment services that can evaluate your organization’s compliance with part or all the recommendations in this MOS Note along with other high risks not considered by Oracle.
Additionally, we can help you identify a partner than tokenize your credit card data to remove most PCI risks from your EBS environment.
Since some of these risks need to be evaluated by reviewing access controls, a SaaS service to review role design may also be appropriate.  We perform that service in conjunction with our partner, CaoSys.
Contact us at erpra.net/contactus.html  for more information about these services or CaoSys GRC solutions if you are interested in learning more.  We offer our Role / Responsibility analysis consulting as a service (CS*Proviso) or via installed software (CS*Comply).  See more about CaoSys GRC solutions at caosys.com.

About ERP Risk Advisors

ERP Risk Advisors is a leading provider of Risk Advisory services for organizations using Oracle Applications.  We provide consulting and training services related to compliance, security, risk management, and controls.  We also assist organizations in implementing GRC-related software from industry-leading companies such as Oracle, CaoSys, Smart ERP Solutions, and MentiSoftware.


About Jeffrey T. Hare, CPA CISA CIA

Jeffrey Hare, CPA CIA CISA is the founder and CEO of ERP Risk Advisors.  His extensive background includes public accounting (including Big 4 experience), industry, and Oracle Applications consulting experience.    Jeffrey has been working in the Oracle Applications space since 1998 with implementation, upgrade, and support experience.  Jeffrey is a Certified Public Accountant (CPA), a Certified Information Systems Auditor (CISA), and a Certified Internal Auditor (CIA).   Jeffrey has worked in various countries including Austria, Australia, Brazil, Canada, Germany, Ireland, Mexico, Panama, Saudi Arabia, United Arab Emirates, and United Kingdom.  Jeffrey is a graduate of Arizona State University and lives in northern Colorado with his wife and three daughters.  You can reach him at jhare@erpra.net or (970) 324-1450.

Jeffrey's first solo book project "Oracle E-Business Suite Controls: Application Security Best Practices" was released in 2009.  His second book project “Auditing Oracle E-Business Suite: Common Issues” was released in 2015.  Jeffrey has written various white papers and other articles, some of which have been published by organizations such as ISACA, the ACFE, and the OAUG.  Request these white papers here.  Jeffrey is a contributing author for the book “Best Practices in Financial Risk Management” published in 2009.

LinkedIn: linkedin.com/in/jeffreythare
Twitter: twitter.com/jeffreythare
Blog: jeffreythare.blogspot.com

Monday, January 30, 2017

Security standards for Oracle E-Business Suite; the good, the bad, the ugly...

Security Standards for Oracle E-Business Suite; the good, the bad the ugly

Organizations that use Oracle E-Business Suite rely on the quality and completeness of the guidance provided to them by Oracle through My Oracle Support (MOS).  There are several documents that organizations should know like the back of their hand and should have documented their compliance with the recommendations in detail.   One such document is MOS Note 403537.1 – Secure Configuration Guide for Oracle E-Business Suite.  Compliance with this document prior to going live is a necessity.  Because of changes being introduced by users, DBAs, security administrators, developers, and via patches provided by Oracle, compliance needs to be reviewed and re-tested on a regular basis. 

Over the last 10 years we have uncovered several issues with this document.  We have published our findings from time to time and Oracle has acknowledged use of our feedback in their documentation.   Recently we have identified four other issues that we’d like to address that frankly has us questioning the quality and completeness of the document as well as questioning the quality and completeness of the internal processes that should be influencing this document.


I wrote an article documenting the pros and cons of this document that I’d encourage you to download and read.  The MOS Note presents various risks that organizations need to be aware of and Oracle provides some recommendations related to these risks.  You can access this article here. 

Conclusion


I have identified several major issues with this MOS note.  Why isn’t Oracle updating their documentation when they release new forms that allow SQL injection?  Could it be the problem is with their development standards and peer review process?  Are they not identifying these risks as part of their development process?  If so, isn’t that a bigger concern.  Perhaps this is why they have backed off making ‘best practice’ recommendations. 



Why doesn’t Oracle see the ability to decrypt credit card and bank account data as a security risk?

How is it these deficiencies exist in their documentation (failure to identify that JTF_FM_QUERY is a view and that they aren’t monitoring the ALR_ACTIONS table) and have gone unnoticed for over three years from the release of this guidance in September 2011?  The only logical conclusion is they are not implementing and testing their own guidance.

Over the past few years, we have noted deficiencies in the easiest of these recommendations – seeded application users and seeded database users.  We have also identified four new functions which allow SQL injection that have not been updated in their documentation.  At one point, there were five, but two of them have been since added to their documentation.  We have published the three functions above.

My concern is that organizations relying on this guidance have a false sense of ‘security’ if they follow this guidance.  Following this ‘guidance’ is certainly necessary at a minimum, but additional risks exist that Oracle isn’t adding to their documentation.  We’d love to see Oracle increase its effectiveness which can only be done by taking a hard look at their internal standards and setting a regular schedule for testing their guidance and updating this documentation.  Compliance with this document is necessary, but with Oracle, sometimes you need to fill in the blanks…


Recommended Services from ERP Risk Advisors


We offer assessment services that can evaluate your organization’s compliance with part or all of the recommendations in this MOS Note along with other high risks not considered by Oracle.  This engagement can range from one to six weeks.



Since some of these risks need to be evaluated by reviewing access controls, a SaaS service to review role design may also be appropriate.  We perform that service through our partner, CaoSys.

Contact us at erpra.net/contactus.html  for more information about these services or CaoSys GRC solutions if you are interested in learning more.  We offer our Role / Responsibility analysis consulting as a service (CS*Proviso) or via installed software (CS*Comply).  See more about CaoSys GRC solutions at caosys.com.


About ERP Risk Advisors



ERP Risk Advisors is a leading provider of Risk Advisory services for organizations using Oracle Applications.  We provide consulting and training services related to compliance, security, risk management, and controls.  We also assist organizations in implementing GRC-related software from industry-leading companies such as Oracle, CaoSys, Smart ERP Solutions, and MentiSoftware.



About Jeffrey T. Hare, CPA CISA CIA


Jeffrey Hare, CPA CIA CISA is the founder and CEO of ERP Risk Advisors.  His extensive background includes public accounting (including Big 4 experience), industry, and Oracle Applications consulting experience.    Jeffrey has been working in the Oracle Applications space since 1998 with implementation, upgrade, and support experience.  Jeffrey is a Certified Public Accountant (CPA), a Certified Information Systems Auditor (CISA), and a Certified Internal Auditor (CIA).   Jeffrey has worked in various countries including Austria, Australia, Brazil, Canada, Germany, Ireland, Mexico, Panama, Saudi Arabia, United Arab Emirates, and United Kingdom.  Jeffrey is a graduate of Arizona State University and lives in northern Colorado with his wife and three daughters.  You can reach him at jhare@erpra.net or (970) 324-1450



Jeffrey's first solo book project Oracle E-Business Suite Controls: Application Security Best Practices was released in 2009.  He published a second book called Auditing Oracle E-Business Suite: Common Issues in 2015.   He is working on an expansion of his first book which will be called Oracle E-Business Suite Controls: Foundational Principles and is working on an update for his second book.  Both are expected to be released in 2017.

He has written various white papers and other articles, some of which have been published by organizations such as ISACA, the ACFE, and the OAUG.  Jeffrey is a contributing author for the book “Best Practices in Financial Risk Management” published in 2009.

LinkedIn: linkedin.com/in/jeffreythare
Twitter: twitter.com/jeffreythare
Blog: jeffreythare.blogspot.com