Egresswatch

pip install cognis-egresswatch

egresswatch scan .            # → prioritized findings in seconds

🔎 Example output

Real, reproducible output from the tool — runs offline:

$ egresswatch-emit --version
egresswatch 0.1.0

$ egresswatch-emit --help
usage: egresswatch [-h] [--version] [--format {table,json}] {audit} ...

Server-side outbound connection auditor (eBPF/Falco-spirit).

positional arguments:
  {audit}
    audit               audit an egress event stream or /proc/net snapshot

options:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --format {table,json}
                        output format (default: table)

Blocks above are real egresswatch output — reproduce them from a clone.

Sample result format (illustrative values — run on your own data for real findings):

{
"findings": [
    {
        "id": "1234567890",
        "title": "Suspicious Network Traffic",
        "description": "Potential malicious activity detected on port 80.",
        "created_by": "EgressWatch",
        "created_at": "2023-02-20T14:30:00Z",
        "updated_at": "2023-02-20T14:30:00Z"
    }
]
}

Usage — step by step

1. Install the CLI:

   pip install egresswatch
   

2. Audit an egress event stream (default events source), reading from a file or stdin (-):

   egresswatch audit events.jsonl --source events --fail-on high
   

3. Audit a host snapshot from /proc/net instead of an event stream:

   egresswatch audit netstat.txt --source proc
   

4. Read the output. The global --format json flag emits a structured report; the process exits non-zero when a finding meets --fail-on:

   egresswatch --format json audit events.jsonl --fail-on medium > egress.json
   

5. Wire it into CI with a custom policy file:

   egresswatch audit events.jsonl --policy policy.json --fail-on high || exit 1
   

Contents

• Why egresswatch? · Features · Quick start · Example · Architecture · AI stack · How it compares · Integrations · Install anywhere · Related · Contributing

Why egresswatch?

Server-side outbound connection auditor — eBPF/Falco wrapper — without standing up heavyweight infrastructure.

egresswatch is single-purpose, scriptable, and self-hostable: point it at a target, get prioritized results in the format your workflow already speaks (table · JSON · SARIF), gate CI on it, and let agents drive it over MCP.

Features

• ✅ Parse Events

• ✅ Parse Proc Net

• ✅ Evaluate

• ✅ Audit

• ✅ Runs on Linux/macOS/Windows · Docker · devcontainer

• ✅ Ports in Python, JavaScript, Go, and Rust (ports/)

Quick start

pip install cognis-egresswatch

egresswatch --version

egresswatch scan .                       # scan current project

egresswatch scan . --format json         # machine-readable

egresswatch scan . --fail-on high        # CI gate (non-zero exit)

Example

$ egresswatch scan .

  [HIGH    ] EGR-001  example finding             (./src/app.py)

  [MEDIUM  ] EGR-002  another signal              (./config.yaml)



  2 findings · risk score 5 · 38ms

Architecture

flowchart LR
  IN[target / manifest] --> P[egresswatch<br/>checks + rules]
  P --> OUT[findings (JSON / SARIF)]

Use it from any AI stack

egresswatch is interoperable with every popular way of using AI:

• MCP server — egresswatch mcp (Claude Desktop, Cursor, Cognis.Studio, uncensored-fleet)

• OpenAI-compatible / JSON — pipe egresswatch scan . --format json into any agent or LLM

• LangChain · CrewAI · AutoGen · LlamaIndex — wrap the CLI/JSON as a tool in one line

• CI / scripts — exit codes + SARIF for non-AI pipelines

How it compares

| | Cognis egresswatch | falcosecurity |

|---|:---:|:---:|

| Self-hostable, no account | ✅ | varies |

| Single command, zero config | ✅ | ⚠️ |

| JSON + SARIF for CI | ✅ | varies |

| MCP-native (AI agents) | ✅ | ❌ |

| Polyglot ports (JS/Go/Rust) | ✅ | ❌ |

| Open license | ✅ COCL | varies |

Built in the spirit of falcosecurity/falco, re-framed the Cognis way. Missing a credit? Open a PR.

Integrations

Pipes into your stack: SARIF for code-scanning, JSON for anything, an MCP server (egresswatch mcp) for AI agents, and a webhook forwarder for SIEM/Slack/Jira. See docs/INTEGRATIONS.md.

Install — every way, every platform

pip install "git+https://github.com/cognis-digital/egresswatch.git"    # pip (works today)

pipx install "git+https://github.com/cognis-digital/egresswatch.git"   # isolated CLI

uv tool install "git+https://github.com/cognis-digital/egresswatch.git" # uv

pip install cognis-egresswatch                                          # PyPI (when published)

docker run --rm ghcr.io/cognis-digital/egresswatch:latest --help        # Docker

brew install cognis-digital/tap/egresswatch                             # Homebrew tap

curl -fsSL https://raw.githubusercontent.com/cognis-digital/egresswatch/main/install.sh | sh

| Linux | macOS | Windows | Docker | Cloud |

|---|---|---|---|---|

| scripts/setup-linux.sh | scripts/setup-macos.sh | scripts/setup-windows.ps1 | docker run ghcr.io/cognis-digital/egresswatch | DEPLOY.md (AWS/Azure/GCP/k8s) |

Related Cognis tools

• dnsaudit — DNS posture & misconfiguration scanner — SPF/DKIM/DMARC/DNSSEC/CAA

• certpatrol — TLS cert lifecycle & rogue-issuance watch via Certificate Transparency

Explore the suite → 🗂️ all 170+ tools · ⭐ awesome-cognis · 🔗 cognis-sources · 🤖 uncensored-fleet · 🧠 engram

Contributing

PRs, new rules, and demo scenarios are welcome under the collaboration-pull model — see CONTRIBUTING.md and SECURITY.md.

⭐ If egresswatch saved you time, star it — it genuinely helps others find it.

Interoperability

{} composes with the 300+ tool Cognis suite — JSON in/out and a shared OpenAI-compatible /v1 backbone. See INTEROP.md for the suite map, composition patterns, and reference stacks.

License

Source-available under the Cognis Open Collaboration License (COCL) v1.0 — free for personal, internal-evaluation, research, and educational use; commercial / production use requires a license ([email protected]). See LICENSE.

---