Isolated analysis environments
We're building Kleydin so each binary is analysed in its own isolated environment, kept apart from other customers.
Security approach.
Kleydin is pre-launch. This is how we're designing it to handle your binaries, your data and its own decisions.
Your binaries stay yours.
How we're designing Kleydin to handle what you upload.
Encrypted in transit and at rest
Binaries, findings and reports will be encrypted in transit and at rest.
Deletion on request
You will be able to delete your binaries and results whenever you ask.
No training on customer data
Your binaries, findings and reports will never be used to train models.
Who can see what.
Least privilege
We will keep access to customer data on our side as narrow as we can.
Team controls
Controls for who can upload, review and export are planned. We'll describe them here once they exist.
Honest about gaps
If something on this page isn't built yet, we'll say so rather than imply it is.
Autonomous agents, on a short leash.
The agents will run code written to be hostile, so we're building them to do it where it can't hurt anyone.
Sandboxed dynamic analysis
Apps and firmware will run in sandboxes, not on shared infrastructure.
Limited network access
Analysis environments will be cut off from the internet, apart from test targets in scope.
Logged agent actions
Every agent action will be logged, so a run can be reviewed step by step.
A human where it matters
Agents are designed to stop and ask when the evidence is unclear, rather than guess.
Only binaries you have the right to test.
Kleydin is being built for defenders. Customers will need the right to test every binary they upload: their own software, or a client’s under a signed engagement.
No certifications yet.
We’re pre-launch and don’t hold any security certifications. We won’t show a badge until we’ve earned one.
- Every finding is designed to carry decompiled code, a call path and a re-runnable check, so you can verify it yourself
- Detection and false-alarm rates will be published at launch with the method behind them, misses included
Security questions, or need a draft DPA for evaluation? Email hello@kleydin.com.
Everything else a security review asks for.
Subprocessors
Will be listed before we process any customer data.
Privacy policy →Responsible disclosure
Found a vulnerability in Kleydin? Here's how to tell us.
Disclosure policy →Security team
Reports, questions and anything that should not wait. Use the subject 'Security'.
hello@kleydin.com