Industry

Cybersecurity for banks and financial institutions

Money and client confidentiality make a double target. CUBRA protects correspondence with clients and places ATMs, cameras and safes in separate segments.

What can happen

A bank break-in does not start with the safe

Attackers most often get in through a camera, an ATM or a contractor.

The ATM pays out everything

An ATM is forced remotely to dispense all its cash.

Correspondence leak

Correspondence with clients in third-party messengers.

Entry through a camera

A camera in the branch leads to the cashiers’ workstations.

Ransomware

Shuts down branches and payments.

!
What has already happened

Remote ATM “jackpotting”, where the machine dispenses all its cash by itself, has been recorded in many countries around the world.

Where CUBRA Node goes

CUBRA Node Edge in every branch

The CUBRA Node security gateway sits in the branch cabinet. ATMs, cameras, safes and the office are kept apart and linked to the head office only over our channel.

  • ATMs talk only to the head office
  • Event log without message content
  • Rules: who may communicate with whom
  • Additional measures to protect staff – we will explain at a meeting
Internetno access to equipmentService companyonly via our channelCUBRA Nodebranch cabinetOfficeStaff PCsATMshead office onlyCamerasrecorder onlySafesalarm systemCustomer Wi-Fiinternet onlySegments cannot see each other: a hacked camera cannot reach the tills
What the gateway does

Six levels of protection

Hides it from the internet

There is no way to reach your ATMs, cameras and safes 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 camera cannot reach the tills.

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)

A command telling an ATM to dispense all its cash 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

Banks (head office)

A head office means correspondence with clients, payments, hundreds of staff and dozens of contractors. Attackers most often get in not through the safe, but through email, a contractor or a camera.

What we offer
What is connected and how we handle it
Staff mail and messages

Correspondence with clients and between departments goes through CUBRA Messenger and our mail. The server sees only ciphertext – not even the bank’s administrator can read other people’s messages. The app flags an email “from the CEO” sent from someone else’s device as suspicious.

Payment and accounting systems

Payment and accounting systems sit in a separate segment that only the staff and servers who need them can access. There is no path there from guest Wi-Fi, cameras or printers, so a hacked device in the banking hall cannot reach the payments.

Contractors and service firms

Contractors need access to maintain the bank’s systems. They connect only through our secure channel: every login is recorded in the log, and access opens for the duration of the work and closes by itself, so no forgotten open access is left behind.

Cameras, access control, alarms

Security staff need these devices. We put them in a separate segment that can see only the recorder and the security control panel, so a hacked camera will not become a way into workstations and payments.

Website and client portal

The website and client portal must be reachable from the internet, so attackers try to bring them down with a flood of requests (DDoS). CUBRA Node filters out unwanted requests before they are processed and changes entry points during an attack, so clients can still get in (switching entry points under attack — in development).

What it protects against
  • Phishing in the CEO’s name
  • Ransomware
  • Entry through a contractor
  • Correspondence leak
  • DDoS on the website
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place payments, office, cameras, security and guests in separate segments
  3. We move staff correspondence to CUBRA Messenger and mail
  4. We connect contractors over our channel and switch on alarms

Branch offices

A branch has tills, an ATM, cameras, a safe and customer Wi-Fi on one small network. One weak device is enough to reach everything.

What we offer
What is connected and how we handle it
Tills and workstations

Tills and workstations work with the bank’s head office. We put them in a separate segment that can see only the head office, so the tills cannot be reached from customer Wi-Fi or cameras.

ATM

An ATM should talk only to the processing centre. We put it in a separate segment and connect it to the centre over our channel. CUBRA Node will not let through an outside “dispense cash” command and will raise an alarm.

Cameras

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

Safe and alarm system

The safe and alarm system are connected so that the security control panel can see alarms. We put them in a closed segment with only one path out – to the control panel over our channel. The alarm cannot be switched off from the tills, cameras or Wi-Fi, and the control panel sees a lost connection at once.

Customer Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • Entry through a camera
  • ATM cash-out
  • Ransomware
  • Disabling security
