Skip to main content

Abhinav A

Lead — VAPT & Security Assessments

VAPT · Web Application Security · API Security · Mobile Security · Network Security · Configuration Review

Leads Security Brigade’s VAPT delivery team. Has executed advanced penetration tests across BFSI, fintech, QSR and telecom.

Articles by Abhinav A

VAPT Tools: What Testers Use and Where Each Tool Stops

The tools a tester runs in each phase of a VAPT, what each produces, and where a person has to take over.

vapt.in

What a Play Integrity verdict actually returns, and who it is evidence for

The Play Integrity API returns three families of verdict, and the labels most conversations about it are really about are not among the ones you get by default. This is what Google documents it returning, the limits Google publishes about its own product, and the reason every documented Android integrity primitive ends up producing evidence for a server rather than an answer for a device. Read 3 September 2026.

androidsecurity.in

Google Play reads your manifest, not your code path

Google Play's restricted-permission rules are written against what an app declares, not against what it calls. An app that never invokes an API can still carry the permission line in its merged manifest, because a library put it there. That is a store problem before it is a runtime one. The SMS and Call Log groups, QUERY_ALL_PACKAGES, and the eight permissions barred outright from personal loan apps, read off Google's own policy pages. Read 3 September 2026.

androidsecurity.in

Your Data safety form is a declaration about a binary, and the binary keeps changing

Google Play's Data safety form binds every developer with a published app. It covers data handled by third-party libraries and SDKs as well as your own code, and Google's position on who answers for it is one sentence long: you alone are responsible. That makes it one of the few store obligations you can actually check. A declaration and a merged manifest are two artefacts, and they can be read against each other. Read 3 September 2026.

androidsecurity.in

Android security advice that expired: fourteen statements, and the version that ended each one

Fourteen statements about Android security that were correct when somebody learned them and are not correct now. Each one is paired with the API level, the Android Gradle Plugin version or the Google turndown that falsified it, the platform page it was read from, and that page's own last-updated stamp. Google revises these pages independently, and a claim without a stamp cannot be re-checked. Read 3 September 2026.

androidsecurity.in

Android 16 is now the submission gate: target API 36, and what the 1 November window actually is

Since 31 August 2026, Google Play has applied two requirements to two different sets of apps under one date, with two very different verbs. A new app or an app update must target Android 16 (API level 36) or higher to be submitted. An app already on Play must target Android 15 (API level 35) or higher to stay available to new users on newer devices. A team that has not shipped an update since it moved to API 35 is compliant on availability and blocked on submission the moment it tries to ship. Checked 2 September 2026.

androidsecurity.in

The manifest two authorities regulate: RBI paragraph 12(i) and Google Play's Financial Services permission list

Two instruments reach the same AndroidManifest.xml. The Reserve Bank of India (Digital Lending) Directions, 2025 name the phone resources a Digital Lending App must desist from accessing, in prose, and permit a one-time access for on-boarding/KYC with the borrower's explicit consent. Google Play's Financial Services policy names eight Android permission constants for personal loan apps. Google's SMS and Call Log rule is written on what an app declares in its manifest, and says so in terms, placeholder text included. That puts the merged manifest, and every library that contributes a uses-permission line to it, inside the question. And a named Chief Compliance Officer of the Regulated Entity certifies that data collection and storage by DLAs comply with para 12 and 13. Every quotation checked 2 September 2026.

androidsecurity.in

Every Play package must be registered by 30 September 2026 — and the install-side milestone is a different obligation

Two obligations, one date. Install-side verification enforcement begins on 30 September 2026 for users installing from seven named stores in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7+. Separately, on the same date, all Play packages must be registered under Android developer verification, and Google's own word for the consequence is global removal from Google Play. Registration is decided on app signing key ownership and install share, so a rotated upload key, an agency-held key, or one package name shipping from two keys has to be resolved before the package can be registered. Every quotation checked 2 September 2026.

androidsecurity.in

Which ransomware is this, and what the family name decides

