How kolide/launcher works
Main Components
a. Core Components:
• Launcher Agent (Main Application)
• Osquery Integration
• Control Server Communication Layer
• TUF (The Update Framework) System
• Desktop Integration Components
• Storage Systems (SQLite, BBolt)
b. Supporting Systems:
• Authentication & Security Layer
• Logging System
• Table Extensions
• Debug & Monitoring Components
┌─ Host System ──────────────────────────────────────────┐
• ┌─ Kolide Agent ─────────────────────────────────┐ │
• ┌─ Core Services ─┐ ┌─ Extension Tables ─┐ │ │
• Osquery │ │ - Custom Tables │ │ │
• TUF Updates │ │ - Platform Tables │ │ │
• Control │ └────────────────────┘ │ │
• ┘ │ │
• ┌─ Storage ──────┐ ┌─ Communication ────┐ │ │
• SQLite │ │ - Control Server │ │ │
• BBolt │ │ - gRPC/JSON-RPC │ │ │
• ┘ └──────────────────┘ │ │
• ┘ │
• ┘
Key Relationships to Highlight
• Bidirectional communication between the Agent and Control Server
• Update flow through TUF
• Interaction between osquery and custom tables
• Storage system integration points
• Platform-specific components
Important Details
a. Component Labels:
• Version information
• Platform support indicators
• Security boundaries
b. Data Flow Indicators:
• Authentication paths
• Update channels
• Log shipping routes
• Query execution paths
Implementation Notes
• Version/platform compatibility notes
• Document security boundaries and trust relationships
Additional Sections
• Detailed update flow
• Security model
• Table extension architecture
• Desktop integration components
• Secure automatic updates
• Extended table capabilities
• Device identification
• Integration with the Kolide service