Skip to content
The sand-coloured stone Reserve Bank of India building in Mumbai with a columned entrance, red railings and trees in front

II Cyber Warfare & Critical Infrastructure·Analysis·South Asia

In India, courts and the RBI, not policies, set banks' cyber burden

Police opened a case into the SBI breach 27 days on. Meanwhile the Supreme Court made negligent banks liable for full compensation and the RBI demanded API safeguards by 3 December. The cover pool is about 1,000 crore rupees and excludes state-backed attacks.

Cyber & Critical Infrastructure Desk · 14 November 2026 · 7 min read · 8 sources

Talay Insight Analysis DeskAI-assisted analysis, reviewed by an editorPublisher of record: Lu Apps LLCTrack recordRequest a correction

The Reserve Bank of India (RBI) headquarters in Mumbai. Photo taken 22 September 2024 (archive photo, illustrative)Photo: DesiBoy101 / Wikimedia Commons · CC BY 4.0 · resized · Source

Why it matters

The noise: headlines claiming data on 3.75 lakh SBI customers were stolen; the bank found personal data in 3,897 of roughly 375,000 records on the dark web. The signal: a Supreme Court interim order published on 7 November ties to RBI rules a requirement that a negligent bank compensate digital fraud victims by no less than the amount lost. The ceiling on Indian banks' cyber losses is now drawn by the courts and the regulator, not by insurance limits. And cover is narrowing exactly where India's threat profile lies: state-linked attacks.

Implications

  • Free Press Journal reports that SBI's Navi Mumbai IT centre went to the police on 12 November; the breach had been detected on 16 October, and as of 13 November there was no public record of notification to 3,897 customers.
  • LiveLaw reports that a 29 October Supreme Court interim order makes a negligent bank liable for compensation no less than the loss; the RBI's deadline for API safeguards is 3 December 2026.
  • Ken Research puts India's cyber premium pool at 900–1,100 crore rupees in FY2026; since 31 March 2023 Lloyd's has required state-backed attacks to be excluded from cover.

Noise

Data on 3.75 lakh SBI customers were stolen

Signal

The court makes negligent banks pay compensation equal to the loss

Signal vs Noise ›

Map: In India, courts and the RBI, not policies, set banks' cyber burden

The noise is the leak; the signal is the compensation rule

SBI's breach was back in the headlines in November. Free Press Journal reported on 13 November that the bank's Global IT Centre in Navi Mumbai approached police on 12 November, and CBD police station registered a case under 2 separate laws. The attacker entered the system on 9 October, exfiltrated data on 15 October, and the breach was detected on 16 October. The headline figure of 3.75 lakh customers is misleading. Business Today reports that SBI told the stock exchange on 21 October that a preliminary review of roughly 375,000 records found personal data in 3,897 customer records.

The real change is not the size of the leak but who carries the loss. In an interim order issued on 29 October and published on 7 November, the Supreme Court tied to forthcoming RBI rules a requirement that a bank found lacking in due diligence compensate victims of digital arrest fraud by no less than the amount lost. Digital arrest is a scam in which fraudsters pose as police on video calls and coerce victims into sending money. MediaNama reports that the RBI plans to bring the relevant KYC direction into force on 31 December.

1 · Constraint: liability is measured in rupees, cover in limits

The RBI is moving the same way. MediaNama reported on 6 November that a confidential RBI advisory dated 3 November demanded at least 1 additional layer of security for fund transfers made via APIs, with a deadline of 3 December for existing integrations. One banker said individual frauds range from 3 to 15 crore rupees. Read together, these 3 steps take the principle that customer losses land on the bank's balance sheet from paper into practice.

The insurance layer is not deep enough to carry that burden. Market research firm Ken Research puts India's cyber premium pool at 900–1,100 crore rupees in FY2026; typical bank limits are $50–100 million, and the average rate in 2025 was 0.62% of the limit. On Talay's arithmetic, a $100 million bank limit implies roughly $620,000 a year in premium. These figures come from a single commercial source and could not be verified against official IRDAI data. The direction is clear all the same: compensation liability is becoming open-ended while cover stays capped by limits.

2 · Threshold: the state-backed attack exclusion

The second constraint is the exclusion. Lloyd's market bulletin Y5381 of August 2022 requires standalone cyber policies renewed from 31 March 2023 to exclude state-backed attacks. The bulletin calls for a robust method of attributing an attack to a state and for exact alignment across reinsurance programmes. Wherever Indian insurers pass risk on to London, the exclusion travels down the chain.

India's threat profile sits squarely on that exclusion. A Lisianthus Tech report based on CERT-In data says there were roughly 15 lakh, or 1.5 million, attack attempts during Operation Sindoor in May 2025, and about 150 of them penetrated systems. The report links part of this activity to the Pakistan-linked APT36 group; the attribution has not been officially confirmed. If an attack on an Indian bank were attributed to the Pakistani state, the loss could fall outside cover, and the compensation liability would still sit with the bank.

3 · Second round: the cost moves to partners and customers

The first link in the chain is the 3 December deadline. API safeguards and transaction limits slow automated payment volumes at non-bank finance companies; the RBI says these customers must pass a CERT-In-empanelled audit by 3 February 2027. In the second link, banks seek higher limits at the 1 April renewals, while insurers tighten exclusions and vendor disclosure requirements. In the third, the cost of prevention and compensation passes to fintech partners as higher fees and fewer integrations.

4 · Falsifiers

Three developments would weaken this reading. If the RBI's 31 December direction caps compensation below the amount lost, the liability is bounded. If IRDAI or the large Indian insurers announce a dedicated pool or buy-back cover for state-backed attacks, the exclusion constraint eases. If SBI notifies the 3,897 customers and no compensation claims linked to the leaked data emerge, the first test case closes quietly.

