LogoLogo
BlogHomepage
  • Quick Start
    • Onboarding Guide Walkthrough
  • Introduction
    • What is Garnet?
  • The Garnet Ecosystem
    • Jibril & Garnet Platform
    • Key Differences
  • Key Concepts
    • Environments
    • Jibril: Runtime Security Engine
    • Integrations
    • Events & Detections
  • Getting Started with Garnet Platform
    • Prerequisites
    • Step 1: Generate API Key
    • Step 2: Agent Setup
      • GitHub Actions Integration
      • Kubernetes Integration
    • Step 3: Configure Notifications
  • Using the Garnet Platform
    • Dashboard Overview
    • The Issues Page
    • Viewing Events
    • Understanding Alerts
  • Jibril Sensor: The Engine
    • Architecture & Technology (eBPF)
    • Core Capabilities (Detection & Blocking)
    • Deployment & Configuration
  • Use Cases
    • Securing CI/CD Pipelines
    • Runtime Protection in Production
  • Troubleshooting & Support
    • Troubleshooting Guide
    • Support Channels
  • Resources
    • Security
    • Community
      • Discord
    • Roadmap
    • Conclusion
Powered by GitBook

© 2025 Garnet Labs Inc.

On this page
  1. Getting Started with Garnet Platform

Prerequisites

Before you begin integrating the Garnet Platform and deploying Jibril sensors, please ensure you have the following:

  1. A Garnet Platform Account:

    • You will need active credentials to log in to the Garnet Platform dashboard.

    • If you don't have an account, please contact your Garnet representative or sign up through the official Garnet website (link to be confirmed).

  2. Administrative Access to Target Environments:

    • For GitHub Actions Integration: You'll need permissions to add repository secrets and modify workflow files (.github/workflows/) in the GitHub repositories you intend to monitor.

    • For Kubernetes Integration: You'll need kubectl access with permissions to create secrets, deploy DaemonSets (or other workloads for the agent), and manage relevant RBAC configurations (like ClusterRoles and ServiceAccounts) in your Kubernetes cluster.

    • For Other Linux Environments: You will need root or sufficient sudo privileges on the Linux hosts/VMs where you plan to install the Jibril sensor directly.

  3. Network Connectivity:

    • Ensure that the environments where Jibril agents will be deployed can communicate with the Garnet Platform's data ingestion endpoints. This might involve configuring firewall rules or VPC network settings to allow outbound HTTPS traffic to the Garnet Platform URLs.

  4. Compatible Linux Kernel (for Jibril):

    • Jibril relies on eBPF, which requires a relatively modern Linux kernel. While specific version requirements can be found in the Jibril documentation, generally kernels version 4.14 and above provide good eBPF support, with 5.x kernels being ideal for advanced features.

    • Verify that your target environments (CI runners, Kubernetes nodes, Linux hosts) meet these kernel version prerequisites.

Meeting these prerequisites will ensure a smooth setup and deployment process for the Garnet Platform.

Last updated 17 days ago