# Page Not Found

The URL `files/IFraySFmICaGlnuwiQd4` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Revil - Kaseya Supply Chain Attack](https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/threat-research-and-analytics/revil-kaseya-supply-chain-attack.md)
- [Why and what of the Project?](https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/untitled.md)
- [Hunting & Detecting Kaseya - Jupyter Notebook](https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/threat-research-and-analytics/revil-kaseya-supply-chain-attack/hunting-and-detecting-kaseya-jupyter-notebook.md)
- [Exploratory Threat Analytics using Jupyter Notebooks](https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/exploratory-threat-analytics-using-jupyter-notebooks.md)
- [Hunts Vs Detections](https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/hunts-vs-detections.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/threat-research-and-analytics/revil-kaseya-supply-chain-attack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://sakshamtushar.gitbook.io/threat-hunting-on-the-rocks/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/threat-hunting-on-the-rocks/threat-research-and-analytics/revil-kaseya-supply-chain-attack.md`).

You may also use `Accept: text/markdown` header for content negotiation.