Zum Inhalt springen

Cybersecurity for ERP: protecting your business data

Your ERP holds your most valuable data — here's how to keep it safe.
8. August 2026 durch
Cybersecurity for ERP: protecting your business data
Adrian Cocos

Your ERP holds your finances, customers, suppliers, prices, payroll and operations. It is the most valuable system you run, and for the same reason the most attractive one to attack. An incident there is not an IT problem; it is the business stopping.

Security for an ERP is less about exotic technology than about a handful of basics done consistently. This article goes through them.

In short

  • Most incidents start with a stolen password or a missed update, not a sophisticated attack.
  • Access control, backups, updates and monitoring cover most of the risk.
  • A backup you have never restored is a hope, not a backup.
  • People and process matter as much as tools.

What can go wrong

  • Ransomware — data encrypted, operations stopped until systems are restored.
  • Account takeover — a real user's login, used by someone else.
  • Payment fraud — supplier bank details changed, or a fake invoice approved.
  • Data leakage — customer or employee data copied out, with legal consequences.
  • Insider misuse — access that was never removed, or broader than the job requires.

The essentials

Access control

  • Two-factor authentication for every user, without exceptions for management.
  • Least privilege: each role sees and changes only what the job requires.
  • Separation of duties: the person who creates a supplier is not the one who approves the payment.
  • Joiners, movers, leavers: access is granted, changed and removed as part of the HR process, the same day.
  • Administrator accounts are few, named and used only for administration.

Backups

  • Automated and frequent, covering both the database and attached files.
  • Stored separately from the production system, with at least one copy that cannot be altered or deleted from it.
  • Restored on a schedule. The test is the only proof the backup works.
  • With a known recovery time: how long until you are operating again?

Secure hosting

Whether in a public cloud or your own infrastructure: encryption in transit and at rest, network isolation so the database is not reachable from the internet, a firewall in front of the application, and separate environments for production and testing. Test copies should not contain unprotected real data.

Updates

Security fixes for the ERP, the operating system and the database are applied promptly, on a defined schedule. An unpatched system is the easiest target there is, because the weakness is public.

Monitoring and logging

Record who logged in, from where, and what was changed in sensitive areas: bank details, user rights, price lists. Alert on what should not happen — a login from an unusual country, a mass export, repeated failed attempts. Logs that nobody reads protect nothing.

Integrations: the side door

An ERP is connected to banks, web shops, carriers and other systems. Each connection is a way in. Give every integration its own credentials with only the rights it needs, rotate keys, and remove connections that are no longer used.

Cloud or on-premise?

A well-configured cloud environment is usually more secure than a server room in the office: physical security, redundancy and patching of the underlying platform are handled by teams that do nothing else. The condition is "well-configured". Responsibility for access, data and application settings remains yours.

People

Most breaches begin with a person: a convincing email, a reused password, a payment request that looked urgent. Short, regular training and a few firm rules work better than a long annual course. The most useful rule is simple: any change of bank details is confirmed through a second, known channel before it is applied.

Regulation

If you process personal data of people in the EU, GDPR requires appropriate technical and organizational measures and notification of certain breaches. The NIS2 directive adds cybersecurity obligations for medium and large entities in a defined list of sectors. Whether and how these apply to you is a question for your legal adviser; the measures above support compliance with both.

Have a plan before you need one

  • Who decides, and who is called, when something happens.
  • How to isolate the affected system.
  • How to restore, and in what order.
  • Who informs customers, partners and authorities.
  • A rehearsal, at least once a year.

Frequently asked questions

We are a small company. Are we really a target?

Most attacks are automated and do not choose by size. Smaller companies are often hit precisely because their defences are thinner.

What should we do first?

Turn on two-factor authentication for everyone, and restore a backup to prove it works. Both cost little and close the most common gaps.

How often should we review access rights?

At least twice a year, and whenever someone changes role or leaves.

Book a free executive diagnostic or explore our Odoo, AI and cybersecurity services.

How to run a successful ERP implementation (and avoid failure)
The habits that separate ERP projects that deliver from those that stall.