SEBI Cybersecurity and Cyber Resilience Framework (CSCRF) Explained

SEBI Cybersecurity and Cyber Resilience Framework (CSCRF) Explained
Table of Contents

SEBI CSCRF compliance means meeting a single consolidated cybersecurity and cyber resilience standard that applies across regulated entities in the securities market, replacing the scattered circulars that previously governed different categories of intermediaries. The framework is built on a simple idea: preventing an attack is only half the obligation. The other half is being able to detect it quickly, contain it, keep critical operations running, and restore normal service within a defined window. Compliance is demonstrated through documented governance, classified assets, tested controls, continuous monitoring, periodic audits and a reporting trail that an examiner can follow. This guide explains who it covers, what each requirement asks for in practice, and the checklist most firms work through before their first submission.

Who the Framework Covers

The framework applies to regulated entities across the securities market rather than to a single category. Stock brokers and depository participants, mutual funds and asset managers, registrars and transfer agents, investment advisers and research analysts, clearing corporations, depositories and stock exchanges all fall within scope, though not identically.

That last point is the one firms most often misread. Obligations are graded by size, client base, transaction volume and systemic importance. A large market infrastructure institution carries requirements that a small advisory firm does not. Before building any control, a firm needs to establish which category it sits in, because the entire compliance effort scales from that answer. Where a firm sits close to a threshold, it is safer to plan for the higher tier, since client growth can move it across the line mid-year.

Why Resilience Sits Alongside Security

Traditional cybersecurity guidance asked whether an entity had firewalls, antivirus, patching and access controls. Those remain necessary, but they answer only the prevention question.

Resilience asks a different set of questions. If an attacker succeeds despite the controls, how long before anyone notices? Which business functions must continue operating regardless? How quickly can clean systems be restored from backups that have themselves been verified as uninfected? Can the firm reconstruct what happened afterwards from its own logs?

In a market context this distinction is not theoretical. A trading platform that is unavailable during volatile hours causes measurable client harm even if no data was stolen. A settlement system that cannot reconcile positions creates downstream failures across counterparties. This is why market infrastructure cyber rules focus heavily on recovery timelines and continuity of critical functions, not only on breach prevention.

The SEBI CSCRF Compliance Checklist

The sections below follow the order most firms find workable. Each one should produce a document, a log or a test result, because compliance is evidenced rather than asserted.

Governance and Accountability

Appoint a senior officer with defined responsibility for information security, give that role direct reporting access to senior management, and record the reporting line formally. Form a committee that reviews security posture at a defined frequency, and minute those meetings. Approve a board-level cybersecurity policy and review it at least annually.

The common failure here is appointing a person without authority or budget. If the role cannot pause a system or block a deployment, it will not survive scrutiny.

Asset Inventory and Classification

Maintain a complete inventory of hardware, software, applications, databases, network devices and cloud services. Classify each asset by criticality to business operations, and classify data by sensitivity. Identify which systems support critical functions and must be restored first.

A firm cannot protect what it has not listed. Shadow systems — a spreadsheet tool, a legacy reporting server, a departmental cloud subscription — are almost always where gaps appear during audit.

Access Control and Authentication

Implement role-based access so that every user holds only what their function requires. Enforce multi-factor authentication for remote access, administrative accounts and any system handling client data. Review entitlements periodically and revoke access immediately on exit or role change.

Privileged accounts need separate treatment: individual credentials rather than shared ones, session logging, and time-bound elevation where possible.

Continuous Monitoring and Detection

Deploy centralised log collection with correlation and alerting. Monitor for unusual login behaviour, privilege escalation, large data transfers and configuration changes. Define what constitutes an alert worth escalating, and who receives it outside working hours.

Monitoring without a defined response path produces alert fatigue, which functions in practice as no monitoring at all.

Vulnerability Assessment and Testing

Conduct vulnerability assessments and penetration testing at the frequency applicable to the firm's category. Test systems that face the internet and those that hold client data. Track every finding through to closure with an owner and a date, and retest to confirm the fix.

Auditors examine the remediation record more closely than the scan report. An open critical finding from two cycles ago is a worse signal than the original vulnerability.

Incident Response and Reporting

