Skip to main content

Siddarth G

Practice Director — Cybersecurity

Penetration Testing · Vulnerability Research · Bug Bounty · Red Teaming · Web Application Security

Leads Security Brigade's offensive security practice with deep expertise in vulnerability research, penetration testing, and red team operations. Ranked Top 80 globally on Bugcrowd.

Articles by Siddarth G

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

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

Ransomware recovery: the paths out, in the order they are tried

Data comes back one of four ways: a backup restore that has actually been verified, a free decryptor for the family you are really dealing with, forensic recovery of what survives on the disk, and last, only as a last resort, the ransom. Each one turns on a fact about your environment you can establish before you commit to it, and none of them is worth doing until the estate is clean.

hacked.co.in

What ransomware negotiation actually looks like

The sanctions question comes before the price question, and it decides whether there is anything to discuss at all. What a negotiation channel does, in the order it does it: who is on the other end under a ransomware-as-a-service model, why proof of decryption has to be run on files you choose, what a deletion promise is and is not, and why the six-hour CERT-In filing runs whatever is happening in the chat.

hacked.co.in

What the ransom decision actually turns on

By the time the question reaches you it is usually framed as pay or don't. It is really five separate findings, and four of them can be established in the first two days: which strain it is, whether a decryptor already exists, whether your backups actually restore, and whether data left the building. The six-hour CERT-In filing is due either way.

hacked.co.in

Preserve it before you rebuild

Powering the machine off, restoring from backup, re-imaging, and quietly cleaning up are four reasonable instincts, and each destroys something no technique recovers afterwards. What each one takes with it, and a preservation sequence a system owner can work through with what they already have, before anyone with a forensics kit arrives.

hacked.co.in

Scoping a phishing simulation programme in India

What has to be decided before the first send: the population and its cohorts, the scope boundary, the cadence, the channels, the exclusions, the escalation contacts and the written authorisation CERT-In requires.

securityawareness.in

Testing the service desk: vishing as a process control test

A vishing test against the service desk measures a procedure, not a person. What CERT-In's CISG-2025-02 requires before the call, and what the finding should say afterwards.

securityawareness.in

What each number in a phishing simulation report measures

A phishing simulation returns a small set of numbers, and each supports a narrow claim. What click rate, credential submission, time-to-click, report rate and repeat exposure each measure.

securityawareness.in

What CERT-In's audit policy guidelines require of a phishing simulation

CERT-In's audit policy guidelines already set the rules for a phishing simulation in India: specific written permission before, anonymised or statistical results after, and no individual identified or penalised.

securityawareness.in

Choosing a Red Team Provider

Every firm answers yes to every capability question. Six questions where the generic yes runs out, and what a real answer sounds like.

red-team.in

Red Teaming and SEBI CSCRF

What the Cyber Security and Cyber Resilience Framework asks of regulated entities, where adversarial testing sits within it, and how the tiering decides how much applies to you.

red-team.in

Social Engineering Assessments and the Consent They Require

Testing people is not testing systems. What can be assessed, what must be agreed first, and why individual results should almost never leave the room.

red-team.in

What the Exercise Tells You About Detection

The findings are about your systems. The timeline is about your team. Read from the defender’s side, a red team report is a much more uncomfortable document.

red-team.in

After the Foothold: Movement and Escalation

One workstation is not the objective. It is the start of credential harvesting, lateral movement and privilege escalation, and four internal weaknesses make that route fast in almost every network.

red-team.in

Threat-Led Penetration Testing: What TLPT Actually Means

In some jurisdictions a supervised regulatory programme with prescribed intelligence and a regulator in the room. In marketing, a synonym for red teaming. The difference is worth establishing.

red-team.in

How Red Teams Get In

Rarely by defeating a control. Usually by asking someone. The four initial-access routes, roughly in the order they work.

red-team.in

The Phases of a Red Team Engagement

Reconnaissance, initial access, foothold, movement, objective, debrief. What happens in each, roughly what share of the weeks it takes, and which phase produces no findings at all.

red-team.in

What a Red Team Report Contains

A red team report traces the route to the objective: what was attempted, what succeeded, what defenders did or did not detect, and where the exercise stopped.

red-team.in

Scoping a Red Team: Objectives and Rules of Engagement

The objective decides whether the exercise is worth anything, and the rules decide whether it is survivable. What to write down before anyone starts.

red-team.in

Adversary Simulation and Breach-and-Attack Simulation

One is a tool that replays known techniques on a schedule. The other is people improvising. Both get sold as red teaming, and both are useful, for different questions.

red-team.in

Red Teaming Under the RBI's 2026 Directions

Four of the six 2026 Directions say red teams may be used. Two do not mention red teaming at all. The paragraph numbers entity by entity, and what the instruments do require about whoever tests you.

red-team.in

Purple Team: When It Beats a Red Team

A red team measures whether you would notice. A purple team fixes the fact that you would not. The one prerequisite, the three outcomes each technique lands in, and the four ways the exercise goes wrong.

red-team.in

Physical Penetration Testing

Tailgating, cloned badges, an unattended meeting room and a network socket. What a physical assessment tests, why the Indian shared-tenancy office moves the boundary outside your control, and the authorisation that has to exist first.

red-team.in

What a Red Team Engagement Costs

Quotes for the same objective can differ threefold. The objective itself is the largest lever, duration and access routes explain most of the rest, and the authorisation work is priced badly or not at all.

red-team.in

What a Red Team Assessment Involves

An objective, a set of rules, and a team that will take any route the rules permit. What you have to have ready, what happens across the weeks, how deconfliction works when your defenders find it, and why the team failing is often the better result.

red-team.in

Red Team vs Penetration Testing

A penetration test asks what is broken. A red team asks whether anyone would notice. Where VAPT sits between them, what each proves to a regulator, and why only one of them has a calendar.

red-team.in