> 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/mdr/common-questions.md).

# Common questions

<details>

<summary>Does the EDR slow down my computer?</summary>

The EDR may use more resources during occasional scans, but it is generally not the cause of a prolonged slowdown. A slowdown usually comes from:

* A high workload on the computer (demanding programs, saturated memory, full disk)
* A network or server connection problem
* A background update or process
* A software malfunction

To help us find the cause, gather this information:

1. Is the slowdown **widespread**, or does it only affect one computer? If only one, note its name or identifier.
2. What is **slow**: the computer itself (applications slow to open, frozen cursor) or the connection to a server or online service?
3. Have all other **security tools** been uninstalled, in particular antivirus software and any other EDR?

Then:

1. Make sure no other antivirus or EDR is installed, and that all related services are stopped.
2. Uninstall and reinstall the EDR on the endpoint.
3. List all the running processes and services during the slowdown.

Send this information to <protect@stoik.io>. It lets us tell a local (computer), network (connection or server) or EDR problem apart.

</details>

<details>

<summary>What if Internet connectivity is lost?</summary>

As long as a device has Internet access, protection is complete and real-time: the agent communicates continuously with the cloud for threat intelligence, detection and response.

A device that is temporarily offline (travel, dead zone, etc.) remains protected:

* **Local ML models**: the agent embeds on-sensor machine learning models that detect and block threats (e.g. malware from a USB drive) without cloud connectivity.
* **No EDR capabilities**: real-time telemetry, threat hunting, and remote response actions from the console are unavailable until the device reconnects.

When the device reconnects, the telemetry recorded offline is uploaded to the console for retrospective analysis.

For private or isolated networks (air-gap), open the required network flows at the firewall: see the network requirements for [CrowdStrike](/mdr/deploy/crowdstrike/network.md) and [SentinelOne](/mdr/deploy/sentinelone/network.md).

</details>

<details>

<summary>Does the EDR also monitor internal vulnerabilities?</summary>

No. Neither CrowdStrike nor SentinelOne detects software vulnerabilities in the standard EDR protection. It is an optional add-on that requires an additional subscription:

* CrowdStrike offers the Spotlight module.
* SentinelOne offers the Vulnerability Management module.

Without one of these modules, keep your own vulnerability monitoring, analysis and patching processes.

With one of these modules:

* Known vulnerabilities on endpoints are **detected automatically**, in near real-time, since the agent is deployed on the endpoints.
* The interface shows **which patches to apply**. You still apply the updates and patches yourself.
* Once the EDR is deployed, no further action is required: the Spotlight option is enabled automatically. In CrowdStrike, it is available to users with "Vulnerability management" rights.

</details>

<details>

<summary>How do I add more licences?</summary>

Deploy the EDR on new endpoints with your customer ID: you can add licences freely. An automatic annual adjustment appears on your invoice, based on the total number of activations.

</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/mdr/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.