SecurityClaw SOC Automation Framework

Analyze OpenSearch or Elasticsearch logs with behavioral baselines and LLM-assisted anomaly triage.

Stars
★ 279
Last updated
4mo ago
License
MIT
Primary language
Python

At a glance

How it runs
Self-hosted serviceCLIWeb app
Works with
Universal · cross-platformOpenAI API · Claude API
Cost
Free software; you pay for model usage
Setup effort
High · needs real infrastructure
You'll need
Python 3.11+OpenSearch 2.x or Elasticsearch 8.xOllamaDocker ComposeNode.jsShell / CLINetwork accessLocal filesystem
Typical use
A SOC team needs behavioral baselines built from network logs in OpenSearch or Elasticsearch.
Not a fit if
  • Teams seeking a turnkey hosted SOC service
  • Teams unable to maintain a database, model service, and local configuration
Maintenance
Commits in the last 6 monthslast commit 2026-07-20

What does this agent do, and when should you use it?

SecurityClaw is a self-hosted, modular SOC framework that uses Python skills to read logs and anomaly findings from OpenSearch or Elasticsearch. APScheduler runs anomaly monitoring and baseline-building jobs; NetworkBaseliner summarizes logs into a vector index, and ThreatAnalyst uses retrieved baseline context to produce verdicts. The LangGraph chat_router supports interactive investigations and checkpoints state to SQLite. Users can operate it through a CLI, a FastAPI service, and a React web interface. Deployment requires configuring a database and LLM provider and running the corresponding services.

After database and LLM configuration, the Runner discovers skills under the skills directory and APScheduler runs those with configured intervals. NetworkBaseliner queries recent logs, aggregates behavior, and stores embeddings in the RAG vector index; anomaly_triage can poll findings, add descriptions, and place high-severity results in working memory; ThreatAnalyst retrieves similar baselines and returns TRUE_THREAT, FALSE_POSITIVE, UNKNOWN, or ERROR verdicts. The LangGraph chat_router runs a DECIDE→EXECUTE→EVALUATE StateGraph for conversational investigations and skill calls. Users can inspect status, dispatch skills, and chat through main.py commands, the FastAPI API, or the React UI; SQLite stores conversation and runtime checkpoints.

  1. A SOC team needs behavioral baselines built from network logs in OpenSearch or Elasticsearch.
  2. Security operations staff want to poll anomaly findings and send high-severity results for analyst review.
  3. Analysts need a chat workflow for querying logs, retrieving baselines, and investigating threats.
  4. Engineering teams want to extend the system with separate skills for database queries, forensic timelines, or field catalogs.

Key setup facts

Pulled from the install and usage notes below. The project README has the current values.

Install / run
  • pip install -r requirements.txt
Environment variables
OPENAI_API_KEY ANTHROPIC_API_KEY SECURITYCLAW_API_ONLY
Config files
config.yaml .env
Runtime
Python 3.11+
Install notes cover
Windows

How do you install or deploy this agent?

Requirements include Python 3.11+, Git, OpenSearch 2.x or Elasticsearch 8.x (a test mock is also available), and Ollama. The README recommends at least 4 GB RAM and about 2 GB of disk space for models and vector indices. Clone the repository, create a virtual environment, and install dependencies:

git clone https://github.com/SecurityClaw/SecurityClaw.git
cd SecurityClaw
python3.11 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

On Windows PowerShell, activate with .venv\Scripts\Activate.ps1. Run onboarding to configure the database, Ollama, configuration files, and optional external APIs:

.venv/bin/python main.py onboard

The example configuration uses qwen2.5:7b-instruct-q4_K_M and nomic-embed-text:latest; pull Ollama models separately. OpenAI, Anthropic, and other chat providers are also configurable, but RAG embeddings continue to use the configured Ollama embedding model.

How do you use this agent?

Start Ollama and the database, then configure config.yaml and .env; credentials depend on the selected services, such as OpenSearch username/password, OPENAI_API_KEY, or ANTHROPIC_API_KEY. Start the service, which runs the web UI, API, and scheduler:

.venv/bin/python main.py service

The current service instructions list the Web UI at http://localhost:5173 and API at http://localhost:7799. The launchers also expose status, stop, chat, skills, and logs. For CLI operation, run the scheduler, start terminal chat, or dispatch a skill:

.venv/bin/python main.py run
.venv/bin/python main.py chat
.venv/bin/python main.py dispatch threat_analyst
.venv/bin/python main.py status

For API-only mode, set SECURITYCLAW_API_ONLY=1 before running main.py service. Set the database provider to opensearch or elasticsearch in config.yaml, and specify the log, anomaly, and vector indices.

What are this agent's strengths and limitations?

Pros
  • Skills are isolated folders containing Python logic.py and LLM guidance in instruction.md, making capabilities extensible.
  • Configuration can switch between OpenSearch and Elasticsearch through the database abstraction.
  • Behavioral baselines are stored in a vector index and retrieved as RAG context for analysis.
  • LangGraph conversation and runtime memory can be checkpointed to SQLite.
  • Provides scheduled operation, CLI chat, a FastAPI service, and a React interface.
Limitations
  • Deployment requires a database and LLM service, several configuration values, and Python dependencies.
  • Ollama is the default model service; remote chat providers still use the configured Ollama embedding model.
  • The README marks anomaly_triage, threat_analyst, and forensic_examiner as under validation or in progress.
  • The README lists Elasticsearch compatibility testing as an improvement area and says in-progress modules weigh down aggregate test coverage.

How does this agent compare with similar options?

OpenSearch and Elasticsearch are documented as selectable database backends. The README does not compare SecurityClaw with other SOC products.

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
SecurityClaw SOC Automation Framework This agent 51 · Major gaps Self-hosted serviceFree + model costs ★ 279 4mo ago Python OpenAI API · Claude API
Home Generative Agent 69 · Some gaps — ★ 383 today Python OpenAI API · Claude API
AiSOC — Open-Source Self-Hosted AI Security Operations Center 84 · Good CLIFree + model costs ★ 7.1k 1d ago Python —
Local OpenAI LLM (Home Assistant Custom Integration) 68 · Some gaps Self-hosted serviceFree + model costs ★ 317 3d ago Python OpenAI API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
51/ 100 5-point scale 2.6 / 5
Trust 12/29
Reliability 6/14
Adaptability 12/18
Convention 10/18
Effectiveness 7/13
Verifiability 4/8
Why each dimension lost points
Trust12 / 29 · 2.1/5

README, SECURITY.md, and server.py show that the service binds to 0.0.0.0 by default and has no authentication or authorization. The documentation clearly warns against untrusted access and recommends firewall isolation, but access control and least privilege remain weak. Startup is operator initiated and external APIs require configured keys, but the packet does not establish confirmation before consequential actions or a recovery path. Data-flow documentation distinguishes local storage from optional external threat-intelligence lookups and names IPs and domains that may be sent. .env isolation, secret masking, and retention notes help, although stored data has no automatic expiry. Dependencies have minimum versions rather than a demonstrated lock or security audit. Capabilities, endpoints, and suggested actions are described, but attribution is limited and no clear rollback mechanism is shown.

Reliability6 / 14 · 2.1/5

The README gives conflicting service ports: quick-start instructions list 5173/7799 while later examples use 3000/500, weakening consistency. requirements.txt specifies open-ended minimum versions and the packet provides no lockfile evidence, so dependency availability is only partially addressed. SECURITY.md says failed connection checks may proceed and describes API errors without stack traces, but concrete error-handling evidence is limited in the supplied implementation excerpt.

Adaptability12 / 18 · 3.3/5

The material targets single-operator SOC use and covers OpenSearch/Elasticsearch, Ollama and several LLM providers, CLI and web interfaces, Docker, and multiple operating systems. Skill listings, manifest contracts, and manual versus scheduled status describe capability boundaries; optional threat-intelligence integrations and configuration switches help control triggers. The sample does not include enough implementation detail to establish that all boundaries and trigger conditions are enforced consistently.

Convention10 / 18 · 2.8/5

The README provides a directory map, skill descriptions, installation steps, configuration, command examples, and notes on in-progress skills, context budgets, and security limitations. Conflicting service-port guidance and older frontend/backend examples reduce naming and information stability. The complete MIT license text earns full marks. The supplied material does not clearly establish a changelog or routine maintenance responsibility/update path. It does provide a vulnerability-reporting route, but that alone does not establish ongoing ownership.

Effectiveness7 / 13 · 2.7/5

The skill-based SOC workflow, RAG behavioral baselines, anomaly analysis, and verdict/recommendation outputs have a clear operational use; CLI, API, and dashboard options support different workflows. The README also says some skills remain under validation and coverage is held back by unfinished modules. Deployment requires OpenSearch, a model runtime, and notable resources, while the packet does not quantify costs or compare them with benefits, limiting these scores.

Verifiability4 / 8 · 2.5/5

The README gives checkable detail on configuration, endpoints, data flows, skills, and limitations; SECURITY.md and server.py provide some corroboration on binding, CORS, and configuration masking. Many performance, security, and test-coverage statements remain documentation assertions, and the conflicting port descriptions further limit corroboration. The materials distinguish current state from planned improvements and known risks sufficiently to support basic fact/inference separation. No execution or independent verification is claimed, so confidence remains low as required.

Risks and how to mitigate them
  • The service binds to 0.0.0.0 by default and has no API authentication; follow SECURITY.md and restrict it to trusted networks behind firewall controls.
  • Documented service ports conflict; verify the current configuration and startup implementation before deployment.
  • Configuring external threat-intelligence services may send IPs and domains from logs to third parties; conversation and runtime SQLite data have no automatic expiry.
  • Dependencies are not locked. Security scans, runtime behavior, and test results were not executed or independently verified in this static review.
Evidence confidence: Low Reviewed Nov 12, 2026 Reviewed revision dbccec572c6f
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/securityclaw.svg)](https://followagents.com/en/agents/securityclaw)
<a href="https://followagents.com/en/agents/securityclaw"><img src="https://followagents.com/badge/securityclaw.svg" alt="FARS review"></a>

FAQ

Is Ollama mandatory?
Chat can use Ollama, OpenAI, Anthropic, compatible providers, or local CLI providers. The README says remote and CLI chat still use the configured Ollama embedding model for local RAG.
Does it automatically respond to threats?
The README describes escalation, threat verdicts, and recommended actions. anomaly_triage and threat_analyst are currently manual skills under active validation.
Can I run it from the command line only?
Yes. main.py run starts the scheduler, main.py chat starts terminal chat, and main.py dispatch <skill> runs one skill.
Which credentials are needed?
Configure database authentication when the environment requires it. Remote model APIs need their corresponding keys; MaxMind or IPinfo credentials are optional for GeoIP features.
Is SecurityClaw SOC Automation Framework free?
The software is free, but SecurityClaw SOC Automation Framework calls an AI model, and you pay that model provider for usage (or run a local model).
Is SecurityClaw SOC Automation Framework open source?
Yes. The source code is on GitHub (SecurityClaw/SecurityClaw) under the MIT licence.
Is SecurityClaw SOC Automation Framework safe to use?
FollowAgents' FARS review (Nov 12, 2026) scored SecurityClaw SOC Automation Framework 12/29 on trust and safety. None of the eight safety controls the review checks for was missing outright.
Is SecurityClaw SOC Automation Framework still maintained?
Development has slowed: the latest commit on GitHub is from 2026-07-20, within the last six months but not the last 30 days.
Who makes SecurityClaw SOC Automation Framework?
SecurityClaw SOC Automation Framework is published on GitHub by the account SecurityClaw. FollowAgents has not verified which person or company is behind that account.
Was this page helpful?
View on GitHub ↗ Install ↓

Related concepts