previous: Provision Nodes
Sufficiently | Contents page | next: Use Remote Signers
Configure Resilient Nodes
BSSC Node Operation - Audit Framework
Domain: 3. Resilience and Performance |
Level: MUST | Type: Preventive /
Detective
Statement of Requirement:
Node Operators MUST provide documentation
of resilience to spikes in activity, with relevant measures assessed and
if necessary updated at least annually.
See it in the specification
Purpose
Ensure operations are not interrupted because nodes lack capacity to
meet requirements at peak demand levels
Audit Procedures
Verify that peak capacity specifications are maintained per Protocol,
with review at least annually
Key Evidence
Evidence of provisioning provided for Provision Nodes Sufficiently
Spike resilience configuration documentation; auto-scaling policies;
rate limiting configs
Internal audit schedule and reports; post-spike performance
analysis
Monitoring data from historical spike events showing node
performance
Auto-scaling event logs; load test results
Infrastructure-as-code showing resilience parameters
Success Criteria
Documentation of spike resilience measures exists, is specific, and
identifies measures implemented
At least one documented measure verified as implemented on sampled
nodes
Operator's own internal audits of resilience measures conducted at
least annually (distinct from certification audit)
If spikes occurred, nodes demonstrated acceptable performance (or
failures analyzed and measures updated)
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documentation of spike resilience measures exists
Documentation describes generic or aspirational measures not
implemented
No internal audit of resilience measures conducted (the NOS
certification audit does not satisfy this requirement)
Nodes failed during spike events and no remediation was
implemented
Common Failure Patterns
Documentation describes spike resilience theoretically without
specifying concrete measures;
auto-scaling is configured but never tested and scaling limits
prevent functioning as intended;
rate limiting is enabled for inbound RPC but not P2P gossip
floods;
periodic audit is not conducted or conducted superficially;
resource headroom is maintained for steady-state but insufficient
for spike scenarios;
operator has never conducted a load/stress test.
Other Relevant Standards
A.8.6, A.8.16, A.5.35, A.8.14
A1.1, A1.2, CC4.1, CC7.2
2.2, 10.7, 11.3
PR.PS-01, DE.CM-01, DE.CM-09, ID.RA-01
previous: Provision Nodes
Sufficiently | Contents page | next: Use Remote Signers