Probabilities

Scenarios

ScenarioProbabilityTriggerMarket impact
H1The burden stays with the banks55%The RBI direction takes effect on 31 December with compensation tied to the amount lost, and insurance limits do not change.Banks step up spending on prevention and carry losses on balance sheet; demand for cyber cover grows but limits stay tight.
H2A major state-linked attack30%A Pakistan-linked group carries out a large, attributable attack on an Indian bank.The state-backed attack exclusion is triggered, the loss falls outside cover and the full compensation burden reverts to the bank.
H3The cover window widens15%IRDAI or the large insurers announce a pool or buy-back cover for state-backed attacks.Banks can transfer part of the risk, and the court ruling's balance-sheet impact is contained.

Module A

Constraints Matrix

STRUCTURAL AVG 4.3 · TACTICAL AVG 2.7Structural constraints dominate: the outcome is set more by these limits than by the actors' preferences.

Hard structural constraintspersistent · beyond the actors' will

  • Compensation tied to the amount lost · India

    5/5

    The Supreme Court's 29 October interim order ties to RBI rules a negligent bank's obligation to compensate victims by no less than the amount lost.

  • State-backed attack exclusion

    4/5

    Since 31 March 2023 Lloyd's bulletin Y5381 has required standalone cyber policies to exclude state-backed attacks, with exact alignment in reinsurance.

  • A shallow premium pool

    4/5

    Ken Research puts India's cyber premium pool at 900–1,100 crore rupees in FY2026; typical bank limits are $50–100 million.

Tactical frictiontemporary · eases over time

  • The 3 December API deadline weeks

    3/5

    The RBI's 3 November advisory requires an extra security layer for existing API integrations by 3 December 2026.

  • Notification delay weeks

    3/5

    SBI detected the breach on 16 October and went to the police on 12 November; there is no public record of notification to 3,897 customers.

  • Attribution uncertainty months

    2/5

    Part of the roughly 1.5 million attempts during Operation Sindoor is linked to Pakistan-linked APT36, but the attribution has not been officially confirmed.

Module B

Signal vs Noise

SIGNAL 60% · NOISE 40%

Module C

Asset-Class and Positioning Implications

Asset classExposureTransmission channelH1H2H3ExpectedConvictionHorizonWhat to watch
EquitiesIndian banking sectorCompensation liability and prevention costs raise operating expenses and the risk discount−−−+−1.00●●●3–12 monthsThe compensation clause in the RBI's 31 December KYC direction
CreditCredit spreads of Indian non-bank finance companiesAPI limits and CERT-In audits slow funding flows and transaction volumes−−−0−1.15●●●3–12 monthsThe 3 February 2027 CERT-In audit deadline
Freight & insuranceAsian cyber reinsurance capacityBanks' demand for limits and state-backed attack risk push renewal pricing higher+++−+1.00●●●3–12 monthsIndia's 1 April 2027 renewal pricing

How to read: ++ strong structural support · + support · 0 neutral · − pressure · −− strong pressure. “Expected” is the direction weighted by scenario probabilities. H1: The burden stays with the banks · H2: A major state-linked attack · H3: The cover window widens.

General, scenario-conditional analysis at asset-class level. It contains no specific security, price target or trade timing and is not personalised investment advice (Turkish Capital Markets Law No. 6362).

Second-order effects

And then what?

Starting point

The Supreme Court made negligent banks liable for compensation no less than the loss, and the RBI demanded extra security on API transfers by 3 December; the cyber premium pool is about 1,000 crore rupees.

  1. 1

    Payment systemwithin weeks

    To meet the 3 December deadline, banks impose limits, payee registration and dual approval on API transfers; automated payment volumes at non-bank finance companies slow.

    Watch: RBI compliance statements after 3 December and NPCI monthly transaction data

  2. 2

    Freight and insurancewithin months

    Banks facing larger compensation liabilities seek higher cyber limits at the 1 April renewals; insurers tighten the state-backed attack exclusion and vendor disclosure requirements.

    Watch: Indian insurers' 1 April 2027 renewal pricing and IRDAI cyber premium data

  3. 3

    Creditwithin months

    The cost of prevention and compensation passes to fintech and non-bank finance partners as higher fees and fewer integrations; funding costs rise for smaller players.

    Watch: The 3 February 2027 CERT-In audit deadline for non-bank finance companies and credit growth data

What breaks the chain

If the RBI's 31 December direction caps compensation below the amount lost, or Indian insurers set up a dedicated pool for state-backed attacks, the chain breaks at the second link.

Triggers

Thresholds to watch

IndicatorThresholdTodayWhat it means
VIX volatility index> 25—If global risk appetite sours, reinsurers cut cyber capacity, making it harder for Indian insurers to secure limits at the 1 April renewal

Sources

  1. Free Press Journal — Navi Mumbai cyberattack exposes alleged data theft of 3.75 lakh bank customers
  2. Business Today — 3.75 lakh records, 3,897 customers: SBI says data leaked in breach
  3. LiveLaw — Supreme Court on digital arrest cyber fraud and bank liability
  4. MediaNama — Supreme Court, WhatsApp and digital arrest
  5. MediaNama — RBI asks banks for extra security on API payments
  6. Ken Research — India Cyber Insurance Market
  7. Insurance Journal — Lloyd's insurers must exclude catastrophic state-backed cyber-attacks
  8. Free Press Journal — India saw 15 lakh cyberattack attempts during Operation Sindoor
Share

Sourcing and verification rules: methodology · Report an error: contact

Related reports