> 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-and-roadmap/development-roadmap.md).

# Development Roadmap

Explore the planned evolution of SHELLZERO X, from website security scanning to autonomous defense and Web3 monitoring.

***

### Overview

SHELLZERO X is progressing toward a broader cybersecurity platform that combines website security assessment, vulnerability intelligence, asset monitoring, and specialized security agents.

The roadmap outlines the platform's development direction. Individual capabilities may have different availability statuses, and planned features should not be considered live until officially released.

### Development Phases

| Phase                   | Focus                                                                                                     | Status      |
| ----------------------- | --------------------------------------------------------------------------------------------------------- | ----------- |
| Phase 1: Scan           | Website security checks, vulnerability matching, domain verification, reports, and Telegram alerts.       | Live        |
| Phase 2: Monitor        | Expanded asset monitoring, change detection, threat intelligence, and additional monitoring capabilities. | In progress |
| Phase 3: Defend & Patch | Firewall and WAF rule preparation, remediation guidance, and incident response workflows.                 | Planned     |
| Phase 4: Web3 Shield    | Smart contract security monitoring and wallet activity alerts.                                            | Planned     |

### Phase 1: Scan

The foundation of SHELLZERO X focuses on identifying publicly observable website and domain security issues.

The published capabilities include:

* SSL/TLS and HTTP security header checks.
* Technology detection and known vulnerability matching.
* DNS and email security checks.
* Subdomain and domain-related risk assessment.
* Scan reports and supported notification capabilities.

### Phase 2: Monitor

The monitoring phase focuses on improving visibility into assets and emerging security concerns.

The broader direction includes:

* Monitoring verified assets.
* Detecting relevant changes in external security conditions.
* Tracking newly confirmed exploited vulnerabilities.
* Expanding threat intelligence and monitoring capabilities.

Sentinel and Hunter are identified as running agents associated with asset monitoring and exploited vulnerability intelligence, respectively.

### Phase 3: Defend & Patch

This phase is intended to move beyond identifying potential weaknesses toward supporting defensive action and remediation.

Planned capabilities include:

* Preparing firewall and WAF rules for review.
* Providing remediation steps and configuration examples.
* Supporting structured incident response workflows.

Guardian and Patch are associated with these development goals. Their planned capabilities should not be interpreted as currently available automated defense or remediation services.

### Phase 4: Web3 Shield

The Web3 phase is intended to extend security monitoring toward blockchain-related environments.

Planned areas include:

* Smart contract security monitoring.
* Wallet activity alerts.
* Monitoring relevant blockchain-related security events.

Chain is the agent associated with this direction.

Supported networks, integrations, and detailed functionality should be confirmed when these features are released.

### Understanding Roadmap Status

| Status      | Meaning                                                                  |
| ----------- | ------------------------------------------------------------------------ |
| Live        | Identified as currently available in the published platform information. |
| In Progress | Under development or expansion.                                          |
| Planned     | A future development objective that is not yet generally available.      |

These labels describe the roadmap at the time this documentation is maintained and may change as development progresses.

### Roadmap Updates

For the latest information about releases and platform developments, consult the official SHELLZERO X website and announcements.

The roadmap represents development direction rather than a guarantee of release dates or specific outcomes.


---

# 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-and-roadmap/development-roadmap.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.