ASD ISM 1319 Avoid static IP addressing on wireless networks
What it says
Static addressing is not used for assigning IP addresses on wireless networks.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishDon't use fixed IP addresses for devices on wireless networks to enhance security.
This control means you shouldn't give wireless devices fixed IP addresses. If you do, it can make your network more vulnerable to hackers who might try to sneak in by guessing or intercepting these fixed spots. By using dynamic addresses instead, it's harder for anyone with bad intentions to predict how to access your network.
Free. Save your status, tasks and notes.
Why it matters
Static IPs on wireless networks can be predictably targeted by attackers, increasing the risk of unauthorised access and data breaches.
How to implement
IT team should configure the wireless network to use dynamic addressing, known as DHCP (Dynamic Host Configuration Protocol).
This means setting up the router to automatically give each connected device a temporary IP address, which can change each time the device reconnects.
System administrators should regularly check the router settings.
Ensure that DHCP is enabled and that there are no devices with static IP entries that could be exploited by intruders.
Network security managers should educate all staff on the importance of using dynamic IP addresses.
Hold a brief training session explaining how static IPs might make the network vulnerable and the benefits of dynamic addresses.
Technical support should monitor the network using available tools to ensure no devices are using static IP addresses without authorisation.
Implement network scanning tools that can alert you to any fixed IPs in use.
Facility managers should collaborate with IT to ensure any network-connected equipment is set up to receive dynamic IPs.
Review the setup instructions for connected devices like printers or smart TVs to confirm they support DHCP and are configured to use it.
Keep it running
Regularly confirm wireless uses DHCP and check for fixed IP entries (reservations/manual settings) to prevent unauthorised static addressing.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
DHCP configuration reports.
Look at
The settings on the network router or management console that confirm DHCP is turned on.
Good evidence
Includes screenshots or logs indicating that DHCP is enabled and functioning correctly.
- Check 2 of 5What an auditor asks for
Look at
Whether any device has a fixed IP address.
Good evidence
Shows no static IP addresses in the list or a clear and justified exception for each one.
- Check 3 of 5What an auditor asks for
Ask for
Records of security awareness training sessions.
Look at
Mention of dynamic versus static IP addressing in the session content.
Good evidence
Includes training slides or attendance records showing the topic was covered.
- Check 4 of 5What an auditor asks for
Look at
Whether they follow a standard procedure that involves setting devices to use DHCP.
Good evidence
Reflects a consistent process across team members.
- Check 5 of 5What an auditor asks for
Look at
Alerts or entries that indicate when a static IP is detected.
Good evidence
Includes logs demonstrating regular detection and correction of static IP issues.
Mappings
Closest match in ISO/IEC 27001: A.8.9, Configuration management for secure IT systems, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.9.
ISM-1319 requires organisations to avoid static IP addressing on wireless networks as a specific configuration choice to reduce risk. Annex A 8.9 requires configurations (including security configurations) of networks to be established, documented, implemented, monitored and reviewed, under which the organisation would define and enforce DHCP versus static addressing standards for wireless segments. ISM-1319 is a prescriptive configuration baseline item, while Annex A 8.9 is a broader configuration management control covering governance and lifecycle management.
This control partially meets A.8.20.
ISM-1319 requires organisations to avoid using static IP addressing for devices on wireless networks. Annex A 8.20 requires networks and network devices to be secured, managed and controlled to protect information in systems and applications, which encompasses secure wireless network configuration practices such as DHCP-based addressing. ISM-1319 is a specific hardening requirement within the broader network security management expectations of Annex A 8.20.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.