Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

ERP Data Security in Uzbekistan: Access Rights, Backups and Internal Controls

ERP data security for companies entering Uzbekistan: least-privilege roles, audit logs, 3-2-1 backups, 2FA, offboarding, localization and a 20-point checklist.

ERP Data Security in Uzbekistan: Access Rights, Backups and Internal Controls

Short answer: ERP data security is not an antivirus product, it is discipline. Every employee sees only the data their job requires. Every significant action is logged. The database is copied daily to a separate location, and restores are tested. When someone leaves, their access is closed the same day. For a foreign company in Uzbekistan there is one more layer: local rules on where personal data may be stored. They changed in March 2026 and should shape your hosting choice.

Where the risks actually come from

Executives often picture an outside attacker. In practice, losses in a local subsidiary come from simpler places:

  • Shared logins. The whole warehouse works under one "warehouse" user. When an error appears, nobody knows who made it.
  • Excess rights. A sales manager can see cost prices and colleagues' clients. When they leave, the client base leaves with them.
  • Access never revoked. An employee or contractor has gone, but their password still works.
  • No usable backup. A server disk fails or ransomware hits, and the last copy is three months old.
  • Internal fraud. A cashier books a refund and keeps the cash. A storekeeper "adjusts" stock.

With a custom system, these controls are far easier to build into the architecture from day one. The overall planning of such a system is covered in the main guide to custom ERP development. This article focuses on the security layer only.

Roles and access rights: the least-privilege principle

The core rule: each employee gets the minimum rights needed to do the job, and nothing more. This is the least-privilege principle.

Also read Your Customer Calls Twice and Still Has to Spell Their Name: Connecting IP Telephony to ERP in Uzbekistan Technology · 10 min

Rights are granted to roles, not to people. Roles are defined first, then each employee is assigned one. Roles follow from the company structure. If reporting lines and responsibilities in the local entity are still unclear, start with the organizational structure.

An indicative matrix for a trading company (adapt it to your business):

  • Sales manager — Can view: Own clients, selling price, stock; Can change: Own orders; Not allowed: Cost price, colleagues' clients, export
  • Storekeeper — Can view: Stock, receipts and issues; Can change: Transfers and goods receipt; Not allowed: Prices, client contacts
  • Cashier — Can view: Daily till, receipts; Can change: Sales and refunds within limit; Not allowed: Deleting documents, changing discount limits
  • Accountant — Can view: Financial documents, reports; Can change: Payments, e-invoices; Not allowed: Managing users and roles
  • System administrator — Can view: Settings; Can change: Users, roles; Not allowed: Editing financial documents

Nobody should both grant rights and use them.

Three rights need extra control: export (downloading to Excel), deletion and changing prices or discounts. In most cases a "cancelled" status is enough instead of deletion. The document stays, and so does its history.

The role and rights list belongs at the start of the project, as a mandatory section of the ERP technical specification.

Logins, 2FA and offboarding

Personal logins for everyone. No shared users. Shift cashiers each sign in with their own account.

Two-factor authentication (2FA). On top of the password, the system asks for a code from an authenticator app or a push confirmation. At minimum, enable it for managers, finance, administrators and anyone connecting from outside the office, including head-office staff abroad. SMS codes are weaker than app codes, but far better than nothing.

Offboarding. Make it a written procedure. On the day the termination order is signed:

  1. Block the ERP login. Do not delete it, because the user's document history is needed.
  2. Close access through the mobile app and the Telegram bot.
  3. Change shared passwords the person knew: Wi-Fi, mailboxes, payment-system dashboards.
  4. Revoke API keys and integration tokens issued in their name.
  5. Reassign their clients and open tasks.

Every month, reconcile active ERP users against the payroll list. Every extra login is an open door.

An employee confirms a system login on her phone next to a key card

Audit trail and internal fraud controls

The audit trail records significant actions: who did what, when, in which document, and what the value was before and after. Ordinary users must not be able to edit it, and neither should administrators.

At minimum, log:

  • logins and failed login attempts;
  • changes to prices, discounts and credit limits;
  • cancelled documents and back-dated entries;
  • manual stock adjustments;
  • exports and large report downloads;
  • changes to roles and rights.

A log nobody reads adds little. Give local management a short weekly exception report: cashiers with the most refunds, discounts above the usual limit, documents posted outside working hours, adjustments after a stock count. A number is not an accusation. It is a prompt to ask a question.

The strongest anti-fraud control is segregation of duties. No single person can run a transaction from start to finish. For example:

  • one employee creates a new supplier, another approves payments to it;
  • a cashier starts a refund above a set amount, the store manager approves it;
  • a storekeeper enters a stock-count variance, finance approves it.

The thresholds are a business decision. What matters is that they are enforced in the system, not held in a verbal agreement.

A store manager turns the register key to approve a return beside the cashier

Backups: the 3-2-1 rule and restore testing

A widely used benchmark is the 3-2-1 rule:

  • 3 copies: the live database plus two copies;
  • 2 different storage media or systems;
  • 1 copy off-site, separated from the main server.

Current practice adds one more condition: one copy is immutable, so it cannot be overwritten or deleted. Ransomware that reaches a server can damage backups on attached disks too.

