Multisig Operations — Security Checklist

Do you maintain documented policies and procedures governing your multisig operations?

Is there a clearly named person or team accountable for multisig operations (policy upkeep, reviews, hygiene)?

Do you operate a documented maintenance process to keep multisig documentation current after any operational or signer change?

Do you keep an up-to-date registry of all multisigs (address, network, purpose, threshold, modules/guards, admin roles, etc)?

Do you maintain an up-to-date list of authorized signers and map them to the correct multisigs?

Do you define and maintain a formal classification system for multisig wallets that covers both impact factors and operational needs?

Do you maintain documented criteria that map each classification level to required controls (thresholds, quorum composition, review cadence, etc)?

Do you periodically review and update classifications and associated controls when conditions change?

Do you maintain documented policies on the use of timelocks, modules and guards, including justification and security review requirements for any exceptions?

Do you maintain a documented exception approval process for deviations from standard multisig policies, including justification requirements, and authorization levels?

Do you maintain a documented process for cryptographic attestation of address ownership and signer affiliation for multisig signers?

Do you maintain a documented standard for signer key management?

Do you maintain documented policies and procedures for securely backing up and protecting signer seed phrases and recovery materials?

Do you operate a documented lifecycle for adding, replacing, and removing signers, including offboarding and periodic access reviews?

Do you have a documented training and readiness program for signers before they are authorized to participate?

Do you maintain documented processes for transaction initiation, approval, simulation, execution, and confirmation, including who is authorized to initiate?

Do you maintain documented signing and verification procedures that must be followed before any signatures are applied?

Do you maintain audit trails and retention for transaction reviews, approvals, execution, and post-execution confirmation?

Do you maintain a policy defining enhanced controls for high-risk transactions (emergency actions, large transfers, protocol configuration changes)?

Do you maintain documented standards for multisig technology and tools, and a formal evaluation process for adopting new ones?

Do you maintain documented backup infrastructure for multisig operations (alternate signing interfaces, RPC/explorers, failover procedures), and test their use?

Do you maintain dedicated primary and backup communication channels for multisig operations with documented membership controls and onboarding/offboarding procedures?

Do you have procedures to verify the identity of signers during sensitive communications, with periodic checks to ensure authenticity?

Do you maintain documented escalation policies that define response-time expectations, on-call coverage, and procedures for urgent coordination?

Do you maintain procedures for responding to suspected communication channel compromise, including switching to backup channels and out-of-band verification, and ensure signers know how to invoke them?

Do you maintain and distribute an up-to-date emergency contact list for multisig operations?

Do you maintain written emergency playbooks covering key compromise, lost access, and urgent protocol actions?

For critical/emergency-class multisigs, do you provide 24/7 paging to reach the required threshold and document escalation paths?

Do you maintain monitoring infrastructure and procedures to detect unauthorized, anomalous, or suspicious activity across all multisigs, with documented alerting and escalation paths?

Do you conduct periodic rehearsals and drills of emergency playbooks to test response procedures, communication channels, and signer coordination under simulated emergency conditions?