<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CSCRF on IntelliXBOM</title><link>https://intellixbom.com/tags/cscrf/</link><description>Recent content in CSCRF on IntelliXBOM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 Apr 2026 18:00:00 +0530</lastBuildDate><atom:link href="https://intellixbom.com/tags/cscrf/index.xml" rel="self" type="application/rss+xml"/><item><title>SEBI's CSCRF Names SBOMs Here's What GV.SC.S5 Actually Demands (and Where It Still Leaves Gaps)</title><link>https://intellixbom.com/blog/sebi-cscrf-sbom-gv-sc-s5-capital-markets/</link><pubDate>Mon, 13 Apr 2026 18:00:00 +0530</pubDate><guid>https://intellixbom.com/blog/sebi-cscrf-sbom-gv-sc-s5-capital-markets/</guid><description>&lt;p&gt;When SEBI published its &lt;strong&gt;Cybersecurity and Cyber Resilience Framework (CSCRF)&lt;/strong&gt; in August 2024 (&lt;strong&gt;Circular SEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113&lt;/strong&gt;, 20 August 2024), many teams scanned the document for one question: &lt;em&gt;does the capital markets regulator treat software supply chain risk as a first class problem?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The answer is &lt;strong&gt;yes, explicitly&lt;/strong&gt;. Under &lt;strong&gt;Governance → Supply Chain Risk Management&lt;/strong&gt;, Standard &lt;strong&gt;GV.SC.S5&lt;/strong&gt; mandates &lt;strong&gt;Software Bills of Materials (SBOMs)&lt;/strong&gt; for Regulated Entities (REs), with &lt;strong&gt;SolarWinds&lt;/strong&gt; and &lt;strong&gt;Apache Log4j&lt;/strong&gt; cited as motivating context. That level of specificity is unusual and welcome for a financial sector framework.&lt;/p&gt;</description></item></channel></rss>