Skip to content

armgit / AiSOC

Public Imported from GitHub
0

Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.

3.4 KB
Raw Blame

Getting help with AiSOC

There are a few places to ask, in roughly the order you should try them:

1. Docs

The Docusaurus site at https://beenuar.github.io/AiSOC/ is published from apps/docs/docs/ in this repo on every push to main. Hit the search box first — it covers connectors, quickstarts, operations runbooks, the eval-harness methodology, deployment guides, and the API reference.

Useful starting points:

2. GitHub Discussions

For questions, ideas, show-and-tell, and roadmap input:

Please don't open a GitHub issue for a question — they're reserved for bugs, feature requests, detection-rule proposals, and benchmark submissions, each of which has its own template.

3. Try it yourself

The fastest way to see the product is the Codespaces quickstart — zero local install, runs in your browser, and drives the real stack rather than a hosted screenshot of it. Offline and even quicker, from a clone: pip install -e packages/aisoc-sandbox && aisoc-sandbox demo. (aisoc-sandbox is built and packed on every tag but not published to PyPI — the upload is blocked on registry credentials — so the from-source path is the one that works today.)

4. File a bug

If you've found a reproducible bug, open a Bug report. Please include:

  • AiSOC VERSION (from VERSION or the /api/v1/version endpoint)
  • Deployment path (Docker Compose / Render / Fly.io / Helm / Terraform / installer)
  • Exact reproduction steps
  • Logs from the failing service (docker compose logs --tail=200 <service>)

5. Report a security issue (privately)

Do not open a public issue or discussion for a security issue. Use GitHub Security Advisories or follow the SECURITY.md policy. We follow coordinated disclosure and credit reporters in .github/CREDITS.md.

6. Contribute

If you have a fix or improvement to share, see CONTRIBUTING.md. First-time contributors are welcome — pick a good first issue.

Response expectations

AiSOC is community-maintained; response times are best-effort:

  • Security advisories: usually triaged within 48 h.
  • Bug reports: triaged within a week for most weeks.
  • Feature requests / discussions: no SLA — community traction (👍, replies, PRs) is what drives prioritisation. See the v8.0 roadmap discussion for what's currently in flight.