Share𝕏inW
← Resources
REGULATORY COMPLIANCE · PRACTITIONER GUIDE · 13 min read

SEBI CSCRF Maturity Assessment:
The Practitioner’s Survival Guide

Most BFSI organizations over-score their CSCRF maturity by 1–2 levels. SEBI auditors know exactly which controls will have thin evidence. This guide shows you how to run an assessment that actually holds up.

Venugopal Parameswara|April 2026|CISO · GRC Practitioner · Internal Audit
6
CSCRF Domains
39
Controls assessed
82%
Fail DR test evidence
1–2
Avg over-scoring (levels)
// The Self-Assessment Trap

The Problem With Scoring Your Own Maturity

The SEBI CSCRF framework requires regulated entities to conduct annual cyber security and cyber resilience maturity assessments and submit them to a SEBI-designated audit firm. The framework uses a 5-level maturity model across 6 domains and 39 controls. Sounds straightforward.

The challenge is that self-assessment frameworks invite optimism bias. When the person who designed the incident response process is also the one scoring it, Level 3 suddenly seems very achievable — even when the last tabletop exercise was 18 months ago and the results were never documented.

CreativeCyber practitioners consistently find a 1–2 level gap between what organizations report in self-assessments and what independent auditors verify. The gap isn’t usually dishonesty — it’s a fundamental confusion between “we have this control” and “we have verifiable evidence that this control works.”

CSCRF Level 3 doesn’t mean your policy is approved and filed. It means your policy is approved, implemented consistently, tested regularly, and the test results are documented. Most organizations have the first part. Few have all four.

// The Maturity Model

What Each Level Actually Requires

The most important discipline in CSCRF assessment is translating each level’s definition into concrete evidence requirements. Here’s how each level translates in practice:

// CSCRF Maturity Levels — What Each Actually Requires
5
Level 5 — OptimizedTARGET

Continuous improvement cycle. Metrics drive control evolution. Board-level risk quantification integrated.

Evidence required: Real-time dashboards, threat intel feeds, automated exception reporting to board.
4
Level 4 — Managed

Controls measured quantitatively. Deviations detected automatically. Evidence collected continuously.

Evidence required: SIEM integration, automated control testing, KRI dashboards with trend lines.
3
Level 3 — Defined

Documented policies and procedures. Consistent implementation across the enterprise. Regular testing.

Evidence required: Approved policy documents with version control, test results, training completion records.
2
Level 2 — Developing

Controls exist but are inconsistent. Depends on individual effort. No formal testing cadence.

Evidence required: Some policy documents, ad-hoc test results, informal records only.
1
Level 1 — BasicNON-COMPLIANT

Reactive. Controls exist only in response to incidents. No formal program.

Evidence required: Incident reports only. No proactive evidence.
// Domain Coverage

The 6 Domains — Where the Gaps Actually Are

The CSCRF framework follows the NIST CSF structure: Govern, Identify, Protect, Detect, Respond, Recover. Indian BFSI organizations consistently score higher in the paper-heavy domains (Govern, Identify) and lower in the evidence-heavy operational domains (Detect, Respond, Recover). SEBI auditors know this asymmetry and test accordingly.

// CSCRF 6-Domain Coverage — Typical BFSI Self-Assessment Scores
GOV
Govern
3.2
/ 5.0
8 controls assessed
Board oversight, CISO mandate, risk appetite framework
IDN
Identify
2.8
/ 5.0
7 controls assessed
Asset inventory, risk assessment, vendor risk classification
PRO
Protect
2.6
/ 5.0
10 controls assessed
Access control, data security, system hardening, training
DET
Detect
2.1
/ 5.0
6 controls assessed
SIEM, anomaly detection, log management, threat intel
RES
Respond
1.9
/ 5.0
5 controls assessed
Incident response plan, communication, containment
REC
Recover
1.7
/ 5.0
3 controls assessed
BCP, DRP, lessons learned, post-incident review
The Detect→Respond→Recover gap is the most common finding. Organizations score 3.0+ in Govern and Identify (paper-heavy) but drop to 1.7–2.1 in Detect, Respond, and Recover (evidence-heavy). SEBI auditors know this pattern.
3.2
Avg score — Govern domain
Highest scored domain
1.7
Avg score — Recover domain
Most commonly weakest
39
Total controls assessed
Across 6 CSCRF domains
Level 3
SEBI minimum expectation
For Qualified REs
// What Passes Audit

Evidence Quality: What Passes and What Doesn’t

The single most common finding in CSCRF audits is not missing controls — it’s missing evidence for controls that do exist. Here’s a practical guide to what auditors consider insufficient, acceptable, and strong evidence across key control areas:

// Evidence Quality Matrix — What SEBI Auditors Actually Accept
Control Area❌ Poor (fails audit)⚠️ Acceptable (borderline)✅ Strong (audit-ready)
Access Control PolicyPolicy document onlyPolicy + quarterly access review reportPolicy + access review + exception log + approval trail
SIEM / Log ManagementScreenshot of SIEM dashboardSIEM configuration doc + 90-day alert summarySIEM config + alert KPIs + tuning log + escalation records
Incident Response PlanIRP document in SharePointIRP + last tabletop exercise reportIRP + tabletop results + post-incident review + plan updates
Vulnerability ManagementList of open vulnerabilitiesScan reports + SLA compliance rateScan reports + SLA data + remediation evidence + exception register
Vendor Risk AssessmentVendor contract with security clauseVendor assessment questionnaire responsesAssessment + independent verification + annual review record
BCP / DRPBCP documentBCP + last DR test resultsBCP + DR test + RTO/RPO actuals + lessons learned + updates
🚨The Screenshot Problem
Screenshots of dashboards are not evidence of controls. A screenshot of your SIEM shows the tool exists, not that it is configured to detect relevant threats, that alerts are actioned, or that the tuning process is governed. Auditors will ask for configuration documentation, alert escalation records, and evidence of periodic tuning. Prepare all three.
// Most Failed Controls

