Access Control
Epycbyte implements several measures to ensure the security and compliance of your data, including DDoS mitigation, SOC 2 compliance, and more. This article outlines Epycbyte's approach to access control, focusing on password protection, SAML SSO, and other security features.
Table of Contents
- Compliance Measures
- Password Protection
- Epycbyte Authentication
- SAML SSO
- Deployment Protection
Compliance Measures
Epycbyte adheres to strict compliance standards to protect your data. Key measures include:
- DDoS Mitigation: Advanced systems to prevent distributed denial-of-service attacks.
- SOC 2 Compliance: Ensures secure handling of your data in the cloud.
Password Protection
Password protection is available for both Preview and Production deployments, depending on the plan:
- Teams on Pro and Enterprise Plans: Password protection is enabled by default.
- Teams on Enterprise Plan Only: SAML SSO is required for access control.
Both methods can be used to protect Preview and Production environments.
Epycbyte Authentication
Epycbyte Authentication adds an extra layer of security for Preview and Production deployments:
- Personal Accounts with Team Membership: Users must use their login credentials to access the deployment.
- Enabled via Teams Project Dashboard: This feature can be turned on separately.
Epycbyte Authentication can be combined with Password protection, allowing users to choose between methods when accessing the deployment.
SAML SSO
SAML Single Sign-On (SSO) is supported for Enterprise plan users:
- Version v0: This implementation is currently in use.
- Security and Compliance: Ensures secure access control for sensitive deployments.
Deployment Protection
Epycbyte provides robust protection for your deployments:
- Preview Deployments: Both password protection and Epycbyte Authentication are available.
- Production Deployments: Password protection, SAML SSO, or a combination of both can be used.
References
This article is based on version v0 of the Epycbyte documentation.