Skip to main content

Security in Bosun Workflows

At Bosun, security is a high priority. We employ a multi-layered approach to ensure that your code and data remain protected throughout the automated workflow execution. Our infrastructure is designed to provide strong isolation and minimize potential risks.

Isolated Execution Environments​

All code within Bosun tasks is executed in highly isolated environments to prevent unauthorized access or interference between different tasks or with the Bosun platform itself.

  • Hardened Docker Images: Tasks run inside hardened Docker images, which are meticulously configured to reduce their attack surface and include only the necessary components for task execution.
  • Kata Containers in Production: For production environments, Bosun leverages Kata Containers. Kata Containers combine the isolation benefits of virtual machines with the speed and manageability of containers, providing an extra layer of security and isolation for critical workloads.

Network Access and Data Isolation​

  • Controlled Network Calls: Code executed within Bosun tasks can make outbound network calls to external services (e.g., fetching data from APIs, interacting with Git repositories). However, these environments are strictly isolated from the Bosun platform's internal network and other running tasks. This ensures that a task cannot interact with the Bosun platform itself or other users' code.
  • No Cross-Task Interaction: Tasks are designed to be self-contained. There is no direct communication or shared state between different tasks, reinforcing isolation and preventing data leakage.

Ephemeral Code and Data Handling​

  • Temporary Storage: Any code or data generated or used by a task is stored temporarily within its isolated execution environment.
  • Secure Deletion: Once a task is completed and its results are processed, the entire execution environment, including all code and data, is securely deleted. This ensures that no residual code or sensitive information persists on the Bosun infrastructure after a task is cleaned up.

Agent Security​

  • Restricted Branch Access: Agents are prevented from directly pushing to protected branches like master or main. All changes are proposed via pull requests, ensuring human review and approval before integration.