> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/discovery/discovered-assets.md). # Discovered Assets Managing assets that have been discovered. As assets are discovered across your attack surface, they'll appear in your account in many places, and there are several actions you can take. The primary goal is to help you add previously unknown or unmonitored assets as targets within your account so you can have a complete picture of external risks. ## View discovered assets You can view assets that have been discovered by visiting the [Assets Overview](https://app.halosecurity.com/user/security/discovery/). Here you will find a breakdown of how many domains and networks have been discovered and either added as targets or acknowledged, as well as a list of all discovered assets. ### Colors Different colors represent the status of the assets that have been discovered. We use the following colors: * **Green**: Scanned * **Light grey**: Acknowledged * **Dark grey**: Shadow assets ## Shadow assets Shadow assets are those that have been identified during the Discovery process, but not yet acknowledged or added as targets. We strongly recommend taking a look at any shadow assets that are discovered and determining whether these are a part of your organization. Shadow assets will appear dark grey with a "+" symbol in the Risk Score column. Clicking them will ask you to either add the asset as a target or acknowledge it. ## Add discovered assets as targets for security monitoring When you've identified a shadow asset that belongs to your organization, you will want to add it as a target. Adding an asset as a target enables all of our scanning services for the target and immediately launches a scan. ## Acknowledged assets Some things we find may not belong to your organization. They could belong to third parties you work with or be unconnected to your organization (false positives). While other systems may automatically add all suspected assets to your inventory, we believe that it's important to have no false positive targets within your account, so we provide simple and quick methods to weed out discovered assets that don't belong within your account. By acknowledging an asset, the system removes it from your Discovery list and does not identify it in the future. To view assets that have been acknowledged, visit *Settings →* [Acknowledged](https://app.halosecurity.com/user/settings/ack/hosts). --- # 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.halosecurity.com/docs/platform/discovery/discovered-assets.md?ask=&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.