CSCRF replaced SEBI’s earlier cybersecurity circulars and applies across regulated intermediaries: brokers, depository participants, AMCs, RTAs, portfolio managers and investment advisers, with obligations graded by entity category. Most of the commentary addresses what you must do. This post addresses the part that gets handled late: what it means for the vendors you depend on.
What applies to vendors, in practice
The clauses to put in the contract
- Right to audit, for you and for SEBI, on-site where required
- Named subcontractors, with prior consent for changes affecting your data
- Processing locations, disclosed and restricted
- Incident notification within a defined window that lets you meet your own
- Log retention configured to your policy, not the vendor's default
- Exit and data portability, agreed at signing rather than at termination
- VAPT evidence provided on request, at defined frequency
The AI question CSCRF didn’t anticipate
SEBI’s position is that the regulated entity is responsible for the outputs of AI tools it deploys, including third-party tools. Read that against a language model in a regulated process and three requirements follow:
The plain summary
CSCRF compliance is yours, not your vendor’s, but it’s unachievable if your vendor’s architecture, logging and contract terms don’t support it. Ask the seven contract questions above before selecting, not during your next examination.