> 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/blog/en/news-blog/security-features-fur-powerio-gerate.md).

# Security features for powerIO devices

Integrated security functions for encrypted communication and controlled access. Easy configuration without prior knowledge.

Secure communication in our building networks is standard today. powerIO devices offer integrated security functions that are easy to configure and provide direct benefits for daily operations.

<figure><img src="https://1859048373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTXmRnUpH3eRGvNZHbUed%2Fuploads%2FlqdqeijSpzNRNURqxiDx%2FScreenshot%202025-11-21%20at%2016.28.05.png?alt=media&amp;token=5a5e9819-9813-4cd9-918b-0c0a0d257df3" alt=""><figcaption></figcaption></figure>

### HTTPS encryption

Encrypted communication protects against unauthorized access and the interception of sensitive data. powerIO offers two ways to enable it:

#### Automatic certificate generation

The device creates an SSL certificate automatically. One click is enough, and HTTPS is active. No prior knowledge or external tools required. The certificate is configured and integrated automatically.

#### Use your own certificates

For companies with their own certificate infrastructure, their own certificates can be uploaded. This enables integration into existing PKI systems and the use of officially signed certificates.

### Control access services

Not every service needs to be reachable at all times. The Access Services can be enabled or disabled individually.

### API keys for external systems

External systems or custom tools need access to the device API. Instead of using passwords, powerIO uses API Keys.

<figure><img src="https://1859048373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTXmRnUpH3eRGvNZHbUed%2Fuploads%2FewLPMRBaB5qoedCWM6Mf%2FBildschirmfoto%202025-11-21%20um%2016.04.39.png?alt=media&amp;token=22f0fcff-1f5e-48f4-9034-6e9b5f7c4115" alt=""><figcaption></figcaption></figure>

**Benefits:**

* Each system receives only the permissions it needs
* No password in scripts or configuration files
* Keys can be revoked individually

### Available across devices

The security features are available identically on all powerIO devices


---

# 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://support.powerio.com/hub/blog/en/news-blog/security-features-fur-powerio-gerate.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.
