BRAINIAC Lateral Movement Detection API is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).
Analyzes security event logs to detect lateral movement indicators such as host-to-host traversal and known attack tooling/protocols, returning structured threat signals with confidence scores.
Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.
Returns a JSON object with a list of lateral movement signal items, each including a title, first/last observed timestamps, confidence level (low/medium/high), observed facts, inferred threat description, whether a confirmed attack was claimed, related event IDs, and the specific reasons triggered (e.g. host_to_host, lateral_keyword). Also includes overall detection status, findings with codes and details, a checked-at timestamp, signal count, and transparency flags (networkAccessed, paidProviderUsed, confirmedAttackClaimed, apiKeyRequired, infrastructureConnected). Limitations of the local rule-based analysis are explicitly listed.
POSThttps://www.brainiac.software/api/v1/security-signals/lateral-movement-detect?utm_source=zero.xyzUse this endpoint when you need lightweight, pay-per-call lateral movement analysis on structured security events without requiring an account, API key, or integration with a full SIEM platform. It is ideal for AI agents performing automated triage, red team validation, or incident response support where the caller supplies the event data and wants explainable, rule-based local analysis without a paid threat intel feed or external network access. Prefer alternatives (commercial SIEM or EDR platforms) when you need real-time endpoint agent telemetry, confirmed threat intelligence enrichment, or continuous monitoring rather than on-demand log analysis.
| Field | Type | Description |
|---|---|---|
| csv | string | |
| asOf | string | |
| file | object | |
| json | string | |
| text | string | |
| files | array | |
| events | array | |
| sequenceWindowMinutes | number | |
| bruteForceWindowMinutes | number | |
| weakSignalWindowMinutes | number | |
| correlationWindowMinutes | number | |
| bruteForceFailureThreshold | number | |
| lowAndSlowFailureThreshold | number |
{
"type": "json",
"example": {
"items": [
{
"id": "lateral-movement-detect-E1",
"title": "Lateral-movement indicator",
"lastAt": "2026-11-04T18:30:00.000Z",
"source": "Caller-supplied events; local rules only",
"status": "signal",
"firstAt": "2026-11-04T18:30:00.000Z",
"reasons": [
"host_to_host",
"lateral_keyword"
],
"detector": "lateral-movement-detect",
"evidence": [
{
"at": "2026-11-04T18:30:00.000Z",
"fact": "Observed host-to-host movement ws-10 → dc-01. Observed lateral-movement tooling/protocol keywords in supplied text.",
"eventId": "E1",
"inference": "Derived only from caller-supplied source/destination fields and keywords.",
"confidence": "medium"
}
],
"confidence": "medium",
"observedFacts": [
"Observed host-to-host movement ws-10 → dc-01.",
"Observed lateral-movement tooling/protocol keywords in supplied text."
],
"inferredThreat": "Suspicious movement between systems may be present in supplied network/auth logs. Not a confirmed intrusion.",
"confirmedAttack": false,
"relatedEventIds": [
"E1"
]
}
],
"status": "detected",
"findings": [
{
"code": "lateral_movement",
"kind": "conflict",
"detail": "Lateral-movement indicator confidence=medium; confirmedAttack=false.",
"subject": "E1"
}
],
"checkedAt": "2026-11-04T21:00:00.000Z",
"limitations": [
"Security events and logs are copied only from labeled fields supplied by the caller. The caller's network and security infrastructure are not accessed.",
"Detections are local rule and time-window analyses over supplied records. Missing values are not invented.",
"Observed facts are separated from inferred threat hypotheses. Events are not labeled confirmed attacks without sufficient multi-signal evidence.",
"No paid threat-intel feed or endpoint agent is used and no API key is required.",
"Severity scores are explainable rule weights over supplied detections/events, not vendor risk scores."
],
"signalCount": 1,
"apiKeyRequired": false,
"networkAccessed": false,
"paidProviderUsed": false,
"confirmedAttackClaimed": false,
"infrastructureConnected": false
}
}No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"