Discover vulnerable behavior and turn a reproducible exploit into validated patch logic.
Client requests
Eden runtimeDiscover risk · apply patch logic
Your application
Discovery signals ↓↑ Over-the-air patch
01 / DISCOVERY
Discover vulnerable interactions.
Requests
Protocol, command and query patterns
Behavior
Request rate, latency, errors and response sizes
Context
Endpoint, identity and policy decisions
Inspection
Sampled analysis and sensitive-data findings
02 / REPRODUCE
Find the vulnerable behavior.
01
Spot the signal
Look for risky patterns, unexpected behavior and sensitive-data exposure.
02
Reproduce the exploit
Turn a suspected weakness into a repeatable test.
03
Confirm in isolation
Understand the triggering request before developing the defense.
03 / SUBMIT LOGIC
Ship the defense as code.
EXAMPLE PATCH LOGIC
if matches_exploit(request):
return block()
return forward(request)
Test exploit + everyday requests
Authorize the rollout
Apply in Eden’s runtimeBlock or transform before the app
Illustrative security workflow. Discovery inputs depend on the deployment and enabled analysis. Patch logic runs in Eden; application code stays unchanged.
DEPLOYMENT
Protect where your applications run.
Choose where Eden Sphinx protects your traffic.
MiddlewareILLUSTRATIVE PATH
Client service
VM
Eden Sphinx
Target server
Route requests from a client service through Eden Sphinx in a VM before they reach the target server.
HOW IT WORKS
The fix takes time. Protection shouldn’t.
A vulnerability usually means a code change, testing, and a redeploy. Eden intervenes in the request itself, so security can act while the application stays unchanged.
Eden understands application traffic and changes how it reaches your software. It blocks unsafe requests or applies validated targeted transformations before vulnerable code handles them.
01
Understand the request.
Identify the interaction and the condition that makes it unsafe.
02
Apply protection.
Block the unsafe request or change the part that triggers the vulnerability.
03
Check the result.
Review the unsafe interaction alongside legitimate requests.
RUNTIME BOUNDARY
CVE-2021-44228 · Log4Shell
How Eden mitigated Log4Shell
Follow a logging request from the vulnerable input to the verified runtime protection.
In affected Log4j configurations, an attacker-controlled log message can trigger a JNDI lookup. We traced the input to the message field on the lab’s logging endpoint.
Request path in the lab
POST /api/log
JSON message field
Simulated JNDI lookup
These results cover the literal lookup pattern on one route in a synthetic fixture. The vendor upgrade fixes the underlying vulnerability. Apache advisory
WHERE TO START
For the software you can’t patch today.
01
Vendor-controlled software
The vendor controls the release schedule. Your security team can still protect the application.
02
Legacy applications
Protect the application even when the source is unavailable or the software is difficult to rebuild.
03
Critical services awaiting a release
Keep production protected while engineering tests the code fix and prepares a release.
QUESTIONS
How Eden fits your environment.
How does Eden protect an application without a code change?
Eden acts directly on application traffic. It blocks requests that trigger vulnerable behavior or applies validated targeted transformations before they reach your application. Your security team can deploy protection without waiting for an engineering release. The underlying code fix remains a separate step.
Can Eden change unsafe requests instead of just blocking them?
Yes. Eden understands application protocols and can transform requests in transit, changing the behavior that makes an interaction unsafe. It can also allow or block requests. We test each transformation against the exploit and legitimate application behavior before deployment.
Do we need to change or redeploy our application?
No application source-code change or application redeploy is required for traffic-path protection. Deploy Eden Sphinx as middleware, as a native service on the application VM, at the container runtime, or in Kubernetes networking. We work with your team to set up routing, TLS, and policies for your environment.
Can Eden inspect encrypted traffic?
Yes, when Eden has authorized access to decrypted traffic. Configure TLS termination or an approved decryption point so Eden can inspect requests and apply protection. We help you establish the certificate, routing, and data-handling setup for your environment.
Which protocols does Eden support, and can we configure them at runtime?
Eden supports multiple database and application protocols, including PostgreSQL, MySQL, MongoDB, Redis, and HTTP. Manage their endpoint and traffic-listener configurations at runtime through Eden’s API, without changing application code. Protection controls vary by protocol; we’ll map your stack to the right configuration and demonstrate it against your use case.
How will Eden perform with our production traffic?
Eden’s traffic engine comes from live database migrations, where real-time translation and tight latency control are essential. Evaluate it with your workload: measure latency, throughput, resource use, and legitimate request behavior with protection enabled. You get evidence from your environment to guide deployment.
How does Eden fit into autonomous security?
Eden provides the runtime intervention layer that turns a defense into action. Our vision is a continuous red-blue loop that discovers vulnerable interactions, reproduces exploits, develops protection, and verifies the result. Start with runtime protection today, then assess the available automation and deployment controls with our team.
Stay ahead of threats. And the competition.
Get early access to real-time vulnerability remediation without changing source code.
