> 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/faq-and-news/en/news-blog/security-features-for-powerio-devices.md).

# Security features for powerIO devices

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

<figure><img src="/files/91db48e474f02b41b868b2b2e67aeb57798fd2c4" alt=""><figcaption></figcaption></figure>

### HTTPS encryption

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

#### Automatic certificate generation

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

#### Use custom certificates

For companies with their own certificate infrastructure, custom 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. Access services can be enabled or disabled individually.

### API keys for external systems

External systems or in-house tools require access to the device API. Instead of using passwords, powerIO works with API keys.

<figure><img src="/files/7128c7c00b5bfc9dd06b1ffa283393801b96f9ce" alt=""><figcaption></figcaption></figure>

**Benefits:**

* Each system receives only the rights it needs
* No passwords 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 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/faq-and-news/en/news-blog/security-features-for-powerio-devices.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.