thomasunise/argus

选用指南

AI 根据 README 整理 · 2026/10/25 08:26:15

适用场景

适用于需要实时检测和响应安全威胁、管理 AI 使用、进行持续渗透测试和攻击模拟的安全运营团队。

查看 README 依据

# Argus **The open-source security operations platform where AI agents do the legwork and you stay in control.** [](https://github.com/thomasunise/argus/actions/workflows/test.yml) [](LICENSE) Argus watches your cloud, identity, code, endpoints, network and Kubernetes. It catches attacks at machine speed, investigates them with AI agents, and contains them in seconds.

Every action is typed, checked against policy, dry-run first and reversible. It is self-hosted, multi-tenant and MIT licensed, so your security data never leaves your hands.  ## Why Argus **Stop attacks while they are happening, not the next morning.** Autonomous response playbooks act the moment a detection fires: block an attacker at Cloudflare, cut a laptop off the network through CrowdStrike or SentinelOne, and more from a catalog of 27 typed actions.

**Prove your detections work before an attacker tests them.** The agentic attack simulator replays 8 AI-driven attack scenarios in an isolated sandbox tenant, with optional evasion variants, and reports exactly which ones you caught, which you missed and which rules were off. **Pentest continuously, not once a year.** Autopilot has the red-team agent plan tests, runs them through the scope-checked harness, and re-plans from what it finds. It only runs inside scopes a human has marked for unattended testing.

目标用户

面向安全运营人员，包括分析师、操作员和管理员，以及需要审计合规的组织。

查看 README 依据

Roles are cumulative (`app/core/rbac.py`): | Role | Adds | |---|---| | viewer | read everything in the tenant, including autoresponse playbooks and the AI inventory | | analyst | edit findings and detections, run agents and evals, manage canaries, record approvals, use the AI gateway | | operator | manage and authorize assets, run tests, scans, autopilot and collectors, request, approve, execute and roll back actions, run detections and simulations |

| admin | users, API keys, settings, collector and integration configuration, the actions kill switch, test scopes (including marking one autonomous), autoresponse playbooks, AI gateway policy | | owner | tenant settings, approving critical actions | API keys carry a role and optional scopes (for example `ingest`) that further restrict them. A `system` principal is used only inside queue handlers. ## How agents, testing and actions are governed **Agents** (`app/agents/runtime.py`). A specialist is an `AgentSpec` with a system prompt, a

使用方式

通过 Web 界面使用，支持 Slack 集成进行审批操作。提供 API 和命令行工具。

查看 README 依据

They start in shadow mode so you can see what they would do, use only reversible actions, stay within hourly and blast-radius caps, and roll themselves back unless you keep the change. **Approve from Slack in one click.** Approve, deny or roll back actions straight from the alert. No console, no context switch. **AI that investigates without taking the wheel.** Seven specialist agents triage, investigate and hunt using read-only tools. They can propose a fix but never execute one. Everything they read is treated as untrusted data, so a prompt injection hidden in a log becomes a signal

python scripts/generate_secrets.py --write # fills the three REPLACE_ values, plus AUDIT_SIGNING_KEY and DATA_ENCRYPTION_KEY when they are empty uvicorn app.main:app --host 127.0.0.1 --port 8080 ``` Open http://127.0.0.1:8080 and sign in as `ADMIN_EMAIL` / `ADMIN_PASSWORD` from `.env`. With `REDIS_URL` empty, jobs run inside the API process (`WORKERS_INPROCESS=true`). With `DB_AUTO_CREATE=true` (the default) tables are created at startup; for Alembic-managed schemas set it to `false` and run `python scripts/migrate.py` (see `docs/MIGRATIONS.md`).

部署要求

需要 Python 3.11 或 3.12 进行开发，生产环境需要 PostgreSQL、Redis、外部审计存储（如 S3 Object Lock 或 Azure immutable blob），并建议使用 OIDC 或 TOTP 认证。

查看 README 依据

| Containers, compose, Helm, Terraform (AWS, Azure), CI, observability, docs | implemented | `Dockerfile`, `compose*.yaml`, `infra/`, `.github/`, `docs/` | Routers are discovered automatically. The full v1 surface is in `docs/API.md`. ## Quick start (development, SQLite, no Docker) Requirements: Python 3.11 or 3.12. ```bash python -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -r requirements.txt -r requirements-dev.txt cp .env.example .env

- `APP_ENV=production` refuses to start without PostgreSQL, `REDIS_URL`, `COOKIE_SECURE=true`, an `https://` `BASE_URL`, `DATA_ENCRYPTION_KEY(S)`, `AUDIT_SIGNING_KEY(S)`, an external audit sink, and either OIDC or `TOTP_REQUIRED=true`. - Dedicated workers (`WORKERS_INPROCESS=false`, `python -m app.worker`). - Use an object-lock audit sink (S3 Object Lock or Azure immutable blob), not only JSONL. - `/metrics` blocked at the edge; egress filtering for workers; secrets in a secret manager. - Images pinned by digest and verified with cosign (`.github/workflows/release.yml`). ## Roles

已知限制

Argus 不是认证产品，合规映射仅提供证据支持而非认证。自主功能默认关闭，需要显式启用。

查看 README 依据

monitoring-only mode (`docs/GO-LIVE.md`) before enabling any action. It is not a certified product; see `docs/COMPLIANCE.md` for what it can and cannot evidence. ## Architecture ``` Browser / SDK / sensors | v HTTPS (Caddy, ALB, Front Door or your ingress) +-------------------------------------------------------------+ | API (FastAPI) auth: session / OIDC+PKCE / TOTP / API keys | | RBAC (viewer < analyst < operator < admin < owner), CSRF, | | per-principal rate limits, request ids, security headers |

(per tenant, sets `actions_enabled=false`) rejects every request and execution. **Autonomy** (`docs/AUTONOMOUS-RESPONSE.md`, `docs/AUTOPENTEST.md`). Both autonomous features need a global switch and a tenant opt-in, and both are off by default. Autonomous response playbooks start in shadow mode (they record what they would have done), may only use reversible, non-critical actions, are capped per hour and by blast radius, roll actions back automatically unless a human keeps them, and ignore detections from the simulator. Autopilot