Use Remote Signers
BSSC Node Operation - Audit Framework
Domain: 4. Security and Access Control |
Level: SHOULD | Type: Preventive
Statement of Requirement:
Remote signers SHOULD be employed
See it in the specification
Purpose
Eliminate sensitive key material on network-connected nodes.
Audit Procedures
Verify that remote signers are deployed, on secured networks, for all
protocols implemented.
Key Evidence
- Key management architecture document; network topology diagrams
- Remote signer deployment guide; risk assessment for network path
security
- Node configuration showing remote signer integration (config files,
process flags, absence of local key files)
- Firewall/security group rules restricting signer access; TLS
certificate configurations
- Infrastructure-as-code showing remote signer deployment
Success Criteria
- Remote signers deployed for protocols where client software supports
them
- Network path between nodes and signers is secured (encrypted or
private network)
- Where remote signers not used, documented rationale and compensating
controls exist
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
- Remote signers not deployed for protocols where support is readily
available
- Remote signers deployed with insecure network paths
- Private key material on network-connected nodes
Justifiable Exceptions
Any exception to meeting this requirement needs to be justified. See
also Secure Remote Signer
Alternatives
Common Failure Patterns
- Remote signers communicate over unencrypted channel;
- remote signer is configured for primary client but not
failover/backup nodes;
- remote signers only used for some protocols
- remote signer is co-located on same host or security boundary
providing no meaningful isolation;
- remote signer availability is not monitored, potentially leading to
an undetected single point of failure.
Other Relevant Standards
A.8.24, A.5.33, A.8.12
CC6.1, CC6.7
3.5.1, 3.6, 4.1
PR.DS-01, PR.DS-02, PR.AC-01