Home›Security›Security Assessment›Cyber Security Audit

XcellSecure|Cyber Security Audit

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.

ISO 27001:2022 Annex A
Aligned to CERT-In guidelines
Sampled, indexed evidence
Findings by severity
CAPA plan & retest
INR invoice with GST
Powered by VXcellHost Vortex SOC · Mumbai Audits aligned to CERT-In guidelines · by XcellHost
✦Ask AI about Cyber Security AuditChatGPTClaudePerplexityGoogle AICopilot
AUDIT FILECSA-2026-014 · sampleControl checklist by domain
WORKPAPERFieldwork day 3 · 64 of 99 controls tested (sample)
Controls tested0of 99 in scope · sample
65%effective
Works with 27ISO/IEC 27001:2022CICERT-In guidelinesDPDPDP Act 2023CSRBI · SEBI CSCRFNINIST CSF 2.0CISCIS Controls v8AWS · Azure · GCPMicrosoft 365
ISO 27001 & 20000-1Microsoft Gold Partner10,000+ customersSince 199999.95% uptime SLA24×7 NOC + SOC
§ 01 Overview

A policy says what should happen. An audit checks that it does.

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.

PlanTestEvidenceFixRetest
What a full audit walks throughISO/IEC 27001:2022 Annex A
0controls · 4 themes
  • 37Organisationalpolicies, roles, suppliers, incidents
  • 8Peoplescreening, awareness, remote work
  • 14Physicalsites, equipment, media
  • 34Technologicalaccess, logging, backup, secure config
  • +CERT-In directions6-hour reporting, 180-day logs, clock sync
§ 02 Why it matters in India

Regulators, customers and insurers now ask the same question: when were you last audited?

Four pressures are making a periodic, evidence-based cyber security audit a normal part of running a business in India.

01

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.

02

DPDP Act 2023 safeguards

Data fiduciaries must take reasonable security safeguards to prevent personal-data breaches. An audit is practical evidence that those safeguards are designed and tested.

03

Sector regulators

RBI, SEBI (CSCRF) and IRDAI expect regulated entities and their technology providers to have periodic audits and to close findings within agreed timelines.

04

Customers & insurers

Enterprise buyers send security questionnaires, and cyber insurers ask for proof of controls. A recent audit report answers most of them in one go.

Found in an audita ranked list, an owner and a date — fixed on your schedulevsFound in an incidenta 6-hour CERT-In clock, a breach notice and a regulator asking for your last audit
§ 03 What we assess

Twelve audit domains — pick the ones that apply to you.

Each domain is tested against the frameworks in your scope. Choose a framework to see where it focuses.

D-01Governance & policy

ISMS scope, policies, roles, risk register, management review.

D-02Asset & data inventory

Hardware, software, cloud and data assets with owners and classification.

D-03Identity & access

Joiner-mover-leaver, MFA, privileged access, periodic access reviews.

D-04Logging & monitoring

Log sources, 180-day retention in India, clock sync, alert review.

D-05Network security

Firewall rule review, segmentation, remote access, wireless.

D-06Vulnerability & patch

Scanning cadence, patch SLAs, configuration baselines, exceptions.

D-07Cloud & Microsoft 365

Tenant settings, public exposure, key management, shared responsibility.

D-08Backup & continuity

Backup coverage, restore tests, BCP / DR plans and their last exercise.

D-09Incident response

Plan, roles, 6-hour CERT-In reporting path, breach notification, drills.

D-10Third parties & vendors

Contracts, security clauses, data processors, vendor reviews.

D-11Data protection & privacy

Personal data flows, consent records, retention, encryption, DLP.

D-12People & physical

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.

§ 04 Methodology

Six phases, one audit trail — every step leaves a workpaper.

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.

  1. P1Plan & scope

    Objectives, frameworks, sites, systems and critical assets; risk-based sampling plan; NDA and audit authorisation letter signed.

  2. P2Document review

    Policies, procedures, risk register, past audit reports and the statement of applicability read against the frameworks.

  3. P3Interviews & walkthroughs

    Control owners explain how each process runs; we observe it on screen or on site.

  4. P4Testing & sampling

    Samples drawn from real records — tickets, access lists, logs, backups, configurations — and tested for design and operating effectiveness.

  5. P5Findings & report

    Each exception rated by severity, linked to evidence, with management responses recorded before the final report.

  6. P6CAPA & retest

    Corrective and preventive actions agreed with owners and dates; closed items re-verified in a retest.

