August 2025

SEBI Extends Cybersecurity Compliance

SEBI Extends Cybersecurity Compliance by Two Months Know It All

SEBI Extends Cybersecurity Compliance by Two Months Know It All INTRODUCTION SEBI Extends Cybersecurity Compliance timeline by two months, providing regulated entities (REs) with more time to put into place and strengthen their cybersecurity and cyber resilience framework. The action, as announced by the Securities and Exchange Board of India (SEBI), is crucial for stockbrokers, depositories, mutual funds, and other market intermediaries who are going the extra step to meet stringent security standards. This extension is not just a relief—it’s also a reminder. In today’s digital-first financial world, cyberattacks are becoming increasingly sophisticated. A well-defined cybersecurity compliance strategy is not optional; it’s essential. By extending the deadline, SEBI is providing breathing space to the industry, but it’s also sending a strong message: cybersecurity is a priority, and compliance is non-negotiable. Background: Understanding SEBI’s Cybersecurity Framework SEBI Extends Cybersecurity Compliance notice is among the efforts of a broader regulatory drive towards cybersecurity.  The framework introduces tough policies for: Infrastructure Security – All trading and investment infrastructure will be secured. Incident Response – Early detection, reporting, and remediation of cyber incidents. Data Protection – Securing investor data from breaches and leaks. Continuous Monitoring – 24/7 surveillance to detect vulnerabilities. Timeline of SEBI’s Cybersecurity Compliance Deadlines Initial Framework Release – SEBI first issued cybersecurity guidelines in 2015, evolving them over time. Mandatory Implementation Phase – Extended to various market participants in different phases. Original 2025 Deadline – Most companies were to comply by June 30, 2025. Extension Notice – SEBI Now Exts Cybersecurity Compliance deadline to August 31, 2025. This two-month extension may not be a great deal, but in the IT realm of infrastructure renewal and security scans, every week counts. Why SEBI Extends Cybersecurity Compliance Its reason for doing so is because of the following: Industry Readiness Gaps – The majority of entities informed that full implementation was still in progress. Complexity of Requirements – The framework involves multiple upgrades, audits, and employee training. Supply Chain Delays – Security hardware and software procurement faced delays. Integration Challenges – Aligning legacy systems with modern security tools takes time. SEBI’s Practical Approach – The regulator prefers enabling genuine compliance over forced, rushed adoption. By extending the SEBI Extends Cybersecurity Compliance deadline, the regulator ensures that the transition is both smooth and effective. Who Must Comply? The SEBI Extends Cybersecurity Compliance notice applies to all regulated entities, including: Stock Exchanges Depositories Clearing Corporations Stockbrokers Mutual Funds and Asset Management Companies (AMCs) Portfolio Managers Investment Advisors Research Analysts No sector participant dealing with sensitive investor data is exempt. Key Requirements of SEBI’s Cybersecurity Framework To meet the SEBI Extends Cybersecurity Compliance mandate, entities must: Conduct Risk Assessments – Determine weaknesses in infrastructure. Implement Security Controls – Firewalls, encryption, intrusion detection, etc. Regular Vulnerability Testing – Use VAPT (Vulnerability Assessment and Penetration Testing). Incident Response Plans – Develop detailed response plans for cyberattacks. Employee Awareness Training – Mitigate insider threat risk. Third-Party Risk Management – Vendors are not excluded. Real-Time Monitoring – Use Security Operations Centers (SOCs). Industry Impact of the Extension The SEBI Extends Cybersecurity Compliance update is helpful to the industry because of the following reasons: Extra Time for Complete Implementation – Refraining from early releases and potential loopholes. Improved Vendor Coordination – Including vendor specifications on third-party service providers too. Improved Testing – Extended time frame for security audits and penetration tests. Reduced Operating Stress – Enables companies to retain the level of service quality resulting from upgrading. Compliance Plan for New Deadline Below is the way market players can maximize this two-month window period: Gap Analysis – Determine what is lacking in your current infrastructure. Prioritize Critical Risks – Mitigate the most crucial security vulnerabilities first. Boost Monitoring Capabilities – Spend in newer SOCs and monitoring tools. Mock Drills – Conduct mock cyber attacks for readiness tests. Document Everything – Keep records of compliance proof for SEBI audits. Risks of Non-Compliance As SEBI Extends Cybersecurity Compliance deadline, failure to comply will have: Regulatory Penalties – Suspension and heavy fines. Damage to Reputation – Loss of investor confidence. Legal Action – When investor information is hacked. Reactions in the Industry Cybersecurity professionals have embraced the SEBI Extends Cybersecurity Compliance move more or less in unity. While almost everyone is on the same page that labeling the extension as necessary is what should be done, they suggest sloth will make end-of-period rushes inevitable, making the value useless. August 31, 2025 To-Do List Carry out thorough VAPT and patch all weaknesses. Activate multi-factor authentication to main systems. Get vendors aligned. Employee phishing detection training. Draft SEBI compliance reports. Conclusion The decision by SEBI to extend cybersecurity compliance by two months is more than just a grace period—it’s a strategic opportunity for market participants to strengthen their cyber defenses, align with regulatory expectations, and build lasting trust with investors. In today’s hyper-connected financial ecosystem, cybersecurity is not merely a regulatory checkbox; it is the backbone of operational resilience and investor confidence. By implementing this extension in the optimum way, companies can perform complete scans for vulnerabilities, introduce advanced threat detection tools, strengthen their talent pool, and become completely compliant with the SEBI cybersecurity framework. By doing this preventive action, compliance at the deadline is not only enabled but valuable information is safeguarded, costly breaches are prevented, and reputation in the market is established. SEBI Accelerates Cybersecurity Compliance to drive readiness, not hinder. The best-positioned firms will be made stronger, tougher, and better positioned to succeed in a more digitally oriented financial world. With cyber threats building at record velocity during an age of historic threat, this window is an opportunity to leapfrog patchwork compliance to the full mastery of cybersecurity. Disclaimer The contents of this blog SEBI Extends Cybersecurity Compliance are intended only for general information and education purposes. Even though all reasonable efforts have been made to confirm the facts stated and their publication as accurate and reliable, SEBI (Securities and Exchange Board of India) issued rules, regulations, and compliance requirements change and are

