So, it is that time of the quarter again!
Oracle released their quarterly Critical Patch Update (CPU) on January 17, 2017
In this Digital Era we live in, Oracle EBS is no longer a system in solitude. Your Oracle EBS has multiple interfaces to many other systems, both on premise and in the cloud. It is exposed now, more than ever, to security breaches which can greatly impact organizations’ security.
Staying current is the only way to stay Secure
Oracle continuously emphasizes the urgency of updating on time. It is important to run a “stay current” policy, and react quickly to CPUs as Oracle releases them.
Panaya’s research shows that 70% of enterprise organizations are exposed to critical risk! In reality, most organizations bundle critical patch updates and plan to install them only once or twice a year. Until there is a disaster, there is a tendency to sweep security under the rug and be reactive instead of proactive. However, there may be security vulnerabilities that you don’t know about and by the time you become aware of them the damage is already done.
One of Oracle’s key aspect of their critical patch program is predictability.
This is Oracle’s way of helping their customers stay current and avoid security gaps, allowing their customers to know, a year in advance, the CPU release schedule and have enough time to plan for it.
Save the Date:
Oracle Critical Patches Schedule
- 17 January 2017
- 18 April 2017
- 18 July 2017
Be proactive when it comes to Oracle EBS Security
One Fortune 100 CEO estimated the cost of an ERP breach in his company at over $22 million per minute. So there is no question that inventorying and addressing security risks is mission-critical for any business. In today’s sensitive security climate, organizations without effective Oracle EBS security are quite simply at risk. To get your organization started on the road to keeping Oracle EBS safe, Panaya’s Oracle experts have leveraged analysis of thousands of Oracle landscapes and compiled 7 tips to keep your Oracle EBS secure »