Industry

Cybersecurity for transport infrastructure

Signalling, depots, traffic lights and ports are controlled over the network. CUBRA connects them over our channel and keeps outside commands out.

What can happen

A city brought to a standstill

Transport is attacked both for money and for chaos.

Outside commands

Trains are stopped and points are switched.

Traffic lights

“Green in every direction” or gridlock across the city.

Ransomware

Ticket offices, departure boards and the control room stand still.

Tunnels

Ventilation switches off during a fire.

!
Real cases

2023: trains in Poland were stopped by radio commands. 2008: a teenager in Łódź switched tram points with a home-made remote control.

Where CUBRA Node goes

CUBRA Node at stations and depots

The CUBRA Node security gateway sits at the station, in the depot or in a junction cabinet. The link to the control centre goes only over our channel.

  • CUBRA Node Edge for junction cabinets
  • Speaks the language of transport equipment
  • Your equipment stays as it is
Internetno access to equipmentService companyonly via our channelCUBRA NodestationSignallingpoints, signalsDepotcharging, repairsTicket offices and turnstileskept apartDeparture boardsown data onlyCamerasrecorder onlySegments cannot see each other: a hacked departure board cannot reach the signalling
What the gateway does

Six levels of protection

Hides it from the internet

There is no way to reach your signalling, depots and ticket offices from outside: they cannot be seen from the internet, whatever vulnerabilities they may have.

Splits it into segments

Each group of devices works in its own segment (a separate part of the network): a hacked departure board cannot reach the signalling.

Lets service in only via our channel

The service company gets in through our secure channel. Every login is logged, and access opens for the duration of the work and closes by itself.

Understands the “language of equipment”

CUBRA Node examines the commands equipment receives over the network: each segment gets only the commands it needs, and the gateway holds back the rest (equipment command filter — after release).

Holds back dangerous commands (after release)

Switching points outside the timetable will not get through silently – the person responsible gets an alarm at once.

Knows every device

CUBRA Node finds all devices, their firmware and known vulnerabilities by itself – and suggests what to do.

Who exactly it is for

Where we help

What is connected and how we handle it
Signalling and points

Signals and points switch on the dispatcher’s commands. We place them in a closed segment that accepts commands only from the dispatcher, over our channel. CUBRA Node will hold back points switching outside the timetable and raise an alert.

Ticket offices and departure boards

Ticket offices and departure boards sit in a separate segment. Even if a board is hacked, there is no path from it to signalling and points.

Crews

Crews contact the dispatcher in CUBRA Messenger: messages, photos and calls stay only among your own people.

What it protects against
  • Outside commands
  • Trains stopped
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Metro and trams

Signalling, depots and ticket gates are separate systems but are often on one network.

What we offer
What is connected and how we handle it
Signalling

Signalling sits in a closed segment and accepts commands only from the dispatcher, over our channel. CUBRA Node will hold back an outside command and raise an alert.

Depot

The depot’s chargers and maintenance systems are connected for servicing. We place them in a separate segment, apart from traffic control, so an attack on the depot will not stop trains on the line.

Ticket gates and cameras

Ticket gates check tickets, and cameras record video to a recorder. We place them in separate segments and hide them from the internet; if a gate or camera tries to scan the network or send data out, the device is isolated and the duty officer receives an alert.

What it protects against
  • Points switching
  • Traffic stopped
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Bus depots

Electric buses charge overnight, and in the morning the control room sends them out on their routes.

What we offer
What is connected and how we handle it
Chargers

Electric bus chargers are controlled from the control room. We place them in a separate segment that accepts commands only from there, so an outside command at night cannot leave the depot without charge.

Control room

The control room assigns vehicles and routes. We place it in a separate segment that only its own staff can access; there is no path here from Wi-Fi, chargers or other parts of the network.

What it protects against
  • Fleet fails to go out in the morning
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Traffic lights

Junction controllers are managed from the city traffic centre.

What we offer
What is connected and how we handle it
Junction controller

The controller switches the traffic lights according to the traffic centre’s plan. We connect it to the traffic centre only over our channel; CUBRA Node will not let through a command that turns on green for crossing directions at the same time, and will raise an alert.

Cameras

A camera should send video only to the recorder. We put cameras in a separate segment and hide them from the internet; if a camera tries to scan the network or send data outside, it is isolated and the duty officer gets an alarm.

What it protects against
  • Accidents
  • Traffic jams
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Tunnels

A tunnel’s ventilation and fire system save lives in an accident.

What we offer
What is connected and how we handle it
Ventilation

