1 | Name of the directions | 0 |
10 | Payment cycle documentation and staged testing | 0 |
11 | External assessment of product process | 0 |
12 | Portfolio risk management processes | 0 |
13 | Security performance limits and indicators | 0 |
14 | Skilled payment staff and vendor oversight | 0 |
15 | Product risk assessment before and after launch | 0 |
16 | Ecosystem and control self assessment | 0 |
17 | Platform and architecture risk review | 0 |
18 | Internal controls before digital payment launch | 0 |
19 | Robust and scalable payment architecture | 0 |
2 | Date the directions take effect | 0 |
20 | Half-yearly backup recovery testing | 0 |
21 | Secure communication protocols and encryption | 0 |
22 | No sensitive data in client-side storage | 0 |
23 | Web application firewall and DDoS mitigation | 0 |
24 | Strong cryptography and approved standards | 0 |
25 | Timely renewal of digital certificates | 0 |
26 | Application logging and anomaly monitoring | 0 |
27 | Multi-tier application architecture | 0 |
28 | Secure by design development approach | 0 |
29 | Security objectives across the application lifecycle | 0 |
3 | Entities covered by the directions | 0 |
30 | Threat modelling in application lifecycle | 0 |
31 | Continuity cover for vendor licensed applications | 0 |
32 | Security testing of payment applications | 0 |
33 | Continuous automated vulnerability scanning | 0 |
34 | Vulnerability closure and no recurrence | 0 |
35 | Authenticated vulnerability scanning | 0 |
36 | Testing before production launch | 0 |
37 | Monitoring for fake and unauthorised apps | 0 |
38 | Server checks against non-genuine applications | 0 |
39 | Payment data handling and API security | 0 |
4 | Digital products and services in scope | 0 |
40 | Masking customer data in messages | 0 |
41 | Multi-factor authentication for digital payments | 0 |
42 | Design goals for multi-factor authentication | 0 |
43 | Optional adaptive authentication | 0 |
44 | Risk-based selection of authentication methods | 0 |
45 | Usability and interoperability of authentication | 0 |
46 | Authentication and alerts for all transactions | 0 |
47 | Merchant name in alerts and OTPs | 0 |
48 | Protection against interception attacks | 0 |
49 | Session integrity and termination | 0 |
5 | Meaning of defined terms | 0 |
50 | Limit on failed authentication attempts | 0 |
51 | Secure reactivation and failure notification | 0 |
52 | Configuration for suspicious behaviour detection | 0 |
53 | Monitoring parameters for system alerts | 0 |
54 | Fraud analysis and prevention | 0 |
55 | Fraud control staff training | 0 |
56 | Stakeholder contacts and incident SOPs | 0 |
57 | Real-time transaction reconciliation | 0 |
58 | Mandatory security guidance in payment apps | 0 |
59 | Grievance section and dispute timelines | 0 |
6 | Meaning of undefined expressions | 0 |
60 | Online dispute resolution per RBI circular | 0 |
61 | Customer education on device security | 0 |
62 | Pre subscription disclosure and no bundling | 0 |
63 | Communication on new operating features | 0 |
64 | Awareness of threats and precautions | 0 |
65 | Service only on customer request | 0 |
66 | In app fraud marking and reporting | 0 |
67 | Web application security controls | 0 |
68 | Mobile application security controls | 0 |
69 | Card payment security standards | 0 |
7 | Board approval and yearly policy review | 0 |
70 | Repeal of earlier digital payment directions | 0 |
71 | Savings for actions under repealed directions | 0 |
72 | Other laws remain in force | 0 |
73 | RBI clarification and interpretation powers | 0 |
8 | Payment security policy content requirements | 0 |
9 | Policy implementation ownership and review | 0 |