If our experts find your requirement can't be fulfilled as scoped, you get a full refund of the professional fee — no questions, no fine print. Government charges already paid are pass-through and go to the government, not us.
Written breakup before you pay
Every quote shows the professional fee, government charges and taxes as separate lines — you approve the full breakup in writing before paying anything.
Government charges are pass-through
Filing fees and department charges go to the government, not to us. They vary by state and case, so we show them separately for your situation.
No payment without your sign-off
The free consultation comes first. You only pay after you have seen the exact scope, the exact breakup and the expected timeline — no surprises later.
1
Free consultation. Tell us what you need; a CA, CS or advocate maps the exact scope.
2
Written quote. You receive the plan, the line-by-line breakup and the timeline in writing.
3
You approve, then pay. Work starts only after you sign off on the quote.
Clear scope
You know exactly which filings, documents and handover items belong to your selected plan.
Extra costs shown separately
State-specific and case-specific government charges are shown separately.
No blind upgrade
Choose the tier around the way you plan to operate, not simply the highest price.
After you pay
What happens after you pay
Five steps, no guesswork — you always know exactly what comes next. Tap a step to see what it involves.
12345
You pay securely. Payment is confirmed instantly, and your receipt with the written fee breakup lands in your inbox.
Is ISO 27001 right for your business?
Certification pays for itself when the certificate opens doors — deals, tenders, partnerships — that stay closed without it. It is an expensive hobby otherwise.
A strong fit if:
You sell to enterprises or bid on RFPs. Vendor security questionnaires and "ISO 27001 certified" as an eligibility criterion are now routine in IT services, SaaS, fintech, and BPO. If you have lost deals at the compliance stage, this is the fix.
You handle customer data at scale — personal data, financial records, health information, credentials. India's DPDP Act 2023 obliges data fiduciaries to implement "reasonable security safeguards," and ISO 27001 is the most recognised way to demonstrate them.
You are a vendor to banks, NBFCs, or insurers. RBI's outsourcing guidelines push regulated entities to check vendor security practices, and an ISO 27001 certificate answers most of that due diligence in one document.
You process card data or operate in regulated supply chains. ISO 27001 does not replace PCI DSS where that applies, but the two overlap heavily and auditors like seeing the ISMS underneath.
You already hold ISO 9001. The shared harmonised structure means overlapping documentation and integrated audits.
Think twice if:
Nobody is asking for it and you handle little sensitive data. A 10-person agency with no customer data holdings will spend more on certification than the risk justifies — basic cyber hygiene (backups, MFA, patching) gives better returns.
Leadership sees it as a marketing checkbox. Clause 5.1 puts ISMS accountability on top management, and the risk assessment at the heart of the standard cannot be delegated to a consultant alone. A disengaged leadership team produces a system that fails at Stage 2.
You want it in six weeks. Possible for a tiny, well-prepared scope — but a credible ISMS needs a genuine risk assessment cycle, and rushing that cycle is the fastest route to major nonconformities.
What the standard actually requires
ISO 27001 has two halves that people constantly confuse. Clauses 4–10 are the management system — the mandatory requirements the auditor weighs most heavily. Annex A is the catalogue of 93 reference controls you select from to treat your risks. You need both, and the clauses come first.
Clause 4 — Context of the organisation. You define the ISMS scope (clause 4.3): which parts of the business, which locations, which systems and data are in. The scope appears on the certificate and is the single most consequential commercial decision in the project — too narrow and buyers reject it, too wide and the audit becomes unmanageable. Since Amendment 1:2024, you must also determine whether climate change is a relevant issue for the ISMS.
Clause 5 — Leadership. Top management must demonstrate leadership and commitment: establishing the information security policy, assigning roles, and ensuring the ISMS achieves its intended outcomes. Accountability cannot be delegated away.
Clause 6 — Planning. The engine room. Clause 6.1.2 requires a defined risk assessment process — identify risks to confidentiality, integrity, and availability of information, assess them against criteria you define. Clause 6.1.3 requires risk treatment: select controls (comparing against Annex A), produce the Statement of Applicability, and formulate a risk treatment plan. Information security objectives (6.2) and planning for changes (6.3) complete the clause.
Clause 7 — Support. Resources, competence, awareness, communication, and documented information. Everyone in scope must know the security policy and their contribution to it — auditors test awareness directly, and "I didn't know" is a finding.
Clause 8 — Operation. Operate the risk assessment and treatment processes, manage changes, and assess risks when significant changes occur. This is where the ISMS meets daily reality.
Clause 9 — Performance evaluation. Monitor and measure ISMS performance, run internal audits, and hold management reviews. As with all ISO management standards, at least one internal audit cycle and one management review must be evidenced before the certification audit.
Clause 10 — Improvement. Nonconformity and corrective action, and continual improvement of the ISMS's suitability, adequacy, and effectiveness.
Annex A — the 93 controls in four themes. The 2022 edition reorganised the old 114 controls (14 domains) into four themes: A.5 Organisational (37 controls — policies, supplier relationships, incident management, threat intelligence, cloud security), A.6 People (8 — screening, training, disciplinary processes, remote working), A.7 Physical (14 — secure areas, equipment, media handling, physical monitoring), A.8 Technological (34 — access control, cryptography, logging, secure development, vulnerability management). Eleven controls are entirely new, reflecting modern practice: threat intelligence, cloud services security, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering, and secure coding.
The Statement of Applicability. For each of the 93 controls: included or excluded, why, and implementation status. This document is the first thing the certification auditor reads, because it shows whether your control choices trace back to your risks or were copied from a template.
Why is ISO 27001 certification important?
Your customers may trust your product and still refuse to appoint you because their security team cannot clear your company. That is now a common point at which software, IT and outsourcing deals stop. ISO 27001 is important because it provides independently audited evidence that information risks have been identified, responsibilities are clear and security controls are actually operating.
It also helps management see what needs attention before a breach forces the lesson under pressure: who can access what, which suppliers touch sensitive data, how incidents will be handled and where the weak points are. Certification cannot promise that no breach will happen, and it does not replace duties under the DPDP Act or a customer contract. It turns security from scattered IT tasks into a discipline the whole business can prove.
Advantages of ISO 27001 certification
Deals stop dying at the questionnaire stage
Enterprise security reviews that took six weeks of back-and-forth collapse to a certificate plus SoA. Procurement teams know what ISO 27001 means; it is the one credential that needs no explanation.
A defensible position under the DPDP Act
India's data protection law requires reasonable security safeguards and breach notification. An operating ISMS with incident management (A.5.24–A.5.28), logging (A.8.15), and tested response procedures is the most credible evidence of "reasonable" available to an Indian company today.
Fewer and smaller incidents
Organisations that run the risk process honestly find their real exposures — the shared admin credentials, the unpatched VPN, the ex-employee with active access — before an attacker does. Access control (A.5.15–A.5.18), vulnerability management (A.8.8), and monitoring (A.8.16) are not paperwork; they are how breaches get prevented.
Vendor and partner trust
Banks, insurers, and global clients increasingly require it contractually. The certificate, with its defined scope, tells a counterparty exactly what security management covers — no vague assurances needed.
Operational discipline that survives attrition
When access provisioning, change management, and backup restoration are documented processes rather than one engineer's habits, people leaving does not take your security with them.
Competitive separation in RFPs
In Indian IT services and SaaS tenders, ISO 27001 is frequently a scoring criterion or an eligibility filter. Certified bidders clear the compliance stage while others scramble for exemptions.
A foundation for SOC 2, PCI DSS, and privacy work
The ISMS maps well onto SOC 2's trust criteria and supports PCI DSS and privacy compliance efforts. Companies that certify first find subsequent audits dramatically cheaper — the evidence machinery already exists.
Continuous improvement instead of audit panic
Internal audits, management reviews, and corrective action turn security from an annual fire drill into a routine. Surveillance audits become non-events rather than ordeals.
Documents and records you will need
ISO 27001 names a short list of mandatory documented information, and then expects evidence that everything else operates. Auditors read the SoA first and the risk assessment second — those two documents carry the audit.
Mandatory documented information (the standard requires these to exist):
Scope of the ISMS (clause 4.3)
Information security policy and topic-specific policies (5.1, 5.10 and others)
Risk assessment and risk treatment process (6.1.2, 6.1.3)
Statement of Applicability (6.1.3 d)
Risk treatment plan (6.1.3 e)
Information security objectives and plans (6.2)
Evidence of competence (7.2)
Evidence of monitoring and measurement (9.1)
Internal audit programme and reports (9.2)
Management review results (9.3)
Nonconformities, corrective actions, and improvement evidence (10.1, 10.2)
Records auditors will ask to see:
Asset inventory and risk register with assessment criteria
Access review records and joiner/mover/leaver logs
Incident tickets and post-incident reviews
Backup and restoration test results
Vulnerability scan and remediation records
Supplier security assessments and agreements
Training and awareness records (including phishing simulations, if used)
Business continuity and DR test evidence
Change management records
Physical access logs for secure areas
What you do not need: a 300-page "ISMS manual" restating the standard. What matters is that required information exists, is controlled, and matches practice. Implementation guidance lives in ISO/IEC 27002:2022 — useful for your IT team, but it is not certifiable and does not replace the risk assessment.
The certification process — step by step
Step 1 — Gap assessment
We assess your current security posture against ISO/IEC 27001:2022 — clauses and Annex A — and deliver a findings report with a risk-based remediation plan. One to two weeks. This sets scope, timeline, and cost honestly; skipping it is how projects discover at Stage 1 that they needed three more months.
Step 2 — Scope definition
The commercial heart of the project. We help you draw ISMS boundaries that satisfy your buyers without swallowing the whole company: which legal entities, sites, systems, and data flows are in. The scope statement goes on the certificate, so we draft it to survive procurement scrutiny.
Step 3 — Risk assessment
The core intellectual work of the standard. We establish assessment criteria with your leadership, inventory information assets, identify threats and vulnerabilities, and assess risks to confidentiality, integrity, and availability. This cannot be templated — auditors probe the reasoning, and a copy-paste risk register is a fast track to major nonconformities.
Step 4 — Risk treatment and the SoA
For each risk, we select treatment options and Annex A controls, document the Statement of Applicability with justifications, and build the risk treatment plan. Controls are chosen for your risks — including the relevant 2022 additions like threat intelligence, cloud security, and data leakage prevention where they genuinely apply.
Step 5 — Implementation
Policies go live, access reviews start, logging is configured, the incident process is tested, suppliers are assessed. The ISMS must operate long enough to generate records — typically two to three months before Stage 2.
Step 6 — Internal audit and management review
A full internal audit against the standard, nonconformities raised and closed, then a formal management review by top management. Both are mandatory before the certification body will proceed.
Step 7 — Stage 1 audit
The certification body's auditor reviews documented information — especially the SoA and risk assessment — verifies the scope, and judges readiness for Stage 2. Expect sharp questions on the SoA: every exclusion needs its justification ready.
Step 8 — Stage 2 audit
The implementation audit: sampling across in-scope processes and sites, interviews, evidence review against every applicable clause and the SoA's claimed controls. Minor nonconformities need corrective-action plans; majors must be corrected and verified before certification.
Step 9 — Certification decision and issue
Independent technical review by the certification body, then the certificate — three-year validity, stated scope, accreditation mark. Surveillance audits follow at roughly 12-month intervals.
How long does it take?
Phase
Typical duration
Depends on
Gap assessment
1–2 weeks
Scope clarity, existing documentation
Risk assessment
2–4 weeks
Asset complexity, leadership availability
SoA and treatment plan
1–2 weeks
Number of applicable controls
Implementation
8–16 weeks
Starting maturity, team bandwidth
Operating history
8–12 weeks
Need 2–3 months of records
Internal audit + management review
1–2 weeks
Auditor availability
Stage 1 audit
1–2 days
Certification body scheduling
Stage 1 → Stage 2 gap
2–6 weeks
Findings to address
Stage 2 audit
2–6 days
Headcount, sites, scope complexity
Certification decision
2–4 weeks
Closure of any majors
A focused 50-person SaaS company typically certifies in 4 to 8 months. Larger, multi-site, or low-maturity starting points run 8 to 14 months. Timelines compress when leadership is engaged and the risk assessment is done seriously the first time.
How ComplyKart helps in this entire process
Gap assessment before quoting. We assess against the 2022 edition — including the 11 new controls and the 2024 climate amendment — before fixing scope and fee. No template quotes.
Risk assessment done for real. This is where certifications are won or lost. Our consultants facilitate the assessment with your leadership rather than handing you a filled spreadsheet — because the auditor will ask *you* to explain it.
SoA that survives scrutiny. We draft justifications tied to your risks, not generic text. Exclusions are reasoned, inclusions are evidenced.
Implementation support, not paper. Policies, access-review rhythms, incident playbooks, supplier assessments — built to operate, with your team trained to run them after we leave.
Internal audit and management review. We conduct or support the mandatory pre-certification cycle so Stage 1 finds a tested system.
Certification body selection. We work with NABCB-accredited bodies, advise on scope wording and audit man-days, and coordinate scheduling.
What we do not do: we do not guarantee certification, fabricate records, write your risk assessment for you to sign blindly, or recommend non-accredited certificates. We also do not confuse ISO 27001 with a CERT-In audit — if your RFP needs both, we will tell you plainly and scope both.
What happens after the certificate arrives
In the first 30 days: update every security questionnaire, RFP response template, and your website with the certificate and scope. Notify the customers whose procurement teams asked. Brief leadership that surveillance is annual — the ISMS keeps running.
In the first 6 months: the risk treatment plan's longer-horizon actions should be progressing, access reviews should be routine, and the first internal audit of the certified cycle should be scheduled. The incident process should have been exercised at least once — tabletop if not for real.
The recurring compliance you are signing up for
Every year, without fail:
Surveillance audit by the certification body (roughly months 12 and 24). Samples the ISMS and the SoA's claimed controls; majors can suspend the certificate.
Internal audit covering the full ISMS.
Management review by top management.
Risk assessment review — risks change as systems, suppliers, and threats change; the register must stay alive.
Also on the calendar:
Recertification audit before the three-year expiry — full-depth, renewing the certificate for another cycle.
Change-triggered risk assessments: new products, new infrastructure, new suppliers, acquisitions, major incidents — each should trigger the clause 8.1/6.1 process.
Standard updates: the 2022 edition is current; Amendment 1:2024's climate wording is already in force. Watch for future amendments through your certification body.
Common mistakes that delay or derail certification
The SoA is a copy-paste. Justifications that do not reference your risks. Auditors read the SoA first; a templated one colours the entire audit.
All 93 controls "implemented." Claiming controls you do not operate is worse than excluding them with reasons. Auditors sample claimed controls — a claimed control with no evidence is a nonconformity.
The risk assessment was outsourced and signed. Leadership cannot explain the methodology or the top risks. Clause 6.1 is the heart of the standard; a borrowed heart does not beat.
Scope games. A scope so narrow it excludes the systems buyers care about ("certified, but not the production environment"). Procurement teams read scopes.
No operating history. Stage 2 with three weeks of logs. Two to three months of records is the practical minimum.
Penetration testing ignored. The standard does not name pen-testing as mandatory, but controls 8.8 (vulnerability management) and 8.29 (security testing) expect weaknesses to be found and fixed — most auditors expect a test report as evidence.
Confusing ISO 27001 with CERT-In empanelment. An RFP asking for a "CERT-In audit" wants your application tested by an empanelled auditor — a different exercise from ISMS certification. Answering with only an ISO certificate can lose the bid.
ISO 27001 vs the alternatives
ISO 27001
SOC 2 Type II
CERT-In audit
ISO 27001:2013 (superseded)
Assures
ISMS meets international standard
Controls operated effectively over months
Technical security at a point in time
Older control set
Valid
3-year certificate + surveillance
Annual report
Per-engagement
Expired after 31 Oct 2025
Best for
Global buyers, RFPs, DPDP posture
US SaaS buyers, investors
Indian govt/RFP "audit" asks
Nothing — transition
Note
Clauses 4–10 weighed most heavily
Design + sustained operation
Does not certify your ISMS
Do not pursue
Sources
ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection — Information security management systems — Requirements (ISO/IEC JTC 1). Checked via ISO catalogue, October 2026.
ISO/IEC 27002:2022, Information security, cybersecurity and privacy protection — Information security controls (guidance companion). Checked October 2026.
IAF transition timeline: ISO 27001:2013 to 2022 transition end 31 October 2025. Confirmed via industry sources (erp-information.com), October 2026.
Annex A structure: 93 controls in four themes (A.5: 37, A.6: 8, A.7: 14, A.8: 34); 11 new controls enumerated. Confirmed via PECB and multiple implementation guides, October 2026.
CERT-In empanelment vs ISO 27001 distinction. Accucia Softwares article, checked October 2026.
NABCB (Quality Council of India) accreditation for certification bodies. Checked October 2026.
Digital Personal Data Protection Act, 2023 (India) — "reasonable security safeguards" obligation. Checked October 2026.
FAQ
Frequently asked questions
11 answers from our consultants.
You pay for our expert's time — document checking, filing, follow-ups — not the government. The government fee goes to the government; our fee is for the work we do so you don't have to figure it out yourself.
It is the international standard for information security management systems. It covers how a company protects data across people, processes, and technology.
Yes. Many large companies make ISO 27001 a condition in vendor contracts, especially for software and data services.
No. Accredited certification bodies issue certificates after an audit. We prepare you with gap analysis, documentation, training, and internal audit, and we coordinate the certification audit with the body.
Most tech companies take 6 to 10 weeks to get audit-ready, depending on team size and existing security practices.
Three years, with a surveillance audit every year. A recertification audit follows at the end of the cycle.
Tell us your situation in plain words — what you're trying to do, not which form you think you need. Half our job is stopping clients from buying the wrong service. The first consultation is free and honest.
Yes. We quote professional fee + government charges + taxes separately, in writing, before you pay. The number doesn't change midway. If the government fee changes, we show you the notification.
Every engagement gets a tracker — you see what's filed, what's pending and what's next. No chasing on WhatsApp for status updates.
Both. Startups get incorporation + early compliance bundles; established companies get annual retainers. About half our clients started with us at incorporation.
Yes — MCA, GST and income tax are central systems, so location doesn't matter for most filings. We're Delhi-based but serve clients across India. State-specific licences (Shops & Establishment, Professional Tax) we handle through our network.
What clients say about working with us
Real stories from businesses we've worked with.
Trademark Registration“
Our Trademark was applied in all the classes with a short span of time by Complykart Trademark Experts and I can say the level of expertise and commitment they carry is remarkable. It's an A+ from my side. We are now sticking to ComplyKart only.
Company Registration“
I found the professionalism of the staff at complykart.com, a pleasure to work with. As a foreigner to India, they took the time to explain the documentation and assisted in every question I raised. I was pleased that complykart.com made it easy for my Business.
Merger & Acquisition“
Trust, Commitment, Dedication and responsiveness are the best things with ComplyKart. Thanks for handling our Merger assignment with so much care. After my business disputes, complykart handles all things with own sense of understanding.
Company Law Specialist · Company Law & ROC Compliance · 10+ years experience
Naman Agarwal specialises in company law and ROC compliance. He manages incorporations, annual filings (AOC-4, MGT-7, ADT-1), board processes and statutory registers for private limited companies, LLPs and Section 8 companies.
Last reviewed: 16 November 2026
Get a free consultation
Talk to a ComplyKart professional about ISO 27001 Certification. The first consultation is free.