The Controls That Will Trip You Up

Based on practitioner assessments across Indian BFSI entities, these are the controls most frequently found to have insufficient evidence for Level 3 or above:

// Most Commonly Failed CSCRF Controls — % of Organizations with Insufficient Evidence
DR test with RTO/RPO actuals[Recover]
82%
Threat intelligence integration[Detect]
74%
Incident response tabletop (last 12 months)[Respond]
71%
Vendor risk re-assessment (annual)[Identify]
68%
Privileged access review (quarterly)[Protect]
63%
Board-level risk reporting (quantified)[Govern]
58%
Security awareness training completion[Protect]
44%

Based on CreativeCyber practitioner assessments across Indian BFSI entities. “Fail rate” = percentage with evidence insufficient to demonstrate Level 3 or above.

⚠️DR Tests Without Actuals Are Useless
82% of organizations have a DR test documented on paper. Far fewer have documented the actual RTO and RPO achieved during that test — and fewer still have compared actuals against their board-approved targets. SEBI auditors ask one question: “What RTO did you actually achieve in your last DR test?” If the answer is “we don’t know exactly,” the control fails regardless of the test certificate.
// Governance Structure

The Maker / Checker Structure That Holds Up

The most defensible CSCRF assessments use a three-tier governance structure with clear separation of duties. SEBI auditors specifically look for evidence that the person who scored a control is not the same person who implemented it. Without this separation, the assessment is presumed biased.

// Maker / Checker / Approver — The Governance Structure That Holds Up
📝
Role 1
Control Owner (Maker)
  • Documents control implementation
  • Collects and uploads evidence
  • Scores control per maturity criteria
  • Flags gaps or exceptions
🔍
Role 2
Assessment Reviewer (Checker)
  • Independently reviews evidence quality
  • Challenges score if evidence is insufficient
  • Approves or returns for remediation
  • Documents review rationale
Role 3
DPO / CISO (Approver)
  • Signs off final assessment scores
  • Escalates unresolved disagreements
  • Submits to SEBI-designated auditor
  • Retains records for 3 years
💡 Key principle: The person who collects evidence cannot be the person who approves the score. SEBI auditors specifically look for evidence of this separation.
// Your 6-Month Plan

The 6-Month Assessment Calendar

A credible CSCRF assessment is not a two-week exercise. Organizations that start collecting evidence 6 weeks before the submission deadline consistently produce thin assessments. Start 6 months out:

// 6-Month CSCRF Assessment Calendar
1
Month 1Governance Setup
  • Appoint Maker/Checker/Approver for each domain
  • Agree on evidence collection templates
  • Baseline current scores against last year
2
Month 2–3Evidence Collection
  • Control owners collect and upload evidence
  • Reviewer challenges and returns incomplete items
  • Track completion rate weekly (target: 80% by Month 3)
3
Month 4Gap Remediation
  • Prioritise gaps by audit risk (fail rate data)
  • Implement quick wins (documentation, test scheduling)
  • Exception register for controls that need >1 year to close
4
Month 5Internal Mock Audit
  • Run internal audit against CSCRF checklist
  • Simulate auditor questions on top 5 failed controls
  • Update scores based on challenge outcomes
5
Month 6SEBI Submission
  • CISO and Board sign-off on final scores
  • Submit via SEBI-designated audit firm
  • Retain evidence package for 3 years
Continuous Assessment Beats Annual Sprint
The best-performing organizations maintain living evidence repositories throughout the year. Every control test, access review, and incident response exercise generates evidence that is immediately filed against the relevant CSCRF control. By the time the annual submission arrives, the assessment is already 80% complete. The Practitioner Toolkit’s Assessment module is designed exactly for this workflow — evidence files linked to controls at collection time, not at audit time.

The SEBI auditor is not there to catch you out. They are there to verify that your self-assessment is honest. The fastest way to pass is to score conservatively and show clear evidence for every point you claim.

// Next Step

Run Your CSCRF Assessment on a Platform Built for It

The Practitioner Toolkit’s Assessment module maps directly to CSCRF’s 6 domains and 39 controls, with built-in Maker/Checker workflow, evidence file attachment at the control level, exception registers, and 5-level maturity scoring with configurable evidence requirements. No spreadsheets. No version confusion.

Practitioner Toolkit

CSCRF Assessment — Built for SEBI Audit Readiness

4 structured assessment modules with Maker/Checker workflow, 5-level maturity scoring, Indian regulatory alignment, and evidence collection built in from day one.

Explore Practitioner Toolkit →Download Datasheet ↓
Found this useful?

Share it with your audit team, GRC leads, and CISO peers running CSCRF assessments.

𝕏 Share on Xin Share on LinkedIn💬 WhatsApp

    We use cookies and analytics (Google Analytics) to improve your experience. Under India's Digital Personal Data Protection Act, 2023, we require your consent before collecting any usage data. Privacy Policy