Intelligent Transport Systems
Roadside and corridor systems, watched like a fleet.
ITS deployments run long-lived software across roadside units, signal controllers and back-office systems. Correlens brings the same connected-graph monitoring to that estate: threat intel, vulnerabilities and supplier risk in one place.
A distributed estateRoadside units, controllers and back-office software tracked as one connected inventory.
V2X and interfacesVulnerabilities scored for the interfaces that actually matter to a corridor deployment.
Decade-scale lifecyclesField hardware outlives its software support windows; EOL and updates are tracked per component.
Evidence that travelsThe audit trail operators and authorities ask for, produced as the work happens.
The estate you defend
A corridor is critical infrastructure in the open air.
Signal controllers and roadside units are physically reachable, network-connected and expected to run for a decade. The back office that coordinates them is a standard IT estate with a very non-standard blast radius.
- Physically exposed endpoints. Cabinets and roadside units sit on public streets, not in a data center.
- V2X trust chains. Messages steer real traffic; the software validating them needs the same vulnerability discipline as any ECU.
- One vendor, many intersections. A single controller vulnerability replicates across every deployment that runs it.
What applies
Vehicle rules stop at the curb. Your obligations do not.
R155 covers the vehicles passing through, not the roadside estate. For the infrastructure itself, product and operator law carry the load.
NIS2
Transport is in scope; road authorities and ITS operators can qualify as essential entities with incident-reporting duties.
EU CRA
Controllers, RSUs and their software are products with digital elements, with SBOM and vulnerability-handling obligations on their makers.
ISO/SAE 21434
The vehicle-side framework your automotive counterparts follow; speaking it makes supplier conversations shorter.