by StoneRock Cyber Editorial Team | Oct 28, 2026 | Recordkeeping
The continuity documentation mistakes that cause the most trouble are not dramatic. They are a document nobody dated, a contact list with a person who left, a runbook written in the author’s own shorthand, and a set of files kept in exactly the one place that...
by StoneRock Cyber Editorial Team | Oct 28, 2026 | Resilience
A continuity exercise is a scheduled conversation in which the people who would have to act walk through a simple scenario using only the documents they actually have. Someone facilitates, someone writes down what they observe, and the session ends with a short...
by StoneRock Cyber Editorial Team | Oct 28, 2026 | Business Continuity
A recovery runbook is one page per process that says what the process is, who performs it, the steps to bring it back, and who to tell. The test of a good one is simple: a competent person who does not normally run that process should be able to follow it without...
by StoneRock Cyber Editorial Team | Oct 28, 2026 | Recordkeeping
To verify backups restore, you take a copy that has already been made, bring the data back somewhere it can be examined, check that what came back is complete and readable by the people who use it, and write down the result with a name and a date against it. A green...
by StoneRock Cyber Editorial Team | Oct 28, 2026 | Business Continuity
To map business dependencies, you list the handful of processes your business genuinely runs on, write down what each one needs in order to work, mark which processes feed each other, and then stop. The result should be short enough that someone unfamiliar with your...