Digital Sierra

Documentation

Everything you need to get started with t2e — from deployment to your first evidence report.

Deployment Guide

Deploy t2e with Docker Compose or Helm in under 10 minutes.

Architecture

Understand how the collector, backend, and dashboard work together.

API Reference

Complete API documentation for ingest, query, and management endpoints.

Configuration

Configure rules, mappings, sources, and environment settings.

Telemetry Sources

Detailed guides for each telemetry source integration.

Compliance Frameworks

SOC 2, ISO 27001, PCI DSS, and ISO 42001 control mappings.

Quick Start

Get t2e running locally with Docker Compose in 5 minutes:

1. Clone and start the stack
git clone https://github.com/t2e/t2e.git
cd t2e/deploy
docker compose up -d
2. Create an API key
curl -X POST http://localhost:8000/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"admin@demo.com","password":"password123"}'
3. Ingest test data
curl -X POST http://localhost:8000/v1/ingest/batch \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $T2E_API_KEY" \
  -d '{"events":[{"source":"kubernetes","event_type":"k8s.workload.upsert","payload":{"name":"web","namespace":"prod","images":["nginx:alpine"]}}]}'
4. View evidence

Open http://localhost:3000 and log in with your credentials.

Framework Mappings

Evidence mappings are defined in YAML and map telemetry event types to compliance controls:

# mappings/evidence_mappings.yaml
evidence_types:
  k8s_policy_violation:
    description: "Kubernetes policy violation"
    controls:
      - soc2:CC6.1
      - iso27001:A.8.9
      - pci_dss:2.2.1
    retention_days: 365

  change_record:
    description: "Code change with review"
    controls:
      - soc2:CC8.1
      - iso27001:A.8.32
    retention_days: 365