> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cloud-attack-surface-management/cloud-asm-concepts/scanning.md).

# Scanning

Attack Surface Management (ASM) in Cortex Cloud uses data collected from global internet scans as well open-source intelligence about the internet to maintain a complete inventory of all the internet-facing assets that belong to an organization. The following topics describe the scans that Cortex Cloud uses to map and monitor your attack surface.

## **Scanning cadences**

Cortex Cloud scans the internet to discover new services at varying cadences depending on several factors such as port, protocol, cloud provider ranges, and customer-attributed assets. All responsive services are monitored regularly.

Below is a list of our targeted scanning cadences:

* **Discovery Scans**
  * **Global Base**— twice per week discovery of approximately 250 of the most common ports on all IPv4 space.
  * **Global Extended**—low background rate discovery of the remaining 65k ports, excluding those covered in KAM base and KAM extended.
  * **KAM (Known Assets Monitoring) Base**—daily discovery of approximately 300 of the most common ports on customer-attributed assets.
  * **KAM Extended**—weekly discovery of approximately 2800 of the most common ports on customer-attributed assets. These do not overlap with KAM Base.
* **Monitoring Scans**
  * Daily on all responsive services.
* **Attack Surface Testing Scans**
  * Daily on configured services.

## **Scanning ports and protocols**

Cortex Cloud detects protocol-validated services on the IPv4 and IPv6 space of the internet through a series of specialized payloads that target specific port-protocol pairs. Following are examples of some of the protocols and ports on which Cortex Cloud checks for active services throughout a standard global scan.

{% hint style="info" %}

### Note

The following lists are not exhaustive. For current and complete lists, contact your customer success team.
{% endhint %}

* **Sample protocols**: SSL, FTS, SSH, Telnet, HTTP, POP3, RDP, FTP, XMPP, Postgres, VNC, UDP, etc
* **Sample Ports**: 0, 20, 21, 22, 23, 25, 53, 67, 68, 80, 81, 82, 83, 88, 110, 111, 118, 123, 135, 137, 138, 139, 143, 161, 179, 389, 401, 443, 444, 445, 465, 500, 502, 554, 587, 593, 808, 873, 888, 943, 987, 990, 993, 995, 1000, 1024, 1025, 1026, 1028, 1112, 1234, 1250, 1433, 1434, 1443, 1521, 1717, 1723, 1900, 1911, 2001, 2002, 2078, 2080, 2082, 2083, 2084, 2085, 2086, 2087, 2096, 2121, 2160, 2161, 2222, 2323, 2443, 2483, 2484, 2525, 3000, 3052, 3306, 3333, 3388, 3389, 3390, 3443, 3493, 3905, 3909, 3917, 3929, 3975, 3978, 4002, 4100, 4117, 4172, 4343, 4430, 4433, 4443, 4444, 4500, 4506, 4567, 4786, 4911, 5000, 5001, 5060, 5061, 5222, 5269, 5351, 5353, 5432, 5443, 5555, 5632, 5800, 5900, 5901, 5902, 5903, 5904, 5905, 5906, 5907, 5908, 5909, 5910, 5916, 5984, 5985, 5986, 6001, 6002, 6363, 6379, 6443, 7001, 7080, 7170, 7443, 7547, 7777, 8000, 8005, 8008, 8009, 8010, 8015, 8020, 8080, 8081, 8082, 8083, 8085, 8088, 8090, 8094, 8139, 8140, 8159, 8194, 8195, 8196, 8197, 8198, 8209, 8210, 8211, 8212, 8213, 8214, 8215, 8216, 8217, 8218, 8219, 8220, 8282, 8290, 8291, 8292, 8293, 8294, 8333, 8443, 8444, 8530, 8531, 8800, 8880, 8887, 8888, 8899, 8991, 8999, 9000, 9002, 9042, 9080, 9091, 9092, 9100, 9200, 9418, 9443, 9444, 9595, 9983, 9997, 10000, 10010, 10443, 11211, 11495, 11553, 12345, 16010, 17185, 17516, 17778, 18080, 18574, 20249, 21242, 22460, 25789, 25827, 27017, 28080, 30005, 30006, 30010, 30083, 30303, 32400, 37443, 37777, 38080, 38520, 40000, 40005, 42713, 44344, 44818, 47001, 47693, 47808, 49501, 49502, 50001, 50067, 50070, 50580, 50805, 50995, 50996, 50997, 51005, 51007, 51200, 51401, 52200, 52311, 52590, 52869, 53300, 53524, 53631, 54041, 54498, 54528, 55918, 56222, 58000, 58603, 60000, 60243, 60443, 61337, 62078

## **Scanning activity**

Cortex at Palo Alto Networks takes an outside-in approach to network security and asset management. We continuously scan the global internet to monitor our customers' internet-facing attack surface and discover emerging threats.

Our scanning activity on the ranges below is CFAA-compliant. You can mark our ranges as non-malicious in your system so that you stop getting alerts, or configure your firewall to drop traffic from our ranges.

```programlisting
35.203.210.0/23
144.86.173.0/24
147.185.132.0/23
162.216.149.0/24
162.216.150.0/24
172.105.147.0/24
198.235.24.0/24
205.210.31.0/24
216.25.88.0/21

2604:a940:300:5b6:0:0:0:0/64 
2604:a940:301:225:0:0:0:0/64 
2604:a940:302:118:0:0:0:0/64 
```

If you believe you have discovered abuse associated with Cortex attack surface management scans, please contact us at <scaninfo@paloaltonetworks.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cloud-attack-surface-management/cloud-asm-concepts/scanning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.