Observability & monitoring
How the district watches its compute, storage, virtualization, cloud, and backup surfaces for operational health — what is covered, what tooling is in use, how alerts reach humans, and who responds. Network device monitoring is captured in Network Infrastructure; security event monitoring lives in the cybersecurity domain.
Capture progress
6 of 6 fields captured
Maturity preview · Defined

Coverage

Categories of infrastructure that are actively monitored for operational health. Check all that apply. Network device monitoring (switches, firewalls, WAPs) is captured separately in Network Infrastructure — not included here. Anchor: NIST CSF DE.CM-1, DE.CM-7.

Categories of monitoring tooling. Specific product names belong in notes. Districts commonly use multiple categories simultaneously. Anchor: NIST CSF DE.CM, ID.AM-3.

Response

How alerts get to humans. The gap between detection and response is where most operational incidents grow. Anchor: NIST CSF DE.AE-2, DE.DP-4.

Who responds to alerts and when. K-12 IT departments often have informal coverage — that's a captured fact, not a hidden one. Anchor: NIST CSF RS.CO-2, RS.AN-1.

Backup watch

How the district verifies that backups actually completed. Captured separately because backup-failure-undetected is the most common pre-cursor to data loss events. Distinct from backup strategy (captured in Data Resiliency) and from restoration testing (also DR). Anchor: NIST CSF PR.IP-4, DE.CM-1.

Notes

Free text — specific tools in use, MSP relationships, planned upgrades, after-hours arrangements, anything the rubric doesn't otherwise capture.