Cadres IT Operations & Infrastructure
Products Architecture Docs Blog
Sheet SYN-07 Rev 2026.08
Start Trial

Sheet SYN-07 — Network Operations Manual

Wi-Fi Standardization Policies

Tenant-defined required SSID sets, legacy detection, label-based exemptions, and per-site pass, fail, or not-applicable results.

Audience: Network operators and compliance owners Focus: The tenant's standard, enforced deterministically

Scope

The Wi-Fi compliance domain answers one question per site: is this site’s Wi-Fi configured the way we decided it should be? This guide covers the rules, the evaluation logic, and the results operators review.

The standard is yours

The required SSID set lives entirely in the policy the tenant writes. There is no built-in SSID list, no assumed naming convention, and nothing customer-specific baked into the engine. A Wi-Fi policy’s rules are:

Rule Meaning
Required SSIDs Names that must be present and enabled at every in-scope site. Names are case-sensitive because broadcast names are literal.
Allow legacy When off, any enabled SSID outside the required set fails the site as legacy
Exemptions Sites whose labels match an exemption are excluded entirely; their result is not-applicable

How a site is evaluated

  1. Exemptions are checked first. An exempt site records the matching exemption as evidence and no SSID logic runs.
  2. The site’s currently enabled SSIDs are collected.
  3. Any required SSID that is not enabled is recorded as missing.
  4. If legacy is not allowed, any enabled SSID outside the required set is recorded as legacy. An empty required set never flags anything as legacy: legacy only means something relative to a defined standard.
  5. The site passes only if nothing is missing and nothing is legacy.

Every site in scope gets one result with structured evidence: what was present, what was missing, and what was legacy. A failure tells you exactly what to fix.

Scoping and running the policy

Wi-Fi policies use the standard policy scopes: one organization, one site, or every site in the account carrying a label. Results refresh after syncs and on the scheduled maintenance pass, and an operator can evaluate on demand for an immediate answer. Disabling a policy stops future evaluation but keeps its historical results.