Step 2: Agent Setup

Once you have your Garnet Platform API Key, the next step is to deploy the Jibril sensor (agent) into the environments you wish to monitor. Jibril is the component that collects system activity data and performs real-time detection and blocking.

Choose the deployment method most relevant to your environment(s):

• GitHub Actions Integration: Ideal for securing your CI/CD pipelines and software releases. This method embeds the Jibril sensor directly into your GitHub Actions workflows.

• Kubernetes Integration: Best for runtime protection of your containerized applications in production or other Kubernetes environments. This typically involves deploying Jibril as a DaemonSet. *

Kubernetes Integration

• Other Linux Environments (Standalone Jibril with Platform Integration):

  • While the primary integrations are highlighted above, Jibril can also be deployed as a standalone agent on individual Linux servers or VMs (e.g., using Docker, systemd, or direct binary execution) and configured to send data to the Garnet Platform using your API key.

  • For detailed instructions on standalone Jibril installation and configuration to connect to the Garnet Platform, please refer to the Jibril Sensor documentation and the official Jibril project resources.

Select the appropriate guide above based on where you want to deploy Garnet's monitoring and protection capabilities.