Skip to content
Networking
ASD ISMISM-1334

ASD ISM 1334 Ensure frequency separation in wireless networks

What it says

Wireless networks implement sufficient frequency separation from other wireless networks.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Wireless networks should use different frequencies to avoid interference with each other.

Wireless networks need to operate on different frequencies to prevent them from interfering with each other. If they don't, it's like trying to have multiple conversations in a room where everyone is talking over one another-nothing gets through clearly. Without this separation, your internet could slow down, drop out, or even leave your business vulnerable to data loss.

Why it matters

Insufficient frequency separation can cause RF interference, reducing throughput and availability and causing unstable or dropped wireless connections.

How to implement

  1. IT team should map out all wireless networks: Create a diagram that shows where each wireless access point is located and which frequencies they use.

    This helps to identify any overlaps or potential interference areas.

  2. Office manager should consult with IT experts: Hire a consultant or reach out to your internet service provider to examine your current wireless setup.

    They can provide advice on adjusting frequencies to ensure optimal performance.

  3. System owner should schedule regular checks: At least twice a year, review the frequency allocations for each wireless network to ensure they remain separate and effective.

    This can prevent new devices or networks from crossing frequencies.

  4. Procurement team should require frequency separation in new equipment: Ensure that any new wireless equipment you purchase has the capability to operate on various frequencies and that you have the flexibility to adjust these as needed.

  5. IT team should use network analyser tools: Employ tools that can scan for frequency usage in your area.

    This helps understand what frequencies are crowded or less used, enabling you to configure your network accordingly.

Keep it running

Perform RF site surveys and tune channel plans, widths and transmit power to maintain adequate separation from nearby wireless networks.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    A map of wireless access points: Request a diagram showing the location and frequency each access point uses.

    Look at

    Clear indications that different networks use different frequencies.

    Good evidence

    Will show no overlaps in frequency channels.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see documentation from IT consultations: Request any reports or notes from IT experts or consultants. Check if they include advice on managing and adjusting frequencies. Good documentation will show action points that have been followed.

  3. Check 3 of 5What an auditor asks for

    Ask for

    To review the schedule for frequency checks: Request records of past reviews and the schedule for upcoming checks.

    Look at

    Regular entries and notes on any frequency adjustments that have been made.

    Good evidence

    Will show bi-annual reviews with documented outcomes.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Procurement specifications: Request specifications or criteria used when purchasing new wireless equipment. Ensure they include requirements for frequency flexibility.

    Good evidence

    Will have checklists or criteria that specify frequency capabilities.

  5. Check 5 of 5What an auditor asks for

    Ask for

    To see results from network analyser tools: Request printouts or screenshots of recent scans.

    Look at

    The frequency scan results for evidence of analysis and action taken.

    Good evidence

    Includes reports showing proactive management of frequencies.

Mappings

Closest match in ISO/IEC 27001: A.8.20, Network and network devices security, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.