1 | Short title of the Directions | 0 |
10 | Payment cycle definition and staged sign-off | 0 |
11 | External assessment of product applications | 0 |
12 | Ongoing portfolio risk management | 0 |
13 | Performance monitoring and security risk limits | 0 |
14 | Trained resources and third-party oversight | 0 |
15 | Risk assessment before launch and periodically | 0 |
16 | Ecosystem assessment and control self-assessment | 0 |
17 | Technology and architecture risk review | 0 |
18 | Internal controls and operational risk before launch | 0 |
19 | Scalable architecture and periodic architecture review | 0 |
2 | Commencement on issuance | 0 |
20 | Half-yearly testing of backed-up data | 0 |
21 | Secure protocols and encryption in payment channels | 0 |
22 | No sensitive data in client-side storage | 0 |
23 | Web application firewall and DDoS mitigation | 0 |
24 | Strong cryptography and published standards | 0 |
25 | Timely renewal of digital certificates | 0 |
26 | Logging and monitoring in banking applications | 0 |
27 | Multi-tier application architecture | 0 |
28 | Secure by design development | 0 |
29 | Security objectives across lifecycle phases | 0 |
3 | Applicability to small finance banks | 0 |
30 | Threat modelling in lifecycle management | 0 |
31 | Source code escrow for vendor applications | 0 |
32 | Security testing of payment applications | 0 |
33 | Continuous automated vulnerability scanning | 0 |
34 | Vulnerability remediation tracking | 0 |
35 | Authenticated vulnerability scanning | 0 |
36 | Testing before production launch | 0 |
37 | Monitoring for fake applications | 0 |
38 | Server-side checks against unauthorised apps | 0 |
39 | Application security standards and API protection | 0 |
4 | Digital payment products and services in scope | 0 |
40 | Masking customer data in messages | 0 |
41 | Multi-factor authentication for payments | 0 |
42 | Robust multi-factor authentication design | 0 |
43 | Adaptive authentication by risk | 0 |
44 | Risk-based selection of authentication methods | 0 |
45 | Usability and performance of authentication | 0 |
46 | Authentication and alerts on transactions | 0 |
47 | Merchant name in alerts and OTPs | 0 |
48 | Protection against man-in-the-middle attacks | 0 |
49 | Session integrity and transaction resolution | 0 |
5 | Definitions of key security terms | 0 |
50 | Limit on failed authentication attempts | 0 |
51 | Reactivation of blocked access | 0 |
52 | Configuration for suspicious behaviour detection | 0 |
53 | Monitoring of fraud alert parameters | 0 |
54 | Fraud analysis and prevention | 0 |
55 | Fraud training for staff | 0 |
56 | Stakeholder contacts and incident procedures | 0 |
57 | Digital payment reconciliation framework | 0 |
58 | Mandatory secure usage guidance in apps | 0 |
59 | In-app grievance reporting and dispute timelines | 0 |
6 | Meaning of expressions not defined here | 0 |
60 | Online dispute resolution for digital payments | 0 |
61 | Customer education on device security | 0 |
62 | Pre-subscription risk and liability disclosure | 0 |
63 | Communication on new security features | 0 |
64 | Public awareness of payment threats | 0 |
65 | Customer-initiated digital payment enrolment | 0 |
66 | In-app fraudulent transaction marking | 0 |
67 | Internet banking security controls | 0 |
68 | Mobile payment application security controls | 0 |
69 | Adoption of PCI card payment standards | 0 |
7 | Board approval and annual review of policies | 0 |
70 | Repeal of earlier digital payment directions | 0 |
71 | Saving of actions under repealed directions | 0 |
72 | Other laws not barred | 0 |
73 | Power of RBI to interpret | 0 |
8 | Policy covering functionality, security and performance | 0 |
9 | Implementation responsibility and annual policy review | 0 |