You know you are encrypted. You do not yet know by what, and the questions that follow are all questions about the family: whether a free decryptor already exists for it, whether its operator publishes stolen data, whether the group appears on a sanctions list. Three things the payload left on your screen name it, two free services will read them for you, and none of it needs a vendor or a tool you do not have.

hacked.co.in

How they got in — and why your logs decide whether you can answer

The morning after, the question is how. A short list of entry classes, each confirmed from a different record. Every one of those records is a log with a retention window set by whoever runs the infrastructure. Where that window is shorter than the intrusion, the honest finding is 'root cause undetermined', and this is how to write one.

hacked.co.in

Website defacement, or a Google warning on your site: the first hour

A replaced homepage, or a Chrome warning on your site. What to copy before you touch the server, and the CERT-In clause that puts a defaced site on a six-hour clock.

hacked.co.in

Measuring the executive population

RBI ¶204 addresses the Board and Senior Management separately, and CERT-In's reporting rule makes a percentage over twelve people an individual result. What an executive exercise reports instead.

securityawareness.in

The lawful basis for testing your own staff

A phishing simulation produces personal data about identifiable employees. DPDP s.4(1) gives two grounds for processing it, s.7(i) is the employment ground, and s.8 governs the dataset on either.

securityawareness.in

Requirements 6.2 and 6.3.1: code review inside a PCI DSS programme

PCI DSS reviews code per release, not per year. What 6.2.3, 6.2.3.1 and 6.3.1 actually require, and the evidence a manual review has to leave behind.

pcidss.in

Requirement 11.4.7: what your customers may demand of you, and since when

Requirement 11.4.7 stopped being a best practice on 31 March 2025. A multi-tenant service provider now owes customers either penetration test evidence or access to test, and cannot refuse both.

pcidss.in

What gets a PCI penetration test report rejected

A QSA examines your penetration test report against the elements of Requirement 11.4. Eight gaps account for most of the reports that come back.

pcidss.in

ASV scan, internal scan, penetration test: three PCI DSS requirements, no substitutes

PCI DSS v4.0.1 separates internal scanning (11.3.1), external scanning by an ASV (11.3.2) and penetration testing (11.4). Different clocks, different testers, one exception at 11.3.2.1.

pcidss.in

What Requirement 11.4 demands of a penetration test — and why you searched for 11.3

Penetration testing moved from Requirement 11.3 to 11.4 in PCI DSS v4.0. Here is the renumbering in full, what each sub-requirement now demands, and why the Council's own supplement still says 11.3.

pcidss.in

The payment page you did not think was in scope: 6.4.3 and 11.6.1

If your checkout redirects to a gateway or embeds its form in an iframe, PCI DSS 6.4.3 and 11.6.1 apply to the page around it. Both have been mandatory since 31 March 2025.

pcidss.in

Segmentation is a claim until Requirement 11.4.5 tests it

Segmentation reduces PCI DSS scope only if it holds. Requirement 11.4.5 is where that claim gets tested, and 11.4.6 makes it six-monthly for service providers.

pcidss.in

What an ASV does, and why Requirement 11.3.2 admits nobody else

Requirement 11.3.2 is the only requirement in PCI DSS Requirement 11 that names a credential. Requirement 11.3.2.1, the post-change external scan, deliberately does not.

pcidss.in

VAPT When No Regulator Requires It

Unregulated companies still end up buying penetration tests. The requirement arrives through customers, contracts, insurers and investors, and each of them wants something slightly different.

vapt.in

Which Indian Regulators Require Security Testing

Which regulator binds you, what instrument sets the requirement, and where to read the detail that applies to your entity type.

vapt.in

Writing a VAPT RFP That Gets Comparable Quotes

Most VAPT tenders return responses that cannot be compared. Four ways an RFP causes that, and what to specify instead so three proposals answer the same question.

vapt.in

The VAPT Certificate: What It Evidences

A VAPT certificate is issued by the firm that tested you, not by a standards body. What the document actually is, what it proves, what it does not, and who accepts it.

vapt.in

What Changes by Your Third VAPT

