Methods to Protect Deployments
Compliance Measures
Epycbyte provides several compliance measures to ensure your deployments are secure and meet industry standards. These include:
- Shared Responsibility Firewall: Ensures that only authorized traffic reaches your applications.
- Access Control: Restricts access based on role-based permissions.
- SAML SSO: Single sign-on for secure authentication across multiple systems.
- HTTPS/SSL: Encrypts data in transit, ensuring secure communication.
Epycbyte Authentication
Epycbyte Authentication is available on all plans and offers robust access control:
- Restrict access to non-public deployments to only users with a Epycbyte account or shared via Sharable Links.
- Users without permission can request access, triggering notifications for branch authors.
- Enable via the Dashboard > Settings > Deployment Protection.
Password Protection
Available on Enterprise plans or with the Advanced Deployment Protection add-on for Pro plans:
- Restrict access to both non-public and public deployments based on environment type.
- Configure settings to control who can view or modify sensitive data.
Trusted IPs
Trusted IPs are available on Enterprise plans:
- Limit deployment access to specific IPv4 addresses or CIDR ranges.
- Returns 404 for unauthorized IPs, ideal for VPNs or external proxies.
More Resources
- Understanding Deployment Protection by Environment: Learn how to protect different environments.
- Methods to Bypass Deployment Protection: Understand potential threats and how to mitigate them.
- Last updated on August 7, 2024
This article provides a comprehensive guide to protecting your deployments using Epycbyte's tools. For more information or assistance, visit the Epycbyte documentation.