The tunnel ventilation is controlled from the control room. We place it in a closed segment; CUBRA Node will hold back a command to switch off ventilation during a fire and raise an alert.

Fire system

The fire system must work under any conditions. We place it in a separate segment that only its own control system can access; there is no path here from other parts of the network, so it cannot be switched off from outside.

What it protects against
  • Ventilation switched off
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Toll roads and car parks

Barriers, pay stations and number plate cameras work together: pay and drive through.

What we offer
What is connected and how we handle it
Barriers

A barrier opens when the pay station has confirmed payment. We place the barriers in a separate segment that accepts commands only from the pay station. CUBRA Node will not let through an outside “open everything” command and will raise an alert.

Tills

A till should talk only to the bank and the accounting system. We put it in a separate segment: there is no path to it from Wi-Fi, cameras or office PCs, and CUBRA Node blocks any other connection the till tries to make.

Number plate cameras

Cameras recognise number plates and send them to the database. We place the cameras and the database in a separate segment and hide them from the internet, so the database of vehicle plates is not visible from outside and cannot be exported.

What it protects against
  • Theft
  • Entry stopped
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Airports

Baggage, jet bridges, departure boards, ticket desks – dozens of systems from different contractors.

What we offer
What is connected and how we handle it
Baggage handling

Baggage belts and sorting run on the commands of their own system, which a contractor services. We place them in a separate segment that accepts commands only from that system; the contractor connects over our channel.

Jet bridges

Jet bridges are operated by staff and serviced by a contractor. We place them in a separate segment accessible only to their own staff and to the contractor over our channel; there is no path here from other airport systems.

Departure boards

Departure boards show the timetable to passengers. We place them in a separate segment that accepts data only from the timetable system, so outside text will not appear on the boards.

Contractors

Each contractor connects only over our channel and only to their own system; access is granted for the duration of the work, and every sign-in is recorded in the log.

What it protects against
  • Baggage stopped
  • Disrupted flights
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Ports and cranes

Cranes load ships using data from the port’s terminal system. Stop either one – and the port stands still.

What we offer
What is connected and how we handle it
Cranes

Cranes are controlled from operators’ consoles. We place them in a closed segment that accepts commands only from there; CUBRA Node will not let an outside command through and will raise an alert.

Terminal system

The terminal system knows where each container is and where it needs to go. We place it in a separate segment that only its own staff can access; there is no path here from Wi-Fi, cranes or other parts of the network.

What it protects against
  • Port shutdown
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)

Ships

On a ship, navigation, the engine room, communication with shore and crew Wi-Fi share one network.

What we offer
What is connected and how we handle it
Navigation

Navigation systems sit in a closed segment. There is no path to them from crew Wi-Fi or from shore, so the course cannot be tampered with remotely.

Engine room

Engines and engine room systems are controlled over the network. We place them in a separate segment that only the engineers can access; there is no path here from crew Wi-Fi or from shore.

Crew Wi-Fi

The crew connects to a separate network where only internet access is open. None of the ship’s devices are visible from it, so even an infected phone will find nothing.

What it protects against
  • Tampered course
How we connect it
  1. CUBRA Node finds the facility’s equipment by itself
  2. We split signalling, ticket offices, departure boards and cameras into segments
  3. We connect the facility to the dispatcher over our channel
  4. We switch on alerts for dangerous commands (after release)
Several sites

The whole network in one dashboard

The dispatcher sees every station, depot and junction. A dangerous command raises an alarm (equipment command filter — after release).

  • The same rules for all sites in one go
  • Alarms sent to the duty officer’s phone
  • Log of service company logins
And people too

Secure communication for staff

Dispatchers, drivers and crews stay in touch in CUBRA Messenger.

  • Messages, calls, mail, files
  • Works on inexpensive phones

FAQ – Transport

How do I protect signalling and traffic lights from outside commands?

Control is connected over a secure channel, and outside commands don’t get through. Switching points off schedule or changing the traffic-light mode won’t go unnoticed – the person on duty gets an alert.

Can depots, ports and airports be protected with one system?

Yes. Each site has its own CUBRA Node, and all sites are in one dashboard with rights shared out.

What about outdated equipment that doesn’t get updates?

Hide it from the internet and put it in separate segments. The gateway lets only the necessary commands through to the equipment, and the equipment itself stays unchanged.

How do we stay in touch if the internet goes down?

Inside a site, communication runs through the node, and between sites messages can be passed without the internet – on a storage medium through CUBRA Offline Gateway (CUBRA Offline Gateway — after release).