> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/security-concept-of-operations-for-snyk/access-requirements.md).

# Access requirements

The access requirements for using Snyk applications such as the CLI

When you are using Snyk applications like the [CLI ](/developer-tools/snyk-cli/getting-started-with-the-snyk-cli.md)or [IDE integrations](/developer-tools/integrations/snyk-ide-plugins-and-extensions.md), certain local and remote resources must be accessible. This documentation explains how to harden your system without affecting Snyk functionality.

## Local filesystem

The required filesystem access may vary by product.

* CACHE\_PATH (Read,Write,Execute)
  * Windows: `C:\\Users\\<USERNAME>\\AppData\\Local\\snyk`
  * Linux/Alpine: `/home/<USERNAME>/.cache/snyk`
  * macOS: `/Users/<USERNAME>/Library/Caches/snyk`
* CONFIG\_PATH (Read,Write)
  * Windows: `%USERPROFILE%\\.config\\configstore`
  * Linux: `$HOME/.config/configstore`
  * macOs: `$HOME/.config/configstore`

## Network resources

### Required

* api.\<SNYK\_INSTANCE>.io:443
* app.\<SNYK\_INSTANCE>.io:443
* 127.0.0.1:\<EPHEMERAL\_PORT\_RANGE>
  * required for Inter Process Communication
  * [Ephemeral Port Range](https://www.rfc-editor.org/rfc/rfc6335.html#section-6) might vary by Operating System and Settings

### Optional

* deeproxy.snyk.io:443 (for Snyk Code)
* downloads.snyk.io:443 (depending on features used, such as downloading the CLI)
* learn.snyk.io:443 (to be able to display Snyk Learn links in issue details)
* static.snyk.io:443 (depending on features used, such as downloading the CLI)
* snyk.io:443 (depending on features used)
* \*.sentry.io:443 (error reporting)


---

# 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.snyk.io/developer-tools/snyk-cli/security-concept-of-operations-for-snyk/access-requirements.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.