digi.ai.in
← digi.ai.in / blog
2026-08-278 min readSecurity

What a Security Review Actually Looks For

A security review checks Google's hacked-site flags, OWASP Top 10 risks, and specific headers — not a vague sense of "secure."

A security review isn't a single test with a pass/fail stamp. Depending on who runs it, it could mean Google checking whether your site harms visitors, a penetration tester working through the OWASP Top 10, or a CERT-In empanelled auditor checking against a formal government methodology. If someone tells you "we did a security review," the first question worth asking is: which one?

This matters because these three layers catch completely different problems. A site can pass Google's automated check and still be riddled with access-control bugs. It can pass a header scan and still fail a CERT-In audit outright. Below is what each layer actually inspects.

Layer 1: What Google's automated review flags

Google runs its own continuous review of every site it crawls, and reports the results in Search Console's Security Issues panel. This isn't a code-quality audit — it's specifically looking for harm to visitors. Google's own definition: a site gets flagged when "a Google evaluation determines that your site was hacked, or that it exhibits behavior that could potentially harm a visitor or their computer," citing phishing and malware/unwanted software as examples Google Search Console Help.

Google splits this into two distinct issue types:

  • Hacked content — anything placed on your site without your permission because of a vulnerability
  • Malware and unwanted software — code specifically designed to harm or deceive the visitor

If either is flagged, the consequences are visible to every visitor: a warning label can appear directly in search results, or browsers can show a full-page interstitial warning before the page even loads Google Search Console Help.

In practice, the patterns Google's crawlers catch most often are:

  • Injected code that silently redirects a visitor to another (usually malicious) site
  • Auto-generated spam pages stuffed with irrelevant keywords, designed purely to game search rankings

One pattern is genuinely hard to catch without a manual look: cloaking, where the compromised version of a page is shown only to Google's crawler, while a human visiting the same URL sees the normal, unaffected page Search Engine Journal. If your Search Console account is clean but something feels off, this is worth checking manually.

Layer 2: What a professional audit checks — the OWASP Top 10

When a penetration tester or security consultant reviews a web application, they typically work through the OWASP Top 10, the industry-standard list of the most critical web application security risks. The current (2021) edition made a significant change from earlier versions: Broken Access Control now sits at number one, displacing injection flaws (like SQL injection), which had topped the list for years INCIBE-CERT.

The 2021 list also added three categories that didn't exist in the prior version at all:

New category What it covers
Insecure Design Flaws baked into the architecture itself, not just the code
Software and Data Integrity Failures Trusting code, plugins or data without verifying integrity
Security Logging and Monitoring Failures Not being able to detect or investigate a breach after it happens

Worth knowing: OWASP didn't build this list purely from opinion. Eight of the ten categories came from actual contributed vulnerability-testing data across real applications, and the other two were added directly from a survey of security practitioners, because some emerging risks don't show up in scan data yet Help Net Security. That's a useful thing to know if a vendor tells you their scanner "covers OWASP" — a scanner alone can't surface the survey-based categories, because by definition those aren't yet common in automated test data.

Layer 3: The specific technical items a reviewer actually checks

Below the checklist level, a real review inspects specific, testable configuration items rather than a vague "is it secure":

HTTPS enforcement (HSTS header). This header "enforces the use of encrypted HTTPS connections instead of plain-text HTTP communication," and can be set with a preload directive so that even a user's very first visit to your site is protected against a man-in-the-middle attack Invicti.

TLS/SSL configuration. Reviewers check for two specific properties: authenticity (proof the data wasn't altered in transit) and confidentiality (an eavesdropper can't read the traffic) Google Cloud CDN docs.

Content-Security-Policy (CSP) header. This lets you restrict which resources a browser is allowed to load on a given page, specifically as a defence against cross-site scripting attacks MDN Web Docs.

A quick checklist a founder can hand to a developer or agency before sign-off:

  • Is HSTS enabled and, ideally, preloaded?
  • Is TLS configured correctly on every subdomain, not just the main one?
  • Is a CSP header set, and does it actually restrict script sources?
  • Has access control been tested — can a normal user reach admin-only pages by changing a URL?
  • Is there logging in place to detect a breach after the fact, not just prevent one?

