Skip to content

Policies

The Policies section enforces governance rules that control how, when, and by whom signing operations can be performed.

Policies Inventory


Policies define:

  • Who can sign
  • Which keys can be used
  • Which certificates are allowed
  • What artifacts can be signed
  • When signing is permitted
  • Whether approval is required

Policies are evaluated before every signing request.


Each policy displays:

  • Name
  • Priority
  • Status
  • Keys Scope
  • Certificates Scope
  • Users Scope
  • Time Window
  • Actions (Edit / Delete)

Higher priority policies are evaluated first.


Create Policy - Basic

  • Policy Name
  • Priority
  • Status (Enabled / Disabled)

  • Select specific keys
  • Leave empty to apply to all keys
  • Key ID acts as authoritative control
  • Restrict by certificate metadata
  • Optional constraint layer

  • Allowed artifact types
  • Maximum artifact size (MB)
  • Optional file-type enforcement

Create Policy - Restrictions


  • Allowed users
  • Wildcard support (e.g., *@company.com)
  • Service accounts and CI/CD identities

  • Start Time (HH:MM)
  • End Time (HH:MM)
  • Leave empty for unrestricted access

Supports business-hour or maintenance-window enforcement.


When a signing request is received:

  1. Platform identifies associated key
  2. Applicable policies are retrieved
  3. Policies evaluated by priority
  4. Approval requirement determined
  5. Decision: Allow / Require Approval / Deny

All evaluations are fully audited.


Policies enable:

  • Separation of duties
  • Dual control approval workflows
  • Least privilege enforcement
  • Risk-based signing controls
  • Compliance readiness (SOC2, ISO 27001, NIST)