There is no single price for ISO/IEC 27001 in Georgia. The total depends on what you put in scope, how much preparation you need and how many audit days the certification body must spend with you.
Companies in Tbilisi and Batumi often ask for "the price of the certificate". In practice you pay for two different things. The first is preparation: gap assessment, risk assessment, policies, implementation of controls, training and an internal audit. You can do this with your own staff, with a consultant such as BALTUM, or with a mix. The second is the certification audit itself, carried out by an accredited certification body that issues the certificate and then audits you every year.
The two budgets behave differently. Preparation cost depends mostly on your starting point. Certification cost depends mostly on the size and complexity of the scope, because audit time is calculated by rules the certification body must follow.
Accredited certification bodies calculate ISMS audit time using the requirements of ISO/IEC 27006-1. The starting figure comes from the number of people working under the control of the organisation within the scope, including contractors who work as part of your team. The auditor then adjusts it up or down for factors such as the complexity of the IT environment, the number of sites, outsourcing, regulatory requirements and how mature your management system already is.
A quote that is much lower than others usually means fewer audit days than the rules allow, or a certificate that is not accredited at all. Both create problems later, when a bank, a foreign client or a regulator looks at the certificate.
An ISO 27001 certificate is valid for three years, subject to annual surveillance. Budget for the whole cycle:
Then add the internal costs that do not appear on any invoice: staff hours for the ISMS, security tools you may need to buy, penetration testing, awareness training and the annual internal audit and management review.
The most common source of waste is a scope that is wider than the business needs. If your foreign clients only care about the platform you develop and host, the scope can be built around that service, the people who run it and the supporting processes. A scope can be extended later.
The second is buying a generic set of templates and then rewriting everything because the documents do not match how the company works. The third is paying for a cheap certificate that the client rejects, and then paying again for an accredited one. Our article on choosing a certification body explains how to check accreditation before you sign.
To give you a meaningful estimate, BALTUM and the certification body will ask for the same basic information:
With this, the audit days can be estimated and the preparation work sized after a short gap assessment. The duration of the project also depends on scope and on your team's availability, so we set it after the first assessment rather than promising a fixed date. More detail on what the standard requires is on our ISO 27001 page.
To request an estimate for your organisation, use the form on this site or write to info@baltum.org with the information listed above.
No. Certification bodies calculate audit time from the number of people in scope and the complexity of the organisation, and preparation effort depends on your starting point. Any fixed price quoted without these details is a guess.
Yes, if the narrower scope still covers what your clients and regulators expect. A scope built around one service or platform is common for software companies and can be extended at a later audit.