Servers
The district's physical compute fleet — what hardware is running, how it is patched and lifecycle-tracked, and how privileged access and change are controlled. The rack-mount surveillance (NVR) server is captured here as compute hardware; the cameras themselves live in Physical Facility.
Capture progress
7 of 7 fields captured
Maturity preview · Developing

Inventory

Every physical server in production — one row each. supportStatus is captured, not derived from age: vendor support windows differ, so the district owns the determination. The rack-mount surveillance (NVR) server belongs here; cameras live in Physical Facility.

Server 1
Server 2
Server 3
Server 4
Server 5
1 server past EOL · 1 EOL this FY · operational risk surface

Practice

How often server operating systems receive security updates. Anchor: NIST CSF PR.PS-1 (configuration management).

How the district tracks server age and end-of-support dates. Drives refresh planning. Anchor: NIST CSF ID.AM-2.

Controls applied to privileged access on server operating systems. Check all that apply. Anchor: NIST CSF PR.AA-3, CIS Control 5.

Process for approving and documenting server changes. Anchor: NIST CSF PR.PS-1, ITIL change management.

Categories of workloads the district runs on its physical compute. Check all that apply.

Notes

Free text — context, refresh planning, vendor relationships, anything the rubric doesn't otherwise capture.