Oracle Java Audit Checklist – 8 Steps For Success

Oracle Java Audit Check List

• Treat the initial email as the start of a soft audit
• Compile an inventory of Java distributions.
• Contact us for expert help.
• Analyze which deployments need licenses.
• Optimize and remove unnecessary Java.
• Craft strategic responses to Oracle emails
• Dispute retroactive usage claims

Oracle’s Soft Audit Process

Receiving an email from Oracle about Java usage can be a prelude to a soft audit. Here’s how it usually unfolds:

1. Initial Email: Oracle sends an email requesting a meeting to discuss Java usage rights and licensing.
2. Meeting Commencement: The soft audit process begins if you attend the meeting.
3. Inventory Request: Oracle will request a detailed inventory of your Java deployments.
4. Refusal to Share: If you refuse to share, Oracle will point out your history of downloading licensable Java over the past five years.
5. Escalation: Oracle’s continued refusal to purchase licenses led to the involvement of its legal and business practices teams, including threats of legal action.
6. Long-Term Proposals: Oracle’s proposals often span 5-10 years, factoring in retroactive payments from 2019 to the present.
7. Upper Management Involvement: Escalations will reach your CFO, CIO, and CEO.

Your Oracle Java Audit Checklist

1. Initial Email Response: Treat the first email as the start of a soft audit.
2. Inventory Preparation: Begin compiling an inventory of all your Java distributions immediately.
3. Contact Experts: Given the high costs of Java, which include purchasing a license for every employee regardless of usage and a mandatory five-year subscription, we recommend you contact us.
4. Deployment Analysis: We can help you understand which deployments trigger a license.
5. Optimization: We’ll assist you in optimizing and removing unnecessary Java deployments.
6. Email Response Strategy: We will help you craft responses to each Oracle email.
7. Dispute Strategy: We have proven strategies to dispute all retroactive usage claims.
8. Licensing Decision: Decide whether to purchase licenses moving forward. If not, we’ll help you develop a strategy to avoid paying Oracle anything.

Oracle Java Audit Case Study

Background

An organization with 600 employees on the United States East Coast faced a soft audit from Oracle. They had removed all Java installations and didn’t need any further licenses.

However, Oracle claimed that the organization owed $108,000 per year for the past four years due to past Java usage.

The total demand was $432,000. Oracle’s evidence included records of security downloads indicating past Java use.

The Challenge

The organization reached out to Redress for assistance. They wanted to know if there was a way to challenge Oracle’s claims or if they had to pay the demanded fees.

The Process

1. Initial Contact: The organization contacted Redress. Within two days, Redress began reviewing the situation.
2. Review: Redress reviewed the communications and evidence. To understand the organization’s past and present use of Java.
3. Negotiation Strategy: Redress crafted a negotiation strategy. They aimed to counter Oracle’s claims with a well-supported argument.
4. Resolution: After negotiations, Oracle offered to settle for less than $15,000 for the backdated usage. The organization accepted this offer, eager to resolve the issue and move on.

Conclusion

This case illustrates how Redress can assist organizations in negotiating and reducing unexpected software audit claims. If you need help with similar issues, we have many references from organizations we have supported.

Please contact us if you need help with your Oracle Java soft audit.