Egothor/ZeroEcho
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects 1 Releases 2 Wiki Activity

Introduce approval workflows for issuance with assurance levels and M-of-N approval #5

New Issue
Open
opened 2026-03-24 17:59:03 +01:00 by galambos · 0 comments
galambos commented 2026-03-24 17:59:03 +01:00
Owner
Copy Link

Design and implement an issuance approval layer that supports multiple assurance levels and configurable approval rules. Example target behavior:

  • low-assurance user certificates: auto-issue or simple L1 approval,
  • server and infrastructure certificates: L2+ approval,
  • high-impact certificates: group approval such as 3-of-4 approvers.

Why this matters

This is a core requirement for highly regulated PKI operation. Issuance policy must not be limited to cryptographic correctness; it must enforce organizational authorization and separation of duties.

Acceptance criteria

  • Approval policies are profile-aware.
  • Approval decisions are modeled explicitly and stored as auditable evidence.
  • Support at least:
    • no approval,
    • single approver,
    • threshold/group approval.
  • Approval state is separate from cryptographic signing state but can gate it.
  • Design remains compatible with future remote signing and ACME automation.
Design and implement an issuance approval layer that supports multiple assurance levels and configurable approval rules. Example target behavior: - low-assurance user certificates: auto-issue or simple L1 approval, - server and infrastructure certificates: L2+ approval, - high-impact certificates: group approval such as 3-of-4 approvers. ## Why this matters This is a core requirement for highly regulated PKI operation. Issuance policy must not be limited to cryptographic correctness; it must enforce organizational authorization and separation of duties. ## Acceptance criteria - Approval policies are profile-aware. - Approval decisions are modeled explicitly and stored as auditable evidence. - Support at least: - no approval, - single approver, - threshold/group approval. - Approval state is separate from cryptographic signing state but can gate it. - Design remains compatible with future remote signing and ACME automation.
galambos added this to the PKI Foundation Hardening and Regulated Operations Roadmap project 2026-03-24 18:56:06 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project PKI Foundation Hardening and Regulated Operations Roadmap
Assignees
Clear assignees
galambos gitea-ci
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Egothor/ZeroEcho#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?