Skip to content
ISO/IEC 27001:2022

ISO 27001 compliance software for certification in India

ISO 27001 certification means an accredited certification body has audited your information security management system (ISMS) and found it meets the standard. BeAuditReady is where you run that ISMS: the risk register, the Statement of Applicability, the Annex A controls and the evidence your auditor will ask for.

The basics

What ISO 27001 certification in India involves

ISO/IEC 27001 is an international standard for running an ISMS. It does not hand you a fixed list of technical settings. It asks you to understand your context, assess your information security risks, choose controls to treat them, and then keep checking and improving the whole thing.

For Indian IT services and SaaS companies, the request usually comes from a customer in Europe, the Middle East or an Indian enterprise, or from a tender that lists ISO 27001 as an eligibility condition. Unlike a SOC 2 report, the result is a certificate with a defined scope, issued by a certification body and valid for three years if you keep passing surveillance audits.

The most common reason first audits go badly is not missing controls. It is an ISMS that exists only as documents: a risk register filled in once, a Statement of Applicability nobody can explain, an internal audit done the week before Stage 2.

Clauses 4 to 10

The ISMS requirements you will be audited on

The mandatory part of ISO 27001 sits in clauses 4 to 10. You cannot exclude any of these. Here is what each one means in day-to-day terms.

Clause 4 · Context

Who your interested parties are, what they expect, and the scope of the ISMS: which products, offices, teams and cloud accounts are in.

Clause 5 · Leadership

Top management commitment, an information security policy, and clear roles. The auditor will want to talk to someone senior.

Clause 6 · Planning

Risk assessment and risk treatment, the Statement of Applicability, and measurable security objectives.

Clause 7 · Support

Resources, competence, awareness, communication and documented information under version control.

Clause 8 · Operation

Actually running the risk treatment plan and the controls you said you would, and reassessing risk when things change.

Clauses 9 and 10 · Evaluation and improvement

Monitoring, internal audit, management review, nonconformities and corrective action.

Annex A

ISO 27001:2022 Annex A: 93 controls in four themes

The 2022 revision reorganised the old 114 controls into 93, grouped under four themes. Annex A is a reference list: you consider every control, then decide which apply based on your risks.

37

Organisational controls

Policies, roles, asset inventory, access rights, supplier relationships, cloud services, incident management, legal requirements.

8

People controls

Screening, terms of employment, awareness training, disciplinary process, remote working, responsibilities after leaving.

14

Physical controls

Secure areas, entry controls, clear desk, equipment security, storage media. Often limited for fully cloud-hosted teams.

34

Technological controls

Endpoints, privileged access, authentication, malware, vulnerabilities, logging, backups, secure development, change management.

The Statement of Applicability

The SoA lists every Annex A control, whether it applies, why, and whether it is implemented. Auditors read it closely, because it is the bridge between your risk assessment and the controls they will test. A good SoA lets you answer "why did you exclude A.7.4?" in one sentence.

The risk assessment

You define a method (how you rate likelihood and impact, and what level of risk you accept), apply it to your information assets and processes, and decide how to treat each risk. The auditor checks that you followed your own method and repeat it when things change, such as a new product line or a move to a new cloud region.

The certification cycle

Stage 1, Stage 2 and the three-year cycle

Certification is not a one-time event. Here is how the audits run once your ISMS is in place, with typical timings.

01

Stage 1 audit

A document and readiness review: scope, policy, risk method, SoA, internal audit and management review. The auditor tells you what must be fixed before Stage 2.

02

Stage 2 audit

Usually a few weeks to a couple of months after Stage 1. The auditor tests whether controls operate as described, through interviews, samples and system walkthroughs.

03

Surveillance audits

Typically once a year in years two and three. A shorter audit that checks the ISMS is still running and samples part of Annex A each time.

04

Recertification

Before the three-year certificate expires, a fuller audit renews it for the next cycle.

Who certifies you

Accredited certification bodies in India

Your certificate is only as credible as the body that issued it. Use a certification body accredited for ISO/IEC 27001 by an accreditation body that is a member of the International Accreditation Forum (IAF). In India, the national accreditation body is NABCB, which operates under the Quality Council of India. Many certification bodies working in India hold accreditation from other IAF members instead.

Before you sign, ask for the accreditation certificate, check that ISO/IEC 27001 is within its scope, and confirm the certificate will be verifiable on the accreditation body's register. Enterprise procurement teams increasingly check.

From the 2013 version

The 2022 transition has closed

The transition period from ISO/IEC 27001:2013 to the 2022 edition ended on 31 October 2025. Certificates to the 2013 version are no longer valid, so any certificate a supplier shows you today should reference ISO/IEC 27001:2022.

