Backup Validation
Plan backup strategy, testing, and restoration verification for "$ARGUMENTS" covering backup inventory, frequency, storage locations, test restoration schedule, and monitoring.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"skipped","artifact":"05-recover.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 5 (Recover) of the NIST CSF workflow (security); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or security when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"refused","artifact":"05-recover.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"started","artifact":"05-recover.md","note":""}.
Read .singularskills/security/<project>/00-govern.md. If this file does not exist, tell the user:
Phase 0 (Govern) has not been completed for "". Run a Govern skill first (e.g., /security-security-policy <project>), or use --skip-checks to bypass.
Process
Read context files:
- Read
references/incident-response-template.md for recovery reference
- Read
.singularskills/security/<project>/00-govern.md for organizational context and data classification
Inventory what is backed up:
- Databases — production databases, read replicas, configuration databases
- File systems — application data, user uploads, shared storage
- Configurations — infrastructure-as-code, application config, environment variables
- Secrets — encryption keys, certificates, API keys (backed up to separate secure vault)
- Code and artifacts — source code repositories, build artifacts, container images
- Identify what is NOT currently backed up and assess whether it should be
Define backup frequency per data type:
- Real-time replication — production databases, critical state stores (synchronous or asynchronous replication)
- Hourly — transaction logs, high-change-rate data stores
- Daily — application data, file systems, configuration snapshots
- Weekly — full database backups, complete system images
- On change — infrastructure-as-code, secrets, certificates (version-controlled)
- Align frequency with RPO targets from recovery plan
Define backup types:
- Full backups — complete copy of all data (weekly or as baseline)
- Incremental backups — only changes since last backup (daily, reduces storage and time)
- Differential backups — changes since last full backup (mid-week, balances recovery speed and storage)
- Snapshots — point-in-time snapshots for cloud resources (EBS, RDS, managed disks)
- Define retention periods per backup type (daily: 30 days, weekly: 90 days, monthly: 1 year)
Define storage locations:
- On-site — local storage for fastest recovery (hot standby)
- Off-site — geographically separate facility for disaster protection
- Cloud — cloud object storage (S3, Azure Blob, GCS) with cross-region replication
- Air-gapped — offline storage disconnected from network for ransomware protection
- Apply 3-2-1 rule: 3 copies, 2 different media types, 1 offsite
- Encrypt all backups at rest with keys stored separately from backup data
Define test restoration schedule:
- Critical systems (Tier 1) — monthly restoration test to isolated environment
- Important systems (Tier 2) — quarterly restoration test
- Supporting systems (Tier 3) — semi-annual restoration test
- Test procedure: restore to isolated environment, verify data integrity, verify application functionality, measure restoration time
- Document test results: success/failure, restoration time, issues encountered, corrective actions
- Annual full disaster recovery exercise simulating complete environment restoration
Define backup monitoring and alerting:
- Monitor backup job completion (success/failure/partial)
- Alert on backup failures immediately (P2 for Tier 1, P3 for Tier 2–3)
- Monitor backup size trends (detect anomalies — sudden growth or shrinkage)
- Monitor storage capacity and forecast depletion
- Track backup and restoration SLA compliance (backup window, retention compliance)
Document restoration procedures step-by-step:
- Per system type: prerequisites, access requirements, step-by-step commands or console actions
- Include rollback plan if restoration fails
- Document known issues and workarounds from past restoration tests
- Maintain runbook in accessible location (not only on systems that might be unavailable)
Write the artifact — append to .singularskills/security/<project>/05-recover.md under a ## Backup Validation section. Create the file with a # Recover — <project> heading if it does not exist; if a ## Backup Validation section already exists, replace only that section. The section contains:
- Backup Inventory — what is backed up and what is not
- Backup Frequency — per data type aligned with RPO targets
- Backup Types — full, incremental, differential, snapshots with retention periods
- Storage Locations — on-site, off-site, cloud, air-gapped with 3-2-1 compliance
- Test Restoration Schedule — testing cadence and procedures per tier
- Monitoring and Alerting — backup job monitoring and anomaly detection
- Restoration Procedures — step-by-step per system type
Output
The backup validation plan appended to .singularskills/security/<project>/05-recover.md. Present a summary to the user highlighting:
- Backup inventory coverage and identified gaps
- Backup frequency aligned with RPO targets
- Storage strategy following 3-2-1 rule
- Test restoration schedule and monitoring approach
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"finished","artifact":"05-recover.md","note":""}.
This artifact is shared by every skill of phase 5 (Recover). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Recover
workflow: security
phase: 5
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Backup Validation section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is security-backup-validation).
End your section with ### Decisions and ### Open questions (one level under your ## Backup Validation heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not a penetration test or audit. This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.
1---2name: security-backup-validation3description: Plan backups and prove they restore — what is and is not backed up, frequency and backup types, 3-2-1 storage, a test restore schedule, backup monitoring and step-by-step restore procedures. Use when the user is unsure their backups work, asks how often to back up, or wants restore testing on a schedule.4metadata:5 source: https://skillmd.com/skills/bromso/security-backup-validation6 argument-hint: "[project] [--skip-checks]"7 workflow: security8 phase: 59 artifact: 05-recover.md10---1112# Backup Validation1314Plan backup strategy, testing, and restoration verification for "$ARGUMENTS" covering backup inventory, frequency, storage locations, test restoration schedule, and monitoring.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"skipped","artifact":"05-recover.md","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 5 (Recover) of the NIST CSF workflow (`security`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `security` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"refused","artifact":"05-recover.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"started","artifact":"05-recover.md","note":""}`.2324Read `.singularskills/security/<project>/00-govern.md`. If this file does not exist, tell the user:2526> Phase 0 (Govern) has not been completed for "<project>". Run a Govern skill first (e.g., `/security-security-policy <project>`), or use `--skip-checks` to bypass.2728## Process29301. **Read context files:**31 - Read `references/incident-response-template.md` for recovery reference32 - Read `.singularskills/security/<project>/00-govern.md` for organizational context and data classification33342. **Inventory what is backed up:**35 - **Databases** — production databases, read replicas, configuration databases36 - **File systems** — application data, user uploads, shared storage37 - **Configurations** — infrastructure-as-code, application config, environment variables38 - **Secrets** — encryption keys, certificates, API keys (backed up to separate secure vault)39 - **Code and artifacts** — source code repositories, build artifacts, container images40 - Identify what is NOT currently backed up and assess whether it should be41423. **Define backup frequency per data type:**43 - **Real-time replication** — production databases, critical state stores (synchronous or asynchronous replication)44 - **Hourly** — transaction logs, high-change-rate data stores45 - **Daily** — application data, file systems, configuration snapshots46 - **Weekly** — full database backups, complete system images47 - **On change** — infrastructure-as-code, secrets, certificates (version-controlled)48 - Align frequency with RPO targets from recovery plan49504. **Define backup types:**51 - **Full backups** — complete copy of all data (weekly or as baseline)52 - **Incremental backups** — only changes since last backup (daily, reduces storage and time)53 - **Differential backups** — changes since last full backup (mid-week, balances recovery speed and storage)54 - **Snapshots** — point-in-time snapshots for cloud resources (EBS, RDS, managed disks)55 - Define retention periods per backup type (daily: 30 days, weekly: 90 days, monthly: 1 year)56575. **Define storage locations:**58 - **On-site** — local storage for fastest recovery (hot standby)59 - **Off-site** — geographically separate facility for disaster protection60 - **Cloud** — cloud object storage (S3, Azure Blob, GCS) with cross-region replication61 - **Air-gapped** — offline storage disconnected from network for ransomware protection62 - Apply 3-2-1 rule: 3 copies, 2 different media types, 1 offsite63 - Encrypt all backups at rest with keys stored separately from backup data64656. **Define test restoration schedule:**66 - **Critical systems (Tier 1)** — monthly restoration test to isolated environment67 - **Important systems (Tier 2)** — quarterly restoration test68 - **Supporting systems (Tier 3)** — semi-annual restoration test69 - Test procedure: restore to isolated environment, verify data integrity, verify application functionality, measure restoration time70 - Document test results: success/failure, restoration time, issues encountered, corrective actions71 - Annual full disaster recovery exercise simulating complete environment restoration72737. **Define backup monitoring and alerting:**74 - Monitor backup job completion (success/failure/partial)75 - Alert on backup failures immediately (P2 for Tier 1, P3 for Tier 2–3)76 - Monitor backup size trends (detect anomalies — sudden growth or shrinkage)77 - Monitor storage capacity and forecast depletion78 - Track backup and restoration SLA compliance (backup window, retention compliance)79808. **Document restoration procedures step-by-step:**81 - Per system type: prerequisites, access requirements, step-by-step commands or console actions82 - Include rollback plan if restoration fails83 - Document known issues and workarounds from past restoration tests84 - Maintain runbook in accessible location (not only on systems that might be unavailable)85869. **Write the artifact** — append to `.singularskills/security/<project>/05-recover.md` under a `## Backup Validation` section. Create the file with a `# Recover — <project>` heading if it does not exist; if a `## Backup Validation` section already exists, replace only that section. The section contains:8788 - **Backup Inventory** — what is backed up and what is not89 - **Backup Frequency** — per data type aligned with RPO targets90 - **Backup Types** — full, incremental, differential, snapshots with retention periods91 - **Storage Locations** — on-site, off-site, cloud, air-gapped with 3-2-1 compliance92 - **Test Restoration Schedule** — testing cadence and procedures per tier93 - **Monitoring and Alerting** — backup job monitoring and anomaly detection94 - **Restoration Procedures** — step-by-step per system type9596## Output9798The backup validation plan appended to `.singularskills/security/<project>/05-recover.md`. Present a summary to the user highlighting:99- Backup inventory coverage and identified gaps100- Backup frequency aligned with RPO targets101- Storage strategy following 3-2-1 rule102- Test restoration schedule and monitoring approach103104**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"security-backup-validation","workflow":"security","phase":5,"project":"<project>","event":"finished","artifact":"05-recover.md","note":""}`.105106This artifact is shared by every skill of phase 5 (Recover). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).107108```yaml109---110skill: Recover111workflow: security112phase: 5113project: <project>114started: <ISO timestamp>115finished: <ISO timestamp>116agent: <the agent you run in, or "unknown">117gate: <passed|skipped>118---119```120121Open your `## Backup Validation` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `security-backup-validation`).122123End your section with `### Decisions` and `### Open questions` (one level under your `## Backup Validation` heading, so the section stays one block), in this shape:124125```markdown126### Decisions127- <what was chosen> — <why> — <what was rejected>128129### Open questions130- <what the next phase or a reviewer must settle>131```132133End the artifact with this paragraph, verbatim:134135> **Not a penetration test or audit.** This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.