beenuar/AiSOC

This is the rolling wishlist for new connectors the community would like to see ingested by AiSOC. How to vote / request 👍 the top comment for a connector you want. Reply with the exact product name + source format (REST? JSONL? syslog? S3 export?) + a link to the vendor's API docs. A signal score helps prioritisation: how many enterprises already rely on this in their SOC? If you've already shipped a custom connector for AiSOC, drop it here — even unmerged forks help. How to build one Start with Hello, connector (on the docs site). It is an end-to-end tutorial that builds a real, runnable connector against a free no-auth HTTP service, so you can walk every line of the contract — schema(), test_connection(), fetch_alerts(), normalize() and a smoke test — without a vendor account or an API key. Connectors overview is the companion reference. Connectors live under services/connectors/app/connectors/, one Python class per source. The shape: Subclass BaseConnector (base.py) and

Welcome 👋 If you've never contributed to AiSOC before, here's the shortest path from "interesting repo" to "merged PR". Step 1 — See AiSOC actually running git clone https://github.com/beenuar/AiSOC && cd AiSOC make up # the CORE profile — the real pipeline make smoke # prove it: one real event in, a retrievable alert out make up creates .env, generates every secret in it, creates an administrator and prints its password once — copy it. Then sign in at http://localhost:3000 (API docs at http://localhost:8000/api/docs). make smoke reports PASS or FAIL for each stage, so you know the pipeline works rather than assuming it: [PASS] raw telemetry accepted by ingest [PASS] event traversed the spine and became an alert [PASS] alert is retrievable by id from the API Needs Docker Compose v2 with 8 GB memory and 20 GB free disk in the Docker VM, plus python3 and bash. make doctor checks all of it and diagnoses a stack that won't come up. Installation says what each number was me