Written authorisationsigned audit letter and scope before fieldwork NDA & data handlingevidence stored encrypted in India, need-to-know access Safe testing windowstechnical checks in agreed IST windows, read-only where possible No production impactno changes to your systems; no disruptive tests
§ 05 Deliverables

Six documents you can act on — and show to anyone who asks.

Hover a deliverable to see what's inside.

Audit report

Scope, method, sample sizes, findings with evidence references, and an overall opinion.

~40–80 pages · PDF
Executive summary

Two pages for the board: posture, top risks, decisions needed, trend since the last audit.

board-ready
Remediation (CAPA) plan

Every finding with root cause, corrective and preventive action, owner and due date.

XLSX tracker
Compliance mapping matrix

Findings mapped to ISO 27001 Annex A, CERT-In directions, DPDP Act and your sector regulator.

one sheet, many frameworks
Evidence index

Every artefact reviewed, with reference, date, source and hash — so findings can be traced.

chain of custody
Retest letter

After fixes, closed findings are re-verified and confirmed in writing.

with the retest package
How sampling worksillustrative · sample
Population · 100 access recordsSampled · 25Exceptions · 2

Finding #12 · public storage bucket · High · fixed in 48 h (sample)

§ 06 India compliance mapping

One audit, mapped to every rulebook you answer to.

The audit helps you meet these expectations. It does not by itself make you compliant, and it is not a certification.

RequirementWhat the audit checksDomain
CERT-In directions (Apr 2022)incident reporting in 6 hoursIs there a named contact, a reporting path and a tested runbook?D-09
CERT-In directions (Apr 2022)ICT logs kept 180 days in IndiaWhich log sources exist, where they are stored, and whether 180 days are really retained.D-04
CERT-In directions (Apr 2022)clock synchronisationSystems synced to an approved NTP source so timestamps line up.D-04
CERT-In audit guidelines (2025)periodic audit, follow-up on findingsAudit cadence, closure of past findings and revalidation evidence.D-01
DPDP Act 2023reasonable security safeguardsEncryption, access control, logging and breach response for personal data.D-11
RBI · SEBI CSCRF · IRDAIsector cyber frameworksGovernance, SOC monitoring, vendor oversight and periodic audit requirements.D-01D-10
MeitY guidancecloud & government workloadsData location, empanelled-cloud use and security controls for public-sector work.D-07
Numbers to remember
0hours · CERT-In incident reporting window
0days · ICT log retention CERT-In expects
0audit a year, at least — and after major change
Regulatory summaries are indicative — confirm obligations with your compliance or legal team.
§ 07 Use cases by industry

Same method, different pressure points.

Banks, NBFCs, brokers & insurers

Annual audits are expected by RBI, SEBI CSCRF and IRDAI, and auditors want evidence that findings from last year were closed.

  • Privileged access & maker-checker
  • SOC monitoring and log retention
  • Outsourcing and vendor oversight
  • Closure of previous audit findings

Hospitals, labs & health-tech

Patient data is personal data under the DPDP Act, often spread across HIS, PACS, lab systems and vendors.

  • Access to patient records
  • Backups of clinical systems
  • Shared and legacy workstations
  • Third-party device and software vendors

Plants, MSMEs & exporters

ERP and plant networks meet; customers abroad send security questionnaires. Plant-floor depth sits in our OT assessment.

  • IT / OT boundary and remote access
  • ERP and Tally servers
  • Ransomware-ready backups
  • Customer questionnaire evidence

SaaS, IT & ITeS companies

Enterprise customers ask for ISO 27001 or SOC 2 evidence before signing. An audit shows where you stand first.

  • Cloud tenant configuration
  • Change and release control
  • Joiner-mover-leaver process
  • Readiness for certification

PSU vendors & government suppliers

Tenders often ask for a recent audit by a CERT-In-empanelled auditor. We align the audit and can arrange one on request.

  • CERT-In-aligned scope
  • MeitY cloud guidance
  • Tender-ready audit letter
  • Application and network review

Retail, D2C & marketplaces

Customer data, payment flows and many SaaS tools. Audits focus on what an outsider can reach.

  • Web and API exposure
  • Payment-flow controls (PCI DSS context)
  • Customer data & consent
  • Marketing and logistics vendors
