Scanner IP Allow List Best Practices

Adding NetSPI's scanner IP addresses to the allow list in your perimeter security devices helps make sure your External Attack Surface Management (EASM) results are accurate. The guidance below covers where to add our ranges, where not to, and how to confirm that scanning is no longer being blocked. It applies to asset discovery, port scanning, vulnerability scanning, and exploit validation testing, and is intended for network, security operations, and firewall administration teams.

Summary

Our EASM service continuously finds and tests everything your organization exposes to the internet, including domains, IP addresses, open ports, services, web applications, and their vulnerabilities. To do this accurately, our scanners need to see your environment the way a determined attacker would.

Many perimeter devices use active, behavior-based defenses such as intrusion prevention, automatic IP blocking, rate limiting, and WAF blocking. These controls are valuable, but they quickly recognize our scanners and block or slow them down. The result is a report that looks better than reality: services look closed, vulnerabilities go undetected, and your real exposure stays hidden. Attackers are not affected, because they rotate through thousands of source addresses.

We recommend adding our scanner IP ranges to the allow list in active, behavior-based security controls only. Do not add them to the access rules (firewall policies, ACLs, and cloud security groups) that decide what is reachable from the internet.

What Our Scanners Do

Our service performs four types of activity. Each one interacts with your perimeter devices in a different way.

Activity What it does How your devices usually react
Asset Discovery Finds internet-facing assets linked to your organization using DNS, certificate transparency, WHOIS data, cloud provider information, and light host probing. Usually low impact. DNS rate limiting, bot management, or CDN protections may slow or challenge requests.
Port Scanning Checks TCP and UDP ports on discovered IP addresses to see which services can be reached from the internet. Often triggers port-scan detection, IPS signatures, flood protection, and automatic IP blocking within seconds.
Vulnerability Scanning Identifies services, software versions, misconfigurations, weak encryption, exposed admin interfaces, and known vulnerabilities (CVEs). Triggers IPS and WAF signatures, rate limiting, bot detection, and brute-force protections.
Exploit Validation Safely confirms whether a vulnerability can really be exploited, using controlled, non-destructive methods. Very likely to trigger IPS, WAF, and automated response playbooks, which can result in blocks and incident tickets.

All exploit validation is performed only with your authorization and within the scope, timing, and safety limits we agree on with you. Adding our ranges to the allow list does not change what we are authorized to test. It only makes sure authorized testing gives accurate results.

Why Use an Allow List

Attackers do not look like a single scanner

When a defense blocks our scanner, it is reacting to one predictable source running a structured assessment. Real attackers spread their reconnaissance across botnets, residential proxies, cloud instances, and anonymization services, using thousands of IP addresses over long periods so that no single source crosses a blocking threshold. They also use search services that continuously index exposed systems.

So if a control blocks our scanner, that does not prove it will block a real attacker. When we are blocked, we end up measuring your blocking threshold instead of the exposure behind it, and the exposure is what you asked us to find.

Blocking leads to missed findings and a false sense of security

When our scanners are blocked or slowed during an assessment, you may see:

  • Missing services. Open ports look "filtered" or "closed" once our IP is blocked, so exposed services such as remote desktop, databases, or admin panels never show up in your inventory.

  • Missed vulnerabilities. If a WAF or IPS drops the request that would reveal a vulnerability, it is not reported, even though the application is still vulnerable and may be reachable another way.

  • An incomplete asset inventory. Hosts that drop all traffic from a blocked source look like they do not exist, which creates blind spots.

  • Inaccurate risk scores. Scores, trends, and dashboards are based on what we can observe, so interference makes your posture look stronger than it is.

  • Unconfirmed exploitability. Without exploit validation, your team has to prioritize fixes without the evidence the service is meant to provide.

Interference makes results inconsistent

Many defenses use temporary blocklists. A scanner may be blocked for an hour, released, and blocked again. Assets and findings then appear, disappear, and reappear between scans, creating false "remediated" and "new" findings that waste analyst time.

Some devices cause the opposite problem. Tarpits, deception tools, and certain SYN-proxy protections answer every probe as if the port were open, which creates many false positives that bury real exposures.

Perimeter controls are one layer, not a guarantee

Any single control can fail through misconfiguration, rule changes, signature gaps, licensing lapses, failover to an unprotected path, evasion techniques, or zero-day vulnerabilities. Cloud and CDN-fronted applications can also often be reached directly at their origin IP address, bypassing the WAF.

