Skip to main content

Chintan J

CISO & Director — Security Advisory

Information Security · CISO Advisory · Regulatory Compliance · RBI Cybersecurity · SEBI CSCRF · ISO 27001

Oversees Security Brigade's cybersecurity advisory practice, helping regulated enterprises meet RBI, SEBI, CERT-In, and IRDAI compliance mandates. Previously held senior security leadership roles across BFSI.

Articles by Chintan J

How Attackers Bypassed NBFC Payout Controls — and What CERT-In Recommends

How attackers abused trusted NBFC payout APIs, what CERT-In's October and November 2026 advisories reveal, and six controls lenders should test now.

Security Brigade

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

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

Business email compromise — the money left this morning

A payment went to an account that was not your supplier's. The instinct is to chase the money, and that is right. But a BEC is a mailbox intrusion first and a fraud second, and the two run on different clocks. What to do in the first hours, in what order, and why the mailbox investigation cannot wait for the recovery attempt.

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

The six-hour report: what actually gets sent, and who else you owe

You noticed at 09:40. CERT-In is due by 15:40. What goes in the six-hour report, who sends it, and which other regulators are owed a filing too.

hacked.co.in

The first hour, and the first seventy-two

The order to work in from the moment you find out: what to stop doing, what to preserve, who to call, and what CERT-In's Direction (ii) of 28 April 2022 requires within six hours of noticing an incident or being brought to notice about it. Preservation comes before remediation. A rebuilt server is an answer nobody can reconstruct.

hacked.co.in

The report route: where a suspicious email goes, and what happens to it

Report rate is the only number in a phishing programme that measures a behaviour you want. It exists only if there is somewhere to report to, staffed by somebody who answers. How to build that route.

securityawareness.in

The clause that names phishing testing, and exactly what it says

One clause in the SEBI CSCRF names phishing testing. It is on page 87, it sits in the Risk Management guidelines, and "for e.g." are the regulator's own words. What item 1(e) asks for.

securityawareness.in

What SEBI CSCRF asks of an awareness programme

SEBI CSCRF puts the awareness obligation in two places: PR.AT sets the training programme and its cohorts, and GV.RM.S3 requires periodic assessment of the awareness level. What each asks, and which REs carry it.

securityawareness.in

NBFC ¶36: measure the training, and keep the repository

The RBI Directions, 2026 place four separately auditable requirements on an NBFC in one paragraph. What ¶36 asks for, phrase by phrase, and what has to exist before a supervisor asks to see it.

securityawareness.in

What the click list may and may not be used for

A simulation produces a list of names. CERT-In's guidelines require anonymised or statistical results with no individual identified or penalised, and a programme that ignores that rule destroys its own report rate.

securityawareness.in

The awareness clauses of the RBI Directions, 2026, entity by entity

The RBI Directions, 2026 carry an employee awareness obligation for every supervised entity, and the paragraph number differs in each. Which clause binds a bank, an NBFC, a CIC or a UCB, and what each one asks for.

securityawareness.in

What is and is not PCI DSS: SSF, P2PE, 3DS, PIN — and where PA-DSS went

PCI DSS assesses your organisation. SSF, P2PE, PTS, 3DS and PIN Security assess products and other parties. Where PA-DSS went, and what a listing changes.

pcidss.in

Which PCI SSC document says what, and which PCI DSS version it is written against

PCI DSS v4.0.1 is the only active version: v4.0 retired 31 December 2024, v3.2.1 on 31 March 2024. Which PCI SSC document answers which question, and what version each carries.

pcidss.in

PCI DSS renewal is a re-scope, not a repeat

Nothing renews on the anniversary. Requirement 12.5.2 asks the entity to re-confirm scope every twelve months, and a test scoped to last year's CDE is the first mismatch an assessor sees.

pcidss.in

The PCI DSS evidence checklist: what twelve months of evidence actually looks like

The artefacts a PCI DSS assessment is conducted against, by requirement and by cadence. What each one has to show, and why four scan reports can still be one failed requirement.

pcidss.in

What actually drives PCI DSS cost: a decomposition, not a range

PCI DSS cost is five separate bills paid to five different parties. Which lines you carry, what moves each, and why the two largest are set by scope before anyone quotes.

pcidss.in

The bank's ATM Switch provider: PCI DSS and PCI SSF as contractual controls

RBI's 2026 Directions make a bank write PCI DSS and PCI SSF into its ATM Switch ASP contract. Which paragraph carries it, what each standard validates, and what evidence satisfies it.

pcidss.in

PCI DSS inside an Indian contact centre or BPO

Take card numbers on someone else's behalf and PCI DSS reaches you as a service provider: 11.4.6 every six months, a sub-requirement responsibility matrix, and recordings holding account data.

pcidss.in

Two clocks: why an RBI-regulated payment aggregator tests twice a year and PCI DSS asks once

PCI DSS sets a twelve-month floor for penetration testing. The RBI Payment Aggregator Directions, 2025 ask for bi-annual VAPT. A PA scoped to PCI's cadence is under-testing against its regulator.

pcidss.in

PCI DSS and the RBI Payment Aggregator Directions, 2025: clause by clause

The 2025 Directions name PCI DSS in four clauses. What each one obliges a payment aggregator to hold, and where the CERT-In empanelled system audit sits alongside it.

pcidss.in

We use a payment gateway, so PCI DSS does not apply to us

Outsourcing to a compliant gateway is the largest scope reduction PCI DSS offers, and the standard still says it does not make you compliant. Where the belief holds, and where it breaks.

pcidss.in

Tokenisation and card-on-file in India: what the regulator already decided

Since 1 October 2022 no Indian entity outside the card issuers and networks may store card data. What that leaves in PCI DSS scope: capture, log residue, the T+4 window, and a re-scope.

pcidss.in

What is in your CDE, and what a scoping exercise produces

PCI DSS scope is three sets of systems, not one, and the third sits outside the CDE. What Requirement 12.5.2 asks a scoping exercise to produce, and why remediation started first is half wasted.

pcidss.in

Which SAQ applies to you: 14, 27, 139, or all of them

For e-commerce the SAQ is decided by where the payment form comes from: 14 requirements, 27, 139, or all of them. The eligibility table for all nine types, from PCI SSC's own guidance.

pcidss.in

Merchant and service provider levels: who assigns yours

Levels come from the payment brands’ rulebooks and are applied by your acquirer. The Mastercard and Amex thresholds, and what a level changes.

pcidss.in

What a QSA does, what a QSA may not assess, and how to verify one

A QSA's qualification is granted per company, per region, per person and per version of the standard. Here is what that covers, what it bars, and how to check it.

pcidss.in

What "PCI DSS certification" actually means, and who signs it

The market says certification. An assessed entity receives a ROC plus an AOC, or an SAQ plus an AOC, and the signature block on each says something different.

pcidss.in

Who does what in a PCI DSS engagement

QSA, ASV, ISA, independent penetration tester, the entity, the acquirer and the payment brand: the six parties in a PCI DSS programme and the artefact each one produces.

pcidss.in