Security and SEO are related, but not the same thing

There's a common claim that security headers directly boost search rankings. The more accurate framing, per a developer-focused security guide: "security headers are primarily security mechanisms rather than direct search-engine ranking factors" dev.to. Where security does hit SEO is indirectly — a botched HTTP-to-HTTPS migration with broken redirects, an overly strict CSP that blocks needed resources, or mixed-content errors can all hurt crawlability and rankings dev.to. Worth fixing for security reasons regardless, but don't sell a CSP header internally as an "SEO win" — it isn't one directly.

An automated scan is not the same as an audit

This is where a lot of confusion happens when businesses shop for a "security review." A quick automated scan of headers and known vulnerabilities is useful, but it is not equivalent to a proper audit. India's CERT-In makes this distinction explicit in its own guidelines: auditors are expected to use "industry standard methodologies and best practices for security testing," and the guidelines specifically discourage "solely tool-based testing," requiring manual components too AZB Partners.

The same guidance goes further than most people expect: applications built with no secure design or development practices at all "should not be considered for audits" until the underlying issues are fixed AZB Partners. In other words, an audit can be refused outright rather than simply flagged as failed — a strong signal that "we'll fix it after launch" isn't an acceptable stance for anything touching sensitive data.

What's specific to doing business in India

CERT-In (the Indian Computer Emergency Response Team) is the statutory national agency for cybersecurity coordination and guidance, established under Section 70B of the IT Act, 2000 Wikipedia. Two of its rules matter directly if you run a business website or app in India:

  1. Six-hour incident reporting. Since a directive effective 27 June 2022, organisations must report cybersecurity incidents to CERT-In within six hours of identification or notification — considerably faster than most global reporting norms Deloitte India. If your incident response plan assumes days to investigate before reporting, it needs revising.

  2. A formal, empanelled-auditor audit regime. On 25 July 2025, CERT-In issued its Comprehensive Cyber Security Audit Policy Guidelines. Any vendor claiming to run a "CERT-In audit" should be checked against CERT-In's published empanelment qualification requirements — the label alone doesn't guarantee the audit meets the actual standard AZB Partners.

If you're building anything for a government body or PSU, note that the Guidelines for Indian Government Websites and Apps (GIGW) require a valid CERT-In security audit certificate before launch — it's a hard prerequisite, not a recommendation India Guidelines Portal.

The scale behind all this: CERT-In has framed its push for stronger baseline security against India now having over 80 crore (800 million) people online PIB press release. At that scale, a compromised small-business site isn't just a business problem — it's a distribution point for phishing and malware at national scale, which is part of why Google's automated detection and CERT-In's audit regime both exist.

What to ask before you commission a "security review"

  • Which layer is being tested — Search Console-style harm detection, OWASP Top 10 vulnerability categories, or a formal CERT-In-aligned audit?
  • Is the testing solely automated, or does it include manual verification, given CERT-In's own stated preference against tool-only testing AZB Partners?
  • Does the report specifically address access control, given it's now the top-ranked OWASP risk category INCIBE-CERT?
  • Is there a six-hour incident reporting process in place if something does go wrong Deloitte India?

Questions people also ask

Is an SSL certificate enough to say a site is secure?

No. TLS/SSL only guarantees authenticity and confidentiality of data in transit Google Cloud CDN docs — it says nothing about access control bugs, injection flaws, or whether the site has been hacked and is serving malware, which are separate checks entirely Google Search Console Help.

Does a clean Google Search Console report mean the site is safe?

Not necessarily. Search Console flags visitor-facing harm like phishing, malware and hacked content Google Search Console Help, but cloaking techniques can hide a compromise from automated crawlers while still affecting real visitors Search Engine Journal. A clean report is necessary, not sufficient.

Do we need a CERT-In audit if we're not a government website?

It depends on your sector and data handled, but GIGW makes a valid CERT-In audit certificate a hard requirement specifically for government websites and apps India Guidelines Portal. Private businesses aren't automatically bound by GIGW, but the six-hour incident reporting directive to CERT-In applies more broadly and is worth checking against your own sector's obligations Deloitte India.

Written by the studio behind digi.ai.in. Questions? hi@digi.ai.in or WhatsApp +91 98605 96905
WhatsApp us