Uzbekistan's IT exports have grown several times over in the last few years, and the companies behind that growth are running into the same question at the same time: a foreign client asks for an ISO certificate, a tender requires one, or an investor wants to see how security is managed before signing. This article explains which standards matter, how certification works in Uzbekistan and what to watch for when choosing a route.
Which standards clients actually ask for
ISO/IEC 27001 is the most requested standard among software companies, outsourcing providers and data centres. It covers information security management: who is responsible for what, how risks are assessed, how access is controlled and how incidents are handled. Clients in Europe and the United States treat it as the baseline before sharing data or systems with a vendor.
ISO/IEC 42001, published in 2023, covers the management of artificial intelligence systems. Companies that develop or deploy AI for European customers are starting to see it in contract requirements, partly because of the EU AI Act.
ISO 9001 remains common in manufacturing and construction tenders, but for IT exporters it rarely replaces ISO/IEC 27001.
Companies working with US clients are also asked for a SOC 2 report. That is not an ISO certificate but an audit report issued by a licensed US CPA firm, and it is often requested alongside ISO/IEC 27001.
Why the demand is rising in Uzbekistan
IT Park residents sell services abroad and face vendor security questionnaires from every new client. A certificate answers most of the questions in one document.
The Law on Personal Data requires operators to protect the data they process, and a certified management system is a practical way to show how that is done.
Exporters of goods and services into the EU and the Gulf meet certification requirements in procurement rules and supply chain audits.
National or international certificate
This is where many companies lose time. A certificate issued under the national accreditation system is recognised within Uzbekistan and is often sufficient for domestic tenders. An international certificate is issued by a certification body whose accreditation is recognised through the IAF multilateral arrangement, and it can be checked by any client worldwide in the IAF CertSearch database.
If your clients are abroad, ask them which they expect before you start. Both can be obtained on the basis of the same management system, but the audit is done by different bodies. A detailed comparison for the region, including how the process works in each country, is on the page about ISO certification in Uzbekistan.
How certification works
Preparation starts with defining the scope: which processes, teams and systems the certificate will cover. For a software company of fifty people this is usually the whole organisation. For a larger group it is often one business line.
A gap assessment then compares current practice with the standard. Most companies that have been operating for a few years already meet a good share of the requirements without having written them down.
Implementation follows: policies, risk assessment, access control, incident procedures, staff training. Before the certification audit the company runs an internal audit and a management review, because auditors expect to see that the system has been working, not just written.
The certification audit itself has two stages. Stage one checks documentation and readiness. Stage two checks that the system works in practice. For most IT and service companies the audit is conducted remotely, with interviews over video and evidence shared through a secure repository.
How long it takes and what it costs
For a company of up to one hundred employees with one location, preparation typically takes three to six months. The certificate is valid for three years, with a surveillance audit each year and recertification in the fourth year.
Audit cost is calculated from auditor days, which depend on the number of employees in scope, the number of sites and the complexity of the activity. Preparation cost depends on how much is already in place. Asking for a breakdown of both before signing helps avoid surprises.
Common mistakes
Choosing the certification body by price alone. If the body's accreditation is not recognised by your client, the certificate will not be accepted and the money is lost.
Writing documents nobody uses. Auditors notice quickly, and the company gets no benefit.
Making the scope too wide for the first cycle. Starting with the core service and extending the scope later is usually faster and cheaper.
Skipping staff training. Most security incidents start with an email that someone opened. Technical controls work at half strength without it.
Where to start
If you have a client request or a tender deadline, begin with a gap assessment. It shows the real amount of work before you commit a budget, and it tells you whether ISO/IEC 27001 alone will solve the problem or whether a SOC 2 report or ISO/IEC 42001 will be needed as well. Questions can be sent to This email address is being protected from spambots. You need JavaScript enabled to view it..