“Buildkite is a strong option for security-conscious enterprises, particularly those that want to keep CI/CD execution inside their own infrastructure while using a managed SaaS control plane.”
“Self-hosted agents: You retain control over where builds execute, the infrastructure they access, and the network boundaries around them.”
“Access control: Buildkite supports team-based permissions, resource-level access controls, SSO, and administrative restrictions.”
“A particularly useful security characteristic is that agents communicate with Buildkite through outbound HTTPS connections. You don't need to expose inbound ports to the internet.”
“Retention is particularly good: Events are stored indefinitely.”
“Buildkite supports job-level identity integration, allowing cloud providers to issue temporary credentials based on workload identity.”
“Shared responsibility | You manage the security of self-hosted agents, including OS patching and infrastructure hardening.”
“Persistent agents | Compromised jobs could potentially leave malicious processes or files behind.”
“Agent tokens | Long-lived tokens require expiry, rotation, and secure storage.”
“Team permission inheritance | Overlapping team memberships can unintentionally grant elevated permissions.”
“Build execution privileges | Pipeline code can access credentials and infrastructure permissions available to its execution environment.”
“Its main weakness isn't a lack of security features. It's that a significant portion of the security responsibility remains with your organization.”