DevSecOps Secret Interception & Orchestration

Stop credential leaks in Git before they reach production.

A high-throughput control plane for engineering teams. Ingests GitHub push webhooks in under 35ms, scans diffs with Shannon entropy and 40+ credential signatures, and reconciles incident lifecycles automatically.

CLI v1.0.0
$curl -fsSL https://aegis.ilyankhan.tech/install.sh | bash
terminal — aegis scan
$ git push origin feature/auth-sync
[aegis] Ingesting commit 8f4b1e2 (3 files modified)...
[!] DETECTED: AWS_SECRET_ACCESS_KEY
   File: services/auth/providers.ts:42
   Entropy: 4.82 bits (Threshold: 4.30)
   Dual-Cipher Hash: 8c3f91...b72a
[aegis] Webhook ACK: 28ms • Forensic ticket #INC-1042 queued
INC-1042: AWS Secret Key
CRITICAL
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY (Masked)
Actor: dev-lead@org.internal
Triage:RESOLVED_IN_COMMIT
The Enforcement Gap

Why local pre-commit hooks and static scanners fall short.

Developers frequently bypass client-side pre-commit hooks using git commit --no-verify. Without an un-bypassable cloud supervisor, leaked secrets sit in Git histories for months until attackers exploit them.

01

Webhook Timeouts & DoS

Large release pushes contain hundreds of file diffs. Synchronous scanners exceed GitHub's 10-second delivery window, dropping events and blinding security teams.

02

Secondary Plaintext Storage Leaks

Naive security tools store detected credentials in plaintext database columns, turning the scanner into a high-value attack target during SQL injections or backup dumps.

03

Phantom Duplication & Alert Fatigue

At-least-once webhook retries and parallel CI runs create duplicate tickets for identical commit SHAs, flooding SecOps channels with ghost findings.

System Architecture

Four architectural solutions built for scale and security.

Sub-35ms Asynchronous Ingestion Gateway

Incoming payloads to /api/v1/webhooks/github are validated using constant-time HMAC-SHA256 comparison and immediately enqueued onto Redis. The HTTP handshake completes in <35ms, satisfying GitHub SLAs with zero dropped events.

Cryptographic Blind Indexing

Dual-Cipher Architecture: secret signatures are salted and blind-indexed via HMAC-SHA256 for instantaneous deduplication queries (WHERE secret_hash = :hash). Raw tokens are never stored in plaintext.

Automated Lifecycle & Regression Reconciliation

When a subsequent commit eliminates the offending token line, the Celery worker automatically updates the ticket status to RESOLVED (REMOVED_IN_COMMIT). If the key resurfaces on another branch, it triggers an instant regression escalation.

Deterministic Fingerprinting & Deduplication

Every detected finding receives a deterministic fingerprint computed from SHA256(RepoID + RuleID + FilePath + BlindHash) with a PostgreSQL UNIQUE constraint, eliminating ghost findings during webhook retries.

CLI & Local Sensor

Pure Go standalone binary for developer workstations and CI runners.

The aegis CLI runs locally with zero runtime dependencies. Install pre-commit hooks or integrate scans directly into GitHub Actions, GitLab CI, and Docker builds.

Local Directory Scan
$ aegis scan .

Inspects uncommitted diffs and full repo history against 40+ credential rule definitions.

Git Hook Auto-Install
$ aegis init

Sets up executable pre-commit intercept hooks in the active Git repository.

Cloud Synchronization
$ aegis login --token <KEY>

Authenticates the CLI sensor with your central control plane organization.

Technical Comparison

How Aegis compares to existing secret scanning solutions.

Capability
Aegis Platform
GitHub Secret Scan
Generic CLI SAST
Webhook Ingestion SLA
< 35ms (Async 202)
Variable
Blocks CI execution
Plaintext Storage Policy
Zero (Blind Indexed)
Encrypted Blob
Plaintext in CI logs
Lifecycle Auto-Resolve
Automatic AST Reconciler
Manual Dismissal
Static State Only
Deduplication Engine
Deterministic Fingerprint
Basic SHA Match
None / Duplicate rows
Self-Hostable Monorepo
Docker Compose / Render
Enterprise Cloud Only
Local binary only
Frequently Asked Questions

Technical specifics and deployment details.

What types of secrets does Aegis detect?

Aegis detects AWS Access Keys (AKIA*), GitHub Personal Access Tokens (ghp_*), Stripe Live Keys (sk_live_*), Private RSA/EC keys, Database Connection Strings, Slack Webhooks, JWT signing keys, and high-entropy API tokens across 40+ detection signatures.

Does Aegis store raw secrets in the database?

No. Aegis enforces a strict zero-plaintext storage policy. Detected secret signatures are transformed into an HMAC-SHA256 blind index using an environment pepper. The web console and Slack notifications render only masked snippets (e.g. sk_live_****3a9f).

Can I self-host Aegis on our private cloud or Kubernetes cluster?

Yes. Aegis is 100% open-source and provides pre-configured Docker Compose, Render Blueprint (render.yaml), and standard PostgreSQL + Redis orchestration manifests.

How does Aegis prevent webhook delivery timeouts during large Git pushes?

The FastAPI ingestion gateway validates the incoming payload's HMAC-SHA256 signature and enqueues the job onto Redis with an immediate HTTP 202 response within 35ms, comfortably satisfying GitHub's 10-second delivery SLA.

Deploy automated secret interception today.

Connect your GitHub repositories in less than two minutes. Open-source, zero-trust, and engineered for high-throughput development pipelines.