Free High Availability Assessment

Core switches are the high availability assessment control area that defines expected configuration, ownership, supporting evidence, and review cadence. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For core switches, the relevant evidence usually includes review running configuration, rule hit counts, stale objects, topology diagrams, firmware levels, remote-access groups, and change tickets. Review the related ACLs, NAT, zone policy, VLAN tagging, trunk ports, route tables, VPN profiles, split tunneling, 802.1X, WPA3, guest isolation, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include firewall manager, switch/router CLI exports, wireless controller, NetFlow/syslog, VPN gateway logs, network monitoring platform.

Firewalls are the operating area where policy, configuration, monitoring, and support records need to agree with the actual environment. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For firewalls, the relevant evidence usually includes review running configuration, rule hit counts, stale objects, topology diagrams, firmware levels, remote-access groups, and change tickets. Review the related ACLs, NAT, zone policy, VLAN tagging, trunk ports, route tables, VPN profiles, split tunneling, 802.1X, WPA3, guest isolation, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include firewall manager, switch/router CLI exports, wireless controller, NetFlow/syslog, VPN gateway logs, network monitoring platform.

Power is the technical and administrative control set used to prove this part of the environment is configured, maintained, and reviewed. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For power, the relevant evidence usually includes collect current-state screenshots or exports for power, plus ownership, exception, and change records. Review the related control objective, evidence trail, exception handling, review cadence, owner accountability, validation record, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include admin console, ticketing system, monitoring platform, configuration export, documentation repository.

Applications are the high availability assessment control area that defines expected configuration, ownership, supporting evidence, and review cadence. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For applications, the relevant evidence usually includes collect current-state screenshots or exports for applications, plus ownership, exception, and change records. Review the related control objective, evidence trail, exception handling, review cadence, owner accountability, validation record, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include admin console, ticketing system, monitoring platform, configuration export, documentation repository.

Documentation is the operating area where policy, configuration, monitoring, and support records need to agree with the actual environment. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For documentation, the relevant evidence usually includes sample recent tickets and changes, verify approval and rollback records, compare documentation against production, and confirm named owners. Review the related SLA, RACI, change advisory review, rollback plan, runbook accuracy, configuration management, evidence repository, operational KPIs, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include ticketing system, documentation portal, change calendar, asset inventory, monitoring alerts, configuration exports.

Monitoring is the technical and administrative control set used to prove this part of the environment is configured, maintained, and reviewed. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For monitoring, the relevant evidence usually includes inspect zone changes, resolver paths, DHCP scope utilization, alert thresholds, log retention, NTP synchronization, and monitoring coverage gaps. Review the related forwarders, secure dynamic updates, DHCP failover, reservations, lease scope utilization, syslog, SNMP, NetFlow, SIEM correlation, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include DNS/DHCP consoles, SIEM, syslog server, network monitoring dashboards, packet captures, availability reports.

Ownership is the high availability assessment control area that defines expected configuration, ownership, supporting evidence, and review cadence. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For ownership, the relevant evidence usually includes sample recent tickets and changes, verify approval and rollback records, compare documentation against production, and confirm named owners. Review the related SLA, RACI, change advisory review, rollback plan, runbook accuracy, configuration management, evidence repository, operational KPIs, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include ticketing system, documentation portal, change calendar, asset inventory, monitoring alerts, configuration exports.

Testing is the operating area where policy, configuration, monitoring, and support records need to agree with the actual environment. A reviewer should be able to confirm the current state from system exports, admin-console settings, monitoring records, tickets, and maintained documentation. For testing, the relevant evidence usually includes sample recent tickets and changes, verify approval and rollback records, compare documentation against production, and confirm named owners. Review the related SLA, RACI, change advisory review, rollback plan, runbook accuracy, configuration management, evidence repository, operational KPIs, then confirm which systems or users are affected, which logs prove the control is operating, and how exceptions are approved, tracked, and revisited. Common review sources include ticketing system, documentation portal, change calendar, asset inventory, monitoring alerts, configuration exports.