How we connect it
  1. We deliver a CUBRA Node Edge, and it finds the devices by itself
  2. We place tills, the ATM, cameras, security and guests in separate segments
  3. We connect the branch to head office over our channel
  4. We switch on alarms for the head office duty officer
What is connected and how we handle it
ATM computer

The ATM’s computer needs a connection only to the processing centre. We let it through only over our secure channel, and CUBRA Node blocks any other connection, so an outside server cannot send the ATM a command.

Service engineer

The engineer connects to update or repair the ATM – only over our channel and only for the duration of the work; every login is in the log. A stranger’s laptop plugged into the ATM cable will see nothing.

Sensors and camera

Casing sensors and a camera watch over the ATM. We put them in a separate segment; opening the casing or connecting an unknown device sends an alarm to the centre.

What it protects against
  • Cash-out
  • Fake processing centre
  • An unknown device on the cable
How we connect it
  1. We install CUBRA Node Edge in the ATM cabinet or next to it
  2. We allow connections only to the processing centre
  3. We connect the service company over our channel
  4. Alarms go to the monitoring centre
What is connected and how we handle it
Doors and access control

Door controllers are connected so that security staff can manage access. We put them in a closed segment that can be controlled only from the security control panel. CUBRA Node will hold back any attempt to open many doors at night and raise an alarm.

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. The office network has no access to the recordings.

Alarm system and security control panel

The alarm system sends alarms to the security control panel. This link runs over our channel, so the signal cannot be faked or jammed unnoticed: if the connection drops, the control panel knows at once.

Counting machines and accounting

Counting machines send totals to the centre’s accounting system. We put them in a separate segment that can see only the accounting system, so the totals cannot be altered from another part of the network.

What it protects against
  • Disabling security
  • Opening doors
  • Access to camera recordings
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place payments, office, cameras, security and guests in separate segments
  3. We move staff correspondence to CUBRA Messenger and mail
  4. We connect contractors over our channel and switch on alarms
What is connected and how we handle it
Correspondence with clients and agents

Agents and clients correspond in CUBRA Messenger and our mail. Emails and messages are encrypted on the sender’s device, so the server – and even our company – sees only ciphertext.

Documents for clients

A client without our app receives a policy or statement via a CUBRA Share link: they open it in a browser and can only read it; the link has an expiry date.

Accounting system

The accounting system with client data sits in a separate segment; only staff can access it, from their own PCs. Guests, printers and cameras cannot see it, and bulk copying of the database raises an alarm.

Guest Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • Client data leak
  • Phishing
  • Ransomware
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place payments, office, cameras, security and guests in separate segments
  3. We move staff correspondence to CUBRA Messenger and mail
  4. We connect contractors over our channel and switch on alarms
Several sites

All branches in one dashboard

Head office sees every branch and every ATM. Alarms go straight to the duty officer.

  • 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

Staff and clients message each other in CUBRA Messenger. Not even an administrator can read other people’s correspondence.

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

FAQ – Finance and banking

Does CUBRA help a bank meet the regulator’s information security requirements?

Yes. Messages and calls are end-to-end encrypted, the event log keeps records without message content, and the algorithm suite is chosen to meet your country’s requirements. We go through certification for a specific system together with the bank.

Can a bank administrator read correspondence with clients?

No. The keys exist only on the devices of the people talking. The administrator manages people and policies in CUBRA Console but cannot see the content of messages.

How do I protect a branch’s ATMs and cameras that haven’t been updated in years?

CUBRA Node hides them from the internet and puts them in separate segments: the ATM sees only the processing centre, the camera only the recorder. A dangerous command to an ATM is held back, and the security team gets an alert. The equipment itself doesn’t need replacing (equipment command filter — after release).

How long does roll-out in branches take?

The compact CUBRA Node Edge goes into the branch’s cabinet without interrupting work, and all branches appear in one dashboard at head office. We’ll put together the exact configuration and price at the demo, based on the number of your sites and people.

See also: How to protect company messages from leaks.