<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on IntelliXBOM</title><link>https://intellixbom.com/blog/</link><description>Recent content in Blog 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/blog/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><item><title>Don't Trust the SBOM Your Vendor Gave You</title><link>https://intellixbom.com/blog/dont-trust-vendor-sbom-certin/</link><pubDate>Thu, 09 Apr 2026 12:00:00 +0530</pubDate><guid>https://intellixbom.com/blog/dont-trust-vendor-sbom-certin/</guid><description>&lt;p&gt;Regulators across the world are finally getting serious about the software supply chain. India&amp;rsquo;s CERT-In SBOM Technical Guidelines (v2.0, July 2025) go beyond just SBOMs they extend to a broader BOM ecosystem, including CBOM, QBOM, AIBOM, and HBOM. This makes the requirement not just about software components, but about understanding the full composition of modern systems.&lt;/p&gt;
&lt;p&gt;Globally, the direction is the same whether it&amp;rsquo;s the US Executive Order 14028, the EU Cyber Resilience Act, RBI Advisory 11/2024, or MeitY&amp;rsquo;s 2025 guidelines.&lt;/p&gt;</description></item><item><title> Your Vendor NDA Won't Stop a Supply Chain Attack</title><link>https://intellixbom.com/blog/irdai-cybersecurity-2026/</link><pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate><guid>https://intellixbom.com/blog/irdai-cybersecurity-2026/</guid><description>&lt;p&gt;&lt;strong&gt;IRDAI&amp;rsquo;s New Rules Won&amp;rsquo;t Save You.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;What the 2026 IRDAI Guidelines on Information and Cyber Security for Regulated Entities get right, what they miss, and the one capability every regulated insurer needs to deploy now.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Insurance Regulatory and Development Authority of India (IRDAI) has significantly raised the bar with its amended Cybersecurity Guidelines 2023 (Annexure A). For every insurer and insurance intermediary operating in India, these amendments are not optional fine print they are a direct signal that cybersecurity governance must now match the sophistication of today&amp;rsquo;s threat landscape.&lt;/p&gt;</description></item><item><title>End of Life is a Blind Spot for Open-Source Packages in Your Supply Chain</title><link>https://intellixbom.com/blog/end-of-life-blind-spot-open-source-supply-chain/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0530</pubDate><guid>https://intellixbom.com/blog/end-of-life-blind-spot-open-source-supply-chain/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;By the time you discover a dependency is abandoned, it&amp;rsquo;s usually already a liability. Here&amp;rsquo;s why EOL detection can&amp;rsquo;t be a metadata lookup and what to do instead.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;Your CI/CD pipeline is scanning for vulnerabilities. Your SCA tool is checking licenses. Your SBOM is up to date. But there&amp;rsquo;s a question none of those tools are consistently answering:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Is this open-source package still being maintained and if not, when did it stop?&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Software Supply Chain Intelligence: Not Just an Inventory</title><link>https://intellixbom.com/blog/sbom-intelligence-not-just-an-inventory/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0530</pubDate><guid>https://intellixbom.com/blog/sbom-intelligence-not-just-an-inventory/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Software Supply Chain Security&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;Most conversations about software supply chain security start and end with one question: &lt;strong&gt;do you have an SBOM?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;That is the wrong question.&lt;/p&gt;
&lt;p&gt;An SBOM Software Bill of Materials is, at its core, a structured list of components, libraries, and dependencies that make up a software product. For years, the industry treated possession of this list as a security milestone. Regulatory frameworks reinforce this narrative: produce an SBOM, share it with your customer, and check the compliance box.&lt;/p&gt;</description></item><item><title>Beyond SCA: Generating SBOMs, CBOMs, QBOMs, and AIBOMs at Runtime</title><link>https://intellixbom.com/blog/beyond-sca-runtime-bom/</link><pubDate>Wed, 09 Jul 2025 10:00:00 +0530</pubDate><guid>https://intellixbom.com/blog/beyond-sca-runtime-bom/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Your SBOM is only telling you half the story here&amp;rsquo;s what it&amp;rsquo;s missing&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;Somewhere in your production environment right now, code is running that your SBOM doesn&amp;rsquo;t capture. A library is loaded that never made it into your inventory. A cryptographic routine is executing without ever being audited. An AI model serves requests from an untracked registry. Meanwhile, your SCA tool the one behind that reassuring green dashboard has no visibility into any of it.&lt;/p&gt;</description></item></channel></rss>