Skip to main content

IT Security Audit Certificate

CERT-In empanelled IT security audit for networks, cloud and systems

An information security audit to CERT-In guidelines covering the systems you name, closed with a dated audit certificate.

An aisle of server racks in a data centre
Valid for
1 year
Guidelines
CERT-In
Verification
QR and register

Accredited and empanelled

What is IT security audit?

An IT security audit examines how well your information systems are protected, from network devices and servers to cloud accounts, mobile applications, APIs and industrial control systems. As a CERT-In empanelled auditing organisation, we carry out these audits in line with the guidelines and directions CERT-In issues for empanelled auditors.

Each audit is scoped by type and by asset list, and tested against references such as ISO/IEC 27001:2022, NIST SP 800-115 and the CIS Benchmarks. The certificate records the audit type, the assets in scope, the audit period and the date on which closure of findings was verified.

Sector regulators in India, including RBI, SEBI and IRDAI, expect the entities they oversee to have their systems audited periodically, and several of their directions call for CERT-In empanelled auditors. Government bodies and critical infrastructure operators often have similar expectations.

Who it is for

  • Banks, NBFCs, insurers and market intermediaries with periodic audit requirements
  • Government departments and public sector undertakings
  • Cloud and data centre service providers
  • Organisations with mobile apps or public APIs
  • Power, utilities and manufacturing sites running OT networks

What sets audit time and cost

Typically three to six weeks from scoping to certificate, depending on the number of assets and locations and the time needed to close findings.

  • Audit type and number of assets in scope
  • Number of sites, data centres or cloud accounts
  • On-site testing versus remote testing
  • Depth of configuration review across servers and devices
  • Regulatory reporting formats required
  • Number of compliance verification rounds

Why it matters

What IT security audit gives you

  1. 01

    Audit evidence in the expected form

    A report and certificate from a CERT-In empanelled organisation, in the form your regulator or customer usually asks for.

  2. 02

    One view of your exposure

    Findings across network, cloud and application layers in one report, ranked by severity.

  3. 03

    Configuration measured against benchmarks

    Servers, devices and cloud accounts compared with CIS Benchmarks, showing where hardening has drifted.

  4. 04

    Verified closure

    A compliance verification step confirms fixes before the certificate is issued, and its date is recorded.

The audit

What our auditors examine

  1. 01

    Network and perimeter

    Firewall rules, segmentation, exposed services, remote access, VPN and wireless configuration, with external and internal vulnerability scanning.

  2. 02

    Cloud configuration

    Identity and access management, storage exposure, logging, encryption and network controls in AWS, Azure, Google Cloud or private cloud.

  3. 03

    Mobile applications and APIs

    Insecure storage, transport security, authentication, authorisation and data exposure in Android and iOS apps and the APIs they call.

  4. 04

    Server and endpoint hardening

    Operating system and database settings checked against CIS Benchmarks, along with patch levels and privileged account controls.

  5. 05

    Information security controls

    Policies, access reviews, backups, logging, incident response and other controls compared with ISO/IEC 27001:2022 Annex A.

  6. 06

    OT and industrial control systems

    Segregation between IT and OT, remote vendor access and the exposure of controllers and HMIs, tested with care not to disrupt operations.

How the audit runs

Audits follow CERT-In guidelines from scoping to the final certificate, with re-testing until findings are closed.

  1. 01

    Scoping

    We agree the applications, URLs, APIs, networks or assets in scope, the test environment and the rules of engagement.

  2. 02

    Testing

    Auditors test against CERT-In guidelines and recognised methods such as the OWASP Testing Guide, using automated tools and manual techniques.

  3. 03

    Findings report

    Each finding comes with its severity, evidence and the risk it poses. Your team fixes them in the audited environment.

  4. 04

    Re-testing

    We re-test until findings are closed or formally accepted, and record the version that was finally audited.

  5. 05

    Certificate and report

    The final report and certificate are issued, and the certificate is listed in the public register with a QR code for verification.

IT security audit questions

We audit; we do not consult.

To keep audits independent, we never design, build or fix the systems we audit, and decisions are made by people who did not take part in the audit. Read our impartiality policy.

Plan your IT security audit audit

Tell us your scope, sites and timeline. We reply with an audit plan and a fixed quote.