Ask Concord
Answers from our documentation
Ask anything about Concord. Every answer comes from our actual documentation.
Technical concepts
The vendor-neutral event schema that won the schema war. Concord by IaxaI sits above OCSF, not parallel to it.
Definition
OCSF is the Open Cybersecurity Schema Framework, an open vendor-neutral standard for representing security events. It defines event categories, classes, and field names so that an alert from CrowdStrike, an event from Okta, and a log from Splunk can be expressed in one canonical shape. By 2026 every credible security platform ships an OCSF pipe. Schema standardization is not a moat anymore. Concord by IaxaI treats OCSF as table stakes and builds the apparatus around it that OCSF itself doesn't provide: calibrated probability on every field mapping decision, deterministic vendor packs that keep machine learning out of the hot path, drift detection on the silent vendor schema changes that break OCSF compliance after the fact, and a signed audit trail so every mapping decision is replayable. The Concord position is above OCSF, not parallel. Translation is the floor, not the product.
See also
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.
Schema Drift
When a vendor silently renames or reshapes a field. The failure mode that quietly breaks every static mapping in your stack.
Sentence Transformer Embeddings
Dense vectors that turn text into geometry, used for translation alignment, entity resolution, and knowledge-graph retrieval.
30-minute walkthrough. Your tools. Your tenants. Your audit cycle. We will show you exactly where Concord earns its keep.