KADERA
Dashboard Districts Assessments Reports Vendors Renewals E-rate
Break glass
JR
Storage
The district's storage estate — SAN, NAS, direct-attached, and hyperconverged arrays — and the practice around redundancy, replication, capacity planning, and refresh. Replication is captured here as a technical fact; backup strategy and recovery objectives live in Data Resiliency.
Capture progress
6 of 6 fields captured
Maturity preview · Defined

Inventory

Every storage array in production — one row each. Storage is heterogeneous: a primary SAN, a general NAS, a surveillance NAS, and a dedicated backup target are different operational realities. Tag each array's use cases; supportStatus is captured, not derived from age.

Storage array 1
Storage array 2
Storage array 3
Storage array 4
0 arrays past EOL · 1 EOL this FY · operational risk surface

Practice

Drive-level protection across the storage estate. RAID, mirror, or equivalent redundancy that survives a single-drive failure without data loss. Anchor: NIST CSF PR.DS-1, CIS Control 11.

Replication of storage to a separate location or array. Distinct from backups (captured in Data Resiliency) — replication keeps a live secondary copy; backups capture point-in-time recoverable copies. Anchor: NIST CSF PR.DS-1, PR.IR-3.

How the district forecasts storage capacity needs and avoids running out unexpectedly. Anchor: NIST CSF ID.AM, PR.IR-4.

How the district tracks storage array age, support windows, and plans refresh. Mirrors the lifecycle-tracking question in Servers — captured separately because storage refresh cycles differ from server cycles in most districts. Anchor: NIST CSF ID.AM-2.

Notes

Free text — refresh planning, vendor relationships, mixed-environment context, replication-target detail, anything the rubric doesn't otherwise capture.