The first report is mostly hygiene. By the third, the findings that remain are the ones that required someone to understand your business. The trap is when that third report comes back quiet.

vapt.in

How Often Should You Run a VAPT

Annual is the default answer, and it sets a floor. What moves the cadence in practice: what changed, what you are subject to, and what the last report found.

vapt.in

Prioritising Findings for Remediation

Sixty findings and two engineers. How to sequence the work so the risk comes down fastest, and why fixing by severity order is rarely the right plan.

vapt.in

How a VAPT Scope Gets Sized

A tester sizes the work by counting functions, roles and entry points. That count becomes the number of days, so the detail in your brief decides how accurate the quote is.

vapt.in

What Can and Cannot Be Tested, and Why

Some things are excluded because they would break something. Others because they are not yours to authorise. Cloud, SaaS, third parties and the paperwork that separates a test from an offence.

vapt.in

Black, Grey and White Box Testing

The three terms describe how much you tell the tester, not how much access they get. Which one to choose, and why the realism argument for black box is usually the wrong way round.

vapt.in

Retest, Closure and the Evidence That Ends an Engagement

A report describes a moment. What turns it into a closed engagement is the retest, and there are three things to agree about it before the first test starts.

vapt.in

What Separates a Written Finding From a Scanner Alert

The same underlying flaw, as a scanner reports it and as a tester writes it up. Six things present in one and absent from the other, using a finding from a published sample report.

vapt.in

How to Read a Security Finding

Severity, CVSS and the vector string, and why a 9.8 on one system is not a 9.8 on another. How to convert a report ranking into your own.

vapt.in

What a Scanner Finds, and What It Cannot

Automated tooling is genuinely good at a defined set of problems and structurally incapable of another set. Both lists are specific, and knowing which is which is how you tell a penetration test from an expensive scan.

vapt.in

The Phases of a Penetration Test

Every credible methodology describes the same arc, under different names. What happens in each phase, how long each takes, and how to tell whether a proposal has a real methodology behind it or a diagram.

vapt.in

External and Internal Network Penetration Testing

External and internal network tests answer different questions. What each one looks for, the findings that recur in almost every internal engagement, and why the first output is usually a corrected asset inventory.

vapt.in

Mobile Application Security Testing, Explained

A mobile test has three parts: the binary, the device, and the API behind them. Most of the serious risk sits in the third, because the app itself runs on hardware the attacker owns.

vapt.in

API Penetration Testing, Explained

APIs fail differently from the applications in front of them. What a tester looks for, why object-level authorisation is the dominant finding, and why the endpoints nobody documented are the ones that hurt.

vapt.in

Web Application Penetration Testing, Explained

What a tester actually does to a web application over two weeks, what they need from you before they start, and which classes of flaw only turn up when a person is holding the keyboard.

vapt.in

What a VAPT Actually Is, and What You Receive

Somebody has asked you for a VAPT. What the two halves are, what happens during one, what you get at the end, and the four things it is not.

vapt.in

Comparing Two CERT-In Empanelled Vendors

Once both firms are empanelled, the empanelment stops helping. What the public register already tells you about each, and the three differences that survive the bar.

vapt.in

Preparing for Your First VAPT

Most of what makes a penetration test go badly is decided before it starts. Eight things to have ready: scope, environment, accounts, contacts, defenders, calendar, paperwork, retest.

vapt.in

What Moves the Price of a Penetration Test

Quotes for the same system arrive at wildly different numbers, and the reason is almost never margin. Testing is sold in tester-days, and the things that move the day count are knowable before you ask anyone for a price.

vapt.in

How to Check an Auditor Is Really CERT-In Empanelled

Empanelment is claimed more often than it is checked. The register is a public PDF, it takes two minutes to search, and it carries more about each firm than the claim itself, including how many audits they say they ran last year.

vapt.in

What Is Actually Inside a VAPT Report

A penetration test ends in a document, and most people receive one before they have any way of judging it. Here is what each section is for, and the specific thing to check in each, from the executive summary to the compliance mapping appendix.

vapt.in