Transaction Security Broker (TSB)
Challenge
Modern financial and digital asset applications require more than basic key usage. They increasingly depend on fine-grained policies and complex workflows.
Implementing these workflows directly inside each application is complex. They require state management, authorization collection, and reliable coordination, while ensuring that all security-critical checks remain inside the HSM.
Solution
The Securosys Transaction Security Broker (TSB) simplifies the implementation of advanced authorization and key-usage workflows and how applications interact with the Primus HSM. TSB is a Java-based service that communicates with the HSM over JCE while exposing a language-agnostic REST API that applications can use without installing client-side libraries. All cryptographic operations and security-critical checks remain inside the HSM, while TSB orchestrates request handling, approval logic, and workflow state.
Approvals can be provided using signing keys held on crypto tokens, in software, or through the Securosys Authorization App. The Securosys Authorization App provides approvers with a simple interface to receive notifications, review requests, and submit approvals. TSB manages communication with the app and collects approvals before forwarding authorized operations to the HSM.
TSB supports two usage modes. In its basic mode, it acts as a REST translation layer, enabling applications to perform signing, decryption, and key management operations through REST calls. In its workflow mode, TSB manages Smart Key Attribute (SKA) approval processes by collecting authorizations, coordinating multi-step workflows, and forwarding completed authorization data to the HSM. This separation ensures that all the approvals required by the SKA policy have been gathered together by TSB outside the HSM, while only the HSM itself enforces all policies
Key Benefits
Why TSB vs. Multi-signature?
- Works with all supported crypto assets — independent of blockchain signature formats
- Lower fees and better privacy due to single-signature on-chain addresses
- Decouples key ownership from key usage for operational and regulatory flexibility
- Supports advanced policy models including time-restrictions
Why TSB vs. Multi-Party Computation (MPC)?
- Supports time-based workflows
- Key material stays hardware-protected
- Redundant deployment without increasing key-exposure risk
- Simpler lifecycle management and operational model
The approval process applies when using Smart Key Attributes with TSB.
To support SKA workflows, the Securosys Authorization App enables approvers to receive notifications, review pending tasks, and provide approvals directly from their devices. The app integrates with TSB, which orchestrates the workflow while the HSM performs all policy enforcement.
Use Cases
Multi-Quorum Transaction Approval
Enable m-of-n or multi-layer approval flows for high-value financial transactions, ensuring controlled and verifiable authorization.
Time-Locked Transaction Security
Enforce time-based policies to delay or restrict key operations, reducing operational risk.
Hybrid Approval Systems
Combine device-based approvals, user roles, or multi-device workflows with HSM-based key protection.
Policy-Driven Key Usage Control
Define complex, granular SKA policies for key usage and enforce them through TSB for digital assets, financial operations, and regulated environments.
Related Products
Securosys Authorization App
Approve cryptographic operations anywhere, anytime
