DRep Key & Account Security Runbook workspace

Never record a seed phrase, private key, password or recovery code here. No field on this page is designed to hold a secret.

This review

0/3 done

Date of this review

Why you are running it

Device and wallet inventory

One row per item. Rows can be reordered, duplicated and removed.

No rows yet. Add the first one below; you can reorder and duplicate rows as you go.

Key custody

0/1 done

Key custody

Tick only what you have actually confirmed. An unticked box is a finding.

0 of 6 checked

DRep key is generated and held on a hardware signing deviceSigning device firmware version checked against the vendor advisory pageGovernance key is separate from any key used for routine spendingNo key material has ever been typed into, pasted into, or photographed on an internet-connected devicePassphrase use is a deliberate decision, documented as used or not usedAny multi-person arrangement is written down with who holds what

NotesOptional

0 words

Backups and recovery

0/1 done

Backups and recovery

Tick only what you have actually confirmed. An unticked box is a finding.

0 of 7 checked

Backup exists for every credential needed to resume governance workBackup medium is durable and stored apart from the signing deviceAt least two geographically separated copies where the threat model warrants itRecovery has been tested end to end on a wiped or spare deviceDate of the last successful recovery test recordedBackup contents are never stored in cloud storage, email, password managers, or photosRecovery procedure is written for someone else to follow without needing you

NotesOptional

0 words

Device and account security

0/1 done

Device and account security

Tick only what you have actually confirmed. An unticked box is a finding.

0 of 8 checked

Full disk encryption enabled on every device used for governanceOperating system and browser patched to current versionsScreen lock and strong device credential in placeBrowser extensions reviewed; unused extensions removedUnique credentials for every governance-related account, held in a password managerPhishing-resistant multi-factor authentication such as a security key on email and social accountsEmail account recovery options reviewed, since email is usually the weakest linkEvery signing request read on the device screen and confirmed against what was intended

NotesOptional

0 words

Phishing and social engineering

0/1 done

Phishing and social engineering

Tick only what you have actually confirmed. An unticked box is a finding.

0 of 6 checked

Treat unsolicited contact about your DRep status as hostile until proven otherwiseNever enter a recovery phrase into any site, support agent, or wallet restore prompt you did not initiateVerify governance tool URLs from a bookmark rather than from search results, links, or messagesAssume urgency is a technique: deadline pressure is the most common lever used against DRepsConfirm any request to sign, delegate, or move funds through a second channelReport attempts publicly so other DReps recognise the pattern

NotesOptional

0 words

Continuity and incident documentation

0/1 done

Continuity and incident documentation

Tick only what you have actually confirmed. An unticked box is a finding.

0 of 5 checked

Named contact who knows a governance role exists and what to do if you are unavailableInstruction on whether delegators should be told to redelegate, and how that message would be publishedPlan for extended absence: retire, pause, or delegate the workloadIncident log: date, what happened, what was affected, what was rotated, what was publishedPost-incident review recorded with the change made to prevent recurrence

NotesOptional

0 words

Recovery test

A backup you have not restored is a hope, not a backup.

0/3 done

Date of the last successful recovery test

Tested on which device

What the test found

0 words

Continuity

0/3 done

A named contact knows the governance role exists

What that contact is instructed to do

0 words

How delegators would be told to redelegate

0 words

Incidents and near misses

0/2 done

Incident logOptional

One row per item. Rows can be reordered, duplicated and removed.

No rows yet. Add the first one below; you can reorder and duplicate rows as you go.

Unresolved items after this review

Anything still open when you stopped. This is the honest part of the record.

0 words

Next review date

When this should be looked at again, if it should.

Working notesOptional

Anything the structured fields do not cover.

0 words

The DRep Standards Institute provides decision-support tools. It does not determine how any DRep votes. This record was produced independently by its author.