This guide is general information, not legal or audit advice. Confirm requirements with your auditor or counsel.
What ISO 27001 certification in India actually means
ISO 27001 certification means an accredited certification body has audited your information security management system (ISMS) against ISO/IEC 27001:2022 and issued a certificate, valid for three years, for a defined scope. The certificate names that scope, for example "development and operation of the Acme SaaS platform from Bengaluru and Pune", and customers will read it.
The standard has two parts that matter for the audit. Clauses 4 to 10 are mandatory requirements for the management system itself: context and scope, leadership, risk assessment and treatment, support, operation, performance evaluation and improvement. Annex A lists 93 reference controls in four themes: organisational (37), people (8), physical (14) and technological (34). You decide which Annex A controls apply, based on your risk assessment, and justify the decision in a Statement of Applicability.
In India, the usual reasons to get certified are enterprise customers asking for it in vendor reviews, global clients of IT services firms writing it into master service agreements, and public-sector or BFSI tenders that list it as an eligibility condition.
The ISO 27001 certification process, step by step
The ISO 27001 certification process has two halves: the work you do to build and run the ISMS, and the external audit. Here is the sequence most Indian SaaS and IT services companies follow, with the record each step should leave behind.
Build the ISMS
- Agree scope and context. List the products, locations, teams and systems in scope, the internal and external issues that affect security, and the interested parties such as customers and regulators. Record: the scope statement and context document, approved by leadership.
- Get leadership commitment on paper. Top management approves the information security policy and objectives, and assigns roles. Record: the signed policy, objectives with measures, and a roles document.
- Define a risk assessment method. How you identify risks, how you score likelihood and impact, and what level of risk you accept. Record: the methodology document.
- Assess and treat risks. Identify risks to your information assets, score them, and decide to treat, accept, avoid or transfer each one. Risk owners approve the treatment plan and the residual risk. Record: the risk register and risk treatment plan with owner sign-off.
- Write the Statement of Applicability. For each of the 93 Annex A controls, say whether it applies, why, and whether it is implemented. Record: the SoA, versioned and approved. Auditors spend a lot of time here.
- Implement controls and policies. Access control, supplier security, logging, backup, secure development, incident management, HR security and the rest. Record: policies with approval dates, and operating evidence such as access reviews, training records and change tickets.
- Run it for a while. Let recurring controls run for at least a couple of months so there is a history to audit. Record: the evidence those controls produce each month.
- Do an internal audit. Someone independent of the work audits the ISMS against the standard and your own policies. This can be an outside internal auditor if you have no one suitable. Record: the audit programme, the report and the corrective actions.
- Hold a management review. Leadership reviews audit results, risks, objectives, incidents and improvement opportunities, and makes decisions. Record: minutes with the inputs the standard lists and the decisions taken.
The certification audit
- Stage 1 audit. The auditor reviews your documentation and readiness: scope, risk method, SoA, policies, internal audit and management review. Often a day or two, sometimes remote. Output: a report listing concerns you must fix before Stage 2.
- Stage 2 audit. Usually a few weeks after Stage 1. The auditor tests whether the ISMS actually operates: interviews staff, samples evidence and checks controls on site or remotely. Output: findings graded as major or minor nonconformities, plus observations.
- Close nonconformities. Submit root cause and corrective action for each finding within the deadline the certification body sets. A major nonconformity has to be closed, usually with evidence that the fix works, before a certificate can be issued.
- Certification decision. A reviewer at the certification body who was not on the audit team makes the decision and the certificate is issued for three years.
See your ISMS in one place
BeAuditReady keeps your scope, risk register, Statement of Applicability, Annex A evidence and internal audit findings together, with owners and review dates, so you answer Stage 1 and Stage 2 requests from one place.
How long ISO 27001 certification takes
For a company of 20 to 200 people with a single cloud and one or two offices, four to nine months from kick-off to certificate is typical. Companies that already run SOC 2 controls often sit at the shorter end. Multiple sites, on-premise infrastructure or a scope that covers several business units push it longer.
| Phase | Typical duration |
|---|---|
| Scope, context, risk method | 2 to 4 weeks |
| Risk assessment, SoA, treatment plan | 3 to 6 weeks |
| Implementing controls and policies | 6 to 16 weeks, often overlapping the step above |
| Operating period, internal audit, management review | 6 to 12 weeks |
| Stage 1 to Stage 2 gap | 2 to 6 weeks |
| Closing findings and certification decision | 2 to 6 weeks |
ISO 27001 certification cost in India
The ISO 27001 certification cost in India has two parts: what the certification body charges for audits, and what you spend to get ready. Certification bodies price by audit days, and audit days depend mainly on the number of people in scope, the number of sites and the complexity of your environment, following the audit-time rules in ISO/IEC 27006.
The figures below are typical ranges for a company of roughly 20 to 200 people, drawn from publicly discussed Indian market rates. They vary with scope, headcount, location and the certification body. Treat them as a starting point for budgeting, then get written quotes.
| Cost item | Typical range (varies) | Notes |
|---|---|---|
| Certification body: Stage 1 and Stage 2 | ₹1.5 lakh to ₹5 lakh | Higher for more staff, sites or complex scope |
| Surveillance audit, years 2 and 3 | ₹60,000 to ₹2 lakh each | Roughly a third of initial audit days |
| Recertification audit, year 3 | About two-thirds of the initial audit fee | Due before the certificate expires |
| Consultant (optional) | ₹1.5 lakh to ₹8 lakh | Gap assessment only at the low end; full implementation at the high end |
| Penetration test and vulnerability scans | ₹1 lakh to ₹5 lakh | Depends on number of applications and environments |
| Internal audit, if outsourced | ₹50,000 to ₹2 lakh | Must be independent of the people who built the ISMS |
| Typical first-year total | ₹4 lakh to ₹15 lakh | Excludes internal staff time and any new security tools |
Two costs rarely appear in quotes. The first is internal time: someone has to own the ISMS, and engineers will spend weeks closing gaps. The second is auditor travel for on-site days outside the certification body's base city. Ask for both to be stated up front. Quotes that look very cheap often come from bodies that are not accredited, which brings us to the most important decision in the process.
How to choose an accredited certification body
Choose a certification body that is accredited for ISO/IEC 27001 by a recognised accreditation body. In India that is usually the National Accreditation Board for Certification Bodies (NABCB), which is part of the Quality Council of India. NABCB is a signatory to the international multilateral recognition arrangement for management system certification, historically the IAF MLA. IAF and ILAC merged into the Global Accreditation Cooperation from 1 January 2026, and existing accreditations under the IAF MLA continue to be recognised, so you may see either name. Accreditation by other signatories, such as UKAS or ANAB, is equally acceptable to most customers.
Before you sign an engagement letter, check:
- Accreditation scope. The body must be accredited specifically for ISO/IEC 27001, not only for ISO 9001 or other standards. Look it up in the accreditation body's directory.
- Certificate verifiability. Ask whether certificates are listed in IAF CertSearch or the accreditation body's public register, so your customers can confirm yours.
- Accreditation mark. The certificate should carry the accreditation body's mark. A certificate without one is a warning sign, however professional it looks.
- Independence. The body must not also sell you implementation consulting. Firms that offer to "do the documents and the certificate" together are a red flag.
- Auditor experience. Ask for the lead auditor's background with cloud-hosted SaaS or IT services companies like yours. An auditor used to factories will ask the wrong questions.
- Customer acceptance. If a key customer has a list of acceptable bodies, or wants a specific one, find out before you choose.
Surveillance audits and recertification
An ISO 27001 certificate runs on a three-year cycle. The certification body carries out a surveillance audit at least once a year in years two and three, with the first one due within 12 months of the certification decision. Surveillance audits are shorter than the initial audit and sample part of the ISMS each time, but they always look at internal audit, management review, corrective actions and changes since the last visit.
Before the three years end, a recertification audit reviews the whole ISMS again. Plan it early, because a lapsed certificate usually means starting over with a fresh Stage 1 and Stage 2.
To make surveillance uneventful, keep a yearly calendar: risk assessment review, SoA review, internal audit, management review, policy reviews and acknowledgements, quarterly access reviews, an annual penetration test, supplier reviews and continuity tests. Teams that treat the ISMS as a once-a-year project tend to find their nonconformities at surveillance, not at Stage 2.
Common nonconformities in ISO 27001 audits
- A Statement of Applicability that excludes controls without a real justification, or marks controls implemented with no evidence behind them.
- A risk register that has not been reviewed since it was first written, or risk owners who never approved treatment.
- An internal audit performed by the same person who wrote the policies.
- Management review minutes that skip the inputs the standard requires.
- Leavers whose access was removed late, and access reviews with no record of removals.
- Supplier security reviews missing for the cloud provider or key SaaS tools.
- Objectives with no measurement, so nobody can say whether they were met.
For more on how BeAuditReady tracks the ISMS, Annex A evidence and audit findings, see our ISO 27001 page and the security compliance solution.