# Power Embedded's internal security

Power Embedded's internal security is extremely robust and the system uses an entire architecture based on self-managed SaaS resources in Azure, where management is done by Microsoft, automatic backups and high availability of the application and database by availability zones with automatic failover and guaranteed availability of 99.99%.

The system is subjected to various complex pentests on a regular basis, both automatic ones carried out by pentest tools and manual validations and tests carried out by security specialists from contracted companies.

The entire cloud environment is protected by Microsoft Defender for Cloud, which provides proactive and continuous protection, analysis and recommendations.

Access to Azure resources is blocked to the internet and only accessible via VPN.

Communication between the system and the browser is encrypted using SSL certificates (HTTPS).

The Power BI access key is stored in the database encrypted using the most secure algorithm on the market (RSA-OEAP) and various protection mechanisms to ensure that even in the event of improper access to the database, this key cannot be decoded, since access to the security key for decryption (which is individual per client) is stored in an Azure KeyVault where only the application has permission and connectivity to access.

The public API key is encrypted using a HASH algorithm that does not allow recovery of the generated value, just like the secret of a KeyVault.

## Power Embedded internal documentation

{% embed url="<https://powerembedded.com.br/arquitetura>" %}


---

# Agent Instructions: 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:

```
GET https://docs.powerembedded.com.br/en/faq/technical-questions/internal-security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
