> For the complete documentation index, see [llms.txt](https://shellzerox.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shellzerox.gitbook.io/docs/security-agents/sentinel-and-hunter.md).

# Sentinel & Hunter

Explore SHELLZERO X's running security agents for asset monitoring and exploited vulnerability intelligence.

***

### Overview

SHELLZERO X uses specialized security agents to expand its capabilities beyond individual website scans. Sentinel and Hunter are identified as running agents, with distinct roles in asset monitoring and vulnerability intelligence.

### Sentinel: Asset Monitoring

Sentinel focuses on monitoring verified assets and identifying changes that may require security review.

Its intended role is to help maintain visibility into monitored assets as their publicly observable security conditions change.

**Key focus areas**

* Monitoring verified assets.
* Rescanning assets to identify changes.
* Supporting visibility into changes that may affect security posture.

Monitoring frequency, notification behavior, and configuration options depend on the capabilities available in the platform.

### Hunter: Exploited Vulnerability Intelligence

Hunter focuses on identifying newly confirmed exploited vulnerabilities relevant to detected software.

Its purpose is to help users recognize when previously detected technologies may be affected by emerging vulnerability intelligence.

**Key focus areas**

* Rechecking detected software against exploited vulnerability information.
* Identifying potentially relevant security developments.
* Supporting investigation and prioritization of vulnerability findings.

A match does not automatically confirm that a particular system is exploitable. Users should verify the affected software, version, and environmental conditions.

### Sentinel vs. Hunter

| Area           | Sentinel                                       | Hunter                                                          |
| -------------- | ---------------------------------------------- | --------------------------------------------------------------- |
| Primary Focus  | Asset monitoring                               | Exploited vulnerability intelligence                            |
| Main Purpose   | Identify changes in monitored assets           | Identify relevant vulnerability intelligence updates            |
| Security Value | Helps maintain visibility into external assets | Helps prioritize investigation of potentially affected software |
| User Action    | Review detected changes                        | Verify vulnerability matches and assess risk                    |

### Using Agent Findings

When an agent identifies a change or potential concern:

1. Review the information provided.
2. Identify the affected asset or software component.
3. Verify the finding against the actual environment.
4. Determine whether corrective action is necessary.
5. Reassess the asset after making any changes.

Agent findings should support informed security decisions rather than replace technical validation.

### Availability and Limitations

Sentinel and Hunter are identified as running agents in the published SHELLZERO X platform information. Their precise operating schedules, notification mechanisms, and user-configurable options should be confirmed through the available platform interface.

The agents' findings depend on accessible asset information and available vulnerability intelligence. They cannot guarantee detection of every change, vulnerability, or security incident.


---

# 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://shellzerox.gitbook.io/docs/security-agents/sentinel-and-hunter.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.