Loading the ATM
An ATM, rendered by nqūb from its parts. Click it to look inside.

ATM security

Keep the fleet secure, working, and looked after.

Your fleet is every ATM, ITM, and video ATM you run. We write its security standards, harden its software, test it against real attacks, bring together what every machine reports, and support you after an incident.

Attacks

The attacks we help you prevent, detect, and recover from.

These apply to ATMs, and to ITMs and video ATMs, which add a network connection to a remote teller.

  • Jackpotting, black-box attacks, and ATM malware (logical attacks)
  • Hook-and-chain and ram-raid attacks
  • Skimming, shimming, card trapping, and cash trapping
  • Safe and cash-vault attacks: cutting, drilling, and explosive
  • Unauthorized access to the machine, its network, and its video teller connection

What we do

We cover security across the life of every machine, from standards to screens.

01StandardsSecurity configuration requirements, control tiers, and a baseline you can hold vendors to.
02Software securityOperating system and BIOS hardening, firmware, network, and golden images.
03TestingPenetration testing, DMA and PCIe attack testing, and chipset-level assessment.
04Incident responseRapid incident response and root-cause analysis after an attack, to help contain cash loss.
05Fleet monitoringDevice telemetry, remote fleet visibility, and continuous mapping against your requirements.
06Hardware and screensBoard security, chassis design, and screen design and development for ATMs and ITMs, tested before rollout.
In a SimFinancial branch in the Branch Experience Simulator, a persona uses a check-in kiosk beside a wall ATM; a bubble shows its score rising
The ATM inside a simulated branch, where customers decide whether to use it.

Independent ATM security review

An independent review shows where your fleet stands against published standards.

We compare your fleet with published standards and current practice, and tell you plainly where it stands, with the fixes in order.

What we need from you, and nothing else: a list of sites, machine models and counts by site, software and configuration baselines, and incident history. Nothing about your customers.

What you get: a findings report, a ranked list of fixes, and a walkthrough with your team.

How we keep it: we use your site list, configurations, and incident history for your review, and we keep each institution’s data separate. Any threat intelligence we pass on comes from public and industry sources, not from you.

Loading the 3D scene

Start here

Ask about an independent review.

Tell us how many machines and sites are in scope. We’ll reply with what we would look at and how long it takes.