SEBI's CSCRF, what it asks of regulated entities
Work out which category you fall in, see the standards that apply, and keep the evidence your cyber audit will ask for.
Official sources
Use SEBI's own pages to read the circular and the full framework document.
Official website
SEBI's circular page for the Cybersecurity and Cyber Resilience Framework. The full framework is attached as a PDF.
Visit sebi.gov.in ↗Get the document
SEBI publishes the circular and the framework free of charge on sebi.gov.in under Legal, then Circulars. Check the same section for any later clarifications or extensions.
Open the official page ↗Works alongside
ISO 27001, NIST CSF and the CIS Controls cover similar ground. The framework itself points to ISO 27000, CIS and NIST sources.
Browse all frameworks →What CSCRF is
The Cybersecurity and Cyber Resilience Framework, known as the CSCRF, is SEBI's single rulebook for cybersecurity at the entities it regulates. It replaces earlier SEBI cybersecurity circulars, guidelines and advisories.
It uses a graded approach. Larger entities such as market infrastructure institutions face more standards than small ones, and smaller entities are expected to join a shared Market SOC. SEBI issued it under Section 11(1) of the SEBI Act, so it is binding on the entities it names.
How CSCRF got to where it is today
The milestones that changed what organisations have to do.
First framework for market infrastructure
SEBI issues a cybersecurity and cyber resilience framework for market infrastructure institutions. Similar frameworks follow for other entity types.
Cyber SOC for exchanges and depositories
A circular dated 7 December 2018 requires stock exchanges, clearing corporations and depositories to run a 24x7 cyber security operations centre, with exceptions for commodity derivatives exchanges.
CSCRF version 1.0
SEBI issues the CSCRF on 20 August 2024. It supersedes the earlier cybersecurity circulars, guidelines and advisories.
First deadline
The circular set 1 January 2025 for the six categories that already had a cybersecurity circular. Check SEBI's site for any later extension.
Second deadline
The circular set 1 April 2025 for other entities receiving a framework for the first time. Cyber audits follow under the CSCRF timelines.
Dates are for orientation. The official website holds the authoritative record.
Do you need it?
If any of these sound familiar, probably yes.
You are a stock broker, depository participant, mutual fund, investment adviser, portfolio manager or another entity SEBI regulates.
You run systems that hold investor data or support trading and settlement.
You rely on cloud, SaaS or outsourced providers for core activities.
You need to prepare for a CERT-In empanelled auditor's cyber audit.
What it asks of you
The standards fall into six areas that follow the framework's cybersecurity functions.
Governance
Clear ownership, an approved policy, a CISO or designated officer, and risk and supplier oversight.
Identify
Know your assets, data flows and vulnerabilities, and use threat intelligence.
Protect
Access control, encryption, secure development, backups, patching and training.
Detect
Round-the-clock monitoring through a SOC, plus testing of detection.
Respond and recover
Crisis management plan, incident reporting to SEBI and CERT-In, and recovery drills.
Evolve and audit
Adapt after incidents, report on the Cyber Capability Index where it applies, and complete cyber audits.
The 7 areas, 23 categories and 128 standards of the CSCRF
The framework groups its standards under governance and five cyber resilience functions, then adds an Evolve goal. Which standards apply to you depends on your entity category, and some are mandatory only for larger entities.
23 categorys · 128 standards
GVGovernanceWho is accountable, which policy applies and how cyber risk is run.6 categorys · 30 standards
GV.OCOrganizational contextKnow the services you must deliver, the rules you must follow and the outside parties you rely on.3 standards
- GV.OC.S1
Understand and communicate the critical services and objectives that outside parties expect from you.
What you do
- List the services clients and markets depend on
- Share the list with senior management and key partners
- GV.OC.S2
Understand and manage the legal and regulatory requirements on cybersecurity, data protection and privacy.
What you do
- Keep a register of applicable rules with an owner for each
- Review the register whenever SEBI or CERT-In issues new directions
- GV.OC.S3
Understand and communicate which outcomes and services depend on external resources such as third-party providers.
What you do
- Map each critical service to the providers behind it
- Record which provider failures would stop a service
Evidence to keep
- Register of critical services
- Register of cybersecurity and data protection obligations
- List of key third parties
GV.RRRoles, responsibilities and authoritiesMake cybersecurity accountability clear from the top down.6 standards
- GV.RR.S1
Leadership owns cybersecurity risk and builds a risk-aware culture that keeps improving.
What you do
- Put cyber risk on the regular board or partners agenda
- Have leaders approve the yearly cyber priorities
- GV.RR.S2
Develop, communicate, understand and enforce cybersecurity roles, responsibilities and authorities.
What you do
- Write a role matrix covering IT, security, business teams and vendors
- Add security duties to job descriptions
- GV.RR.S3
Appoint a CISO or designated officer who reports to a named authority.
What you do
- Name the officer in writing
- Record the reporting line
- GV.RR.S4
Align budget planning with information security and privacy goals and give them enough resources.
What you do
- Link the security budget to the risk register
- Keep a note of how resources were sized
- GV.RR.S5
Allow staff and third parties onto information systems only after they sign a confidentiality and integrity agreement.
What you do
- Add confidentiality terms to onboarding
- Block account creation until the agreement is signed
- GV.RR.S6
Include cybersecurity in human resources training programmes.
What you do
- Add a security module to induction
- Track completion by person
Evidence to keep
- Role and responsibility matrix
- CISO or designated officer appointment record
- Security training records
GV.POPolicyA written, approved cyber policy that stays current.5 standards
- GV.PO.S1
Document and implement a cybersecurity and cyber resilience policy approved by the Board, partners or proprietor, covering the framework's standards and guidelines.
What you do
- Write the policy against the framework's standards
- Minute the approval
- GV.PO.S2
Review the cybersecurity and cyber resilience policy periodically.
What you do
- Set a yearly review date
- Log every change
- GV.PO.S3
Set a policy for managing cyber risk based on your context, strategy and priorities, then communicate and enforce it.
What you do
- Publish it to staff
- Ask staff to confirm they have read it
- GV.PO.S4
Review and update the risk policy as requirements, threats and technology change.
What you do
- Trigger a review after a major incident or system change
- Keep a change history
- GV.PO.S5
Define an owner and custodian for every asset and a clear chain of command for approvals.
What you do
- Add owner and custodian columns to the asset register
- Document who approves access and changes
Evidence to keep
- Approved cybersecurity and cyber resilience policy
- Policy review log
- Asset ownership list
GV.OVOversightUse results to steer the cyber programme, including the Cyber Capability Index where it applies.4 standards
- GV.OV.S1
Review the outcomes of the cyber risk strategy to inform and adjust direction.
What you do
- Hold a review each quarter
- Record decisions and actions
- GV.OV.S2
Adjust the risk strategy so it covers organisational needs and risks.
What you do
- Compare the strategy to the latest risk register
- Update priorities that no longer fit
- GV.OV.S3
Evaluate and review how well cyber risk management is performing.
What you do
- Track a few simple measures such as open vulnerabilities and incident counts
- Report them to management
- GV.OV.S4
Assess cyber resilience with the Cyber Capability Index on a periodic basis, where it applies to your category.
What you do
- Check whether your entity category must report the index
- Plan the evidence needed for each index domain
Evidence to keep
- Management review minutes
- Cyber Capability Index submissions where applicable
- Security metrics pack
GV.RMRisk managementRun a documented cyber risk process with an appetite statement and a risk register.4 standards
- GV.RM.S1
Prepare a cyber risk management framework to identify, assess, mitigate and monitor risks, with objectives agreed by stakeholders.
What you do
- Write the method for rating and treating risks
- Get stakeholders to agree the objectives
- GV.RM.S2
Include cybersecurity activities and outcomes in your wider risk management processes.
What you do
- Feed cyber risks into the enterprise risk register
- Report them alongside other risks
- GV.RM.S3
Document different scenarios and responses and test them periodically to check the risk plan.
What you do
- Run a tabletop exercise each year
- Record the lessons and fixes
- GV.RM.S4
Set, communicate and maintain risk tolerance and appetite statements and keep a risk register reviewed by the IT Committee for REs.
What you do
- Write a short appetite statement
- Put the register on the IT Committee agenda
Evidence to keep
- Cyber risk management framework
- Risk register with review dates
- Scenario test reports
GV.SCSupply chain risk managementManage the risks that come from the suppliers and software you rely on.8 standards
- GV.SC.S1
Identify, establish, assess, manage and agree a cybersecurity supply chain risk management process with stakeholders.
What you do
- Write a supplier risk process
- Agree it with business owners
- GV.SC.S2
Identify, prioritise and assess suppliers and third-party providers with a supply chain risk assessment.
What you do
- Rank suppliers by how critical they are
- Assess the top tier first
- GV.SC.S3
Include measures in supplier contracts that support your cybersecurity programme, including enough cybersecurity manpower.
What you do
- Add security clauses to contract templates
- Ask providers to confirm staffing for your account
- GV.SC.S4
Monitor and review compliance of providers that perform critical activities, on a periodic basis.
What you do
- Request regular service and security reports
- Review them at set dates
- GV.SC.S5
Obtain a software bill of materials for new software used in core and critical activities and keep it updated, with approval from the Board, partners or proprietor for legacy exceptions.
What you do
- Ask vendors for an SBOM in the purchase process
- Record approved exceptions with the reason and limits
- GV.SC.S6
Run response and recovery planning and testing together with third-party providers.
What you do
- Invite key providers to incident and recovery exercises
- Record joint actions
- GV.SC.S7
Assess and review concentration risk on outsourced agencies to support operational resilience.
What you do
- List services that rely on a single provider
- Plan an alternative for the riskiest ones
- GV.SC.S8
Require third-party providers to follow similar information security standards.
What you do
- State the expected standards in contracts
- Collect proof such as audit reports or certificates
Evidence to keep
- Supplier risk assessments
- Contract clauses on cybersecurity
- Software bills of materials
- Concentration risk review
IDIdentifyKnow what you have and what could go wrong.2 categorys · 11 standards
ID.AMAsset managementKeep a complete, current inventory of assets, data and data flows.6 standards
- ID.AM.S1
Inventory physical devices, digital assets such as URLs, domains, applications and APIs, shared and cloud resources, and interfacing systems, in a time-bound manner.
What you do
- Use discovery scans to find assets
- Set a date by which the inventory is refreshed
- ID.AM.S2
Map and inventory communications, data flows and encryption methods across IT systems and network resources.
What you do
- Draw data flow diagrams for critical systems
- Note the encryption used on each link
- ID.AM.S3
Make sure no shadow IT assets exist in the organisation.
What you do
- Compare network scans with the inventory
- Remove or register unknown assets
- ID.AM.S4
Have the Board, partners or proprietor approve the list of critical systems.
What you do
- Prepare the list with business owners
- Record the approval
- ID.AM.S5
Maintain inventories of data and the related metadata for designated data types.
What you do
- Record where each data type lives and who owns it
- Review the inventory yearly
- ID.AM.S6
Manage all inventoried IT assets and data through their full lifecycle.
What you do
- Track purchase, change and disposal dates
- Remove assets that are retired
Evidence to keep
- Asset inventory including cloud, domains, URLs and APIs
- Data flow and encryption map
- List of critical systems approved by the Board or partners
ID.RARisk assessmentUnderstand the risk to your assets and use threat information to act on it.5 standards
- ID.RA.S1
Identify, validate and document asset vulnerabilities and assess risk factors for all IT assets.
What you do
- Run regular vulnerability scans
- Log each finding with an owner and rating
- ID.RA.S2
Assess the risk of the IT environment on a periodic basis, including post-quantum risks.
What you do
- Run a risk assessment at least yearly
- Add quantum readiness as a line item
- ID.RA.S3
Receive cyber threat intelligence from trusted sources, join the CERT-In intelligence platform and act on CERT-In and CSIRT-Fin advisories promptly.
What you do
- Register for the CERT-In platform
- Track each advisory to closure
- ID.RA.S4
Use threats, vulnerabilities, likelihood and impact to understand inherent risk and prioritise responses, with attention to access and authentication.
What you do
- Score risks on likelihood and impact
- Rank access and login risks highly
- ID.RA.S5
Choose, prioritise, plan, track and communicate risk responses.
What you do
- Keep a treatment plan for each high risk
- Report progress to management
Evidence to keep
- Vulnerability scan and assessment records
- Periodic IT risk assessment report
- Threat intelligence and advisory log
PRProtectControls that keep systems and data safe day to day.5 categorys · 48 standards
PR.AAIdentity, authentication and access controlLimit access to the right people, devices and processes and log what they do.17 standards
- PR.AA.S1
Issue, manage, verify, revoke and audit identities and credentials for authorised devices, users and processes.
What you do
- Run joiner, mover and leaver steps through one process
- Audit accounts every quarter
- PR.AA.S2
Protect network integrity, for example through segregation and segmentation.
What you do
- Separate production, office and guest networks
- Review firewall rules on a schedule
- PR.AA.S3
Grant access on the principle of least privilege with segregation of duties, on premises and in the cloud.
What you do
- Give role-based access by default
- Keep duties split for sensitive tasks
- PR.AA.S4
Follow a Zero Trust model when allowing people, devices and resources to reach your resources.
What you do
- Verify user and device on each request
- Remove implicit trust inside the network
- PR.AA.S5
Review and document access rights periodically and use a maker-checker process for granting, revoking and changing rights.
What you do
- Run a regular access review
- Require a second approver for changes
- PR.AA.S6
Document and implement an authentication policy, with strength matched to the risk of the transaction.
What you do
- Define when single factor or multi-factor is required
- Prove identity before issuing credentials
- PR.AA.S7
Use multi-factor authentication on all critical systems for users connecting from an untrusted to a trusted network.
What you do
- Turn on MFA for remote and admin access
- Report any exceptions
- PR.AA.S8
Document and implement a log management policy.
What you do
- State which logs are kept and for how long
- Name an owner for log review
- PR.AA.S9
Identify user logs uniquely and store them for a specified period.
What you do
- Use named accounts rather than shared ones
- Set retention in the policy
- PR.AA.S10
Manage, monitor and protect physical access, record access to critical systems continuously and screen people before they get access.
What you do
- Keep visitor and entry logs for server areas
- Run background checks before granting access
- PR.AA.S11
Review privileged user activity periodically and limit employee and third-party access to what is needed, for a limited time and under close supervision.
What you do
- Review admin session logs
- Time-box vendor access
- PR.AA.S12
Track and administer remote access to assets strictly.
What you do
- Approve and log remote sessions
- Disable unused remote access
- PR.AA.S13
Document and implement a data disposal and data retention policy.
What you do
- Set retention periods by data type
- Record secure disposal
- PR.AA.S14
Document standard procedures for handling and disposing of storage media.
What you do
- Write a media handling procedure
- Keep disposal certificates
- PR.AA.S15
Define and implement access control for endpoints, networks, APIs, removable media, laptops and mobiles.
What you do
- Control USB and removable media use
- Enforce device policies
- PR.AA.S16
Vet mobile applications against security requirements and test them before deployment.
What you do
- Run security tests before each release
- Record the sign-off
- PR.AA.S17
Define and implement API security with proper authentication and authorisation.
What you do
- Require tokens or keys on every API
- Apply rate limits and review API access
Evidence to keep
- Access control policy and review records
- Authentication policy
- Log management policy
- Privileged access reviews
- Remote access records
PR.ATAwareness and trainingGive people the knowledge to do their security duties.5 standards
- PR.AT.S1
Run mandatory, periodic awareness programmes on cybersecurity, cyber resilience and system hygiene, updated for new threats.
What you do
- Run yearly training and phishing tests
- Refresh content as threats change
- PR.AT.S2
Make sure privileged users understand their roles and responsibilities.
What you do
- Give admins extra training
- Record acknowledgement
- PR.AT.S3
Make sure third-party stakeholders such as suppliers, customers, investors and partners understand their roles and responsibilities.
What you do
- Share short security guidance with suppliers
- Include it in onboarding packs
- PR.AT.S4
Make sure senior executives and Board members understand their roles, with a dedicated programme for the Board.
What you do
- Brief the Board on cyber risk each year
- Keep attendance records
- PR.AT.S5
Make sure physical and information security personnel understand their roles and responsibilities.
What you do
- Provide role-specific training
- Test understanding with short quizzes
Evidence to keep
- Awareness programme plan and attendance records
- Role-based training records
- Board training record
PR.DSData securityProtect data at rest, in transit and in the right location.6 standards
- PR.DS.S1
Protect data at rest and in transit with industry-standard encryption, and for market infrastructure institutions explore protection of data in use.
What you do
- Encrypt disks, databases and links
- Retire weak algorithms
- PR.DS.S2
Classify data into Regulatory Data and IT and Cybersecurity Data and keep both available and readable within India.
What you do
- Tag datasets by class
- Confirm storage locations and exceptions with your cloud and SOC providers
- PR.DS.S3
Maintain enough capacity to keep data available.
What you do
- Track storage and processing headroom
- Plan upgrades before limits
- PR.DS.S4
Put measures and tools in place against data leaks.
What you do
- Deploy data leak prevention rules
- Review alerts regularly
- PR.DS.S5
Keep development and test environments separate from production, with at least one non-production environment to test critical software before release.
What you do
- Block developer access to production data
- Test every critical release first
- PR.DS.S6
Use integrity mechanisms to verify software, firmware and information in critical systems, for market infrastructure institutions.
What you do
- Use file integrity monitoring
- Sign and verify releases
Evidence to keep
- Encryption standards and configuration records
- Data classification scheme
- Data leak prevention records
- Environment separation diagram
PR.IPInformation protection processes and proceduresThe configuration, development, backup and assurance processes that hold protection together.17 standards
- PR.IP.S1
Create and maintain a baseline configuration for IT systems based on security principles such as least functionality.
What you do
- Publish hardening standards
- Check systems against them
- PR.IP.S2
Implement a system development life cycle to manage systems.
What you do
- Add security steps to each stage
- Keep design and test records
- PR.IP.S3
Put in place configuration change control and change management.
What you do
- Log, approve and review every change
- Keep a rollback plan
- PR.IP.S4
Scan critical software and applications thoroughly to make sure no malicious code is present.
What you do
- Run code and malware scans before release
- Store the results
- PR.IP.S5
If you do not own the source code, get an undertaking from the provider that the software is free of known vulnerabilities, malware, malicious code and covert channels.
What you do
- Ask vendors for a signed statement
- Re-request after major upgrades
- PR.IP.S6
Test or certify software so that it works only as intended, follows secure design and coding practice and addresses known flaws.
What you do
- Run security tests aligned to secure coding standards
- Fix issues before go-live
- PR.IP.S7
Document a backup and recovery plan so that no data is lost.
What you do
- Define what is backed up and how often
- Name the owner
- PR.IP.S8
Implement, test and maintain data backups, with periodic restore drills.
What you do
- Run restore tests each quarter
- Keep a copy offline or isolated
- PR.IP.S9
Define and follow policies for the physical operating environment of assets.
What you do
- Set rules for server rooms and equipment
- Inspect on a schedule
- PR.IP.S10
Measure how effective protective technologies are on a regular basis in line with service levels.
What you do
- Track detection and block rates
- Review against agreed targets
- PR.IP.S11
Have incident response, business continuity, incident recovery and disaster recovery plans in place, regularly tested and updated.
What you do
- Keep one current set of plans
- Test them at least yearly
- PR.IP.S12
Develop and implement a vulnerability management plan.
What you do
- Set fix times by severity
- Report overdue items
- PR.IP.S13
For cloud use, comply with SEBI's framework for adoption of cloud services by regulated entities.
What you do
- List cloud services in use
- Check each against the cloud framework
- PR.IP.S14
Use only CERT-In empanelled information security auditors for external audits, including the cyber audit, against the standards and mandatory guidelines.
What you do
- Check the auditor's empanelment before engaging
- Keep the engagement record
- PR.IP.S15
Certify SaaS, hosted services, off-the-shelf, customised and in-house software for application security and functional audit.
What you do
- Plan an application security audit for each critical product
- Keep the certificates
- PR.IP.S16
Obtain ISO 27001 certification, for market infrastructure institutions and qualified entities.
What you do
- Scope the certificate to critical operations
- Schedule surveillance audits
- PR.IP.S17
Follow globally recognised standards such as the CIS Critical Security Controls, for market infrastructure institutions and qualified entities.
What you do
- Map your controls to the CIS list
- Track gaps to closure
Evidence to keep
- Baseline configuration standards
- Change records
- Backup and restore test reports
- Application security test and audit reports
- Auditor empanelment evidence
PR.MAMaintenanceKeep systems patched and maintained safely.3 standards
- PR.MA.S1
Perform and log maintenance and repair of assets using approved and controlled tools.
What you do
- Keep a maintenance log
- Use only approved tools
- PR.MA.S2
Approve and log remote maintenance and perform it in a way that prevents unauthorised access.
What you do
- Require a ticket for each remote session
- Review session logs
- PR.MA.S3
Identify and rank patches by severity, apply critical patches at the earliest and test patches in non-production before applying them to the data centre and disaster recovery site.
What you do
- Set patch deadlines by severity
- Test, then deploy to production and DR together
Evidence to keep
- Maintenance logs
- Remote maintenance approvals
- Patch records
DEDetectSpot attacks and unusual activity quickly.2 categorys · 10 standards
DE.CMSecurity continuous monitoringWatch systems and assets round the clock through a security operations centre.5 standards
- DE.CM.S1
Run a security operations centre covering network, endpoints, physical environment, personnel activity, malicious code, mobile code and third-party activity, available 24x7x365.
What you do
- Use your own, a group or the Market SOC
- Confirm coverage in writing
- DE.CM.S2
Set up continuous monitoring in the SOC to detect unusual or malicious activity in time.
What you do
- Collect logs from key systems
- Tune detection rules
- DE.CM.S3
Monitor and investigate all anomalies and alerts within the stipulated time.
What you do
- Set triage times by severity
- Report missed targets
- DE.CM.S4
Monitor capacity use of all critical systems.
What you do
- Set capacity alerts
- Review trends monthly
- DE.CM.S5
Run cybersecurity, configuration, implementation and change management audits and VAPT to find weaknesses in the IT environment.
What you do
- Schedule the audits each year
- Track findings to closure
Evidence to keep
- SOC coverage and service agreement
- Alert triage and investigation records
- Audit and VAPT reports
DE.DPDetection processKeep detection roles and processes defined and tested.5 standards
- DE.DP.S1
Define roles and responsibilities for detection so that someone is accountable.
What you do
- Name detection owners
- Add them to the role matrix
- DE.DP.S2
Test detection processes with playbooks and use cases.
What you do
- Write playbooks for common attacks
- Test them twice a year
- DE.DP.S3
Communicate event detection information as required by regulation and your own policy.
What you do
- List who must be told and when
- Rehearse the notification steps
- DE.DP.S4
Run periodic goal-based red team exercises that simulate attackers, for market infrastructure institutions and qualified entities.
What you do
- Set clear goals for each exercise
- Fix gaps found
- DE.DP.S5
Run threat hunting and compromise assessments on a regular basis.
What you do
- Search logs for known attacker techniques
- Record findings
Evidence to keep
- Detection role definitions
- Playbooks and use-case tests
- Red team and threat hunting reports
RSRespondHandle incidents in an organised, reported and learning way.4 categorys · 15 standards
RS.MAIncident managementPlan for incidents and act as soon as one occurs.5 standards
- RS.MA.S1
Document a Cyber Crisis Management Plan with scenario-based procedures and an incident response plan, and trigger it as soon as an incident occurs.
What you do
- Write scenario playbooks
- Define how the plan is triggered
- RS.MA.S2
Maximise your ability to respond quickly and well to adverse conditions, attacks or signs of them, to keep operations running.
What you do
- Set response targets
- Practise with simulated attacks
- RS.MA.S3
Prepare contingency plans, continuity of operations, training, exercises, and incident response and recovery plans, approved by the Board, partners or proprietor.
What you do
- Collect the plans in one pack
- Record the approval
- RS.MA.S4
Contain and mitigate incidents and either fix newly found vulnerabilities or document them as accepted risks.
What you do
- Define containment steps
- Record risk acceptance by an accountable owner
- RS.MA.S5
Join the Cyber Swachhta Kendra and other CERT-In initiatives, for market infrastructure institutions and qualified entities.
What you do
- Register with the programmes
- Act on notified guidance
Evidence to keep
- Cyber Crisis Management Plan
- Approved contingency and recovery plans
- Incident register
RS.COIncident reporting and communicationCoordinate and report to SEBI, CERT-In and others in time.3 standards
- RS.CO.S1
Prepare and implement a procedure that sets out the roles and responsibilities of staff in cyber incident response.
What you do
- Write the procedure
- Name deputies for each role
- RS.CO.S2
Notify SEBI, CERT-In and NCIIPC, as applicable, of incidents within the stipulated time, and report other incidents under the guidelines.
What you do
- Keep a contact and deadline sheet
- Use SEBI's reporting formats
- RS.CO.S3
Coordinate with stakeholders during a cyber incident as set out in your crisis management plan.
What you do
- List stakeholders and contact routes
- Practise communications in drills
Evidence to keep
- Incident response SOP with roles
- Regulator notification records
- Stakeholder communication log
RS.ANIncident analysisWork out what happened, why and how bad it was.5 standards
- RS.AN.S1
Set up processes to receive, analyse and respond to vulnerabilities and incidents disclosed from internal and external sources.
What you do
- Provide a channel for reports
- Track each one to closure
- RS.AN.S2
Categorise incidents in line with the categories in your crisis management plan.
What you do
- Use SEBI's severity levels
- Record the category for each incident
- RS.AN.S3
Investigate incidents and alerts in detail, with forensic analysis where appropriate, to find the root cause, the attacker's methods and any lateral movement.
What you do
- Preserve logs and evidence
- Use a forensic specialist for serious cases
- RS.AN.S4
Carry out root cause analysis to find the gaps in people, process and technology and strengthen your security posture.
What you do
- Write a short report per major incident
- Create actions for each gap
- RS.AN.S5
Always carry out an impact analysis of incidents, with root cause and forensic analysis as set out in the classification and handling guidance.
What you do
- Record the business and data impact
- Follow the handling guidance for each severity
Evidence to keep
- Incident analysis and forensic reports
- Root cause analysis
- Impact analysis records
RS.IMResponse improvementsLearn from each incident and exercise.2 standards
- RS.IM.S1
Build lessons learned from incident handling into response plans, training and testing, and implement the changes.
What you do
- Hold a review after each incident
- Update the plan within an agreed time
- RS.IM.S2
Communicate changes to the response plan to designated key personnel.
What you do
- Circulate the revised plan
- Record acknowledgement
Evidence to keep
- Lessons learned records
- Updated response plans
RCRecoverRestore systems and communicate while recovering.3 categorys · 9 standards
RC.RPRecovery plan executionRestore affected systems on time and without losing data.4 standards
- RC.RP.S1
Classify recovery plans by different cyber scenarios.
What you do
- Write recovery plans for ransomware, data loss and outage
- Review them yearly
- RC.RP.S2
Meet the recovery time and recovery point objectives set by SEBI when restoring systems after a cyber incident.
What you do
- Record the targets that apply to you
- Test that backups meet them
- RC.RP.S3
Conduct drills periodically to test different recovery scenarios.
What you do
- Schedule drills each year
- Record results and fixes
- RC.RP.S4
Document backup and recovery plans so that no data is lost.
What you do
- Document backup scope and frequency
- Review after system changes
Evidence to keep
- Recovery plan with scenario classes
- Recovery drill reports
- Backup and recovery documentation
RC.CORecovery communicationKeep people informed while recovering.3 standards
- RC.CO.S1
Manage public relations during a cyber incident as set out in the recovery plan.
What you do
- Name a spokesperson
- Pre-approve holding statements
- RC.CO.S2
Communicate recovery activities to internal and external stakeholders and to executive and management teams.
What you do
- Send regular status updates
- Keep a communication log
- RC.CO.S3
Tell all related stakeholders what was done during recovery.
What you do
- Send a closure summary
- Keep it with the incident record
Evidence to keep
- Communication plan for recovery
- Public relations guidance
- Stakeholder updates
RC.IMRecovery improvementsImprove recovery from what you learn.2 standards
- RC.IM.S1
Update and improve recovery plans using lessons learned from cyber incidents.
What you do
- Add lessons to the plan
- Record the version change
- RC.IM.S2
Upgrade cyber resilience capabilities through periodic drills so critical operations are restored safely and on time.
What you do
- Test critical services at least yearly
- Track improvement actions
Evidence to keep
- Recovery lessons learned
- Drill schedule and results
EVEvolveKeep adapting as threats change.1 category · 5 standards
EV.STStrategiesAdapt your defences and learn from adversity.5 standards
- EV.ST.S1
Form strategies to anticipate new attack vectors, apply or remove controls to cover weaknesses and reduce attack surfaces.
What you do
- Review the threat landscape each quarter
- Retire exposed services you no longer need
- EV.ST.S2
Show diversity in technology so that one common weakness cannot take everything down.
What you do
- Avoid a single vendor for every critical layer
- Document the diversity you rely on
- EV.ST.S3
Confirm that business functions and processes are changed after incidents so they handle adversity better, and build the learning into your resilience posture.
What you do
- Record changes made after each incident
- Check they were completed
- EV.ST.S4
Keep adapting and evolving to counter new threats, for market infrastructure institutions and qualified entities.
What you do
- Plan yearly security improvements
- Track delivery
- EV.ST.S5
Evaluate your cyber resilience posture periodically, for mid-size and small entities.
What you do
- Run a yearly self-assessment
- Share results with management
Evidence to keep
- Cyber resilience strategy
- Post-incident change records
- Resilience posture evaluation
Nothing matches. Clear the search or pick another function.
Outcomes and implementation examples are from SEBI circular SEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113, Cybersecurity and Cyber Resilience Framework (CSCRF) for SEBI Regulated Entities, published by NIST. Descriptions of what to do and the evidence lists are our own plain-English guidance. Check the official source for the authoritative text.
Your path to getting started
Five steps from first look to a clean audit report. Effort depends on your size and starting point.
- 1
Find your category
Check the thresholds in the framework to see whether you count as a market infrastructure institution, qualified, mid-size, small or self-certification entity.
- 2
List what applies
Mark each standard and mandatory guideline that applies to your category and note any exemptions.
- 3
Close the gaps
Fix policy, SOC, access, backup, supplier and incident response gaps and keep evidence.
- 4
Plan the audit
Book a CERT-In empanelled auditor for the cyber audit and vulnerability testing your category needs.
- 5
Report on time
Submit audit reports and other required documents under the framework's timelines.
How Optimus GRC helps
Each area maps to a part of the platform, so the work and the evidence sit together.
| What it asks | What you do in Optimus GRC |
|---|---|
| Governance | Policy and role records, risk register, supplier assessments |
| Identify | Asset and data inventory, risk assessments |
| Protect | Controls library with evidence, access reviews, training records |
| Detect | Monitoring evidence, alert records, red team reports |
| Respond and recover | Incident register, notification log, drill results |
| Evolve and audit | Audit plans, findings and follow-up tasks |
Free CSCRF readiness checklist
A one-page PDF you can print or share with your team. No sign-up needed.
Download the checklist (PDF)- Cybersecurity and cyber resilience policy
- Asset and data inventory template
- Cyber crisis management plan outline
- Incident classification and reporting checklist
Share or cite this page
Writing about CSCRF? You are welcome to link to this guide. Copy the link below.
<a href="/frameworks/sebi-cscrf/">CSCRF explained in plain English - Optimus CyberX</a>Common questions
Is the CSCRF mandatory?
Yes for the entity types it names. SEBI issued it under Section 11(1) of the SEBI Act, and it covers 19 types of regulated entity.
Do small firms need a SOC?
The framework requires a SOC for all entities except client-based stock brokers with fewer than 100 clients. Small and self-certification entities must join the Market SOC.
Must data stay in India?
Regulatory Data must be kept available and readable within India. IT and cybersecurity data sent to a global SOC or a SaaS security tool is exempt, but it must be reviewed yearly by the IT Committee and approved by the Board, partners or proprietor.
What is the Cyber Capability Index?
A score based on 23 parameters that rates cyber maturity from exceptional to fail. It applies to market infrastructure institutions and qualified entities.
Related frameworks
See how ready you are for CSCRF
Answer questions across every area. We email you a report showing where you comply and where you do not.