CERT-In issues AI Security Auditing Guidelines v1.0 with four risk tiers and independent audit for high-risk AI
TaxByKK · Compliance News · taxbykk.com4 Nov 2026
In short
CERT-In has released version 1.0 of its AI Security Auditing Guidelines, a 107-page framework for auditing the security, governance and accountability of AI systems. AI systems are sorted into four risk tiers; the higher the tier, the deeper and more independent the audit, with the top two tiers needing audit by a CERT-In empanelled auditing organisation. The document is dated 4 November 2026.
- Authority
- Indian Computer Emergency Response Team (CERT-In), Sub-group 03 of its Working Group on Indian Standards for Cybersecurity Auditing
- Document
- AI Security Auditing Guidelines v1.0, dated 4 November 2026
- Type
- Guidelines (audit framework)
- Risk tiers
- Tier 1 Low, Tier 2 Moderate, Tier 3 High, Tier 4 Critical (composite score 8 to 32)
- Audit domains
- Nine, from AI governance to third-party and supply-chain assurance
- Maturity model
- Five levels
- Aligned with
- MeitY India AI Governance Guidelines, ISO/IEC 42001, 23894 and 27001, NIST AI RMF, MITRE ATLAS, OWASP guidance
What changed
| Item | Before | Now |
|---|---|---|
| Tier 1 (Low) AI system | — | Self-assessment or basic internal review with documented evidence |
| Tier 3 (High) AI system | — | Independent audit by a CERT-In empanelled auditing organisation at least annually |
| Tier 4 (Critical) AI system | — | Independent audit by an empanelled auditor, with continuous monitoring |
| Unsatisfactory opinion or two or more Critical findings | — | Mandatory re-audit within 3 months, or sooner if the regulator directs |
| Risk-tier reassessment | — | At least once a year |
The framework covers AI developed, bought or used through APIs, and also generative, agentic and multi-agent AI. Research AI that is not deployed to the public is outside the mandatory scope. The document marks some requirements as mandatory for a tier and others as recommended; a referenced standard becomes mandatory only if the Guidelines or another applicable external requirement make it so. The text read does not name a commencement date, a transition period or the statutory provision under which it is issued, and it does not say which regulators will make it binding on their regulated entities.
Who it applies to
- Organisations that build, buy or run AI systems: government bodies, public sector entities, critical infrastructure operators, regulated entities and private companies
- CERT-In empanelled cybersecurity auditing organisations
- Internal and external auditors, chartered accountants in assurance and risk roles, and compliance and risk officers
- AI vendors, SaaS and cloud providers and data labelling or outsourced AI development firms in the supply chain
What to do
- List the AI systems in use and score each on the risk factors to arrive at a tier; repeat at least annually.
- For Tier 3 and Tier 4 systems, plan independent audit by a CERT-In empanelled auditor.
- Prepare evidence across the nine domains: governance, data and privacy, model risk, bias, explainability, security, monitoring, human oversight and third-party assurance.
- Check whether a sector regulator or contract already makes the framework binding for you before treating it as mandatory.
Reference
CERT-In, AI Security Auditing Guidelines v1.0, 4 November 2026.
Read the official PDF: CERT-In guidelinesWritten by TaxByKK from the official notification. Check the official text before you act on it.
Frequently asked questions
What are the CERT-In AI Security Auditing Guidelines?
A risk-based framework, version 1.0 dated 4 November 2026, for auditing the security, governance and accountability of AI systems across their life cycle.
Which AI systems need an audit by a CERT-In empanelled auditor?
Systems in Tier 3 (High) and Tier 4 (Critical). Tier 1 needs only a self-assessment or basic internal review.
How many audit domains are there?
Nine, including AI governance, data lifecycle and privacy, model risk, ethics and bias, explainability, security and incident reporting, continuous monitoring, human oversight and third-party assurance.
Is there a deadline to comply?
The document does not state a commencement or compliance date.