Portainer Documentation
Official Website
Search…
BE 2.7
Welcome
Release Notes
Getting Started
Introduction
Portainer architecture
Requirements and prerequisites
Install Portainer BE
Upgrading Portainer
Using Portainer
Docker/Swarm
Kubernetes
Azure ACI
Edge Compute
Administering Portainer
Users
Endpoints
Registries
Licenses
Authentication logs
Settings
Frequently Asked Questions
Portainer Concepts
Installing
Upgrading
Troubleshooting
Contributing
Advanced Topics
CLI configuration options
App templates
The Portainer Edge Agent
Access control
Reset the admin user's password
Security and compliance
Using SSL with Portainer
Using Portainer with reverse proxies
Helm chart configuration options
Kubernetes roles and bindings
Deprecated and removed features
API
API documentation
API usage examples
Get More Help
YouTube
Open a support request
Contribute to Portainer
Contribute
Powered By GitBook
Security and compliance
Portainer runs exclusively on your servers, within your network, behind your own firewalls. As a result, we do not currently hold any SOC or PCI/DSS compliance because we do not host any of your infrastructure. You can even run Portainer completely disconnected (air-gapped) without any impact on functionality.
We comply with GDPR in relation to the anonymous analytics we collect. Data collection can be disabled at startup (or at any time), and if you are disconnected, it silently fails.
The Portainer code itself does not undergo any formal code analysis, however we scan our published images for vulnerabilities as part of the DockerHub process.
We are also the subject of regular third-party vulnerability analyses. No issues have been reported for some time, and any issues that are discovered are resolved within six weeks.
Advanced Topics - Previous
Reset the admin user's password
Next - Advanced Topics
Using SSL with Portainer
Last modified 9d ago
Copy link