By testing the assets behind your active defenses, we show you the exposure that remains when one of those layers fails. Each layer should be sound on its own.

Measuring exposure is different from measuring detection

  What is exposed? Would my defenses detect or block an attack?
Purpose Find every internet-reachable asset, service, and vulnerability so it can be fixed or removed. Assess how well your detection and prevention controls work.
Best method EASM scanning with active defenses on the allow list (this service). Red team exercises, breach and attack simulation, or a separate "defenses-on" test.
If our scanners are blocked The result is corrupted because real exposure is hidden. That is the result being measured.

Our service answers the first question. Testing how your defenses respond to attacks is a separate exercise and should not be mixed with your EASM baseline.

Less work for your security team

Without an allow list, recurring scans repeatedly trigger IPS alerts, SIEM rules, and SOAR playbooks. Your Security Operations Center (SOC) then spends time on known, authorized activity, and automated responses may open tickets or page on-call staff. A properly scoped allow list, with logging kept on and traffic tagged, reduces alert fatigue while keeping full visibility.

Consistent with industry practice

Allowing authorized scanners through active protection systems is a widely recognized practice. For example, the PCI Security Standards Council's Approved Scanning Vendor (ASV) Program Guide expects that active protection systems such as IPS do not interfere with external vulnerability scans. NIST SP 800-115 also recommends coordinating authorized testing with security operations so results are accurate and testing is not mistaken for a real attack.

Where to Add Our Ranges to the Allow List

The tables below show where we recommend adding our scanner ranges to the allow list and where we do not. The rule of thumb: exempt us from controls that react to behavior, and do not change controls that define access.

Add our ranges in these devices and features

Device or feature What to do and why
Intrusion Prevention Systems (IPS), inline IPS signatures fire on scanning and exploit checks, then drop traffic or block the source. Exempt our ranges from IPS blocking actions. Keep logging on and tag the traffic (see Best Practices for Setup).
Intrusion Detection Systems (IDS), passive IDS does not block, but it creates many alerts and may feed automated blocking elsewhere. Tag or suppress alerts from our ranges, or send them to a low-priority queue. Make sure these alerts do not trigger automated blocking.
Next-Generation Firewall (NGFW) threat prevention Built-in IPS, anti-scan protection, and threat profiles can block us even when the access rule permits the traffic. Exempt our ranges from threat inspection and reconnaissance protection only. Do not broaden access rules (see NGFWs and Cloud Firewalls That Do Both).
Port-scan, reconnaissance, and flood protection These features are built to detect and block port scanning, often within seconds. Exempt our ranges from scan detection, SYN-flood thresholds, and connection-rate limits.
Automatic IP blocking and dynamic blocklists Tools that automatically block offending IPs cause inconsistent results between scans. Add our ranges to the exception list so they are never blocked automatically.
Web Application Firewalls (WAF) WAFs block the requests used to find web vulnerabilities, which hides flaws in the application. Exempt our ranges from WAF blocking rules and bot challenges. See the WAF note below.
DDoS protection and rate limiting (on-premises, ISP, or cloud) Rate limits and challenge pages slow or block scanning. Exempt our ranges from rate limits and challenges. Check with your ISP or DDoS provider if they manage this for you.
CDN and edge security services CDN edges often include bot management, WAF, and reputation-based blocking. Add our ranges to the CDN security allow list or bypass rules for bot and WAF features.
Bot management and CAPTCHA or JavaScript challenges Automated scanners cannot complete challenges, so content behind them goes untested. Exempt our ranges from bot scoring and challenges.
Geo-IP blocking Our scanners may operate from regions you block. Attackers routinely use infrastructure inside the regions you allow, so blocking us by location does not reflect real risk. Exempt our specific ranges from geo-blocking.
IP reputation and threat intelligence feeds Scanning infrastructure can appear in reputation feeds and be blocked automatically. Add our ranges as an override to reputation-based block lists.
SIEM and SOAR automated response playbooks Playbooks may push blocks to firewalls, open incidents, or page staff when they see our activity. Exclude our ranges from automated blocking actions and tag alerts as authorized scanning.
Tarpits, honeypots, and deception technologies These return false "open" responses or slow scans to a crawl. Exclude our ranges so we see only your real production services.
Brute-force and account lockout protections (for example, fail2ban or VPN and portal lockout thresholds) Credential checks may trigger lockouts that block our source IP. Exempt our ranges from source-IP blocking. Keep account lockout policies for real user accounts in place.

Do not add our ranges in these devices and controls

