Free Wireless Network Security Assessment Tool

Why it matters

Business SSID Security should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Business SSID Security is

Business SSID Security is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained business ssid security can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak business ssid security evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Monthly, and after major changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for business ssid security.

Why it matters

Guest Network Segmentation should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Guest Network Segmentation is

Guest Network Segmentation is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained guest network segmentation can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak guest network segmentation evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Monthly, and after major changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for guest network segmentation.

Why it matters

WPA Configuration should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What WPA Configuration is

WPA Configuration is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained wpa configuration can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak wpa configuration evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Monthly, and after major changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for wpa configuration.

Why it matters

Shared Password Rotation should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Shared Password Rotation is

Shared Password Rotation is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained shared password rotation can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak shared password rotation evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for shared password rotation.

Why it matters

Admin Console Security should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Admin Console Security is

Admin Console Security is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained admin console security can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak admin console security evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for admin console security.

Why it matters

Rogue Access Points should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Rogue Access Points is

Rogue Access Points is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained rogue access points can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak rogue access points evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for rogue access points.

Why it matters

Wireless Coverage should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Wireless Coverage is

Wireless Coverage is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained wireless coverage can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak wireless coverage evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for wireless coverage.

Why it matters

IoT Separation should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What IoT Separation is

IoT Separation is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained iot separation can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak iot separation evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for iot separation.

Why it matters

Logging should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Logging is

Logging is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained logging can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak logging evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for logging.

Why it matters

Firmware Updates should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Firmware Updates is

Firmware Updates is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained firmware updates can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak firmware updates evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for firmware updates.

Why it matters

Administrative Access should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Administrative Access is

Administrative Access is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained administrative access can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak administrative access evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for administrative access.

Why it matters

Logging and Monitoring should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Logging and Monitoring is

Logging and Monitoring is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained logging and monitoring can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak logging and monitoring evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for logging and monitoring.

Why it matters

Backup and Recovery should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Backup and Recovery is

Backup and Recovery is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained backup and recovery can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak backup and recovery evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for backup and recovery.

Why it matters

Documentation should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Documentation is

Documentation is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained documentation can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak documentation evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for documentation.

Why it matters

Change Control should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Change Control is

Change Control is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained change control can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak change control evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for change control.

Why it matters

Vendor Support should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Vendor Support is

Vendor Support is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained vendor support can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak vendor support evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for vendor support.

Why it matters

Policy Exceptions should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Policy Exceptions is

Policy Exceptions is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained policy exceptions can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak policy exceptions evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for policy exceptions.

Why it matters

User Awareness should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What User Awareness is

User Awareness is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained user awareness can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak user awareness evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for user awareness.

Why it matters

Incident Response should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Incident Response is

Incident Response is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained incident response can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak incident response evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for incident response.

Why it matters

Executive Reporting should map to an approved baseline, named owner, and recent validation evidence. Scheduled review confirms that access, policy, logging, backup, and exception records match production rather than stale documentation.

What Executive Reporting is

Executive Reporting is the wireless network security control area that should have an assigned owner, approved baseline, dated evidence, and a defined review cadence. Evidence should come from the relevant admin console, configuration baseline, access model, logs, exception register, and change history.

A reviewer should be able to identify affected systems or users, the records proving that the control is operating, and the approval path for exceptions. If this area is outdated or undocumented, the effect can reach security, availability, support response, audit readiness, and recovery during an incident.

Risk

Poorly maintained executive reporting can create outages, unauthorized access paths, audit findings, or delayed recovery during an incident.

Business impact

Weak executive reporting evidence can leave unsupported systems, excessive privilege, unmonitored changes, or untested recovery paths in place, increasing triage time and remediation cost.

Review frequency

Quarterly, and after material changes.

Technical notes and evidence context

Review approved configuration records, ownership records, administrative access, logs, exceptions, change history, and supporting documentation for executive reporting.