> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/security/security-en/readme.md).

# Cybersecurity and Communication

This overview describes the security and communication functions of the controllers <code class="expression">space.vars.covered\_products</code>. It supports the product-specific assessment in the context of the Cyber Resilience Act (CRA), but is not a declaration of conformity.

{% hint style="info" %}
**Test bench:** <code class="expression">space.vars.review\_date</code>

The actual functional scope depends on model, hardware revision, firmware version, installed applications, CODESYS Runtime, licenses, and project configuration. For the binding assessment of a supplied system, article number, serial number, firmware version, and installed applications are required.
{% endhint %}

## Short answer

{% columns %}
{% column %}

### Device and supply chain

* Encrypted web interface via HTTPS and X.509 certificates, plus optionally encrypted diagnostic archives
* Access via a device password, finely graded API keys.
* Signed firmware packages, which the device from version <code class="expression">space.vars.signed\_firmware</code> checks before installation
* Signed CODESYS Libraries, many with an SBOM in the format <code class="expression">space.vars.sbom\_format</code>
  {% endcolumn %}

{% column %}

### BMS and connectivity

* Modbus TCP and RTU, depending on model and application
* BACnet/IP optionally via a licensed CODESYS application
* Ethernet and, depending on the model, RS485
* LTE with SIM card on H1.M200-CDS-LTE
  {% endcolumn %}
  {% endcolumns %}

## Topics

<table data-view="cards"><thead><tr><th>Topic</th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Access and authentication</strong></td><td>Login, API keys, access services, password recovery</td><td><a href="/pages/f5e59a8d82620c4c8cc291eacae64553f87a4a49">/pages/f5e59a8d82620c4c8cc291eacae64553f87a4a49</a></td></tr><tr><td><strong>Encryption and certificates</strong></td><td>HTTPS/TLS, certificates, diagnostic archives</td><td><a href="/pages/7386b6402be41e7a3d5ec7cfe4699b41b22fc33a">/pages/7386b6402be41e7a3d5ec7cfe4699b41b22fc33a</a></td></tr><tr><td><strong>Signed firmware and updates</strong></td><td>PIOP signature, verification on the device, procurement channels</td><td><a href="/pages/1b291ae8bd5971e6c3efc583be696e8a43d2e576">/pages/1b291ae8bd5971e6c3efc583be696e8a43d2e576</a></td></tr><tr><td><strong>CODESYS and Libraries</strong></td><td>CODESYS Security, signatures and SBOMs</td><td><a href="/pages/3fd34900420adf5b9e6de9fc54b76155bc97c36c">/pages/3fd34900420adf5b9e6de9fc54b76155bc97c36c</a></td></tr><tr><td><strong>Network and BMS communication</strong></td><td>Modbus, BACnet, LTE and protective measures</td><td><a href="/pages/4e5d40f7ca701d3fa329f3379b14062293d05e44">/pages/4e5d40f7ca701d3fa329f3379b14062293d05e44</a></td></tr><tr><td><strong>Report vulnerabilities</strong></td><td>Responsibly report security vulnerabilities</td><td><a href="/pages/6420e29f18701dab863fb0a11466286db503a3b5">/pages/6420e29f18701dab863fb0a11466286db503a3b5</a></td></tr></tbody></table>

{% hint style="warning" %}
Modbus TCP, Modbus RTU, and classic BACnet/IP do not provide encryption or user login on their own. Operate them in protected automation networks and secure untrusted networks with segmentation, firewall rules, and a secured tunnel such as VPN or TLS.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.powerio.com/hub/security/security-en/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.