Remediation
Vulnerability remediation with Eden
Eden can enforce a supported policy or run a separately compiled Rust patch in front of an application. The control must see the relevant input and act before the prohibited effect on every traffic path included in the protection claim. Patching the application to an upstream fixed release remains a separate action; a gateway mitigation does not replace the installed vulnerable component.
Start with method selection, use the API and package lifecycle, then follow the testing and operations procedure.
Current native HTTP state
The shared engine's 1.103.0 native HTTP functional MVP is integrated in the shared project source. Separately compiled optimized Rust modules execute in the same serving process through the shared SDK and a versioned C ABI. The native request path does not use WebAssembly, a worker RPC or a registry/database lookup. Management changes publish small local state copies to the relevant CPU shards; serving requests borrow that local state.
Independent qualification of the normal installed single-node Linux x86-64 Service and matching CLI passed 17 functional groups, including seven exact package imports/downloads and ten pinned manifest/TOML inventory pairs. The application and Service identities stayed unchanged through the live patch sequence. The benign examples removed a debug header and changed a small body, with independent upstream byte/effect checks, replacement, revoke and reclamation.
This is functional integration evidence. Eligible real-application protection remains unqualified; no named-vulnerability protection is established by those examples. Broader performance diagnosis and extended installed pressure remain deferred, with earlier numeric failures preserved. The qualification does not establish maximum throughput, all HTTP forms, HA native loading, another gateway, all delivery forms or general production readiness. Shared source integration alone does not mean the corresponding artifact is released or deployed.
Package and signature boundaries
Native and API/declarative patches share an immutable schema-2 package with a name, release version, applicability, publisher, license, compatibility and exact content identities. API and registry delivery carry the same archive bytes. Importing that archive does not activate protection.
The package envelope reserves a signatures field. Its current value must be []; new envelope-signature verification is deferred. This does not remove the existing native publisher signature or independent host approval required before native executable admission.
Before operating
Identify the actual application image/version/configuration and the vulnerable operation, then verify that the chosen Eden profile observes it early enough. Confirm the deployment's product/engine identities, features, TLS boundary, endpoint, interlay, current authority and traffic path. Use the installed build's OpenAPI discovery, supplemented by its matching runtime contracts. Feature availability and qualification are specific to the artifact.
Operate within the authorized environment and scope. A useful protection result includes independent evidence that the harmful effect is prevented and the required ordinary application workflow still works. An API success, a local ready status or a changed response code cannot establish that alone.
Agent skill
The repository includes the portable [eden-vulnerability-remediation skill](https://gitlab.com/eden7445803/eden-dev/-/tree/project/eden-runtime-dynamic-virtual-patching-mvp/skills/eden-vulnerability-remediation). Retain its SKILL.md and references/ together when adding it to an agent's configured skill directory. It guides method selection, exact API discovery, publication, validation and rollback; invoking it does not itself authorize changing a deployment. Repository access may be required.
For the implementation contracts, see native module authority, native ABI and wire edits and packages and running inventory. Those pinned contracts describe the reference source; reconcile them with the actual installed revision before sending management operations.