Write down answers to two questions:

  • How much data can the business afford to lose? With daily backups, the worst case is re-entering one day of work.
  • How fast must the system be back? For a retail chain this is hours, for some back-office processes a day or two.

The most common mistake is taking backups that are never restored. At least once a quarter, restore a copy to a separate server and confirm the reports open. Record the result with a date.

Where the server lives: hosting, encryption and localization

There are three options: a server in the local office, a rented server in a data centre, or a cloud service. The questions are the same for each:

  • Who has physical and remote access to the server or the control panel?
  • Who installs operating system and database patches, and when?
  • What happens during a power or internet outage?
  • Is a backup stored somewhere else?
  • Does the provider contract state who owns the data and how it is returned if the service ends?

An office server looks cheap, but often nobody owns it and patches are not installed.

Encryption is needed in two places. In transit: the system is reachable only over HTTPS. At rest: disks, backups and the most sensitive fields (passport data, bank account numbers) are encrypted. Encryption keys are not stored alongside the database.

Legal requirements. Uzbekistan's Law on Personal Data (No. ZRU-547) requires database owners and operators to protect personal data. Its localization rule changed in March 2026. From 2021, personal data of Uzbek citizens had to be stored on servers physically located in the country. Under the amended law, mandatory in-country storage now applies mainly to biometric and genetic data and to data on subscribers of telecom operators. Other personal data may be stored and processed abroad if one of the conditions listed in the law is met: for example, the destination country is recognised as offering equivalent protection, or the operator applies standard contractual clauses or binding corporate rules that meet the regulator's requirements.

What this means for an ERP:

  • If attendance terminals use face or fingerprint recognition and the templates are stored in the system, keep them on servers in Uzbekistan.
  • Before moving the subsidiary onto a regional or global ERP instance hosted abroad, confirm which legal condition covers client and employee names, phone numbers and passport details.
  • Implementing regulations may still be evolving. Review the hosting setup and data categories with local counsel before go-live.

External integrations and API keys

An ERP rarely works alone. It exchanges data with a CRM, online cash registers, local payment systems, marketplaces, Telegram bots and often a group reporting system. Every connection is another door into the database.

Rules:

  • One key per integration. Never share one key. If one service has a problem, only its key is revoked.
  • Least privilege for keys too. If a service only needs to read orders, it gets no write or delete rights.
  • No keys in code or chats. Store them in protected server settings or a password vault.
  • Rotate keys regularly, and immediately when a contractor or developer leaves.
  • Log integration traffic. You can see which service received how much data and when.

How to design and test an integration is covered in ERP and CRM integration. Check what each user can see through a bot against the guidance in ERP and Telegram bot. Treat the bot as a system user in its own right: give it a dedicated role with minimal rights and log its requests.

Practical checklist

Answer yes or no for each item:

  1. Every employee has a personal login; there are no shared users.
  2. The role and rights matrix is documented and approved.
  3. Export, deletion and price-change rights are restricted.
  4. The administrator cannot edit financial documents.
  5. 2FA is enabled for managers, finance and remote users.
  6. An offboarding procedure exists and runs on the same day.
  7. Active users are reconciled with payroll every month.
  8. The audit trail is on and nobody can edit it.
  9. Management reviews a weekly exception report.
  10. Large payments, refunds and stock adjustments need a second approver.
  11. Backups run automatically and one copy is off-site.
  12. One copy cannot be changed or deleted.
  13. A restore has been tested in the last three months.
  14. The system is reachable only over HTTPS.
  15. Disks, backups and sensitive fields are encrypted.
  16. Someone is responsible for server patching.
  17. The hosting contract states data ownership and return terms.
  18. Each integration has its own key with minimal rights.
  19. Keys are not stored in code or chats.
  20. Where personal and biometric data is stored has been reviewed with local counsel.

Split the "no" answers into two groups. Close items 1, 6, 11 and 13 first: they give the fastest and cheapest protection.

Key takeaway

ERP data security is not a one-off setting but a daily routine. Rights follow roles and stay minimal. Significant actions are logged, and management reads the log. Backups live elsewhere, and restores are tested. Access closes the day someone leaves. Start with the checklist and repeat it every quarter.

Frequently asked questions

Can a global ERP security policy simply be applied to an Uzbek subsidiary?

Mostly yes, but it needs local translation. Group roles must be mapped to the actual local structure, local integrations such as online cash registers, payment systems and Telegram bots must be covered, and hosting must be checked against local personal-data requirements. Review the hosting question with local counsel before go-live.

Is cloud hosting riskier than a server in the local office?

Either can be secure or weak. What matters is discipline: who has access, whether patches are installed, whether a backup is kept separately. An office server is often the weaker option because nobody owns it. Where personal data of Uzbek citizens is processed, the storage location also has legal implications, so confirm it with local counsel.

How often should the ERP database be backed up?

It depends on how much data you can afford to lose. If re-entering a day of sales would hurt, back up at least daily, and more often for a busy database. Even more important is testing restores on a regular schedule.

Will audit logging upset local staff?

Not if the rules are announced openly in advance. An audit trail is a history of documents, not personal surveillance: who changed what and when. It also protects honest employees, because in a dispute the record shows exactly who did what.

How well protected is the data in your Uzbek operations?

Let's review roles, access rights, backups and integrations together and calmly assess which gaps are worth closing first.

Discuss data security →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.