Explainer

How to defend against cyberattacks: the checklist that matches how attacks actually happen

Every incident in this series has a dull cause: a controller left on the internet, an old firmware, a password with no second factor, a payment approved on a phone call. The defence is just as dull and works. Here it is, in the order that tends to matter, with the incident that proves each point.

Updated · 2 min read

01Eight things that matter

Do thisBecause of
Take management interfaces off the public internetFrance's CERT-FR said exposing a refrigeration controller's interface was against best practice. Fridge attacks
Know what you own, then patch or replace itDanfoss said the affected French units ran outdated firmware. IoT and OT
Require multi-factor sign-in everywhere that mattersColonial Pipeline reportedly lacked it on the account used. Infrastructure
Verify payments out of band, with two approversArup lost HK$200m to a fake video call. Deepfakes
Tighten the help desk and password reset processM&S's chairman said attackers impersonated an employee to get a help-desk password reset. Retail
Keep offline, tested backups and a manual fallbackDowntime, not the ransom, is the main cost. Ransomware
Map and limit your suppliers' accessThird-party involvement doubled to 30% in Verizon's report. Concentration
Alert on physical reality, not just ITAttackers reportedly stretched freezer defrost cycles from one hour to eight to delay alarms. A temperature alert that does not depend on the controller cannot be silenced by it.

02Close the gap faster than AI can open it

CrowdStrike's data puts average time from first access to lateral movement at 29 minutes, and Belgium's cyber centre says AI can now be used to exploit weaknesses. The practical consequence is to treat time to patch and time to detect as the numbers you manage. Anything that does not need to be on the internet, remove; anything that must be, update first. See how AI is making attacks faster.

03If you take or send payments

  • Use a dedicated, least-privilege API key per integration, and rotate it when staff leave.
  • Sign every API request. Payaries requests are signed with HMAC-SHA256, so a forged request without the secret is rejected.
  • Verify the signature on every incoming webhook before you mark an order paid; never trust a redirect alone.
  • Set withdrawal limits and require human approval above a threshold, particularly if an AI agent is involved: see AI agents and Payaries.
  • Reconcile invoices against your own records daily.

None of this makes a business attack-proof, and Payaries is a payment gateway rather than a security product. It narrows the one slice of exposure that a payment integration controls.

04The larger point

Technology is not turning on civilisation; people are using powerful, cheap and widely shared tools against systems that were built for efficiency before safety. The answer is not less technology but the unglamorous discipline we expect elsewhere: inspection, maintenance, redundancy and checking who you are dealing with. A freezer controller is now critical infrastructure, and it should be treated like it.

Questions

What is the most effective defence against cyberattacks?
No single control, but the common causes in recent incidents are exposed management interfaces, unpatched or unsupported devices, missing multi-factor authentication, and payments approved on an unverified request. Fixing those covers a large share of real incidents.
How can a small business protect itself?
Turn on multi-factor authentication, keep software and devices updated, back up offline and test the restore, verify payment changes by calling back on a known number, and keep a list of the suppliers you depend on.
How do I secure a crypto payment integration?
Use least-privilege API keys, sign requests, verify webhook signatures before fulfilling an order, set withdrawal limits with human approval, and reconcile regularly.

Next

Run a real invoice before you commit

Test keys work immediately, with no approval step. Payaries runs on real mainnet networks, so use a small real payment to test.