How opentidehq/inittide works
Project type and purpose
• This repository, “InitTide,” is not a traditional full-stack application but rather a content-and-configuration management tool for security detection assets.
• It houses YAML-based detection objects, JSON schemas, lookup tables, and system-specific configuration files, all coordinated via CI/CD pipelines to validate, transform, and deploy detection rules to various security platforms (Splunk, Sentinel, CrowdStrike, etc.).
File structure
• Top-level CI definitions:
• .azure-pipeline.yml
• .gitlab-ci.yml
• These drive the validation, packaging, and deployment pipelines on Azure DevOps and GitLab.
• Configurations/
• deployment.toml, documentation.toml, lookups.toml
• systems/*.toml — settings for each target security platform.
• Lookups/
• Global, Sentinel, Splunk — metadata mappings used during rule conversion.
• Objects/
• Business Detections, Detection Models, Detection Rules, Threat Vectors — YAML definitions of each detection artifact.
• Schemas/
Key insights from the README
• The README is a generic GitLab starter template; it does not contain domain-specific architecture details.
• We must infer from the folder layout that the core workflow is: Author detection artifacts → Validate against schemas → Transform via lookups and configurations → Deploy to systems.