Device or control What to do and why
Perimeter firewall access rules (permit and deny rules) These rules define your real internet exposure. A "permit" rule for our ranges would let us reach services that are hidden from everyone else, so we would report exposures that do not exist for real attackers. Leave access rules unchanged. Our scanners should follow the same rules as any internet user.
Router and edge ACLs ACLs decide what is reachable from the internet, just like firewall rules. Do not add permit entries for our ranges.
Cloud security groups, network ACLs, and cloud firewall rules (for example, AWS, Azure, and GCP) These define exposure for cloud workloads. Allowing our ranges would reveal workloads that are not publicly reachable. Do not add our ranges to inbound security group or network ACL rules. Only exempt us from cloud-native WAF, DDoS, or threat-detection blocking.
NAT and port-forwarding rules Changing these changes what is exposed. Make no NAT or port-forwarding changes for our scanning.
VPN, remote access, and Zero Trust (ZTNA) gateways: authentication and access policies Giving our ranges trusted status, skipping authentication, or exempting us from MFA would test a setup attackers cannot reach. Do not grant trust, bypass authentication, or issue credentials. Exempting us from source-IP lockout or IPS on the gateway is fine.
Internal segmentation firewalls and internal network controls We assess only your external attack surface. No changes needed.
Email security gateways (content filtering, anti-malware, anti-phishing) Our service does not need mail delivery or content inspection bypass. No changes needed, unless we ask for connection-throttling exemptions for SMTP service checks.
Endpoint protection (EDR/AV) and host-based security These are not involved in external scanning. No changes needed.
Broad "trusted source" rules (any-to-any) A rule like "permit any from scanner ranges to any destination on any port" bypasses inspection and grants access beyond your public exposure. Never create blanket trust rules for our ranges.

NGFWs and cloud firewalls that do both

Many modern firewalls combine access control and threat prevention in one policy. On these devices, the goal is to remove inspection-based blocking without expanding what is reachable.

Do this Not this
Create an exception for our source ranges that applies only to the destinations, ports, and services already open to the internet, with threat prevention, IPS, anti-scan, and DoS profiles removed or set to alert-only. Create a rule that permits our source ranges to any destination, any port, or any internal or non-public service, even temporarily.
Use the device's built-in exception mechanism for IPS signatures, reconnaissance protection, and DoS or zone protection, limited to our source ranges. Place our ranges in a "trusted" zone or address group that permissive internal access rules refer to.
Keep logging on for all traffic from our ranges. Turn off logging for our ranges to reduce noise.

For help applying this guidance on your specific platform, contact NetSPI Customer Support at help@netspi.com.

Best Practices for Setup

Follow these steps to add our scanners to your allow list safely and effectively:

  1. Use exact ranges only. Add only the specific IP addresses and CIDR ranges published at https://www.netspi.com/allowlist/. Do not add broader provider blocks, ASNs, or entire cloud regions.

  2. Exempt actions, not access. Limit exceptions to blocking and throttling actions. Leave access rules, authentication requirements, and other controls that define exposure unchanged.

  3. Keep logging on. Continue logging all traffic from our ranges so you keep your audit trail and can verify our activity at any time.

  4. Tag the traffic. Create a named address object (for example, "EASM-Authorized-Scanners") and tag related SIEM alerts as authorized scanning so analysts can recognize them right away.

  5. Cover every internet path. Apply exceptions to all internet-facing entry points: each ISP circuit, data center, branch office, cloud account and region, CDN, DDoS provider, and third-party hosted service. One missed path will cause inconsistent results.

  6. Include your providers. If a managed security service provider (MSSP), ISP, hosting provider, or SaaS platform runs any of the controls listed above for you, share this information and our ranges with them.

  7. Use change management. Make the change through your normal change control process and record the business reason (authorized EASM assessment).

  8. Check for range updates. Our scanning ranges can change, and https://www.netspi.com/allowlist/ always shows the current list. Check it regularly and before changing any allow list entries.

  9. Review regularly. Review your allow list entries at least once a year, and remove them promptly if you stop using service.

  10. Verify your changes. Check the results of your next cheduled scan for the signs of interference listed below.

Verifying Your Configuration

Signs that scanning is still being blocked

