Skip to content
Networking
ASD ISMISM-1316

ASD ISM 1316 Ensure default wireless SSIDs are changed

What it says

Default SSIDs of wireless access points are changed.

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

What it means

In plain English

Change default wireless network names to enhance security.

Changing the default name of your wireless network (also called the SSID) is crucial for security. If you keep the default name, it can signal to potential attackers that you might not have changed other default settings, making your network an easier target to exploit.

Why it matters

Default SSIDs can reveal the access point vendor and suggest default configuration, aiding targeted attacks and unauthorised access attempts.

How to implement

  1. IT staff should identify all wireless access points: Use network scanning tools to find all devices broadcasting a wireless signal in your organisation.

    This ensures no access points are overlooked.

  2. The network manager should change the default SSID: Log into each wireless router using the admin interface and navigate to the wireless settings page to rename its SSID to something unique and non-identifiable.

  3. The IT team should establish a naming policy: Develop a consistent naming scheme for SSIDs that avoids using company names or addresses.

    This policy helps maintain an organised and secure network environment.

  4. Managers should inform staff about the SSID change: Communicate any new network names and related changes to employees so they can connect correctly.

    This could be done via email or during team meetings.

  5. The IT department should document all changes: Record each new SSID change along with the date and reason for changing in a secure and accessible document.

    This provides a historical record of network changes for future reference.

Keep it running

Change all wireless access point SSIDs from vendor defaults, and document approved naming conventions to avoid revealing organisation or location details.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The network inventory report: Request a document listing all active wireless access points and their corresponding SSIDs.

    Look at

    Any SSID that still matches common default names like 'Linksys' or 'Netgear'.

    Good evidence

    Shows a list with unique, non-default SSIDs.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see the SSID naming policy: Request the document outlining the organisation's naming conventions for wireless networks.

    Look at

    The guidelines to ensure they specify avoiding personal or company identifiers.

    Good evidence

    Is a clear, specific policy document with unique guidelines.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Meeting notes or emails regarding staff notifications: Check documents or emails showing that staff were informed about SSID changes.

    Look at

    Communication date and clarity in the message.

    Good evidence

    Is a record or message explaining the change.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Network change logs: Request logs or reports showing changes made to SSIDs.

    Look at

    Entries with dates, user who made the change, and the before-and-after SSID names.

    Good evidence

    Includes detailed records confirming actions.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Access to wireless access point settings: Request a demonstration of the current SSID settings via the access point's administration interface.

    Look at

    Evidence of customised, non-default SSIDs.

    Good evidence

    Is a live demonstration showing the configured settings.

Mappings

Closest match in ISO/IEC 27001: A.8.9, Configuration management for secure IT systems, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

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