India

RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators (2026)

58 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

58 controls 0 frameworks share controls with it India verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Authority for the Master Directions0
10Senior executive for security accountability0
11Key risk and performance indicators0
12IT assessment reports to oversight committee0
13Cyber risk assessment before product launch0
14Inventory management of assets, roles and data flows0
15Identity and access management0
16Network security and security operations monitoring0
17Application security life cycle (ASLC)0
18Security testing of applications0
19Vendor risk management0
2Official title of the Directions0
20Data security0
21Patch and change management life cycle0
22Incident response and reporting to RBI and CERT-In0
23Business continuity plan and disaster recovery drills0
24Application programming interface (API) security0
25Employee awareness and training0
26Cloud security0
27Other security measures: MFA, fraud monitoring, logs, anti-phishing, awareness0
28Online transaction alert mechanisms0
29Customer alerts: masking, transaction details and OTP placement0
3Commencement dates by PSO category0
30Customer facility to report fraud0
31Mobile payment security controls0
32Terminal validation for card payments0
33Card network limits alerts and data protection0
34Customer language choice for PPI alerts0
35Cooling period for loaded prepaid funds0
36Annual system audit report submission0
37Independence of the system auditor0
38System audit scope and coverage0
39Follow up of prior audit observations0
4Applicability to authorised PSOs0
40Reporting deviations from approved process flow0
41SAR placement and time bound closure0
42ASP contract cyber security mandate0
43Preventing access of unauthorised software at the ASP0
44Environmental controls at the ASP0
45Network management and security at the ASP0
46Secure configuration of ASP systems0
47Application security life cycle at the ASP0
48Patch, vulnerability and change management at the ASP0
49User access control and management at the ASP0
5Board approved policy for unregulated ecosystem entities0
50Data leak prevention strategy at the ASP0
51Audit logs at the ASP0
52Incident response and management at the ASP0
53Advanced real-time threat defence at the ASP0
54Vulnerability assessment and penetration testing at the ASP0
55Forensics and DDoS mitigation support at the ASP0
56Continuous surveillance through a cyber security operations centre at the ASP0
57Compliance with applicable security standards at the ASP0
58Repeal of earlier directions0
6Purpose of the Directions0
7Board oversight of cyber risk0
8Board approved information security policy0
9Cyber crisis management plan0

Tell me when RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators (2026) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators (2026), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition