LangGraph Architecture Combines Hybrid RAG with YARA and Sigma Engines for Streaming Log Analysis
A research team has developed an architectural pattern titled LangGraph, hybrid RAG + Signature Engine that creates a universal graph for processing streaming data, demonstrated on cybersecurity logs but designed to be modular for other text analysis tasks.
Architecture Overview
Logs are ingested by Vector with a Lua chunker producing 250-line segments and 20-line overlap, then published to a Kafka topic. An aiokafka consumer with retry logic and dead-letter queue forwards batches to an 8-node LangGraph DAG whose results are persisted in PostgreSQL.
The graph contains two parallel branches. The AI branch routes filtered logs through Agent 1 for event grouping and anomaly detection, Description Agent for natural-language summaries, and Agent 2 for hybrid RAG retrieval against MITRE ATT&CK. The deterministic branch parses logs and runs them through custom YARA and Sigma engines. All outputs converge at Agent 3, which produces the final report, validates hypotheses, and flags events requiring manual review.
Hybrid RAG Component
Agent 2 improves queries with an LLM, executes hybrid search combining vector similarity (weight 0.6) and BM25 (weight 0.4) over a Russian-translated MITRE ATT&CK collection in ChromaDB, then applies LLM re-ranking on the top-3 candidates. This approach reduces token usage while maintaining classification accuracy for techniques such as T1110 and T1190.
Deterministic Engines and Rule Generation
The YARA engine compiles .yar files and matches concatenated log fields using the native yara-python library. The Sigma engine parses YAML rules into selection conditions evaluated with contains, startswith, endswith, and regex operators. When RAG identifies an uncovered technique, Agent 3 triggers an LLM-based YARA rule generator that iterates up to three times with validation before storing the rule in a pending queue for analyst approval.
Performance and Metrics
On a 43-minute synthetic dataset of approximately 850 lines containing 38 ground-truth MITRE ATT&CK techniques, the pipeline recorded 85.7% precision, 78.9% recall, and an F1 score of 0.82 while processing 3.5 lines per second. The system was developed as part of a project practicum at UrFU and tested with Gemini 2.5 Flash.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.