CERT-In expects regular audits
CERT-In's cyber security audit guidelines (2025) set out how audits should be scoped, performed and reported, and expect organisations to audit at least once a year and after major changes.
An independent look at whether your controls work — with the evidence to prove it.
XcellHost auditors test your policies, access, logging, backups, cloud and vendors against ISO/IEC 27001:2022 and CERT-In guidelines, map every finding to DPDP Act and RBI / SEBI expectations, and stay with you through the fix and the retest.
Most organisations have an information security policy, a firewall, backups and some form of access review. Far fewer can show — with dated evidence — that each of those controls actually works today, across every site, cloud account and vendor that touches their data.
XcellHost Cyber Security Audit is an independent evaluation of your security controls and practices. We plan the scope with you, review documents, interview owners, test a sample of each control, and record exactly what we saw. You get findings ranked by severity, a corrective and preventive action (CAPA) plan with owners and dates, and a retest that closes the loop.
Four pressures are making a periodic, evidence-based cyber security audit a normal part of running a business in India.
CERT-In's cyber security audit guidelines (2025) set out how audits should be scoped, performed and reported, and expect organisations to audit at least once a year and after major changes.
Data fiduciaries must take reasonable security safeguards to prevent personal-data breaches. An audit is practical evidence that those safeguards are designed and tested.
RBI, SEBI (CSCRF) and IRDAI expect regulated entities and their technology providers to have periodic audits and to close findings within agreed timelines.
Enterprise buyers send security questionnaires, and cyber insurers ask for proof of controls. A recent audit report answers most of them in one go.
Each domain is tested against the frameworks in your scope. Choose a framework to see where it focuses.
ISMS scope, policies, roles, risk register, management review.
Hardware, software, cloud and data assets with owners and classification.
Joiner-mover-leaver, MFA, privileged access, periodic access reviews.
Log sources, 180-day retention in India, clock sync, alert review.
Firewall rule review, segmentation, remote access, wireless.
Scanning cadence, patch SLAs, configuration baselines, exceptions.
Tenant settings, public exposure, key management, shared responsibility.
Backup coverage, restore tests, BCP / DR plans and their last exercise.
Plan, roles, 6-hour CERT-In reporting path, breach notification, drills.
Contracts, security clauses, data processors, vendor reviews.
Personal data flows, consent records, retention, encryption, DLP.
Screening, awareness training, site access, clear desk, media disposal.
Technical checks (configuration review, authenticated vulnerability scan) are included where agreed in writing. Deeper testing is available as a separate, authorised red team or cloud security assessment.
The approach follows recognised audit practice: plan on risk, test on a sample, record what you saw, and report it so the right person can act.
Objectives, frameworks, sites, systems and critical assets; risk-based sampling plan; NDA and audit authorisation letter signed.
Policies, procedures, risk register, past audit reports and the statement of applicability read against the frameworks.
Control owners explain how each process runs; we observe it on screen or on site.
Samples drawn from real records — tickets, access lists, logs, backups, configurations — and tested for design and operating effectiveness.
Each exception rated by severity, linked to evidence, with management responses recorded before the final report.
Corrective and preventive actions agreed with owners and dates; closed items re-verified in a retest.
Hover a deliverable to see what's inside.
Scope, method, sample sizes, findings with evidence references, and an overall opinion.
~40–80 pages · PDFTwo pages for the board: posture, top risks, decisions needed, trend since the last audit.
board-readyEvery finding with root cause, corrective and preventive action, owner and due date.
XLSX trackerFindings mapped to ISO 27001 Annex A, CERT-In directions, DPDP Act and your sector regulator.
one sheet, many frameworksEvery artefact reviewed, with reference, date, source and hash — so findings can be traced.
chain of custodyAfter fixes, closed findings are re-verified and confirmed in writing.
with the retest packageFinding #12 · public storage bucket · High · fixed in 48 h (sample)
The audit helps you meet these expectations. It does not by itself make you compliant, and it is not a certification.
| Requirement | What the audit checks | Domain |
|---|---|---|
| CERT-In directions (Apr 2022)incident reporting in 6 hours | Is there a named contact, a reporting path and a tested runbook? | D-09 |
| CERT-In directions (Apr 2022)ICT logs kept 180 days in India | Which log sources exist, where they are stored, and whether 180 days are really retained. | D-04 |
| CERT-In directions (Apr 2022)clock synchronisation | Systems synced to an approved NTP source so timestamps line up. | D-04 |
| CERT-In audit guidelines (2025)periodic audit, follow-up on findings | Audit cadence, closure of past findings and revalidation evidence. | D-01 |
| DPDP Act 2023reasonable security safeguards | Encryption, access control, logging and breach response for personal data. | D-11 |
| RBI · SEBI CSCRF · IRDAIsector cyber frameworks | Governance, SOC monitoring, vendor oversight and periodic audit requirements. | D-01D-10 |
| MeitY guidancecloud & government workloads | Data location, empanelled-cloud use and security controls for public-sector work. | D-07 |
Annual audits are expected by RBI, SEBI CSCRF and IRDAI, and auditors want evidence that findings from last year were closed.
Patient data is personal data under the DPDP Act, often spread across HIS, PACS, lab systems and vendors.
ERP and plant networks meet; customers abroad send security questionnaires. Plant-floor depth sits in our OT assessment.
Enterprise customers ask for ISO 27001 or SOC 2 evidence before signing. An audit shows where you stand first.
Tenders often ask for a recent audit by a CERT-In-empanelled auditor. We align the audit and can arrange one on request.
Customer data, payment flows and many SaaS tools. Audits focus on what an outsider can reach.
Fixed-scope packages for one entity. Larger groups, more sites or deeper technical testing are quoted after a short scoping call.
Audits are aligned to CERT-In guidelines. A CERT-In-empanelled auditor is available on request* — quoted separately after scoping.
*Indicative placeholder prices · excl. 18% GST · to be confirmed by XcellHost. Cart total = price × quantity × 1.18.
Fixed-scope packages can be added to the cart. Nothing starts until scope and the audit authorisation letter are signed.
A rough guide for planning and budgeting. Your final scope is agreed with an auditor.
Estimates only — effort depends on evidence quality and availability of owners.
Answer honestly; nothing is stored or sent. "Partly" counts half.
—
We run certified security and service management ourselves.
01Auditors backed by engineers who fix and monitor, not just report.
02Microsoft 365, Entra and Azure controls reviewed by people who run them.
0310,000+ customers across India.
04Input-tax-credit friendly, one vendor.
05Encrypted storage, need-to-know access, deleted on request.
0630 minutes on entities, sites, systems and frameworks.
day 0Fixed scope, fee, timeline; NDA and audit authorisation signed.
week 1Document request list, owners named, fieldwork dates booked.
week 1Interviews, walkthroughs, sampling and technical checks.
weeks 2–4Draft findings shared; your management responses recorded.
week 5Report, executive summary, mapping matrix and CAPA plan.
week 6Closed findings re-verified; retest letter issued.
when ready