Security

OrcaCD is designed to be safe by default, but of course, there are always additional steps you can take to further secure your OrcaCD installation. Here are some best practices to consider:

Harden OrcaCD

• Disable password authentication for the Hub and use a secure OIDC provider instead, that enforces strong authentication methods, including secure multi-factor authentication (MFA).
• Always run the hub behind a secure reverse proxy and ensure that all communication is encrypted using TLS.
• Make sure to configure the TRUSTED_PROXIES environment variable correctly to prevent IP spoofing attacks.
• Restrict the IPs that can access the hub by configuring the ALLOWED_IPS environment variable. This will prevent unauthorized access to the hub and does not apply to webhooks or the agent connections.
• Restrict the volumes that can be mounted to locations within the OrcaCD deployments directory by setting the RESTRICT_VOLUMES_TO_DEPLOYMENTS_DIR environment variable to true. This will prevent malicious applications from accessing sensitive files on the host system.

Why is it safe by default?

A big focus of OrcaCD next to ease of use is security. Here are some of the measures we have taken to achieve this:

• All sensitive data is stored encrypted in the database using a modern encryption algorithm (AEGIS-256).
• Messages between the Hub and the Agents are encrypted with the same algorithm. The key is computed using the quantum-resistant ML-KEM algorithm in combination with X25519.
• We take all security issues seriously. You can find our security policy here.