After your allow list is in place, look for these signs in your scan results that a device may still be interfering:

  • A sudden drop in open ports or services partway through a scan, or after the first few hosts.
  • Hosts that respond at the start of a scan and then stop responding.
  • Assets or findings that appear and disappear between scans with no matching change on your side.
  • Connection resets, block pages, CAPTCHA challenges, or HTTP 403, 406, or 429 responses on web applications.
  • Hosts that report all or nearly all ports as open, which often points to a tarpit or SYN proxy.
  • Exploit validation results marked "inconclusive" because connections were blocked or reset.

Frequently Asked Questions

Does using an allow list weaken my security?

When set up as described here, the risk is minimal and limited. The allow list does not open any port or service that is not already reachable from the internet. It only stops your active defenses from singling out our dedicated scanning addresses. All traffic still follows your access rules and stays fully logged.

Are your scanner IP ranges shared with anyone else?

No. The ranges published at https://www.netspi.com/allowlist/ are dedicated to NetSPI's scanning service and are not shared with other organizations. Traffic from these ranges comes only from NetSPI's scanning platform, so the allow list is limited to authorized assessment activity.

Could an attacker spoof your IP addresses to get past my defenses?

Spoofing a source IP is only practical for one-way, connectionless traffic. Meaningful attacks on TCP services need a completed handshake, which means the attacker must receive replies at the spoofed address, and they cannot do that for addresses they do not control. Keeping logging and access rules in place, as recommended, limits any remaining risk. If you want to narrow it further, ask NetSPI to set up scan windows and limit your exceptions to those times.

Can I limit the allow list to scan windows only?

Yes. NetSPI can configure scan windows so scanning happens only on the days and times we agree on with you. If your devices support scheduled policies, you can match your exceptions to the same windows. Keep in mind that frequent or continuous scanning gives the most accurate picture of a changing attack surface, and exceptions that do not exactly match the scan windows are a common cause of inconsistent results. To set up or change scan windows, contact help@netspi.com.

Will exploit validation harm my systems?

No. Exploit validation uses safe, non-destructive techniques that confirm exploitability without disrupting services, changing data, or removing data. Tests run only within your authorized scope and rules of engagement. For questions about scope, contact help@netspi.com.

Our IPS is managed by a third party. What should we do?

Share this information and our published ranges with your provider and ask them to apply the exceptions described in "Add our ranges in these devices and features."

What if we cannot add our ranges to the allow list in some devices?

Apply exceptions wherever you can, starting with the controls in "Add our ranges in these devices and features." Findings for assets protected by defenses that are not exempted may be incomplete, and your view of their true exposure will be limited.

Should our SOC still monitor your traffic?

Yes. We encourage your SOC to keep visibility of our traffic. Tagging our activity instead of suppressing it lets analysts confirm that what they see matches our published ranges and schedule, and quickly spot anything that does not.

Scanner IP Ranges

Our scanner IP ranges are published and kept current in one place:

Why we do not list the ranges here. Scanning infrastructure is added, retired, and rebalanced over time. Static copies in PDFs, emails, tickets, or firewall change records quickly go out of date. That can cause new scanner addresses to be blocked, which gives incomplete results, or retired addresses to stay trusted when they should not be. Using the live page avoids both problems.

We recommend that you bookmark the page, refer to it in your firewall change records, and check it before any change to your allow list entries and during your regular allow list reviews.

Implementation Checklist

  • Got the current list of scanner IP ranges from https://www.netspi.com/allowlist/.

  • Created a named address object or group for our ranges on each relevant device.

  • Exempted our ranges from IPS blocking, reconnaissance and anti-scan, and DoS and flood protections.

  • Exempted our ranges from WAF blocking, bot management, and CDN edge security challenges.

  • Exempted our ranges from automatic IP blocking, reputation feeds, geo-blocking, and SOAR blocking playbooks.

  • Excluded our ranges from tarpits, honeypots, and deception technologies.

  • Confirmed that no firewall access rules, router ACLs, cloud security groups, NAT rules, or VPN and ZTNA policies were changed to grant extra access.

  • Kept logging on for all traffic from our ranges and tagged related SIEM alerts as authorized scanning.

  • Applied changes to all internet entry points, cloud accounts, and third-party or MSSP-managed controls.

  • Recorded the change in change management with a review date.

  • Bookmarked the allow list page and scheduled a regular allow list review.

  • Reviewed the results of the next scheduled scan for signs of interference.

Contact and Support

For questions about these recommendations or to set up scan windows, contact NetSPI Customer Support at help@netspi.com.

This information is provided for guidance only. Customers remain responsible for configuring their own security devices and for evaluating changes against their internal policies and risk tolerance. Product and vendor names mentioned are the property of their respective owners.