> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/security-requirements.md).

# Security Requirements

Follow these requirements to keep your Solink devices secure.

To ensure your Solink recording device is properly secured within your network, follow these requirements:

* **Place the recording device behind a network security appliance** such as a Firewall, UTM, Gateway, or next-generation Firewall with a private IP address.
* **Never expose the recording device directly to the internet** - Ensure there are no NAT and port forwarding rules to the device.
* **Isolate the recording device on a dedicated subnet or VLAN** to limit lateral network access. Restrict management access to specific subnets, VLANs, or source IP addresses.
* **Allow outbound communication from the recording device to the required domains** for the Solink service to function. See the full list at [Allow List URLs](/docs/install-connect-and-integrate/allow-list-urls.md).
* **Do not update or modify the firmware or software on the recording device**. Solink manages the recording device firmware version (QNAP) and software (Interlink) versions. Installation or modification of any software is strictly forbidden.
* **Access to the device is strictly forbidden without written permission from Solink**.

If you have any questions regarding this matter, please email us at <security@solinkcorp.com>.


---

# 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://help.solink.com/docs/install-connect-and-integrate/security-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.