Telecom Vertical
Evidence-bound assurance for telecom AI.
Telecom automation runs on agents and apps that act inside the network — rApps, xApps, orchestrators. HAIEC evaluates what they can reach, what they did, and where the evidence stops.
RAN & tower forensics
Handover and cell-level evidence reconstructed into a path: which cell, how many were touched, and what capability the action required — from declared relation evidence, never inferred.
Slice isolation
Cross-slice traffic is evaluated against declared isolation policy. Cross-slice flow is evidence of a path — not automatically an isolation breach.
Service-based interface analysis
SBI call records, registration events, and SCP routes evaluated against declared communication patterns — deregistration anomalies and schema mismatches surfaced as findings.
rApp / xApp security
Application lifecycle, supply-chain, excessive-capability, and A1-policy detection families for non-RT and near-RT applications — with O-RAN WG11 threat IDs where the mapping exists.
Telecom entity model
Evidence binds to typed domain entities — 17 of them, from cell sites to slice subnets to SBI transactions. Full reference: /developers/entities.
Telecom detection families
Domain-specific families alongside the general AI-risk catalog — every rule carries real framework IDs where the mapping exists (O-RAN WG11 threat IDs, 3GPP specs, NIST AI RMF). Where no official mapping exists, none is claimed.
TOWERTower access-path integrityRAPP_SCrApp supply chainRAPP_EXrApp excessive capabilityRAPP_LMrApp lifecycle mismatchRAPP_A1A1 policy integritySBIService-based interfaceSLICESlice isolation
See it on real evidence
The ATP scenario — an evaluated traffic-protection agent with declared telecom relations and a qualified behavioral divergence.