<img alt="" src="https://secure.weed6tape.com/193471.png" style="display:none;">
Join us at SUDC 2026 – Discover the latest in cybersecurity, cryptography, and digital trust. Secure your place.

Register now

About
About
Learn more about our mission, explore career opportunities, and access our resources. Discover how we’re shaping the future of cybersecurity and how you can be part of it.
Contact us
  • There are no suggestions because the search field is empty.

Why should business logic run in a trusted execution environment?

In many security architectures, encryption keys are protected inside Hardware Security Modules (HSMs), but the logic that decides how and when those keys are used remains outside — on vulnerable application servers or reliant on human interaction. This introduces a critical risk: even if the keys are safe, compromised applications or manipulated operators can misuse them, bypassing your security protocols.

How does VaultCode work?

Securosys VaultCode provides a secure and isolated environment to execute your sensitive business logic — either inside the Primus HSM or on a trusted external host. By embedding decision-making logic alongside the cryptographic keys, VaultCode ensures that transactions can only be approved and signed when authorized logic is successfully executed. Each execution is cryptographically signed and accompanied by verifiable evidence (attestation) of what code was run, when, and in what environment.

VaultCode acts as a "safe room" for your business logic, ensuring sensitive workflows are protected with the same security standards as your cryptographic keys.

Why do organizations choose VaultCode?

blocks-lock-b&w
End-to-End Trust
Business logic and key usage are unified within a tamper-proof environment — no external manipulation possible.
locket-key-b&w
Cryptographic Attestation
Execution is not only isolated but also digitally signed by an HSM, providing verifiable integrity.
locket-circle-blocks-b&w
Flexible Deployment
Run inside the HSM for maximum protection in production, or outside as a container during testing and integration.
key-circle-people-b&w
Fine-Grained Access Control
Alongside SKA, VaultCode logic can process automated approvals or enforce granular multi-actor approvals, according to business policy.

What is VaultCode used for?

colourful-background-patterns-14 Automated Transaction Approval Enforce rules for transaction signing within the HSM, such as limits, schedules, or role-based conditions.
colourful-background-patterns-11 Decentralized Signing Workflows Secure business workflows that need provable evidence of logic execution before using a key.
colourful-background-patterns-13 Regulatory Compliance Deliver cryptographic proof of policy enforcement to meet strict audit or regulatory requirements.

FAQ

What is VaultCode?
VaultCode is a secure runtime environment that executes custom business logic inside a trusted environment protected by a Securosys Primus HSM. It generates cryptographic evidence (attestation) proving which code was executed, when it ran, and in which environment.
How does VaultCode work?
VaultCode executes customer-defined code within a secure runtime environment inside the HSM. Before execution, only approved executables can be loaded. After execution, VaultCode cryptographically signs the output together with attestation data, providing verifiable proof of the execution. 
Why run business logic inside an HSM?
Running business logic inside an HSM eliminates the gap between protected cryptographic keys and untrusted application servers. Sensitive decisions are executed within the same trusted boundary as the keys, significantly reducing the risk of compromised applications or unauthorized manipulation.
What is cryptographic attestation?
Cryptographic attestation is a digitally signed proof that verifies the integrity of an execution. VaultCode attests the executable, runtime environment, timestamp, and output, allowing organizations to prove exactly what code was executed and under which conditions. 
What can VaultCode be used for?
VaultCode is designed for security-critical workflows such as automated transaction approvals, fraud detection, compliance validation, escrow services, and other business processes that require trusted execution before cryptographic keys are used.
Can VaultCode automate approval workflows?
Yes. VaultCode can execute custom approval logic that automatically approves or rejects requests based on predefined business rules. When integrated with Smart Key Attributes (SKA) and the Transaction Security Broker (TSB), automated and manual approvals can be combined within the same workflow. 
What programming languages does VaultCode support?
VaultCode executes JAR executables, allowing developers to write business logic in Java or any programming language that compiles to JVM bytecode.
How does VaultCode prevent unauthorized code execution?
Only executables that have been explicitly allow-listed by Security Officers can run in VaultCode. Organizations can approve individual executable hashes or trusted code-signing keys, ensuring that unauthorized or modified code cannot be executed. 
Can VaultCode be tested before deployment?
Yes. For development and integration testing, VaultCode can run as a Docker container outside the HSM or in a simulator. Production deployments run inside a Primus HSM to provide full hardware-backed security and attestation.
How is VaultCode different from running code on an application server?
Unlike an application server, VaultCode executes business logic inside a trusted environment protected by the HSM. It prevents runtime tampering, enforces authorized code execution, and produces cryptographic evidence that proves the integrity of every execution.