Regulation · Banking and NBFCs · India
RBI cybersecurity directions 2026: what changed and what to do
The RBI cybersecurity directions 2026 are the Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions the Reserve Bank of India issued on 31 July 2026, one set per type of regulated entity. They took effect immediately, replace the 2016 cyber security framework, and require six-hour incident reporting through DAKSH.
What you need to know about RBI Cybersecurity Directions
Who must comply with the RBI cybersecurity directions?
RBI-regulated entities, each under the Directions written for its type.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What do the RBI cybersecurity directions require?
The RBI cybersecurity directions require Board-led technology governance with a CISO, baseline cybersecurity controls, a C-SOC, six-hour incident reporting, tested business continuity, managed third parties and independent IS audits.
Governance
Board, RMCB, IT Strategy Committee and CISO.
In QULDEX: Approvals and reviews trackedBaseline controls
Network, endpoint, access and crypto controls.
In QULDEX: Controls mapped to evidenceTesting cadence
VA every 6 months, PT every 12 months.
In QULDEX: Due dates on the dashboardSecurity operations
Continuous monitoring and metrics.
In QULDEX: SOC metrics trackedIncident reporting
Within six hours, plus CERT-In.
In QULDEX: Six-hour timersContinuity
DR drills for critical systems half-yearly.
In QULDEX: Drill results storedIS audit
Independent audit with tracked findings.
In QULDEX: Findings into CAPAWhich RBI cybersecurity requirements matter most?
These 19 requirement areas carry most of the work, grouped by theme. Select any one to see what it asks for, typical evidence and the matching ISO 27001 or CERT-In reference.
Showing up to 6 per group. Search, filter, or open a group to see all 19.
Governance 5
BoardBoard and committee oversightTechnology governance sits with the Board, the Risk Management Committee of the Board and the IT Strategy Committee, with senior management accountable.
In QULDEXCommittee reviews and approvals are recorded with dates.
- Typical evidence
- Board and committee minutes
- Maps to
- ISO 27001 5.1
PoliciesBoard-approved policiesBoard-approved IT, information security and cybersecurity policies, reviewed periodically.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Approved policies
- Maps to
- ISO 27001 A.5.1
CISOChief Information Security OfficerA CISO with defined responsibilities, reporting to the executive overseeing risk management.
In QULDEXThe CISO's role, reporting line and reports are on record.
- Typical evidence
- CISO appointment
- Maps to
- ISO 27001 5.3
ISCInformation Security CommitteeA committee that oversees information security and cyber risk across the entity.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Committee minutes
IT riskIT and cyber risk managementIdentify, assess and treat IT and cyber risks as part of enterprise risk management.
In QULDEXThe risk register holds IT and cyber risks with treatment owners.
- Typical evidence
- Risk register
- Maps to
- ISO 27001 6.1
Controls and testing 6
BaselineBaseline cybersecurity controlsMinimum controls for network, endpoint, application and data security.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Control evidence
- Maps to
- ISO 27001 Annex A
AccessUser access managementLeast privilege, privileged access controls and periodic access reviews.
In QULDEXAccess reviews run as recurring tasks.
- Typical evidence
- Access reviews
- Maps to
- ISO 27001 A.5.15–A.5.18
CryptoCryptographic controlsEncryption and key management for data at rest and in transit.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Crypto policy, key records
- Maps to
- ISO 27001 A.8.24
VAVulnerability assessment every six monthsFixed cadenceRun vulnerability assessments at least every six months and fix findings.
In QULDEXScan findings become CAPA items with due dates.
- Typical evidence
- VA reports
- Maps to
- ISO 27001 A.8.8
PTPenetration testing every twelve monthsFixed cadenceRun penetration tests at least every twelve months.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- PT reports
DataData protectionProtect customer and business data across its lifecycle.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Data protection evidence
- Maps to
- DPDP Act
Operations and resilience 6
C-SOCCyber Security Operations CentreContinuous monitoring through a C-SOC with defined use cases and metrics.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- SOC reports
- Maps to
- ISO 27001 A.8.16
IncidentsIncident reporting within six hoursFixed cadenceReport cyber incidents within six hours of detection through RBI's DAKSH platform, and notify CERT-In.
In QULDEXIncidents carry six-hour reporting timers.
- Typical evidence
- Incident reports
- Maps to
- CERT-In Directions 2022
CrisisCyber crisis managementA cyber crisis management plan with response and recovery playbooks.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Crisis management plan
BCP/DRBusiness continuity and DR drillsFixed cadenceBusiness continuity and disaster recovery, with DR drills for critical systems at least half-yearly.
In QULDEXDrill schedules and results are tracked.
- Typical evidence
- DR drill reports
- Maps to
- ISO 22301
Third partiesThird-party arrangementsManage risks from IT outsourcing and third-party service providers, with audit and access rights.
In QULDEXEach provider is assessed and linked to the services it supports.
- Typical evidence
- Vendor assessments
- Maps to
- ISO 27001 A.5.19–A.5.22
MetricsCybersecurity metrics and awarenessTrack cybersecurity metrics and run employee and customer awareness programmes.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Metrics, training records
Assurance 2
IS auditInformation Systems AuditIndependent IS audits of IT systems and controls, with findings tracked to closure.
In QULDEXIS audit findings flow into CAPA.
- Typical evidence
- IS audit reports
- Maps to
- ISO 27001 9.2
PaymentsDigital Payment Security Controls DirectionsA separate set of Directions issued the same day requires a board-approved policy for digital payment products and specific security controls.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and maps it to ISO 27001 and SEBI CSCRF.
- Typical evidence
- Digital payments policy
Nothing matches that search.
Areas summarise the 31 July 2026 Directions as published; exact paragraphs differ by entity type. Summaries are QULDEX paraphrases, not legal advice; your entity's Directions are the authority.
How do you comply with the RBI cybersecurity directions?
Read the Directions for your entity type, map them against your existing controls, close the gaps and evidence the new cadences. Because they applied immediately, most entities run this as a 3 to 6 month remediation programme.
Identify your Directions
Confirm which entity-specific Directions apply and to which group entities.
Map against current controls
Compare with your 2016-framework and 2023 IT governance controls to find what is new.
Fix governance
Board and committee mandates, CISO reporting line and policy approvals.
Set up the new cadences
VA every six months, PT every year, half-yearly DR drills and six-hour reporting through DAKSH.
Third parties and digital payments
Reassess providers and align digital payment products with the companion Directions.
Assure and report
Every 6 monthsVA and DR drillsEvery yearPT and policy reviewEvery incidentReport within 6 hours
The Directions took effect on 31 July 2026. Durations are QULDEX planning ranges.
Which documents do the RBI directions need?
Supervisors and IS auditors will ask for these records.
| Document | Area | Where it lives in QULDEX |
|---|---|---|
| Board-approved IT, IS and cybersecurity policies | Policies | Policy library |
| Board, RMCB and ITSC minutes | Governance | Policy library |
| CISO appointment and reports | CISO | Policy library |
| IT and cyber risk register | IT risk | Risk register |
| VA and PT reports with closure | VA, PT | CAPA automation |
| C-SOC reports and metrics | C-SOC | Evidence vault |
| Incident reports to RBI and CERT-In | Incidents | CAPA automation |
| BCP and DR drill reports | BCP/DR | Evidence vault |
| Third-party assessments and contracts | Third parties | Vendor register |
| IS audit reports | IS audit | Audit workspace |
Document names are QULDEX recommendations based on the Directions.
How long does RBI compliance take and what drives the effort?
Entities that met the 2016 framework typically need 3 to 6 months to close new gaps. Governance changes, new testing cadences and third-party reassessment drive most of it.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Entity type: requirements differ by Directions
- Group entities: each regulated entity needs its own evidence
- Critical systems: each needs DR drills
- Providers: every outsourcing arrangement is reassessed
- Existing ISO 27001: covers much of the baseline
How ready are you for the RBI cybersecurity directions?
Check these eight things first. Nothing you enter leaves this page.
How the RBI directions map to SEBI CSCRF, CERT-In and ISO 27001
Many groups are regulated by both RBI and SEBI, and every entity follows CERT-In. One control set mapped to all three avoids collecting evidence twice.
India cybersecurity crosswalk
| RBI Directions 2026 | SEBI CSCRF | CERT-In Directions | ISO 27001:2022 | Shared evidence |
|---|---|---|---|---|
| Board and ITSC | GV.RR, GV.OV | — | 5.1 | Minutes |
| CISO | GV.RR | Point of contact | 5.3 | Appointments |
| VA and PT | ID.RA | — | A.8.8 | Test reports |
| C-SOC | DE.CM | Logs for 180 days | A.8.15–A.8.16 | SOC reports |
| 6-hour incident reporting | RS.MA | 6-hour reporting | A.5.24–A.5.26 | Incident reports |
| BCP and DR drills | RC.RP | — | A.5.29–A.5.30 | Drill reports |
| Third parties | GV.SC | — | A.5.19–A.5.22 | Vendor assessments |
Indicative mapping for planning, not legal advice. RBI vs SEBI requirements are compared in full on the blog.
How QULDEX runs RBI compliance from mapping to IS audit
QULDEX is RBI cybersecurity compliance and audit management software built from EGV Group's audit delivery, used by banks and NBFCs, their advisors and the IS auditors who test them. Pick your role to see who does what.
For RBI-regulated entities.
- ScopeConfirm your DirectionsApplicable Directions per entity
- GovernSet mandatesBoard and committee records
- ControlsClose gapsRequirements mapped to evidence
- CadencesRun VA, PT and drillsDue dates and results tracked
- IncidentsReport within six hoursSix-hour timers per incident
- AssureHost the IS auditControlled evidence sharing
For RBI compliance consultants and internal audit.
- ScopeRun the gap assessmentA reusable RBI 2026 gap template
- GovernBrief the boardBoard-ready reports
- ControlsReview evidenceReview and approval states
- CadencesTrack cadenceCadence dashboard
- IncidentsAdvise on reportingDecision record per incident
- AssurePrepare the packAn audit-ready pack
For independent information systems auditors.
- ScopePlanScope in a standard format
- GovernReview governanceView-only access to minutes
- ControlsSample evidenceView-only evidence with download control and an access log
- CadencesVerify testsRetest evidence
- IncidentsReview incidentsIncident history with audit trail
- AssureAuditFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →RBI Cybersecurity Directions questions people ask
What did RBI issue on 31 July 2026?
The Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, one set for each type of regulated entity, plus Digital Payment Security Controls Directions. They took effect immediately.
What happened to the 2016 cyber security framework?
The 2026 Directions replaced it, together with earlier IT governance and cybersecurity circulars, as part of RBI's consolidation of instructions.
What is the RBI cyber incident reporting timeline?
Cyber incidents must be reported within six hours of detection through RBI's DAKSH platform, with notification to CERT-In.
How often are VA and PT required?
Vulnerability assessments at least every six months and penetration tests at least every twelve months; DR drills for critical systems at least half-yearly.
Do the Directions apply to NBFCs?
Yes. NBFCs have their own Directions, with applicability depending on their regulatory layer and asset size.
Go deeper on RBI Cybersecurity Directions
References
- RBI Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 31 Jul 2026 (entity-wise). rbi.org.in
- RBI Digital Payment Security Controls Directions, 31 Jul 2026. rbi.org.in
- KPMG India, RBI's technology-focused master directions, Sep 2026. kpmg.com/in
- CERT-In Directions under Section 70B(6), 28 Apr 2022. cert-in.org.in
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Page first built on the 31 July 2026 Directions: requirement explorer, cadences, six-hour reporting and readiness check
Close the gaps the 2026 Directions opened
Answer a short readiness check and get a gap summary by area. No sales call needed to see the result.