Document an incident response plan that classifies severity, names decision-makers, sets internal escalation steps and specifies regulatory reporting obligations and timelines. Run tabletop exercises so the plan has been rehearsed before it is needed.

Reporting timelines matter. A delayed notification is treated as a separate failure from the incident itself, and firms have been penalised for the delay even where the breach was contained well. The systems discipline required here overlaps substantially with the broader fraud detection obligations brokers now carry, and teams that build one well usually find the other far cheaper.

Data Protection and Retention

Encrypt sensitive data at rest and in transit. Apply controls that limit unauthorised movement of client data out of the environment. Retain logs and records for the period prescribed, in a form that supports later reconstruction.

Backups deserve explicit attention. They should be isolated from the production network, tested by actual restoration rather than by checking that a job completed, and held in a manner that ransomware cannot reach.

Third-Party and Vendor Risk

Assess the security posture of technology vendors, cloud providers and outsourced service partners before onboarding and periodically thereafter. Include security obligations, audit rights and incident notification duties in contracts.

Outsourcing a function does not outsource the regulatory responsibility. When a vendor is breached, the regulated entity answers for it.

Audit, Reporting and Evidence

Conduct cyber audits at the prescribed frequency, submit reports in the required format and timeline, and retain the evidence underlying every assertion. Maintain a compliance register mapping each requirement to the control that satisfies it and the document that proves it.

This register is the single most useful artefact a compliance team can build. It converts an examination from a search exercise into a retrieval exercise.

Training and Awareness

Train staff on phishing recognition, credential hygiene, data handling and incident reporting. Train according to role, since a dealing desk, a technology team and a back-office function face different exposures. Record attendance and test retention.

Most successful intrusions still begin with a person, not a system.

Where Firms Commonly Fall Short

Three patterns recur.

The first is documentation that describes an intended state rather than the actual one. A policy saying logs are reviewed daily, in a firm where nobody reviews them, is worse than having no policy, because it establishes a standard the firm visibly failed to meet.

The second is treating compliance as an annual event. Controls drift. A new application goes live without being added to the inventory, an ex-employee's access survives for months, a vendor changes its hosting arrangement. By the next audit cycle the documented position and the real one have separated.

The third is ignoring the primary sources. The framework and its subsequent clarifications are published as formal circulars, and the specifics — thresholds, timelines, submission formats — are revised from time to time. Any internal checklist should be reconciled against the latest circular text before a submission, not against a summary written months earlier.

The Reputation Layer After a Cyber Incident

A cyber incident at a regulated financial firm does not stay a technical matter. It becomes a public one within hours, and what surfaces in search results afterwards is rarely the firm's own account.

Speculation spreads faster than confirmed facts. Impersonation attempts frequently follow a publicised breach, with fraudulent pages offering "compensation claims" or "account verification" to clients who are already anxious. Older coverage of the incident often outranks the firm's resolution statement for months.

Handling this well is partly a communications task and partly a legal one, since fraudulent impersonation and deliberately false claims may need formal removal action rather than a reply. Firms that have already mapped out how court-backed content removal works tend to move far faster when it becomes necessary, because the process is understood before the pressure arrives.

Frequently Asked Questions

Is SEBI CSCRF compliance mandatory for all intermediaries?

It applies across regulated entities, with obligations graded by size, client base and systemic importance rather than applied uniformly.

What is the difference between cybersecurity and cyber resilience?

Cybersecurity prevents incidents. Cyber resilience ensures detection, containment, continuity of critical functions and restoration when prevention fails.

How often should vulnerability testing be conducted?

Frequency depends on the firm's category under the framework and should be confirmed against the current circular before scheduling.

Who is accountable if a vendor causes a breach?

The regulated entity remains accountable. Outsourcing a function does not transfer the regulatory obligation to the service provider.

What is the most common audit finding?

Documented controls that do not match actual practice, followed closely by unclosed vulnerability findings from earlier testing cycles.

Closing Note

SEBI CSCRF compliance is less a technology project than an operating discipline. The firms that handle examinations comfortably are not necessarily the ones with the largest security budgets — they are the ones whose inventory is current, whose logs are actually reviewed, whose backups have been restored at least once, and whose documentation describes what genuinely happens. Build for the audit you would face on a random Tuesday, and the scheduled one stops being an event.

Share this article

Loading latest posts...