Ask Concord
Answers from our documentation
Ask anything about Concord. Every answer comes from our actual documentation.
Reference
A working reference for the Concord engine, the surfaces that ride on top of it, the technical primitives the architecture is built on, and the security operations vocabulary the buyer cares about. Twenty-five terms, cross-linked, each anchored to the capability it powers.
Concord engine vocabulary
The capabilities that make up the Concord by IaxaI engine and the surfaces that ride on top of it.
Reverse Transpiler
Compiles OCSF detections back into vendor-native query languages so one rule runs across every tool in the stack.
Universal Adapter
The connectivity layer that ingests events from any source and hands clean, canonical OCSF events to the rest of the engine.
Auditability Ledger
An append-only, hash-chained, Ed25519-signed evidence chain threading every decision the engine makes.
Compliance Evidence Auto-Packets
FFIEC, SOC 2, HIPAA, and PCI evidence bundles assembled directly from the audit ledger. Not screenshotted into a PDF.
Detection Portability Layer
Author a detection once against OCSF; Concord deploys it across every vendor surface in the stack.
Semantic Alert Dedup
Collapses alerts that describe the same incident across different tools into one narrative, using calibrated identity, not string matching.
Drift Detection
Streaming statistical tests on input, output, and schema-shape that catch silent vendor changes before they break detection coverage.
Auto-Repair (self-healing pipeline)
When drift fires, Concord proposes a new mapping, runs it in shadow, calibrates it, and only promotes after operator approval. Every step is ledgered.
Knowledge Graph (retrieval)
A dense-sparse graph of entities, events, and triples queried through tiered retrieval with embedding similarity and Personalized PageRank.
Calibrated Identity
Entity resolution with a coverage-guaranteed prediction set. Concord tells you when it doesn't know, instead of guessing.
Technical concepts
The standards, statistics, and primitives that the engine is built on. Useful for the engineers reviewing the architecture.
OCSF (Open Cybersecurity Schema Framework)
The vendor-neutral event schema that won the schema war. Concord by IaxaI sits above OCSF, not parallel to it.
Conformal Prediction
A distribution-free statistical wrapper that gives any predictor a coverage-guaranteed prediction set. Useful for honest "I don't know" outputs.
Bhattacharyya Distance
A statistical measure of overlap between two probability distributions. Concord by IaxaI uses the related Bhattacharyya coefficient to score how much two entities could plausibly be the same.
Maximum Mean Discrepancy (MMD)
A kernel-based two-sample test for whether two batches of data come from the same distribution. The drift detector's primary statistic.
Personalized PageRank
A graph traversal algorithm that ranks nodes by their importance relative to a chosen seed set. The retrieval primitive in the knowledge graph.
Hash Chain (append-only ledger)
A sequence of records where each entry contains the cryptographic hash of the previous entry. Tamper any past row, every later row breaks.
Sentence Transformer Embeddings
Dense vectors that turn text into geometry, used for translation alignment, entity resolution, and knowledge-graph retrieval.
Schema Drift
When a vendor silently renames or reshapes a field. The failure mode that quietly breaks every static mapping in your stack.
Security operations
Buyer-facing categories (SIEM, SOAR, XDR, MDR, MSSP) and how Concord sits next to them, not on top of them.
SIEM
Security Information and Event Management. The log-aggregation and rules platform every security practice runs. Concord by IaxaI sits above the SIEM, not next to it.
SOAR
Security Orchestration, Automation, and Response. The playbook engine that fires actions on alerts. Concord enriches the alerts SOAR fires on.
XDR
Extended Detection and Response. Vendor-locked telemetry stacks that correlate within one ecosystem. Concord works across XDRs, not inside one.
MDR
Managed Detection and Response. A service where humans run security operations on behalf of a customer. Concord is the engine an MDR runs, not a competing service.
MSSP (Managed Security Service Provider)
The primary buyer for Concord by IaxaI. A firm that delivers security operations to multiple end-clients, often regulated mid-market.
Multi-Tenant Security Operations
Running security for many isolated end-clients from a single platform. The structural problem an MSSP solves; the problem Concord makes solvable.
SOC Analyst
The persona doing the daily work: triaging alerts, running investigations, writing detections. The MSSP variant works across many tenants from one console.
30-minute walkthrough. Your tools. Your tenants. Your audit cycle. We will show you exactly where Concord earns its keep.