> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/prevention-tools/ad-scan/common-questions.md).

# Common questions

Answers to the questions most often asked about the script of the Active Directory scan.

<details>

<summary>Why is the script not signed?</summary>

The script is generated for each download and contains a token unique to your company, valid 24 hours. That is also why it cannot be reused or shared. Allow its execution as described in the [prerequisites](/prevention-tools/ad-scan/setup.md#prerequisites).

</details>

<details>

<summary>What does the script send to Stoïk?</summary>

The PingCastle report, plus the error and an excerpt of the log if the run fails. The script downloads PingCastle from Stoïk, runs it on the machine, uploads the report over HTTPS to Stoïk's storage in AWS Ireland, then deletes its files.

</details>

<details>

<summary>Can I run the script offline or check the results before sending them?</summary>

Not possible. The scan only works if the report is sent to Stoïk, and a PingCastle run outside the script does not show up in Stoïk Protect. For exceptional cases, contact <protect@stoik.io>.

</details>


---

# 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.stoik.io/prevention-tools/ad-scan/common-questions.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.