The Reserve Bank of India (RBI) has heightened supervisory enforcement under its unified Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions. The comprehensive directive binds Scheduled Commercial Banks, Non-Banking Financial Companies (NBFCs), Urban Co-operative Banks, and Payment System Operators to rigorous governance standards. Crucially, the directions mandate that all cyber incidents must be formally reported within six hours of detection via the RBI's centralized DAKSH portal, with concurrent statutory disclosures to CERT-In.

The Six-Hour Incident Disclosure Clock & Multi-Tier Reporting

The mandatory six-hour window represents one of the most stringent regulatory reporting thresholds globally, aligning India's financial sector with national CERT-In mandates under Section 70B of the Information Technology Act. Regulated Entities (REs) must classify and escalate events according to their systemic severity.

RBI Regulatory Incident Escalation & Compliance Matrix

Milestone Timeline Required Regulatory Filing Supervisory Channel Statutory Penalty for Non-Compliance
T + 6 Hours Initial Incident Notification (root vector, affected systems, preliminary containment) DAKSH Portal & CERT-In Incident Form Supervisory audit action, business restrictions
T + 24 Hours Detailed Technical Update (IOCs, exfiltrated telemetry, forensic telemetry) RBI Cyber Security and IT Risk Cell (CSITE) Financial penalties up to ₹5 Crore under BR Act
T + 14 Days Comprehensive Post-Incident Review & Root Cause Analysis (RCA) Board IT Strategy Committee & RBI Panel Regulatory embargo on digital banking onboarding

Step-by-Step Technical Audit & SIEM Log Retention Playbook

Banking security teams must implement automated alerting and verification scripts to meet regulatory compliance:

  1. Automated DAKSH Incident JSON Dispatch Payload Validation:
    # Example validation script for RBI DAKSH incident submission schema
    import json, sys
    
    def validate_daksh_payload(payload_path: str):
        with open(payload_path, "r") as f:
            data = json.load(f)
        required = ["entity_pan", "incident_timestamp", "category", "blast_radius", "certin_ack_id"]
        missing = [k for k in required if k not in data]
        if missing:
            raise ValueError(f"DAKSH submission rejected: Missing fields {missing}")
        print("DAKSH schema validated successfully. Ready for submission.")
    
    if __name__ == "__main__":
        validate_daksh_payload(sys.argv[1])
  2. Verify 180-Day Immutable Log Retention in Cloud SIEM:
    # AWS S3: Verify Object Lock is ENABLED on financial SIEM log archive bucket
    aws s3api get-object-lock-configuration --bucket banking-siem-audit-logs
    
    # Output must report ObjectLockEnabled: Enabled with Compliance retention mode
  3. Automated SIEM Alert for Critical Infrastructure Outages:
    # Splunk / Elasticsearch query detecting CBS downtime exceeding 5 minutes
    index=banking_cbs sourcetype=transaction_engine status="FAILED" 
    | timechart span=5m count 
    | where count > 500

Board-Level Governance & Disaster Recovery Standards

Boards of Directors must establish an independent IT Strategy Committee chaired by an outside director, meeting at least quarterly. Core banking systems (CBS) must conduct unannounced live switchovers to secondary Disaster Recovery sites at least twice annually, proving recovery point objectives (RPO) within seconds and recovery time objectives (RTO) under two hours.