§ 08 Audit packages

Start with the gaps, or go straight to the audit. Retest when you've fixed.

Fixed-scope packages for one entity. Larger groups, more sites or deeper technical testing are quoted after a short scoping call.

Before the auditGap Assessmentone entity · 2–3 weeks
₹74,999*
Indicative · excl. 18% GST
  • Policy & document review
  • Owner interviews
  • Gap list against ISO 27001 & CERT-In
  • Prioritised 90-day roadmap
Configure
Most chosenCyber Security AuditISO 27001 / CERT-In-style · 4–6 weeks
from₹1,99,999*
Indicative · excl. 18% GST
  • Everything in the gap assessment
  • Sampled testing of each control
  • Configuration review & vulnerability scan
  • Audit report & executive summary
  • CAPA plan with owners & dates
Configure
After the fixesRetestre-verify closed findings
₹49,999*
Indicative · excl. 18% GST
  • Re-test of every closed finding
  • Updated evidence index
  • Before / after severity view
  • Retest letter
Configure

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.

§ 09 Configure & buy

Choose a package and the number of entities — see the total with GST.

Fixed-scope packages can be added to the cart. Nothing starts until scope and the audit authorisation letter are signed.

Package Cyber Security Audit
Entities / legal companies each audited separately
Frameworks in the report
Your estimate
Cyber Security Audit
ISO 27001 / CERT-In-style · per entity
Payable incl. GST₹2,35,999
Indicative · excl. 18% GST · confirm with XcellHost. Multi-site groups and deeper technical testing are quoted.
§ 10 Tool · Audit scope estimator

Describe your organisation — see the effort, timeline and package.

A rough guide for planning and budgeting. Your final scope is agreed with an auditor.

Locations / sites
Critical applications
Cloud accounts / tenants
Key vendors with data access
Frameworks
Technical checks Config review + scan
Estimated effort0 auditor-days
Calendar time— weeks
Controls in scope—
SuggestedCyber Security Audit—

Estimates only — effort depends on evidence quality and availability of owners.

§ 11 Tool · Readiness self-check

Ten questions — are you ready for an audit, or for a gap assessment first?

Answer honestly; nothing is stored or sent. "Partly" counts half.

    0%audit readiness
    —

    —

    § 12 Checklist audit vs XcellHost

    The difference is what happens after the report.

    Typical checklist auditXcellHost Cyber Security Audit
    EvidenceScreenshots on request, no indexSampled, dated and hashed evidence index
    Technical checksQuestionnaire answers taken as givenConfiguration review and authenticated scan in scope
    FindingsFlat list of non-conformitiesSeverity, business impact and owner per finding
    FrameworksOne standard per reportISO 27001, CERT-In, DPDP and sector mapping in one matrix
    RemediationLeft to youCAPA plan with dates, tracked with you
    RetestA new engagement next yearRetest of closed findings, ₹49,999*
    Board viewTechnical report onlyTwo-page executive summary with trend
    ISO 27001 & 20000-1

    We run certified security and service management ourselves.

    01
    24×7 NOC + SOC

    Auditors backed by engineers who fix and monitor, not just report.

    02
    Microsoft Gold Partner

    Microsoft 365, Entra and Azure controls reviewed by people who run them.

    03
    Since 1999 · Mumbai

    10,000+ customers across India.

    04
    INR invoice with GST

    Input-tax-credit friendly, one vendor.

    05
    Evidence stays in India

    Encrypted storage, need-to-know access, deleted on request.

    06
    § 13 How an engagement runs

    From first call to retest letter — seven steps.

    1. 1Scoping call

      30 minutes on entities, sites, systems and frameworks.

      day 0
    2. 2Proposal & NDA

      Fixed scope, fee, timeline; NDA and audit authorisation signed.

      week 1
    3. 3Kick-off

      Document request list, owners named, fieldwork dates booked.

      week 1
    4. 4Fieldwork

      Interviews, walkthroughs, sampling and technical checks.

      weeks 2–4
    5. 5Draft & responses

      Draft findings shared; your management responses recorded.

      week 5
    6. 6Final report & CAPA

      Report, executive summary, mapping matrix and CAPA plan.

      week 6
    7. 7Retest

      Closed findings re-verified; retest letter issued.

      when ready