CSAA Insurance. One point five million dollar Oracle Java claim resolved at zero cost.

CSAA Insurance is a US insurance group operating across multiple states with roughly three thousand five hundred employees. Oracle opened a Java claim of approximately one and a half million dollars.

That is more than four hundred dollars per employee for a mid sized insurer, which shows how the per employee metric behaves well below enterprise scale.

The claim closed at zero cost.

The customer profile

Around three thousand five hundred employees across multiple US states, running policy administration, claims and underwriting systems alongside a conventional corporate desktop estate.

Insurance technology is heavily third party. Policy and claims platforms are bought rather than built, and a good number of them ship their own Java runtime under the supplier's control.

Java was present across desktop, server and application tiers, which is normal and is also why the inventory has to cover all three.

The opening position

Oracle's opening claim was approximately one and a half million dollars, priced across the employee population under the Universal Subscription.

At this size the claim is a material capital decision rather than a line item, which raises the stakes on getting the evidence right.

The approach

We inventoried by distribution across all three tiers, separating Oracle's own binaries from OpenJDK builds and from runtimes embedded inside policy and claims platforms.

The embedded category mattered most. Where a platform vendor supplies and controls the runtime, the licensing question belongs to that vendor's agreement.

We then assembled dated evidence for every Oracle Java removal already performed and reconciled the position against Oracle's download records.

At this estate size the inventory could be complete rather than sampled, which makes for a considerably stronger position.

The eleven moves

1. Inventory by distribution. Oracle builds, OpenJDK builds and vendor embedded runtimes are three different licensing positions.
2. Find the bundled runtimes. Third party applications that ship their own Java are the most commonly missed category.
3. Evidence every removal. Dated and systematic. An undocumented uninstall proves nothing.
4. Reconcile against download records. Know what Oracle can see before the conversation opens.
5. Test the employee count definition. Understand precisely who the metric includes.
6. Scope the audit in writing. Entities, systems and periods, agreed before data moves.
7. Answer system by system. A total invites negotiation; a system invites correction.
8. Establish the OpenJDK path. For anything Oracle branded that remained.
9. Keep the audit separate from any renewal. They are different conversations.
10. Put controls on Oracle downloads. Otherwise the position rebuilds within a year.
11. Re inventory annually. Java arrives inside other software continuously.

The commercial outcome

The claim closed at zero cost, approximately $1.5M below Oracle's opening position.

Mid sized organizations often assume they lack the scale to defend one of these claims. The opposite is true: a smaller estate can be inventoried completely, and a complete inventory is the strongest position available.

How we engage

• Oracle Java scoping. A six week engagement that inventories Java by distribution, finds the bundled runtimes, and assembles the removal evidence. Oracle services practice.
• Oracle Java audit defense. We run the response, reconciling download records against evidenced deployment. Oracle Java audit defense playbook.
• Oracle Java exit. Costed migration to an OpenJDK build, with the controls that stop the position rebuilding. Oracle Java exit.
• Vendor Shield. Always on cover across Oracle and the wider software estate. Vendor Shield.
• Run the numbers. The Oracle Java license calculator sizes the employee metric against your actual estate.