# BRAINIAC Lateral Movement Detection API

> 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.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/security-signals/lateral-movement-detect?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-lateral-movement-detection-api-6c419737
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MH0VYaVT7GJmE883vF_Em

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-lateral-movement-detection-api-6c419737 -d '<json body>'
```

Example prompt: I have a batch of authentication and network events from the last hour — can you analyze them for lateral movement indicators, like host-to-host pivoting or known attack tooling, and tell me the confidence level and what specifically triggered any signals?

## When to prefer this

Use 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.

## Known failure modes

- Missing or malformed event fields result in incomplete detection coverage — gaps are not invented
- Events without source/destination host fields will not trigger host-to-host detection rules
- Very large payloads approaching the 200KB text or 12MB file limit may be rejected
- Ambiguous or unlabeled log formats may reduce detection accuracy
- Low-signal event sets may return status 'none' with no findings
- Lateral movement confirmed only with multi-signal evidence — single indicators return confirmedAttack: false

## How this service works

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.

## Output

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.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "fileBase64"
   ],
   "properties": {
    "role": {
     "type": "string",
     "maxLength": 80
    },
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json",
      "application/octet-stream"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "fileBase64"
    ],
    "properties": {
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "filename": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
     },
     "mediaType": {
      "enum": [
       "text/plain",
       "text/csv",
       "application/json",
       "application/octet-stream"
      ],
      "type": "string"
     },
     "fileBase64": {
      "type": "string",
      "maxLength": 12000000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20
  },
  "events": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "at": {
      "type": "string",
      "maxLength": 40
     },
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "host": {
      "type": "string",
      "maxLength": 253
     },
     "count": {
      "type": "number",
      "maximum": 1000000000,
      "minimum": 0
     },
     "action": {
      "type": "string",
      "maxLength": 120
     },
     "labels": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 80
      },
      "maxItems": 40
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "userId": {
      "type": "string",
      "maxLength": 120
     },
     "message": {
      "type": "string",
      "maxLength": 4000
     },
     "mfaUsed": {
      "type": "boolean"
     },
     "outcome": {
      "enum": [
       "success",
       "failure",
       "unknown"
      ],
      "type": "string"
     },
     "process": {
  
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "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
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-lateral-movement-detection-api-6c419737/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