If you are certifying for the first time, you work only with the 2022 Annex A. If your team still has an old control set mapped to the 114 controls of 2013, BeAuditReady lets you remap your existing controls to the 2022 requirements and see which ones are still uncovered.

Who does what

What ISO 27001 compliance software does for your ISMS

BeAuditReady gives you the registers and the trail. The judgement on risk, scope and conformity stays with your people and your certification body.

ISMS needWhat BeAuditReady handlesWhat stays with you
Annex A and the SoAISO 27001 framework pack (no licensed ISO text), applicable or not applicable per control with rationale, reviewer and date; exclusions need approvalDeciding applicability based on your risks and context
Risk assessmentRisk register with 5 by 5 likelihood and impact, treatment, linked controls, residual risk and risk acceptance with expiryDefining your method and acceptance criteria, and owning each risk
Policies and awarenessTemplates, versions, approvals and acknowledgement campaigns with remindersMaking the policies fit how you work
Operating the controlsRecurring tasks with owners and due dates; daily read-only checks on AWS, Google Cloud, Azure, Kubernetes, GitHub, Google Workspace and Microsoft Entra IDDoing the work and fixing what the checks find
SuppliersVendor register, risk tiers, contract notice dates, scheduled reviews and versioned questionnairesChoosing suppliers and accepting their risk
Internal audit and findingsFindings workflow from triage to verified closure, with evidence and a reviewer required to closeRunning an independent internal audit and management review
Certification auditsAudit workspace with scoped, time-bound auditor access, evidence requests, comments and a hashed exportThe certification body decides on conformity and issues the certificate

Every control mapped to ISO 27001 can also map to SOC 2, DPDP and selected RBI obligations, so work done for one framework is counted once across all of them. Read more on our security compliance page.

FAQ

ISO 27001 certification questions

Straight answers. If yours is not here, ask us on a demo call.

How long does ISO 27001 certification take in India?
For a 30 to 300 person IT services or SaaS company, a typical range is four to nine months from kick-off to certificate. Setting up the ISMS, doing the risk assessment and getting controls running takes most of that. The Stage 1 and Stage 2 audits themselves take days, and the certification body usually issues the certificate a few weeks after Stage 2, once any major nonconformities are closed. Our ISO 27001 certification guide for India walks through each phase.
Do we need to implement all 93 Annex A controls?
No. You must consider all 93 and record a decision for each in your Statement of Applicability. A control can be excluded when your risk assessment and context show it is not needed, for example physical controls for a data centre you do not run because everything is on a public cloud. Each exclusion needs a written justification that holds up in front of the auditor. In BeAuditReady, exclusions carry a rationale, a reviewer and a date, and need approval.
How do we choose a certification body in India?
Pick a certification body accredited for ISO 27001 by an accreditation body that is a signatory to the IAF multilateral recognition arrangement. In India that is NABCB, under the Quality Council of India; many bodies operating in India are instead accredited by overseas IAF members such as UKAS or ANAB. Check the accreditation certificate and its scope yourself. A certificate from an unaccredited body is often rejected by enterprise customers.
Is our ISO 27001:2013 certificate still valid?
No. The transition period for moving to ISO/IEC 27001:2022 ended on 31 October 2025, and certificates to the 2013 edition are no longer valid after that date. If your organisation missed the transition, you will need to go through certification against the 2022 version. Talk to your certification body about the route they offer.
What happens after we get certified?
The certificate runs on a three-year cycle. The certification body comes back for surveillance audits, usually once a year in years two and three, and then a recertification audit before the certificate expires. Between audits you are expected to run the ISMS: internal audits, management reviews, risk reviews, corrective actions and the recurring controls in your Statement of Applicability.
Does ISO 27001 compliance software certify us?
No. Only an accredited certification body can audit and certify your ISMS. BeAuditReady does not certify anyone or make you compliant. It gives you the register, workflow and evidence trail that an ISMS needs, so that you can show the auditor what you decided, who approved it and what proves it.
We already have SOC 2. How much of that carries over?
A lot of the operational controls carry over, such as access reviews, change management, logging and supplier reviews. In BeAuditReady those controls map to both frameworks, so the same evidence counts for each. The extra ISO 27001 work is mostly the management system: context, risk methodology, Statement of Applicability, internal audit and management review. See our SOC 2 page.
Book a demo

See what your ISMS would look like in BeAuditReady

Bring your scope and your target audit date. We will walk through the risk register, the Statement of Applicability and the evidence your Stage 2 auditor is likely to ask for.

No sales script. Bring your auditor's questions if you have them.