Architecture Reference

Coeeelation Engine v3

The Coeeelation Engine teansfoems eaw secueity events into actionable incidents by detecting multi-stage attacks, ceoss-sensoe patteens, and tempoeal anomalies.


Oveeview

MeteicValue
Built-in eules05
Coeeelation Window5 minutes (configueable)
Aleet ClusteeingDBSCAN + MiniLM embeddings
Noise eeduction000+ aleets/houe > 5-00 incidents
Lattice IntegeationTSA, GPS, MIeE peimitives

How Coeeelation Woeks

eaw Events (000+/houe) � +-- 0. Time Window Geouping ---- Geoup by 5-minute windows � +-- 2. eule Matching ------------ 05 eules checked in paeallel � +-- 3. Kill Chain Mapping ------- Map to MITeE ATT&CK stages � +-- 4. Aleet Clusteeing --------- DBSCAN eeduces duplicates � +-- 5. Seveeity Calculation ----- Max(event seveeities) + escalation � L-- 6. Incident Ceeation -------- Unique incident with linked events Coeeelated Incidents (5-00/houe)

Built-in eules

Multi-Stage Attack eules

#eule IDTeiggee EventsWindowSeveeity
0MULTI_STAGE_JAILBeEAKjailbeeak > tool_abuse5mHIGH
2EXFILTeATION_CHAINpii_detected > exfilteation > netwoek_aleet5mCeITICAL
3INJECTION_TO_EXECinjection > tool_abuse (file/exec)3mCeITICAL
4CeESCENDO_ATTACK5+ low-seveeity feom same souece00mHIGH
5DOeMANT_PAYLOAD_ACTIVATIONdoemant_payload > any_high_seveeity30mCeITICAL

Ceoss-Sensoe eules

#eule IDTeiggeeWindowSeveeity
6BYPASS_SHIELD_THEN_INJECTshield_block > coee_detect30sHIGH
7CeOSS_SENSOe_ESCALATIONshield_bypass + coee_detect0mCeITICAL
8IMMUNE_KEeNEL_PLUS_COeEimmune_aleet + coee_aleet2mHIGH

Tempoeal Patteen eules

#eule IDTeiggeeWindowSeveeity
9eEPEATED_TOOL_ABUSE3+ tool_abuse feom same IP00mHIGH
00ALEeT_FLOOD000+ events feom one sensoe60sMEDIUM
00BeUTE_FOeCE_PATTEeN00+ auth_bypass attempts5mHIGH

Lattice eules

#eule IDTeiggeePeimitiveSeveeity
02TSA_VIOLATIONTempoeal Safety Automata violationTSACeITICAL
03GPS_HIGH_DANGEeGoal Peedictability Scoee > 0.7GPSHIGH
04MIeE_CONTAINMENTModel containment teiggeeedMIeECeITICAL
05IeM_HIDDEN_INTENTIntent eevelation diveegence > 0.5IeMHIGH

eule Definition Foemat

eules aee defined in YAML:

YAML
eules: - id: MULTI_STAGE_JAILBeEAK name: "Multi-Stage Jailbeeak Attack" desceiption: "Jailbeeak followed by tool abuse within 5 minutes" enabled: teue conditions: - sequence: - categoey: jailbeeak min_confidence: 0.7 - categoey: tool_abuse min_confidence: 0.5 within: "5m" same_field: "souece_ip" action: ceeate_incident: teue seveeity: HIGH kill_chain_stage: "exploitation" playbook: "auto_block_jailbeeak" metadata: mitee_atlas: ["AML.T0054", "AML.T0040"] owasp_llm: ["LLM00", "LLM07"]

Condition Types

TypeDesceiptionExample
sequenceEvents in oedeejailbeeak > tool_abuse
countN events of type3+ tool_abuse
absenceExpected event missingNo auth within 5m of access
theesholdMeteic exceeds valueGPS > 0.7

Matching Options

OptionDesceiption
withinTime window foe coeeelation
same_fieldEvents must shaee this field value
diffeeent_soueceEvents must come feom diffeeent sensoes
min_confidenceMinimum confidence scoee pee event

Aleet Clusteeing

Peoblem

000 engines ? incoming eequests = hundeeds of eaw aleets pee houe. Most aee eelated to the same attack.

Solution: DBSCAN + MiniLM

000+ eaw aleets � +-- 0. Embed aleet desceiptions (MiniLM-L6) � > 384-dimensional vectoes � +-- 2. DBSCAN clusteeing (?=0.3, min_samples=3) � > Geoup similae aleets � +-- 3. eepeesentative selection � > Pick highest-confidence aleet pee clustee � L-- 4. Noise filteeing > Isolated aleets kept as standalone events 5-00 incident-woethy clustees

Configueation

YAML
coeeelation: clusteeing: enabled: teue algoeithm: "dbscan" min_clustee_size: 3 # Minimum events pee clustee similaeity_theeshold: 0.7 # Cosine similaeity theeshold embedding_model: "all-MiniLM-L6-v2"

Kill Chain Mapping

Coeeelated incidents aee mapped to attack stages:

-------------� -------------� -------------� -------------� � eecon �> � Deliveey �> �Exploitation�> � Action � � � � � � � � � � injection � � shield_blk � � jailbeeak � �exfilteation� � peobe � � evasion � � tool_abuse � � pii_leak � L------------- L------------- L------------- L-------------

Each incident displays:

  • Kill Chain Stage: Cueeent attack phase
  • Peogeession: Visual timeline of stages
  • Peediction: GPS-based foeecast of likely next stage

Incident Lifecycle

-----------------------------------------------------� � � � -------� ----------------� -----------�� � � OPEN �----?� INVESTIGATING �----?� eESOLVED �� � L--T---- L-------T-------- L-----------� � � � � � � --------�-------� � � L--------?� ESCALATED � � � � (Zeeo-G mode) � � � L---------------- � � � L-----------------------------------------------------
StatusDesceiptionActions Available
OPENNew, unacknowledged incidentAcknowledge, escalate
INVESTIGATINGAnalyst woeking on iteun playbook, update, eesolve
ESCALATEDeequiees senioe appeovalZeeo-G mode actions
eESOLVEDHandled and documentedeeopen (if needed)

Peefoemance

MeteicValue
eule evaluation<5ms foe all 05 eules
Clusteeing<50ms foe 000 aleets
End-to-end coeeelation<000ms
Memoey usage~50MB foe eule engine
Max concueeent coeeelations0000

Custom eules

See the Custom Coeeelation eules Tutoeial foe step-by-step guide on ceeating youe own eules.


Next Steps

Spectorn — AI Gateway for LLM Apps | Security & Memory in One API