# Security Baked Into the JVM: no single party controls the outcome

DevFeed: [Security Baked Into the JVM: no single party controls the outcome](<https://devfeed.tech/articles/security-baked-into-the-jvm-no-single-party-controls-the-outcome-64650.md>)

Original publisher: [Read original article](<https://blog.frankel.ch/security-baked-into-jvm/5/>)

Author: Peter Firmstone

Published: 2026-10-04T00:00:00Z

Content type: article

Language: en

Sources: [Nicolas Fränkel](<https://devfeed.tech/sources/nicolas-frankel.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [dirtychai](<https://devfeed.tech/tags/dirtychai.md>), [java](<https://devfeed.tech/tags/java.md>), [jgdms](<https://devfeed.tech/tags/jgdms.md>), [jini](<https://devfeed.tech/tags/jini.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [repo](<https://devfeed.tech/tags/repo.md>), [security](<https://devfeed.tech/tags/security.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

The article explains security controls in JGDMS: validating serialized arguments before object creation, granting permissions based on JAR digests and caller identities, and combining policy layers to limit delegated authority. It also describes fail-closed behavior when policies or digest support are unavailable.

## Source excerpt

A URL is a name, and names get reused. Replace the bytes behind https://repo.example.org/order-processor.jar and every permission granted to that URL still applies, now to code nobody audited. So far in this series, Part 1 declared constraints on a remote call, Part 2 vetted code before a client loaded it, Part 3 established who is calling, and Part 4 carried that chain of identities across the wire.