Mitigate the risks entailed by not reacting rapidly to any protocol
changes.
Audit Procedures
Verify that documented procedures describe:
staff or roles responsible for monitoring protocol changes;
sources of protocol change information;
monitoring responsibilities;
review frequency or monitoring mechanism; and
requirements for updating risk assessments when material protocol
changes occur.
Interview responsible staff and verify that they understand the
protocols they are monitoring, and are aware of and capable of
efficiently performing their role in responding to protocol changes
If protocol changes occurred during the assessment period verify
that:
the change was identified by the operator;
associated risks were evaluated; and
risk management procedures, operations and documentation were all
updated as relevant in a timely manner.
Key Evidence
Protocol monitoring policy/procedure and change tracking log
Updated risk assessments reflecting protocol changes with revision
dates
Alert/notification logs from monitoring tools
GitHub/repository watch configs, RSS/mailing list subscriptions
Ticketing system logs, showing responses to protocol changes
Success Criteria
Documented, repeatable monitoring process exists covering all
operated protocols
Evidence demonstrates continuous monitoring throughout the audit
period
Operator demonstrates detection and response to at least one
protocol change per operated protocol
Risk assessments are updated when material protocol changes
occur
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documented monitoring process exists
Monitoring is ad-hoc or inconsistent across protocols
A material protocol change occurred that the operator failed to
detect or respond to
Risk assessments are never updated post-onboarding
Common Failure Patterns
Monitoring relies on a single individual rather than a systematic
process
Sources are incomplete (e.g., "Crypto-Twitter" or blog posts only,
missing on-chain governance or GitHub commits)
Changes are detected but risk assessments never updated
No escalation path for high-severity changes
Monitoring cadence is too infrequent (e.g. quarterly or monthly
rather than continuous)