bifrost

Least-privilege permissions

• Separate API keys by service: Don't use one master key for all 10,000+ model providers. Create individual keys for each service you actually use, so if one leaks, only that service is exposed.
• Rotate keys monthly: Set a calendar reminder to replace all gateway credentials regularly. Keep old keys disabled for 24 hours before deletion in case rollback is needed.
• Limit gateway's read/write access: Configure each API key to only perform required actions (e.g., inference-only, no model training or account changes).
• Restrict who can add new credentials: Only designated admins should be able to input API keys into the gateway; others should only read results.

Network isolation

• Run bifrost behind a firewall: The gateway should not be directly accessible from the public internet. Place it on a private network and route traffic through a secure proxy or VPN.
• Encrypt all connections: Require HTTPS/TLS for every request entering and leaving the gateway; disable unencrypted HTTP entirely.
• Use separate networks for sensitive models: If some downstream services are more critical, run dedicated gateway instances on isolated network segments.
• Disable unnecessary ports: Only expose the single port needed for API traffic; close all others to reduce attack surface.

Monitoring

• Log all API key usage with timestamps: Track which keys access the gateway, when, and from which IP addresses. Alert immediately if a key is used from an unexpected location.
• Watch for unusual request patterns: Set alarms for sudden spikes in requests, repeated failed authentication attempts, or requests asking for suspicious information.
• Audit cache hits and misses: Monitor the semantic cache for unexpected high-hit rates on sensitive queries, which could indicate poisoning.
• Review dependency updates weekly: Check for security patches to bifrost and all its underlying libraries; apply critical patches within 24 hours.

Red flags to watch for

• Unapproved changes to cached responses: If saved answers suddenly change or seem incorrect, the cache may have been tampered with.
• Keys working from unknown locations or times: Access to your API keys outside normal business hours or from countries you don't operate in suggests compromise.
• Requests asking for credentials or system details: Prompts that try to extract API keys, passwords, or internal configuration indicate active injection attacks.
• New dependencies appearing in updates: Before updating bifrost, verify all new libraries are legitimate and from trusted sources; early-stage projects can be targeted for supply-chain attacks.