> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/reconnaissance/censys_scanning.md).

# censys\_scanning

Explanation The censys\_scanning NDM is designed to detect any activity on your network that is related to Censys scanning. What to Look For If the censys\_scanning NDM is triggered, you should examine

**Explanation**

The censys\_scanning NDM is designed to detect any activity on your network that is related to Censys scanning.

**What to Look For**

If the censys\_scanning NDM is triggered, you should examine network configurations of devices like the firewall to ensure that you want to allow Censys to scan your network. Additionally, examine endpoint logs to identify any anomalies or security events that may have been caused by the scanning activity. To remediate the issue, you may need to block traffic from the identified IP addresses or take additional security measures to protect your network from potential attacks.

**Related MITRE ATT\&CK Categories**

[Reconnaissance: Active Scanning, Technique T1595 - Enterprise](https://attack.mitre.org/techniques/T1595)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fusion.vectra.ai/detection-models/library/reconnaissance/censys_scanning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
