Skip to content
Gateways
ASD ISMISM-1427

ASD ISM 1427 Prevent IP source address spoofing in gateways

What it says

Gateways perform ingress traffic filtering to detect and prevent IP source address spoofing.

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

What it means

In plain English

Gateways block fake IP addresses to protect network entries.

Gateways, which are entry points to your network, need to block any fake addresses trying to come in. This is like having a bouncer at a club who checks IDs to make sure only real, authorised people get in. Without this check, malicious actors could pretend to be someone they're not and sneak into your network, potentially accessing sensitive data or causing harm.

Why it matters

If gateways don't filter spoofed source IPs, attackers can masquerade as trusted hosts, bypass ACLs and enable attacks.

How to implement

  1. IT team should configure the gateway: Ensure the gateway devices are set up to check all incoming traffic for fake addresses.

    This can be done by adjusting the settings on your firewall or router to verify that incoming requests are from legitimate and known sources.

  2. System administrator should update filtering rules: Regularly update the rules that the gateway uses to identify fake addresses.

    This includes staying informed about current threats by reviewing cyber security advisories from the Australian Cyber Security Centre (ACSC).

  3. Network engineer to monitor logs: Set up a system where network logs are reviewed daily to spot any anomalies.

    This involves checking for repeated access attempts from unusual locations which might indicate spoofing attempts.

  4. Business owner to establish a review schedule: Schedule quarterly reviews of gateway security with the IT team.

    Include a review of the logs, settings, and any incidents to ensure everything is functioning correctly.

  5. Manager to provide training: Ensure that staff responsible for network monitoring are trained in recognising signs of IP spoofing.

    This includes recognising unusual patterns in the logs and knowing the correct escalation procedures.

Keep it running

Implement ingress anti-spoofing (BCP38/uRPF) on gateways; maintain allowlists for expected source ranges and alert on drops.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    Gateway configuration documentation: Request the current configuration settings of the network gateway.

    Look at

    Settings related to IP filtering and spoof detection.

    Good evidence

    Result shows active filtering rules specifically designed to block spoofed IP addresses.

  2. Check 2 of 5What an auditor asks for

    Ask for

    A list of security advisories: Request the records of recent security advisories followed by the organisation.

    Look at

    How these advisories are reviewed and integrated into current practices.

    Good evidence

    Result shows a list of actions taken in response to advisories from credible sources like the ACSC.

  3. Check 3 of 5What an auditor asks for

    Ask for

    A report on log reviews: Obtain the logs and the last few reviews conducted on them.

    Look at

    Any identified suspicious activities and actions taken. A well-maintained log will have clear records of checks and flagged anomalies.

  4. Check 4 of 5What an auditor asks for

    Ask for

    The training records of IT staff: Request documentation of recent security training sessions for staff.

    Look at

    Details on the topics covered and attendee lists.

    Good evidence

    Record will show focused training sessions on identifying and managing spoofing attempts.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Minutes from review meetings: Request minutes from the last few security review meetings.

    Look at

    Discussions specifically addressing the gateway security and any follow-up actions. A comprehensive record will include identified issues and plans to address them.

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.