Skip to content

Components

The Code Signing API acts as the external entry point for signing requests.

Responsibilities:

  • Authentication and authorization
  • Request validation
  • Policy enforcement
  • Request routing to the signing engine

The API never has direct access to private signing keys.


The Signing Engine performs cryptographic signing operations.

Responsibilities:

  • Validate approved signing requests
  • Invoke cryptographic providers
  • Generate digital signatures
  • Return signed artifacts

The signing engine operates within a restricted execution boundary.


The Key Management Layer provides controlled access to signing keys.

Supported options include:

  • Software keystore (non-production)
  • Hardware Security Module (HSM)
  • Cloud or on-prem KMS via PKCS#11

Private keys are never exposed outside this layer.


This component maintains:

  • Signing policies
  • Certificate metadata
  • Key associations
  • Configuration state

It does not store private key material.


Audit Logs

The audit subsystem records all security-relevant actions, including:

  • Signing requests
  • Policy changes
  • Key usage events
  • Administrative access

Audit logs are immutable and suitable for compliance review.