Skip to content

SafeNet Signing Server

Centralized digital signing for enterprises

SafeNet Signing Server is a centralized digital-signing system — a "digital notary office" inside your infrastructure. Instead of scattered USB tokens, every application simply sends a document and gets it back signed: "Send a document — get it back signed."

The problem

Traditional signing scatters USB tokens across machines, leaving signing keys dispersed and uncontrolled, each app re-implementing signing (and breaking standards), with no central audit trail. Scaling up only multiplies operating cost.

Features & capabilities

One synchronous API call

  • Authenticate the calling application
  • Use a signing key protected in a security device
  • Sign, add timestamp and validation evidence
  • Write a tamper-proof log and return the signed document instantly

Multi-format signatures

Supports the 8 most common AdES formats, plus signature verification.

  • PAdES (PDF), CAdES (binary), XAdES (XML)
  • JAdES (JSON), ASiC (container), OOXML (Office), XMLDSig
  • Multiple assurance levels up to long-term archive (B-LT / B-LTA)

Security & compliance

  • Signing keys never appear in readable form
  • Software keys encrypted with AES-256, or kept in a certified HSM
  • Layered checks: IP allowlist, API key and mTLS
  • Append-only, sealed audit log

Scale & operations

  • Stateless architecture, run multiple servers in parallel
  • Modern web console for keys, certificates, apps and logs
  • Flexible keys: software, USB/HSM hardware or cloud key service
  • Runs fully inside your network — on-premise ready

Use cases

E-invoicing & accounting

Auto-sign batches of XML invoices every day.

E-contracts

Sign PDFs as soon as parties complete approval.

Public service portals

Stamp decisions, licenses and procedure results.

Digital transactions / API

Sign JSON data to ensure integrity between systems.

Standards & compliance

ETSI PAdES / CAdES / XAdES Circular 15/2025/TT-BKHCN

Frequently asked questions

Does it replace USB tokens? +

Yes. Signing keys are centralized on the server (in an HSM or encrypted in the database) and apps call via API instead of plugging in a token.

Are my documents stored on the server? +

No. Documents are processed in memory during signing and returned immediately. The server only stores the document digest in the log, not its contents.

Can a signature still be verified years later? +

Yes, with a long-term level (B-LT / B-LTA): the signature embeds a timestamp and certificate-validation evidence.

Interested in SafeNet Signing Server?

Book a free consultation with a SafeNet expert for a demo and a fit assessment for your organization.