SEBI Extends Cybersecurity Compliance by Two Months Know It All Read More »

RBI .Bank.In Domain Mandate Explained: What Banks Must Do in 2026

RBI .Bank.In Domain Mandate Explained: What Banks Must Do in 2026 As digital banking becomes the default for millions of Indians, the Reserve Bank of India (RBI) has introduced a major update aimed at improving online safety the mandatory use of the “.bank.in” domain by all Indian banks. It might sound like a small technical change, but this shift carries huge significance for cybersecurity, customer trust, and how users identify legitimate banking websites. Let’s break it down simply and clearly. What Is “.bank.in”? The “.bank.in” domain is a new, restricted top-level domain that can only be used by banks licensed and regulated by the RBI. Unlike regular “.com” or “.in” domains, “.bank.in” is exclusive to verified Indian banks, ensuring that customers can easily identify authentic websites. This domain is managed and approved by the Institute for Development and Research in Banking Technology (IDRBT) the technology and cybersecurity arm of the RBI. The IDRBT ensures that only authorised banks can register for this secure domain, helping to eliminate fake or look-alike URLs that often lead to phishing scams. Why Did the RBI Introduce It? To Combat Rising Online Fraud: Digital payments have brought convenience but also risk. Fraudsters often create fake websites that mimic official bank portals. The RBI’s new mandate aims to stop this by giving banks a trusted, standardised online identity that’s easy for customers to recognise. To Strengthen Trust:When a user sees a URL ending with “.bank.in”, they can be confident it’s genuine. This reduces the chances of falling victim to phishing or spoofing attacks. To Modernise Banking Infrastructure: Globally, banks have been adopting restricted domains such as “.bank” to enhance security. By introducing “.bank.in”, the RBI is aligning Indian banking with international best practices while maintaining national oversight. What’s the Deadline — and Are There Penalties? According to the RBI’s directive (April 2025), all Indian banks must migrate to the “.bank.in” domain no later than October 31, 2025. So far, no extension or penalty framework has been publicly announced but non-compliance could attract regulatory scrutiny and reputational risks. Banks that haven’t started migration are expected to act immediately to ensure a smooth transition. For customers, this means that by late 2025, every genuine Indian bank’s official website should end with “.bank.in”. Role of IDRBT — The Technology Partner Behind the Change The Institute for Developement and research in Banking Technology (IDRBT), based in Hyderabad, plays a crucial role in making this transition successful. It acts as the official registrar for the “.bank.in” domain, authorised by the National Internet Exchange of India (NIXI) and MeitY IDRBT’s responsibilities include: Managing domain registration for RBI-approved banks. Providing technical guidance on DNS setup, SSL certificates, and safe redirects. Ensuring all registered domains follow strict cybersecurity standards. Offering support and documentation to help banks complete migration smoothly. For banks, engaging early with the IDRBT ensures they meet RBI’s compliance timeline and minimise operational disruptions during migration. How Does This Help Customers and Banks? For Customers: Quickly identify genuine banking websites. Reduced phishing risks. More secure digital transactions. For Banks: Improved trust and brand credibility. Enhanced compliance with RBI’s cybersecurity policy. Protection against fake domains and impersonation. The Bigger Picture The RBI’s “.bank.in” initiative isn’t just a technical change it’s a trust-building exercise. It creates a safer online environment where customers can confidently interact with banks, knowing their data is protected. For financial institutions, it’s a chance to modernise, secure their brand, and lead the way in a safer digital era for India’s banking ecosystem. At Lumiverse Solutions, we view it as a critical move toward a secure, transparent, and future-ready banking ecosystem. Need help migrating your bank domain securely? Partner with Lumiverse Solutions to ensure a smooth transition to “.bank.in”. Get Expert Assistance Learn more from official sources: RBI Circular and Economic Times. Frequently Asked Questions Is .bank.in mandatory for all banks? As of 2026, .bank.in is not universally mandatory for all banks. However, regulators strongly encourage secure and verified domain infrastructure to reduce phishing risks and strengthen digital trust. Many licensed banks are evaluating restricted banking domains as part of their cybersecurity and compliance strategy. Do fintechs have access to .bank.in domains? Restricted banking domains such as .bank.in are generally available only to licensed banking institutions that meet strict identity verification and regulatory compliance standards. Most fintech companies cannot register such domains unless they hold an approved banking license and meet regulatory authentication requirements. Won’t existing bank domains suffice? Traditional domains like .com or .in function normally but do not provide restricted registration controls. Specialized banking domains require enhanced ownership validation, DNS security standards, and stronger authentication measures, which significantly reduce impersonation and phishing risks. Is .bank.in secure? Yes. Restricted banking domains are designed with stricter security policies, including verified registration checks, DNSSEC implementation, and strong encryption requirements. These measures improve consumer trust and help financial institutions mitigate cyber fraud risks. Recent Posts February 14, 2026 7 Cybersecurity Gaps Regulators Flag During VAPT Audits February 10, 2026 Why Vendor Risk Is the Biggest Compliance Failure in 2026 February 3, 2026 Cybersecurity Compliance in 2026: Why Continuous Audits Have Replaced Annual Checks January 21, 2026 From CSCRF to DPDP: The Growing Link Between Cybersecurity and Data Privacy in 2026 December 12, 2025 SEBI CSCRF Audit: Why You Must Be Ready For 2026 December 6, 2025 Why Every Business Needs a Red Team Assessment | Strengthening Cybersecurity November 27, 2025 What Is IRDAI ISNP Audit? A Simple Guide for Insurers November 18, 2025 Understanding DPDP 2025 Rules: Key Changes, Compliance Requirements, and Next Steps November 1, 2025 Top 10 VAPT Best Practices for 2025: What Organisations Should Be Doing Now October 29, 2025 How to Get STQC GIGW 3.0 Certification | Complete Audit & Compliance Process Explained Categories Cyber Security Security Operations Center Cloud Security Case Study Technology Trends Don’t Let Cyber Risks Disrupt Your Business Growth Certified Cybersecurity & Compliance Experts: 12+ years of industry experience delivering VAPT, ISO 27001, SOC 2, and regulatory compliance aligned with global standards. Proven Real-World

RBI .Bank.In Domain Mandate Explained: What Banks Must Do in 2026 Read More »