One requirement an external wrapper cannot meet

PCI DSS Requirement 3.5.1 says the primary account number must be rendered unreadable anywhere it is stored. A heap dump of a payment service stores live card numbers in cleartext. That makes dump contents a dump-writer problem inside the JVM, not a flag anyone can set from outside it. No wrapper, chart, or webhook can reach into how the VM serialises the heap. It is one of several requirements that live in the capability space, reachable only by whoever builds the runtime; the policy point essay sets out the general case.

What Eliya gives a financial-services workload today

One flag, -XX:EliyaProfile=Production, activates the Phase 1 operational-readiness defaults: heap dump on OutOfMemoryError to a structured path, a predictable crash-log path, Native Memory Tracking (summary), reinforced container support, and exit on OutOfMemoryError. Crucially, all diagnostic capture runs locally: no SaaS, no telemetry. Cardholder and transaction data captured in an incident stays inside your cardholder data environment rather than crossing into a third-party processor.

Eliya is the same Java you already run, built from the upstream OpenJDK 25 source tree under GPLv2 with the Classpath Exception, with no API changes, and maintained on a quarterly Critical Patch Update cadence on an LTS line.

What does not ship today

Eliya does not ship a PCI-aligned profile today, and it does not yet redact PAN inside a heap dump. What it ships is the policy point and the structured diagnostic foundation that such controls require, plus local-only capture so the dump never leaves your perimeter. A FIPS 140-3 variant is a Phase 2 deliverable; compliance-aligned profile values, such as a PCI-aligned profile, are demand-gated and sit in Phase 4. Neither is in the 25.0.3 binary. The roadmap sets out what is built and what is not.


Next: download Eliya, read the thesis, or see the security posture.

[ } Eliya Eliya Dial Dial
Privacy
[ }
[ }
// PRODUCTS Eliya Eliya Dial Dial