<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Lineaje - Medium]]></title>
        <description><![CDATA[Follow us to stay on top of cutting edge opinions and happenings in The Software Supply Chain - Medium]]></description>
        <link>https://medium.com/lineaje?source=rss----2b358a0c9e89---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Lineaje - Medium</title>
            <link>https://medium.com/lineaje?source=rss----2b358a0c9e89---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:53:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/lineaje" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[XZ: A Perfect Use Case For Why “Lineaje Attestation” Matters]]></title>
            <link>https://medium.com/lineaje/xz-a-perfect-use-case-for-why-lineaje-attestation-matters-7c31787fe77d?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/7c31787fe77d</guid>
            <category><![CDATA[software-integrity]]></category>
            <category><![CDATA[supply-chain-risk]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[cyberattack]]></category>
            <dc:creator><![CDATA[Nick Mistry]]></dc:creator>
            <pubDate>Tue, 02 Apr 2024 01:30:53 GMT</pubDate>
            <atom:updated>2024-04-02T01:30:27.490Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*BmvnWgY6unU-bjumZyrOXQ.png" /></figure><p>XZ is in the news. The compromise of widely used Linux distros is big news. It is a sophisticated attack. So sophisticated, that the impacted Linux distros shipped it — without catching it! <a href="https://arstechnica.com/security/2024/04/what-we-know-about-the-xz-utils-backdoor-that-almost-infected-the-world/#:~:text=Through%20sheer%20luck%20and%20Freund&#39;s,backdoor%20in%20the%20compression%20software.">Click here</a> to get a deeper look at what is known about it.</p><p>The fundamental issue is — Would the tooling in your CI/CD pipeline have detected this attack? More than 70% of your software is sourced from external suppliers, including your OS — in this case the Linux distribution image published by respective suppliers. However, your CI/CD tools would not detect these types of compromises. Even Microsoft’s sophisticated supply chain tools missed it, leaving it to an eagle eyed developer to raise the alarm.</p><p><strong>What technology should you deploy to detect Supply Chain Tampers?</strong></p><p>Software integrity attestation is the capability to ensure what you deploy is what you built and what you built comes from your source code. And what you sourced is identical to what was published by maintainers of the source — essentially creating a full chain of attested trust.</p><p>XZ attack — from an integrity attestation perspective — boils down to detecting what is shipped (by Linux distros) is validated to be what was published by their open source dependencies. The fingerprints of the installed XZ component in the shipping Linux distros does not match with the one originally published by XZ utility supplier.</p><p>In recent years, code signing techniques and “build-system” driven attestations (such as Google’s SLSA approach) have been advocated as valid software integrity attestation solutions. XZ demonstrates that these attestation techniques check the compliance box but fail to achieve the basic goal of attestation — detecting software tampers. In fact- they create a reverse issue- the illusion of untampered software when they certify the attestation of software they know little about.</p><p>The supply chain attestation approach matters — Lineaje’s supply chain attestation capability detects the XZ compromise for all our customers. In fact, it detects all such compromises out of the box.</p><p><strong>Lineaje Attestation — High Integrity Detection for Identifying Software Supply Chain Tampers:</strong></p><p>Lineaje’s attests the integrity of every software component in your supply chain — including all direct and transitive components irrespective of what depth they are in your software supply chain tree. These attestations proactively assess the <strong><em>integrity of software components</em></strong> within the supply chain, to identify tampers and tamper risks.</p><p><strong>High-Level Lineaje Attestation Process</strong></p><ul><li><strong>Deep Scan:</strong> Lineaje conducts thorough scans of all software components including product OS images and patches for current and past versions.</li><li><strong>Package Verification:</strong> Each software component is linked to its original package and verified for presence and integrity using fingerprints.</li><li><strong>Metadata Collection:</strong> Metadata including source repository and build tags are captured for each component.</li><li><strong>Contributor Analysis:</strong> Contributor and commit data are collected for additional security checks.</li><li><strong>Threat Detection: </strong>Lineaje attestation detects malicious tampers like the XZ compromise, components of dubious origin, unknown components and much more.</li></ul><p>Using these parameters, the Lineaje Attestation approach will establish an attestation level for each component in your source code, artifactory, or deployed containers — so if the deployed container contains Linux with XZ utils, it would go through an attestation for its full supply chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*YTs1IPz5ASwh1CbKG0tU1w.png" /></figure><p>In this compromise, the fingerprints of installed XZ component in the shipping Linux distros do not match the one originally published. Hence even though the component is “known” and the package PURL can be detected, the Lineaje Attestation score will flag it as <strong>tampered, </strong>or LCAL 1, since the fingerprints of the published component do not match the fingerprints of the installed component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDxoPT-a7IWwn7_zwhkYCg.png" /></figure><p>Any component with a Lineaje Attestation score of Level 1 indicates a serious software supply chain tamper and must be addressed immediately.</p><p><strong>Conclusion:</strong></p><p>As we mentioned earlier, the robustness of the software integrity attestation technology required for the software supply chain is significantly more elaborate than for the CI/CD pipeline. If you want to stay secure, you need Lineaje Attestation.</p><blockquote><strong>It’s Time to take back security by managing the integrity of your supply chain not just your CI/CD pipe with Lineaje Attestation — schedule a demo of our capabilities today at </strong>www.lineaje.com</blockquote><p>#SoftwareSupplyChain #CyberSecurity #ThreatDetection #VulnerabilityManagement #Tamper #BackDoorVulnerability</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c31787fe77d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/xz-a-perfect-use-case-for-why-lineaje-attestation-matters-7c31787fe77d">XZ: A Perfect Use Case For Why “Lineaje Attestation” Matters</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finalization of CISA Attestation Letter: Ensuring Software Security for Federal Agencies]]></title>
            <link>https://medium.com/lineaje/finalization-of-cisa-attestation-letter-ensuring-software-security-for-federal-agencies-f26dbe59aa40?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/f26dbe59aa40</guid>
            <category><![CDATA[cisa-attestation-letter]]></category>
            <category><![CDATA[eo-14028]]></category>
            <dc:creator><![CDATA[Nick Mistry]]></dc:creator>
            <pubDate>Wed, 13 Mar 2024 01:19:13 GMT</pubDate>
            <atom:updated>2024-03-13T00:35:50.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*C2ms0tQ1xs1U3zlk1BdIQQ.png" /></figure><p>The Cybersecurity and Infrastructure Security Agency (CISA) on March 11th finalized the Attestation Letter for software vendors, marking a significant step towards addressing software security across federal systems.</p><p>Software producers must furnish Attestation letters to CISA (<a href="https://www.cisa.gov/resources-tools/resources/secure-software-development-attestation-form">https://www.cisa.gov/resources-tools/resources/secure-software-development-attestation-form</a>) and linked SBOMs to agencies using their software. The clock starts with the final approved release of the CISA Attestation form yesterday.</p><p>Expected date for critical software vendors to adhere: June 11, 2024</p><p>Expected date for all software vendors to adhere: September 11, 2024</p><p><strong>What Does This Mean for Software Vendors?</strong></p><p>For software vendors engaging with Federal Government Agencies, the finalized CISA Attestation Letter carries immense significance. It serves as a formal declaration of adherence to critical security requirements outlined in the Executive Order 14028 Section 4(e) which is mapped to the National Institute of Standards and Technology (NIST) Secure Software Development Framework (SSDF, NIST SP 800–218).</p><p>Among these requirements are the following key aspects:</p><ol><li><strong>Build System Integrity</strong>: Vendors must ensure the integrity of their build systems, guaranteeing that software is developed and maintained in a secure environment.</li><li><strong>Trusted Supply Chain</strong>: Maintaining a trusted supply chain is essential, ensuring that all components and dependencies used in software development come from reliable and verified sources.</li><li><strong>Provenance Data Maintenance</strong>: Vendors are required to maintain detailed provenance data, tracking the origin and history of software components throughout the development lifecycle.</li><li><strong>Vulnerability Management</strong>: Effective vulnerability management practices are crucial, including timely identification, assessment, and mitigation of security vulnerabilities within software products.</li></ol><p>SBOM360 Hub, from Lineaje, is designed to help Software publishers to meet these requirements.</p><ul><li>Create, publish and privately share NTIA compliant SBOMs for each product and SKU Software Producers sell.</li><li>Generate the CISA Attestation form with the evidentiary artifacts so Software Producers can attest with confidence that they meet the compliance requirements.</li></ul><p><strong>Additional Software Vendor Requirements:</strong></p><ul><li><strong>CEO Signature: </strong>The form must be signed by the Chief Executive Officer (CEO) of the software producer or their designee, who must have the authority to bind the corporation. By signing, they attest that the software is developed in conformity with secure software development practices outlined above.</li><li><strong>Third-Party Assessment: </strong>Software producers can demonstrate compliance with minimum requirements by submitting a third-party assessment conducted by a Third-Party Assessor Organization (3PAO) that has been FedRAMP certified.</li><li><strong>POAM If Vendor Cannot Attest:</strong> If a vendor is unable to meet the requirements outlined in the Attestation Letter, the agency may still opt to utilize the software under certain conditions. In such cases, if the vendor identifies specific practices that they are unable to attest to, they must document their mitigation strategies and submit a comprehensive Plan of Actions and Milestones (POA&amp;M) to the agency.</li></ul><p>These requirements ensure that software producers provide accurate information about their software and attest to its secure development practices, aligning with federal government cybersecurity objectives outlined in Executive Order 14028 and related directives like OMB M-22–18 and M-23–16.</p><p><strong>Conclusion</strong></p><p>The finalization of the CISA Attestation Letter marks a significant milestone in the ongoing efforts to fortify software security within Federal Government Agencies. By requiring vendors to attest to critical security requirements outlined in the NIST SSDF, CISA is ensuring that software deployed across federal systems adheres to robust security standards.</p><p>At Lineaje we automate the CISA Attestation Letter, along with evidence collection to attest with confidence. Come check out what we can do at <a href="http://www.lineaje.com/">www.lineaje.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f26dbe59aa40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/finalization-of-cisa-attestation-letter-ensuring-software-security-for-federal-agencies-f26dbe59aa40">Finalization of CISA Attestation Letter: Ensuring Software Security for Federal Agencies</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lineaje AI & its BOMbots help source, secure, and fix software faster]]></title>
            <link>https://medium.com/lineaje/lineaje-ai-its-bombots-help-source-secure-and-fix-software-faster-edc7cab379a9?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/edc7cab379a9</guid>
            <category><![CDATA[eo14028-compliance]]></category>
            <category><![CDATA[open-source-security]]></category>
            <category><![CDATA[open-source-remediation]]></category>
            <category><![CDATA[sbom-security]]></category>
            <category><![CDATA[fix-vulnerabilities]]></category>
            <dc:creator><![CDATA[Javed Hasan]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 22:24:00 GMT</pubDate>
            <atom:updated>2023-08-16T18:41:17.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQ9IseqQcUR5cI_fuY2DZA.png" /><figcaption>Source, secure, and fix your Open Source Software with Lineaje AI &amp; BOMbots!</figcaption></figure><p>Organizations now <strong>Continuously Source</strong> (CS) more than 70% of components from outside their CI/CD pipeline. 90% of the fixes needed in these sourced components cannot be fixed by your developers- even when available. Current SCA tools with developer integration lack the necessary visibility, the required intelligence, and the remediation capabilities to resolve these issues that can ONLY be addressed left of shift-left — in your software supply chain. Lineaje AI with BOMbots creates the industry’s first remediation solution to remediate open-source dependencies.</p><h3>Software innovation is humming bringing opacity</h3><p>Pre-built open-Source Software is helping developers unleash an amazing amount of innovation. Developers assemble pre-built components alongside those built by them to deliver capabilities and features. Today, the CI/CD (Continuous Integration/Continuous Deployment) process integrates and deploys more code from outside the organization than that built by your developers. In some cases, 99% of components now come from outside your organization.</p><p>Pre-built Open source is also used by Open-source developers in projects you source from them. Our research “<a href="https://www.lineaje.dev/reports">What’s in your Open Source Software</a>” showed that 68% of all components in the software you source are not built by the developers of the project you sourced but are pre-built components from other Open-source projects. The fact is that supply chain depths now exceed 20 levels of pre-built components frequently. Much of the code your developers consume is compiled code. And much of what your dependencies consumed from other open-source projects is also compiled code. Not just innovation but opacity is high for developers.</p><h3>Software Maintenance pipes are clogged.</h3><p>The implications of this opaque, software supply chain are significant and are impacting both security and development organizations negatively. Supply chain tools like <a href="http://www.sbom360.com/">SBOM360</a> can now detect the comprehensive supply chain tree our software consumes. With only a small percentage of your software built in-house, software maintenance has become complex, and developers are overwhelmed being asked to fix issues in opaque software they didn’t create.</p><ul><li><strong>What you did not build, cannot be maintained by your developers</strong>: In fact, if you analyze your software, your developers can only fix about 10% of the vulnerabilities in your products without modifying those components. <strong>They cannot fix 90% of vulnerabilities</strong>. Add other issues like code quality, security posture, unmaintained components etc. and you realize that <em>the more pre-built components you have, the more your software ages badly.</em></li><li><strong>Fixing vulnerabilities is making it harder to fix vulnerabilities</strong>: This is counterintuitive so let me explain. Security tools in recent years, have driven the prioritization of vulnerabilities and then done amazing integrations to get developers to fix those vulnerabilities. Given the pressure from security teams, developers fix vulnerabilities both in their code and in open-source pre-built components. This creates a branch specific to your organization in that code line. From that moment on, your developers now own updating it every time that dependent project evolves. In short, security tools have made software maintenance worse- clogging developer queues, effectively inner-sourcing open-source components. <em>These pre-built projects are now inner-sourced -without funding- slowing follow-up innovation and increasing maintenance load.</em></li><li><strong>Upgrading on demand is an inefficient idea</strong>: Fixing security issues frequently requires upgrading a component. And developers can upgrade one component that already exists easily. However, Pre-built components are assembled together and tested to work together. Compatibility is not what security tools worry about but it is critical for software to co-operate. It’s made more complex because a pre-built open-source component is used an average of 2.7 times in the same application — in different contexts working with different parents, peers, and children. When a developer upgrades a single component, the “blast radius” of that change is significant. This is one reason why we deliver hotfixes, minor updates, and major releases. The blast radius of each is dramatically different. <em>Security tools have failed to comprehend this different blast radius of independent patches, minor updates, and upgrades even as they merrily push software developers into upgrades.</em></li><li><strong>Shiny pre-built dependencies also need to be well maintained: </strong>Slightly more than half of critical vulnerabilities in pre-built components are not fixable. Why? Developers in the project are less enthusiastic about maintaining their project than about adding new, exciting features. Many open-source developers no longer maintain their pre-built projects you may depend on. <em>Ensuring better dependency selection is key to ensuring that your software maintenance load is manageable.</em></li></ul><h3>Lineaje AI with BOMbots: Unclogs Software Maintenance and reduces costs upto 40%</h3><p>BOMbots are AI-powered automation bots that can deeply analyze your SBOM. They work together seamlessly through a simple, interactive generative AI paradigm. Each BOMbot is trained to solve a single complex problem exceedingly well. Because BOMbots can process and understand incredibly large amounts of data, their recommendations are superior and tuned for each user for their unique situation. The automation around BOMbots enables execution that reduces software maintenance overhead by up to 40 percent enabling organizations to decrease maintenance investments and costs and fix more vulnerabilities and issues.</p><p>All BOMbots also interact with each other and influence each other’s decisions so Lineaje AI creates a single coherent experience for the user delivering interactions that resolve conflicts between recommendations automatically based on a user’s needs.</p><p>BOMbots can assess your SBOM and Software Supply Chain, so they can comprehend the right place to drive a fix- when to rely on pre-built dependencies to fix issues, when to let your developers fix them and when to inner-source or to eliminate a dependency. They offer the most comprehensive integration balancing security goals with developer efficiency across your software supply chain.</p><p>​Regardless of company size, BOMbots alleviate compounded pain points associated with software maintenance. Key BOMbots available in this release include:</p><ul><li><strong>Compatibility BOMbot</strong>: Fixing vulnerabilities, resolving security issues, and taking advantage of new features frequently means that software components must be upgraded to newer versions — which may or may not be compatible with the other software components. The Compatibility BOMbot evaluates thousands of components in an SBOM and creates a compatibility matrix aligned with an organization’s goals to tune the recommendations from “least effort” to “most secure.” This enables organizations to eliminate as much as 25% of effort through the “compatibility dividend.”</li><li><strong>Maintainability BOMbot: </strong>Software components, including open-source dependencies, frequently age badly. The Maintainability BOMbot identifies<strong> </strong>dependencies that are risky and no longer maintained. It remediates by driving developers to fix that issue in the dependency themselves or choose a better alternative.</li><li><strong>Vulnerability BOMbot:</strong> <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=http%3A%2F%2Fwww.lineaje.dev&amp;esheet=53501951&amp;newsitemid=20230802938454&amp;lan=en-US&amp;anchor=95%25+of+vulnerabilities&amp;index=2&amp;md5=a2fd115faba1a28e995f470d3e0d376e">95% of vulnerabilities</a> now come from the software supply chain. Unfortunately, many vulnerability prioritization approaches today focus on security urgency and not executability by developers. The Vulnerability BOMbot considers both executability and security parameters in its prioritizations, separating out all vulnerabilities into fixable by the organization’s developers or by dependency organizations. It then works together with the Compatibility and Maintainability BOMbots to figure out the most optimal recommendation. The Vulnerability BOMbot can distinguish between independent patching and upgrades, as well as implications of major and minor versions. It then automates execution through the software supply chain to save up to 20% in effort.</li></ul><p>These are game-changing innovations for software producers and key feature additions to SBOM360. Please <a href="https://www.lineaje.dev/schedule-demo">connect</a> with us to see them in action or ping me directly on <a href="https://www.linkedin.com/in/javedhasan/">Linked-In</a>. We would love to show you what Lineaje AI with BOMbots can do for you!</p><p><a href="http://linkedin.com/company/lineaje">Follow us on Linked In</a>. We are just getting started and there is much to do. Be the first to know!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edc7cab379a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/lineaje-ai-its-bombots-help-source-secure-and-fix-software-faster-edc7cab379a9">Lineaje AI &amp; its BOMbots help source, secure, and fix software faster</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Software Supply Chain has a Software Distribution Chain Problem!]]></title>
            <link>https://medium.com/lineaje/the-software-supply-chain-has-a-software-distribution-chain-problem-f15b14d1aed8?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/f15b14d1aed8</guid>
            <category><![CDATA[software-bill-of-material]]></category>
            <category><![CDATA[lineaje-inc]]></category>
            <category><![CDATA[executive-order-14028]]></category>
            <category><![CDATA[third-party-risk]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <dc:creator><![CDATA[Javed Hasan]]></dc:creator>
            <pubDate>Sun, 18 Jun 2023 16:44:21 GMT</pubDate>
            <atom:updated>2023-06-18T16:44:21.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFD0cfWDSLdykCiQI9b0Wg.png" /><figcaption>How do you distribute your SBOM Attestations privately &amp; Securely?</figcaption></figure><p>Executive Order 14028 Requires that Software Consumers assess SBOMs and related compliance artifacts when software is procured or upgraded. How do they get those SBOMs from their software sellers? We discuss how software producers, software sellers, and software consumers can collaborate to mitigate risk and improve the software they are all so deeply vested in.</p><h3>The Software Distribution Chain</h3><p>The software distribution chain — call it the Software Consumption Chain- serves as a large ecosystem through which software producers can deliver their software to their consumers. This chain delivers revenue to the software supply chain for its existence and growth. According to <a href="https://www.statista.com/statistics/203935/overall-it-spending-worldwide/">Statista</a>, <em>Global IT spending exceeded $4.4 trillion in 2022</em>. <em>Millions of organizations purchase software every year- with one thing in common: They don’t know what’s in the software they buy and how to assess it.</em></p><p>This vast distribution chain consists of:</p><ul><li><strong>Software producers </strong>who<strong> </strong>toil hard to create great software we all use. They select components from a vast software ecosystem including open source software and build their own intellectual property on top of it. They package and deliver/deploy it. This software is then monetized through direct sales, indirect sales channels, System Integrators, MSPs, and others. All revenue flows through these routes to software producers and sustains their vast software ecosystem.</li><li><strong>Software consumers</strong> unlock the value locked inside the creations of software producers. They use this software to solve business and technical problems. The more value they create with each software they use, the more valuable it becomes. Without software consumers, software producers will not exist. However, software consumers have a significant concern — they spend significant resources to configure, manage, update, and upgrade the software they use. As their digital sprawl increases, software management, and security efforts are overwhelming them.</li><li><strong>Software sellers</strong> help software producers reach software customers. Software sellers sell directly to our customers; they are with our <strong>distributors and resellers and system integrators</strong>. They learn the software they sell. They are passionate about the value it can create. And they passionately toil to ensure that software consumers are taken care of. They make the business of software possible.</li></ul><p>As this great software distribution chain creates more than $5 trillion in value and wealth in 2024, there is a concern- <em>will my software producer put my business at risk?</em> Just like you need to know what’s in the food you buy, software consumers need to know what is in the software they buy from you. They need the ability to assess their ingredients. <em>If there are bad ingredients, it affects not just the software producer but everyone in the software distribution chain.</em></p><p>Everyone understands that most software is imperfect- but knowing the inherent risks in software helps them stay safe while operating this software. <strong><em>A fully Accurate, Attested, Assessed, and Compliant SBOM helps them select and operate the best software for their business needs.</em></strong> <strong><em>Transparency creates better, more secure usage of the software.</em></strong></p><p>Hence, Executive Order 14028 is driving this transparency. However, software sellers have a new friction point in their well-oiled machines. <em>They must ensure that attested and compliant SBOM gets to the right software consumer when needed.</em> They have a huge stake in the success of both software producers and consumers.</p><h3>Building an accurate SBOM is challenging, Distributing it privately &amp; securely is complex</h3><p>As software moves from software developers to software sellers, it changes in deep ways. This causes specific challenges for the distribution chain that must be addressed.</p><ol><li><strong>Software producers build products, Software consumers buy SKUs</strong>: Software producers build software products but sell software SKUs. So, our sellers sell SKUs. SKUs differ from products for many reasons-language, currency, bundling, unbundling, governmental regulations, compliance, technical stack support, and many other reasons. Each product that we create may ship in hundreds of configurations, and tens of languages be assembled into attractive bundles that delight software consumers. This allows us to deliver just the right value and product configuration to each consumer. This takes us to the first wrinkle of the distribution chain — can you publish and share an <strong>accurate SBOM per SKU </strong>you sell?</li><li><strong>SBOMs and their attestations are valuable. Should they be public and available to everyone or privately distributed?</strong> With 70–80 percent of software made up of third-party and open-source components, SBOMs reveal the recipe of the software they are associated with. Most software producers we have spoken to want to publish their SBOM and artifacts privately only. So, we want to ensure private, controlled sharing but at the same time maintain the benefit of frictionless selling. The right balance between privacy and sharing of published SBOMs has to be struck.</li><li><strong>Everyone needs to share SBOMs. So how how do you control sharing of SBOMs and artifacts? </strong>Sellers at Software Producing organizations need the ability to share SBOM and artifacts with their Customers during and after the sales cycle. The indirect channel needs to do so as well. Distributors need to share with resellers, and resellers with software consumers, and so on and so forth. They all want to be able to share a published SBOM and artifacts as needed. Additionally, the Software Consumer needs the ability to enable multiple people in their organization to access and assess SBOMs- from licensing terms to searching for a newly discovered vulnerability to Open-source usage or to Assess Third Party Risk. And at the same time, losing control over the SBOM and artifacts can cause all kinds of challenges. The ability to share SBOMs with full visibility and control over them is critical.</li><li><strong>Producers create product portfolios, Consumers buy from many vendors, Distributors deal with everyone &amp; new software versions appear faster every day</strong>. No one manages only one product and one version. The Distribution chain and software consumers have hundreds of products — all evolving. Software consumers need access to the SBOM and related artifacts of every version of all their vendors products. Not only that, but they also need the same from all their vendors. Software sellers rarely sell a single product. Software distributors distribute entire portfolios from hundreds and thousands of vendors. Software consumers buy hundreds of products every year. And SBOMs and their artifacts are digital artifacts that are complex and can contain thousands of component details. We need a distribution chain solution that can scale for these environments.</li></ol><p>So, to <strong>comply, assess, attest, update, search, remediate, to understand risk</strong> — the software distribution chain needs a solution much beyond an <strong>immutable, attested, assessed, compliant SBOM</strong>.</p><p>Well…the software distribution chain has a software supply chain problem! <strong><em>Software not built securely will compromise its customers and the whole $5 trillion eco-system loses.</em></strong></p><p>Luckily, there is a solution to that tailor-made for the distribution chain. Talk to <a href="http://www.lineaje.com/">Lineaje Inc.</a></p><blockquote><strong>Evaluate our new </strong><a href="http://www.sbom360hub.com/"><strong>SBOM360 Hub</strong></a><strong> for Software Consumers, distributors and resellers.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f15b14d1aed8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/the-software-supply-chain-has-a-software-distribution-chain-problem-f15b14d1aed8">The Software Supply Chain has a Software Distribution Chain Problem!</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EO 14028 Update (M-23–16): A Quarter of More Time, Clarifying Scope and POA&Ms!]]></title>
            <link>https://medium.com/lineaje/eo-14028-update-m-23-16-a-quarter-of-more-time-clarifying-scope-and-poa-ms-a15f7b48b03b?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/a15f7b48b03b</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[eo-14028]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Nick Mistry]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 17:33:57 GMT</pubDate>
            <atom:updated>2023-06-13T17:33:57.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*HiXaGQmiuViR_h4sCIwP-A.png" /></figure><p>TL;DR:</p><p>The latest guidance (memo <a href="https://www.whitehouse.gov/wp-content/uploads/2023/06/M-23-16-Update-to-M-22-18-Enhancing-Software-Security.pdf">M-23–16</a>) on <a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/">EO 14028 </a>offers several updates but most notably it extends the deadline for vendor attestation letters. Most anticipate an extension to the end of 2023 or beginning of 2024 at the latest. The memo also clarifies that the Agency CIOs determine if contractor developed software is “agency-software”; and, therefore out of scope. Lastly, it states that all attestation extension requests require a POA&amp;M, otherwise the agency must discontinue use of the software. <a href="http://lineaje.com/">Lineaje</a> offers solutions for EO 14028, check us out at <a href="http://lineaje.com/">lineaje.com</a> to learn more.</p><p>On June 9, 2023, the US Government released new guidance, <a href="https://www.whitehouse.gov/wp-content/uploads/2023/06/M-23-16-Update-to-M-22-18-Enhancing-Software-Security.pdf">M-23-16</a>, for the implementation of the <a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/">Executive Order (EO) 14028</a>, “Improving the Nation’s Cybersecurity”. This memo provides several key clarifications, most notably extensions to the deadlines for software producers to submit attestations to the Federal Government.</p><p>As organizations strive for EO14028 compliance, our team at <a href="http://lineaje.com/">Lineaje</a>, a software supply chain security company from Silicon Valley, is dedicated to developing solutions that assist software producers and agencies, alike.</p><p>Specifically, this memo (M-23-16) updates key aspects including:</p><ol><li>Extending the deadline for software producers to provide attestations</li><li>Clarifying scope of what types of software require attestations</li><li>Guidance on use of POA&amp;Ms by software producers</li></ol><p><strong>1. Extending the Deadline for Software Producers to Provide Attestations</strong></p><p>The memo M-23-16 extends the original deadlines for software producers to submit the EO conformity of attestation letters (based on requirements outlined in EO Guidance <a href="https://www.whitehouse.gov/wp-content/uploads/2022/09/M-22-18.pdf">M-22-18</a>).</p><p>According to the the update, software producers have three months for critical software, and six months for all software once the Attestation Letter is finalized and approved.</p><p>CISA has been aggressively pursuing the implementation of the EO and many speculate that CISA will move quickly; anticipating that the Attestation Letter will be finalized 1 to 2 months after the comment period closes on June 26, 2023. Requiring software producers to provide attestations by the end of the calendar year 2023 or at the latest by the beginning of 2024.</p><p><strong>How </strong><a href="http://lineaje.com/"><strong>Lineaje</strong></a><strong> can help:</strong> <em>We not only help create SBOMs (Software Bill of Materials) with the right dependency level depth and risk information but also automate generation of attestation letters which is immutably tied to the SBOMs. Lineaje enables software producers to tie multiple SBOMs to a single attestation letter, not just for products, but also for the SKUs software producers sell.</em></p><p><strong>2. Clarifying Scope of What Types of Software Requires Attestations</strong></p><p>This memo restates that the burden is placed on software producer of the end product to demonstrate that secure coding practices have been applied including “minimizing the risk third-party code”.</p><p><strong>Freely obtained and publicly available software is out of scope — but must be identified correctly</strong></p><p>The memo clarifies that agencies are not required to collect attestations for proprietary software that is <strong><em>freely obtained and publicly available. </em></strong>However, the memo reinforces that agencies are required to assess the risks of using such software and appropriately mitigate the risks. This implies that while agencies are not responsible for obtaining attestations from publicly available software — they are highly impacted by the inherent risks in the open source software they use.</p><p><strong>How </strong><a href="http://lineaje.com/"><strong>Lineaje</strong></a><strong> can help:</strong> <em>Lineaje helps organizations correctly identify their open source dependencies and reports on the inherent risks they drag in.</em></p><p><strong>Is federal contractor developed software in scope? — it depends</strong></p><p>The memo states that agency-developed software is considered out of scope; however, determining whether a federal contractor developed software under a federal contract is deemed “agency-software” — the answer is, it depends. According to the memo the agency CIO is responsible for determining if the software is “agency-developed”.</p><p>As previously noted in the original EO, organizations are required to identify all third-party and open source dependencies. They are also required to list any “Known Unknows” as part of their attestations.</p><p>If the dependencies are deemed too risky by the agencies (even though software producers think they are acceptable),agencies may not be able to use their software.</p><p><strong>How </strong><a href="http://lineaje.com/"><strong>Lineaje</strong></a><strong> can help:</strong> <em>Lineaje provides EO 14028 and SLSA attestations and compliance checks for software producers — with simple extensions for software that is built by either agency or federal contractors to help automate their processes.</em></p><p><strong>3. Guidance on use of POA&amp;Ms by Software Producers</strong></p><p>If a software producer cannot attest to the practices outlined in the attestation letter an agency may still use the software but requires a POA&amp;M (Plan Of Actions and Milestones) and risk mitigations.</p><p>A POA&amp;M is a formal “living document” agreed to by the software producer and agency, listing when and how the software producer will conform to the requirements, and what actions it will take to mitigate risks.</p><p><strong>How </strong><a href="http://lineaje.com/"><strong>Lineaje</strong></a><strong> can help</strong>: <em>With our “Publish” mechanism software producers can easily publish SBOMs, attestations, vulnerability disclosure reports and POA&amp;Ms across the entire software portfolio, enhancing transparency and compliance with the agencies that use their software.</em></p><p><strong>Conclusion</strong></p><p>In summary, the government has extended the deadline for Attestation Letters, but remains firm on their continued commitment to holding software producers accountable for the security of their products.</p><p><a href="http://lineaje.com/"><strong><em>Lineaje</em></strong></a><strong><em> offers a solution. With our EO14028 compliance automation, independent assessments, and secure sharing of Attestations, vulnerability disclosure, POA&amp;Ms, and artifacts, we help software producers and agencies achieve EO14028 compliance before the deadlines.</em></strong></p><p>Visit <a href="http://www.lineaje.com/">Lineaje.com</a> to learn more and contact us today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a15f7b48b03b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/eo-14028-update-m-23-16-a-quarter-of-more-time-clarifying-scope-and-poa-ms-a15f7b48b03b">EO 14028 Update (M-23–16): A Quarter of More Time, Clarifying Scope and POA&amp;Ms!</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing SBOM360 Hub from Lineaje Inc.]]></title>
            <link>https://medium.com/lineaje/introducing-sbom360-hub-from-lineaje-inc-4832a4b7178d?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/4832a4b7178d</guid>
            <category><![CDATA[sbom-exchange]]></category>
            <category><![CDATA[sbom-distribution-chain]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[supply-chain-security]]></category>
            <dc:creator><![CDATA[Javed Hasan]]></dc:creator>
            <pubDate>Wed, 17 May 2023 00:50:19 GMT</pubDate>
            <atom:updated>2023-05-18T01:51:29.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZ5Z_aAq7AsBGJ0vBfux1A.png" /><figcaption>Software supply chain security for your distribution chain</figcaption></figure><h3>Introducing SBOM360 Hub</h3><h4>Publish, Share &amp; Use compliant SBOMs with confidence</h4><blockquote>Today, Lineaje is proud to introduce the industry’s first comprehensive SBOM Exchange- <a href="http://www.sbom360hub.com/"><strong>SBOM360 Hub</strong></a> for the complex software distribution chain.</blockquote><h3>What does SBOM360 Hub do?</h3><p>SBOM360 Hub connects software producers, software consumers (customers), and software sellers (Sales organizations at Software Producers, Software Distributors, and Software Resellers) — enabling them to publish, share and use complaint SBOMs and related compliance artifacts.</p><p>As <a href="https://www.nist.gov/itl/executive-order-14028-improving-nations-cybersecurity">Executive Order 14028</a> takes effect starting September 2023, software producers and their distribution chain will see significant friction unless they can deliver SBOMs and linked attestation artifacts to their customers. This creates challenges for software sellers across the distribution chain as they scramble to acquire SBOMs from producers and share SBOMs and related artifacts with evaluators and buyers. Software consumers need access to their vendors’ SBOMs and related artifacts to evaluate them and assess compliance. The SBOM360 Hub addresses these needs directly.</p><h3>Who uses SBOM360 Hub?</h3><p>With the <strong>SBOM360 Hub</strong> organizations can manage their software distribution chain with a unified platform that enables frictionless sales between the producers and consumers of software.</p><ul><li><strong>Software Producers and Sellers </strong>can now create and publish approved, attested, assessed, compliant SBOMs, self-attestation forms, and related artifacts for their products, map them to SKUs they sell, and share privately with their customers and distribution chain in a timely manner</li><li><strong>Software Distributors and Resellers</strong> can request SBOMs and related artifacts from their vendors, make them available to their n-tier distribution (or distribution channels), and share them with their customers with a single click.</li><li><strong>Software Consumers</strong> can simply subscribe to SBOM360 Hub, and search and request access to specific vendor SBOMs and related artifacts in one location. They can also communicate directly with their vendors to request all SBOMs and related artifacts needed for evaluation, purchase, and compliance.</li></ul><p>Since all software is dynamic, the SBOM360 Hub provides automated notifications as software changes, new versions are released, or as new vulnerabilities, weaknesses, IOCs, etc. in the software become known. The SBOM360 Hub provides comprehensive security profiles of all open-source dependencies of these commercial products.</p><p>Users can search their SBOMs, their vendor’s SBOMs, and their entire dependency chain for vulnerabilities, threats, provenance, suppliers - or any of the more than 150 attributes providers give access to — in seconds.</p><p>Each version of every software is assessed by the SBOM360 Hub — enabling users to identify trends in the security profile of each software component enabling better roadmap planning and collaboration across the software distribution chain.</p><h3>SBOM360 Hub : Bringing trust back into software</h3><p>The SBOM360 Hub has been designed with all stakeholders in the software distribution chain. SBOM360 Hub aligns visibility between software producers and software consumers while providing software sellers the match-making ability to ensure software commerce is not impacted. SBOM360 Hub creates a safe, transparent &amp; collaborative exchange.<br> <br> SBOM360 Hub is feature rich. Key features Include:</p><h4>Private, secure &amp; searchable</h4><p>Software producers can now publish SBOMs for their specific distribution chain with restricted sharing, ensuring their privacy. All SBOMs are encrypted if downloaded but visible to, and shareable with, all stakeholders.</p><h4>Compliant SBOMs &amp; compliance artifacts</h4><p>SBOM360 Hub generates a compliance report (Does your SBOM meet EO14028 minimum compliance requirements?) and compliance artifacts (SDLC attestations and component-level attestations) for each version of each product ensuring that your distribution chain can continue to support your business seamlessly. These sets of documents are digitally linked and immutably notarized so the distribution chain and software consumers can use untampered, attested SBOMs that are tied to specific versions.</p><h4>SBOM publishing with controlled SBOM depth &amp; width</h4><p>SBOM360 Hub allows organizations to publish their SBOMs and compliance artifacts at Minimum, Recommended, or Custom depths, giving agencies the ability to request more detailed information in compliance with Executive Order 14028.</p><h4>SKU SBOMs or Product SBOMs: What’s your poison?</h4><p>Software Producers offer multiple versions of the same product- configured differently; with features enabled and disabled, language support, specific compliance needs, various form factors, various operating systems supported, and various target segments. These versions are packaged and sold as SKUs through the distribution chain which software consumers, distributors, and resellers interact with.</p><p>With SBOM360 Hub software producers can create and publish SBOMs for both their products &amp; SKUs which is useful for products that have multiple SKUs.</p><h4>Customer invitations, requests &amp; sharing with full visibility.</h4><p>The SBOM360 Hub is a private, secure, and collaborative workspace for software producers, consumers, resellers, and distributors to participate in the ecosystem easily. New members can be invited with a single click, allowing for easy sharing across the distribution chain.</p><h4>Subscribe to ALL SBOMs in one location!</h4><p>Software consumers now have the option to request their vendors’ SBOMs or be invited to access them. With SBOM360 Hub , just like Software producers can now publish all their SBOMs to their entire distribution chain in one place, software consumers can now subscribe to their vendors’ SBOMS and manage their entire software supply chain in one location. They can also subscribe to specific notifications such as when new versions are available or when new vulnerabilities are found. SBOM360 Hub assessment engines continuously scan all subscribed SBOMs and provide automated notifications for relevant updates like new critical vulnerabilities discovered.</p><h3>Software distributors &amp; resellers</h3><p>SBOM260 Hub allows for seamless software distribution while promoting collaboration and interaction between vendors and customers to improve the software that they both rely on.</p><p>The SBOM360 Hub upload API is compatible with any SBOM creation tool your organization may have chosen.</p><h3>Pricing</h3><p>Start with a free trial as a software producer, consumer or distributor, reseller, or system integrator. SBOM360 Hub is very attractively priced for our early customers. Take a look at our <a href="http://www.sbom360hub.com/">website</a> and start now.</p><h3>Getting started and availability</h3><p>SBOM360 Hub is available immediately for Early Access. Go to <a href="http://www.sbom360hub.com/">SBOM360Hub.com</a>, create an account and get started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4832a4b7178d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/introducing-sbom360-hub-from-lineaje-inc-4832a4b7178d">Introducing SBOM360 Hub from Lineaje Inc.</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3CX — A Way Forward as Another Software Supply Chain Attack compromises a Software Company and…]]></title>
            <link>https://medium.com/lineaje/3cx-a-way-forward-as-another-software-supply-chain-attack-compromises-a-software-company-and-4a051e51ad3b?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a051e51ad3b</guid>
            <dc:creator><![CDATA[Anand Revashetti]]></dc:creator>
            <pubDate>Fri, 07 Apr 2023 21:41:52 GMT</pubDate>
            <atom:updated>2023-04-07T03:28:54.079Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>3CX — A Way Forward as Another Software Supply Chain Attack compromises a Software Company and attacks its customers</strong></h3><h3>TLDR</h3><p>As the industry rallies around the 3CX attack and secures deployed 3CX electron App instances, the root cause is being ignored — a compromised software supply chain. For 3CX — there<em> is a mismatch between the source code they ingested and the packaged code they created. The threat was left of shift-left and so should the detection</em>. Not just 3CX but almost all software companies could be compromised this way. We discuss the way forward in this blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*u0WbM5YCJ4M5CGnpfxs5ag.png" /></figure><h3>The Fog of a Supply Chain Attack</h3><p>Runtime Threat detection companies have done a commendable job in detecting the 3CX software supply chain attack. The broader ecosystem has reacted well by containing the attack — with vendors adding detections, revoking certificates, and 3CX itself rapidly releasing a new version of its software.</p><p>3CX CISO has apologized. CEO Nick Galea has asked all customers to uninstall their own product. This software supply chain attack is directly impacting a company with 600,000 customers and 12 million users. A global software brand has just been taken advantage of.</p><p>However, much needs to be understood, even as researchers write intricate blogs about how the attack worked and how you can step-through the attack using advanced tools. The fog will lift eventually as 3CX will investigate and release details.</p><p>Just wanted to point out that this is a really good line! Great writing!</p><h3>Runtime Security Tools Failed to Stop 3CX Breaches</h3><p>The attack was executed by a known Lazarus threat actor group with known malicious C2 servers being contacted. Since the actor group was recognizable, EDR systems were able to flag suspicious activity from these applications early on, which brought the breaches to light.</p><p>At the same time, a sobering implication has been made apparent: multiple layers of security tools have failed.</p><p>First, 3CX was comprehensively compromised — whatever security tools they had — application security tools, malware scans, and SCA tools all were bypassed.</p><p>Second, all threat prevention tools — endpoint threat prevention products did not prevent the malware as it was deployed on millions of endpoints. The silence from network players is interesting for an attack that was detected by malicious network activity.</p><p>After the fact, when the attack became common knowledge, every runtime security tool claimed to detect and prevent malicious 3CX electron app versions.</p><p>The table below lays out a chronology of 3CX attack timeline. Effectively, the best estimate available is that the effort to compromise started Dec 7, 2022. The first infection was in January 2023 and the first detection was on March 29, 2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSIhpoOuAo2wSGVZhV3B0w.jpeg" /><figcaption>Chronology of 3CX attack timeline</figcaption></figure><h3>The Root Cause: An Unmanaged Software Supply Chain</h3><p>On March 30, 2023, the universal multi-media toolkit, makers of ffmpeg.dll announced the following on their twitter account:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8stAGy4QVv7aHhdfdjY34Q.png" /><figcaption>Makers of the universal multi-media toolkit’s statement</figcaption></figure><p>They effectively said that their source code is clean. 3CX build systems as they built the tampered versions were compromised. This is similar to SolarWinds, but the industry must wait for 3CX to explain the gory details. The net of this is that the source code is clean, but the built bits are compromised: <em>there is a mismatch between the source code and the packaged code. The threat was left of shift-left and so should the detection</em>. This is the reason the detection is post compromise and too late for many customers of 3CX. If the attackers never used known C2 servers, even EDR would not have raised a flag. This is the nature of modern supply chain attacks and runtime security tools cannot detect them.</p><p>Basically, the plumbing in place at 3CX — like every enterprise examined — could not attest to the integrity of their software. SCA tools and App Sec tools do not do this kind of attestation.</p><p>Establishing software supply chain integrity is hard — that is why we founded Lineaje.</p><h3>What Is Software Supply Chain Integrity and How Is It Achieved?</h3><p>Software supply chain integrity develops a chain of trust from your shipping product to the built components included in it to the source code they were built from — whether by you or in an open-source project. And then, integrity is established for each component you depend on, and so on and so forth, until every transitive component’s integrity is detailed.</p><h3>A Way Forward: Attest to the Integrity of Your Software Supply Chain Using Lineaje Component Attestation Levels (LCAL)</h3><p>Lineaje bases the supply chain integrity attestation on our proprietary and amazing fingerprinting technology. This enables us to create a software supply chain of trust with each link having its own integrity rating from a shipping product down to its last leaf component that has no further dependencies. Our fingerprinting-centric LCAL methodology has a significant advantage over build system-centric attestation approaches. Lineaje uses what is accessible, specifically package and source code. If you are using open-source software for example, those are accessible to you. So why not use them for attestation? If you modify those dependencies, you still have access to both enabling deep fingerprinting-based attestation.</p><p>Lineaje enables component attestations without dependency on any tools. This attestation is at a component level. A key thing to understand is that each attestation level is for the component itself, not for its dependencies. <strong><em>A highest-level component of attestation does not mean that its dependencies have as high an attestation as the parent. This is also true for SLSA and NIST and an inherent weakness of component-level attestation.</em></strong> This understanding is critical for supply chain security.</p><p>Last, but not the least, LCAL levels identify the weakest links in the software supply chain.<strong><em> With chained LCAL levels, Lineaje can attest that what you shipped is what you built, what you built is what you sourced, and what is sourced is what was published by your dependency, what was published is what was sourced by them, and so on and so forth all the way upstream to the leaf transitive dependency — a provable end to end attested software supply chain.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MCC8NrLfSLcgeHLNR74Gw.png" /><figcaption>Lineaje Component Attestation Level</figcaption></figure><p>Lineaje’s flagship product SBOM360 auto-attests all your software against these software integrity levels.</p><h3>Chronology of the 3CX breaches with Lineaje Attestation Levels In place</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fH52UQAVuaagHlkZnShVrg.jpeg" /></figure><p>A LCAL-3 violation would have triggered a mismatch between source code and a built package from it.</p><h3>Next Steps</h3><p>Attacks like the 3CX highlight the inherent weakness in the software supply chain. It’s not that 3CX was less prepared than other software development groups are, it’s just that they are unfortunate enough to be targeted first. Anyone could be vulnerable to this same scenario. You need to look at Supply Chain Integrity Management Software like SBOM360. If you are at RSA, look for us at <a href="https://www.eventbrite.com/e/visit-lineaje-to-experience-whats-in-your-software-supply-chain-rsac2023-tickets-590617792717">Lineaje.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a051e51ad3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/3cx-a-way-forward-as-another-software-supply-chain-attack-compromises-a-software-company-and-4a051e51ad3b">3CX — A Way Forward as Another Software Supply Chain Attack compromises a Software Company and…</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Ticking TimeSBOM, Howitzer Destruction, and Why Your SBOM Matters!]]></title>
            <link>https://medium.com/lineaje/a-ticking-timesbom-howitzer-destruction-and-why-your-sbom-matters-5fb73274012e?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/5fb73274012e</guid>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[sbom360]]></category>
            <category><![CDATA[lineaje-inc]]></category>
            <category><![CDATA[sbom]]></category>
            <category><![CDATA[eo-14028]]></category>
            <dc:creator><![CDATA[Javed Hasan]]></dc:creator>
            <pubDate>Sun, 12 Feb 2023 03:07:22 GMT</pubDate>
            <atom:updated>2023-02-13T20:59:40.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*0T7TzzdGKexdBjsLob8RSA.png" /></figure><h4>Tracing the Lineaje of all your software</h4><h3><strong>A lesson from Ukraine for every software developer</strong></h3><p>On December 22, 2016 Cybersecurity firm CrowdStrike published an interesting blog “<a href="https://www.crowdstrike.com/blog/danger-close-fancy-bear-tracking-ukrainian-field-artillery-units/">Danger Close: Fancy Bear Tracking of Ukrainian Field Artillery Units</a>” talking about the compromise of an application written by a Ukrainian military officer that reduced the time to fire D-30 122mm towed howitzers, from minutes to 15 seconds. Clearly a huge advantage in the middle of a war.</p><p>An Android app with the same name, and some Russian code inserted, surfaced soon after and was also used by the Ukrainian military. As per the blog, this inserted code in the application enabled Russian troops in the Crimea war to detect the location of Ukrainian D-30s. In subsequent conflict, 80% of the Ukrainian D-30s were destroyed resulting in a software supply chain attack with lethal consequences for Ukraine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/1*HlqgdHyWIF3lyrlEn-CULg.png" /></figure><blockquote>A supply chain lesson was learnt: Knowing what’s in your software is interesting but <strong>knowing what is unknown in the software you ship, and use, is critical</strong>. Cyber-security tools fail to identify the ‘Known Unknowns’ and take your focus ONLY to the ‘Known Knowns.’ Supply Chains can be poisoned!</blockquote><p>You would be right to wonder about the lax cyber-security of the Ukrainian defense establishment. Shouldn’t they be more careful? The fact is that they are very careful and to-date, use the best cyber-security tools. So, what went wrong? The fact is that the technology to unearth all the components within an application — with all its dependencies- didn’t really exist back then. This, lack of insight, provided an opportunity for their adversaries to infiltrate their operations.</p><p>Today, in your organization, even with app-sec tools, software composition analysis and shift-left security tools and runtime security controls you too cannot detect a supply chain tamper. That’s where more than 70% of your code comes from and where your biggest security risk ultimately comes from, leaving the software you ship or use susceptible to tampering. That’s why we created <a href="http://www.lineaje.com/"><strong>Lineaje!</strong></a></p><p>Read more about our company <a href="https://www.businesswire.com/news/home/20230207005224/en/Elite-Roster-of-Cybersecurity-Investors-Backs-Lineaje-to-Deliver-Industry-first-Supply-Chain-Security-Solution">here</a> .</p><h3>Executive Order 14028: Protecting Your Brand from Being Blown Up Like The D-30 Howitzer</h3><p>Fast forward to May 12, 2021. The Biden Whitehouse published its <a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/">Executive Order on Improving the Nation’s Cybersecurity</a> (Executive order 14028) to “Enhance Software Supply Chain Security”.” A key part of this mandate is for companies to <strong>Attest</strong> to two things:</p><blockquote><strong>What is in your software?</strong></blockquote><blockquote><strong>What part of your software is ‘unknown’ to you?</strong></blockquote><p>It also requires that procuring organizations now <strong>Assess</strong> the risk in using your software! For most of us who have built software used by millions, no one has ever truly <strong>Assessed</strong> your software. Now they will.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*YpG2897o-ki4coficXV4ew.png" /><figcaption>What will an Assessment of your software find? Do you actually know?</figcaption></figure><h3><strong>Tick-tock, Tick-tock….A Ticking TimeSBOM?</strong></h3><p>Following this Executive Order, NIST provided its guidance (<a href="https://csrc.nist.gov/publications/detail/sp/800-218/final">SP800–218</a>) a year later. It modified the SDLC and gave specific guidance on how software providers must attest the software they sell. The Office of Management and Budget (OMB), on September 14, 2022 , stepped in to require federal agency conformance to this guidance (<a href="https://www.whitehouse.gov/wp-content/uploads/2022/09/M-22-18.pdf">M-22–18</a>). Make sure you review the deadlines that vendors need to pay attention to carefully:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*it_RzSmEqcoFEpZwSgv2vQ.png" /></figure><p>A recent memo (<a href="https://www.gsa.gov/cdnstatic/MV-23-02_0.pdf">MV-23–02</a>) issued by the US General Services Administration (GSA) on January 111th, 2023 states that it will start collecting attestation letters for all impacted software, <em>regardless of whether it is considered critical</em>, on June 12th 2023. That is a full quarter earlier than the previously established date of September 14th, 2023.</p><blockquote>Net, you should be prepared by June 12 with your self-attestation letters and associated artifacts if you want to sell to these agencies.</blockquote><p>Additionally, artifacts like SBOMs, output from tools that validate integrity of the source code, checks for potential vulnerabilities etc. can be requested depending on the procurement agency. You need a tool that collects these for all the software you sell in any form.</p><p><strong>Ticking TimeSBOMs! Do You Know the Lineaje of your software?</strong></p><p>EO14028 is complicated. Hundreds of pages of follow-up documentation will make your eyes glaze over. However, at the core of it there are two simple requirements. For achievers, we have one recommendation:</p><p><strong>Requirement: A Self-Attestation Letter</strong></p><p>You should sign it with confidence if you know the answers to these two questions:</p><blockquote><strong><em>Q1: Do You know the which components that make up your software and can you attest to their integrity?</em></strong></blockquote><blockquote>You need the Lineaje of all software you deploy or ship, to attest the known unknowns?. If you use third party components that were not built in your CI/CD, can you attest to their integrity ?</blockquote><blockquote><strong><em>Q2: Do you know what components in your software are not known?</em></strong></blockquote><blockquote>That’s a tough one, isn’t it? This is the D-30 Howitzer question. Tell us about the components that you are not 100% confident of the source. Lineaje analysis has shown that about 20–30% of all COTS software is unknown today. Your current tools, including SCA tools, have no attestation basis. And if you have high OSS dependencies, that percentage is higher. And that is why Lineaje’s SBOM360 makes an explicit list of u<strong>n-attestable known knowns</strong> in your software- so you can resolve them BEFORE you a<strong>ttest</strong>.</blockquote><p><strong>Requirement 2: A Published SBOM</strong></p><p>You will need to publish a compliant SBOM. The SBOM you need to publish must be just right! And One size doesn’t fit all. That means:</p><blockquote><strong>The right format</strong>: Standard Digital format like SPDX. .</blockquote><blockquote><strong>The right information</strong>: Expect to ship multiple versions of your SBOM to comply with requests that are misaligned. Expect that civilian agencies need much less information than if you sell to the defense or military for example. Your customers in high regulation verticals will have their own demands.</blockquote><blockquote><strong>The right updates</strong>: When your software changes, so should its SBOM. In fact, software upgrades on previously purchased and currently deployed existing purchased software now requires SBOMSs. So, if you sold your software before the deadlines and now have a new version, that version cannot be taken unless you update your SBOM. If your update your SaaS software daily, update your SBOM daily too! You need continuous SBOM creation and delivery!</blockquote><h3>Does Your SBOM Truly Reflect Your Product and Your Brand?</h3><blockquote>Recommendation: Assess each SBOM BEFORE you publish it? Will your SBOM showcase your weaknesses or strengths?</blockquote><p><strong>Recommendation 1: SBOM Assessment</strong></p><p>EO14028 requires procuring organizations to Assess the SBOMs of all software they buy.</p><p>While your sales organization may be on the frontlines, addressing concerns shared by customers, the responsibility for addressing assessment findings in a timely manner falls squarely on your product team and CISO organizations. This is where Lineaje SBOM360 helps, by being the industry’s first SBOM assessment tool to proactively manage and monitor your SBOMs, no matter how they are created.</p><blockquote>With SBOM360, you can not only know what’s in your software but also know “how good is it” in terms of code quality, provenance, maintainability, security posture, vulnerabilities and so on and so forth. Not only that, but you can also compare across versions to show that your software is getting better with age!</blockquote><p>If you’re a software vendor, and this post has resulted in sudden heartburn and anxiety, put away that bottle of Pepto, and reach out to us today.</p><p><a href="http://www.lineaje.com/schedule-demo"><em>www.lineaje.com/schedule-demo</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fb73274012e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/a-ticking-timesbom-howitzer-destruction-and-why-your-sbom-matters-5fb73274012e">A Ticking TimeSBOM, Howitzer Destruction, and Why Your SBOM Matters!</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you know the Lineaje of your software?]]></title>
            <link>https://medium.com/lineaje/do-you-know-the-lineaje-of-your-software-ef258a609a34?source=rss----2b358a0c9e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef258a609a34</guid>
            <category><![CDATA[sbom360]]></category>
            <category><![CDATA[introducing-lineaje]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[sbom]]></category>
            <category><![CDATA[eo-14028]]></category>
            <dc:creator><![CDATA[Anand Revashetti]]></dc:creator>
            <pubDate>Mon, 26 Sep 2022 09:04:50 GMT</pubDate>
            <atom:updated>2022-09-26T09:04:50.350Z</atom:updated>
            <content:encoded><![CDATA[<h3>TL;DR</h3><h3><strong>SEO Meta Descriptions:</strong></h3><p>● Software supply chain management must be a major focus area for all companies using software. Read on to know why.</p><p>● Lineage provides SBOM360 — a unique Software Supply Chain Integrity Management solution. Learn more.</p><p>● 95% of software security vulnerabilities originate in the software supply chains, and SBOM360 is a one-stop-shop solution to address them.</p><h3><strong>Introduction</strong></h3><p>Every brand in every industry delivers on its brand promise through uncompromising focus on what it creates combining what it builds and what it sources from its suppliers. To do that, companies manage their supply chains not just their direct vendors. There is one exception to this rule- our software industry.</p><p>Our developers are innovative and smart. They like to do new things. If a capability can be sourced from the vibrant Open Source Software eco-system or bought from a private source, it is appropriate to do that. They then use those components (artifacts) and include them in their software. In-fact, we now assemble our software more than write it ourselves. Industry analysis puts third party code at 70–80 percent of any modern software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mbu8RgvajbiFkp6YAEbl6A.jpeg" /></figure><p>The software we source also has smart developers. Large parts of what they create is also sourced from third parties. And those third-party developers are also smart and so on and so forth. The software we deliver to our customers, contains what are called deep, n-level transitive dependencies embedded inside each artifact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*HUv608F_PsjkRQgXQzmEQg.png" /></figure><p>Some dependencies are static while some are dynamic. And each dependency can continue to change and evolve to the last second it is pulled. So, our software is as still as the ocean. This dynamic nature of software sets Software Supply Chain Management apart from the other, relatively static supply chains other industries deal with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*ZmGbgDxqjMNaLj8lxEAuDA.png" /></figure><p>To compound the challenge, we sometimes source pre-compiled binaries-where we don’t have access to the source code. Our customers don’t know what’s inside those and nor do we. For they too embed third party artifacts from their software supply chain.</p><p>And before we deploy the applications we have built, we will pull standard container images which again have deep third party dependencies and are part of our application as we deploy. That adds another layer of opaqueness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WaiQ67HMuuf-xGiQz9zPKg.jpeg" /></figure><p>This opaqueness in your software comes from three sources: Open Source Code, Private Code written by your developers and also third party code you sourced from your vendors. Missing any one of these gives you an incomplete picture of your software.</p><h3><strong>Beyond Cybersecurity Executive Orders Lies A Greater Corporate Responsibility</strong></h3><p><a href="https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity">Cybersecurity Executive Order 14028</a> requires many of us to publish a correct SBOM. The key word there is correct. How important is it to be correct? Think of food labels on food we buy — what is the value of a brand that is incorrectly states its ingredients? Your SBOM accuracy is a direct reflection of your brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GlAU1U-JpEoYWYbTuipOng.jpeg" /></figure><p>As supply chain attacks continue to rise, an incorrect SBOM puts your customers at risk. Missing out peanuts as an ingredient in a food label can have a catastrophic impact on peanut-allergic customers as well as on that food brand. Product teams have a special responsibility to ensure the correctness of their SBOM. Your failure to mention your software contains Log4J, and every instance of it, would compromise your customers. The sin of omission becomes a sin that commissions a crime — a breach downstream. Remember Solar Winds.</p><p>As software gets deeper into everyday lives of people, we have a special responsibility to build safe, better software. Should your brand be the one that omits to tell your customers that your software contains peanuts? Determining what makes up your software, is too important a call to be left to the whims of individual developers. Remember, the very smart software developers who build our amazing software are experts in their individual domains but software security in not necessarily their gig. This is a collective corporate governance issue. Companies that fail to do this will be exploited — smart hackers will breach them and, unfortunately, their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*w_eEEZx1_kMXELwTy0NK9g.png" /></figure><p>An omission here, commissions a criminal breach downstream.</p><p>And for those companies that use software, insist on an accurate SBOM. If not, you can be SolarWinded by your trusted software vendor.</p><h3><strong>Vulnerabilities Overwhelm Us And We Let that Happen</strong></h3><p>Our Industry is overwhelmed with vulnerabilities. In fact, we are so overwhelmed with vulnerabilities that we now spend effort &amp; real dollars to prioritize vulnerabilities for us. Smart companies help us find real breach paths and trace execution paths in our software. Why? So we can decide which vulnerabilities are safe for us to not do anything about!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*o50qaHjodsouc3HH53rkqQ.png" /></figure><p>Would you buy a car that had safe vulnerabilities? And people discovered new ones every day. If the car manufacturer could turn around and tell you that they have now found a new critical vulnerability that you should fix for them? Would you buy that car again? The fact is that we discovered 10 High and 32 Medium vulnerabilities every day in 2021.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fsSgsINwMSDAR3b4EXWiuA.jpeg" /></figure><p>What’s the Software Supply Chain link here? More than 95% of all vulnerabilities come from our Software Supply Chain. Vulnerabilities are security defects and 95% come from your supply chain. And yet, today, Lineaje analysis shows us that you don’t know who your top software suppliers are and no one in your company has ever evaluated them, spoken to them or probably even heard of them. Why? Software companies don’t manage software supply chain.</p><p>Not just who the suppliers are,, we don’t even know if our software has those artifacts that have those vulnerabilities. Today, for most companies, it is a journey of painful discovery to figure out if their software is impacted by a new vulnerability. If you have more vendor software, good luck in finding that out. And if your customers have concerns — your security, product and sales people spend days sorting that out with them An immense loss of productive capacity.</p><p>After you have done all that, go back to the opaqueness of the Software Supply Chain we discussed, and you now have an iceberg analogy. Today, you just see the iceberg above water. Under the water line, lies the opaque risk in your software. Get visibility underwater and then manage it. Build a correct SBOM and then manage that SBOM. Your vulnerability pain will drop as you hold your supply chain accountable for what they do to you- everyday.</p><p>And this is why we built <a href="https://www.sbom360.com/">SBOM360</a>. To solve basic hygiene and integrity issues in the Lineaje of your software.</p><h3>The Myth Behind Software Composition Analysis Tools</h3><p>Many Software Composition Analysis (SCA) tools claim that they can create a Software Bill of Materials (SBOM) that discovers what’s in your software. We analysed all SCA tools and found none of them could generate a correct SBOM. Why would that be?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*gWsF76ZHLvp9xORzbn4lVw.png" /></figure><p>The issues are many but the key challenges are:</p><ul><li>SCA tools trust the software they interrogate and believe the answers it gives. Hence a SCA tool has never detected a Supply Chain Compromise.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*2F-ElfpdFiByhh68jDfUJQ.png" /></figure><ul><li>SCA tools cannot get past the opaqueness of the software they interrogate. Hence they miss the majority of transitive dependencies</li><li>SCA tools , in most cases, will analyze part of what your software contains- the builds, source code, binaries OR container Images. The operative word there is OR. The rest is opaque.</li><li>SCA Tools can easily be tampered with. It is trivial for any software developer or attacker in the supply chain to fool a SCA tool. SCA tools are no security guardians.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li__wvA5i2OJcb0TcfzH_w.jpeg" /></figure><h3>A Correct SBOM Is Not Necessarily A Good SBOM</h3><p>Once you have a SBOM, generated by us or by your SCA tool, Shouldn’t you know what your Customers will find when they evaluate it?</p><p>Just like we look at ingredients of food labels to decide whether we want to buy a food product, our Customers will evaluate our SBOM. In fact, the US Senate passed a law Supply Chain Security Training act to train federal procurement offices to evaluate software procured for supply chain attacks. Our SBOMs will be exhibit one in that analysis.</p><p>A correct SBOM evaluation may bring some bad visibility to you but you also know what you must fix. There is, however, an immediate upside. Once SBOM360 has your SBOM there are hundreds of operational benefits. For example:</p><ul><li>How long did it take you to find how many instances of Log4j were in your software? Or in your vendors software? Or in OSS software you used? SBOM360 does it in seconds.</li><li>More than 95% of vulnerabilities are come from your software supply chain. Vulnerabilities are one type of security/software defects. That set of developers may know their domain but really are not security conscious. Can you quantify that risk? SBOM360 can.</li><li>A stable dormant OSS artifact you use, just got a new version. Should you take it automatically? Do you know that the new update came from contributions of an author that had not contributed to that OSS project before? SBOM360 does.</li></ul><h3><strong>The Solution: Introducing SBOM360</strong></h3><p><a href="https://www.sbom360.com/">SBOM360</a> is the industry’s first SBOM Manager. Take your SBOM in any standard format and SBOM360 can ingest it in seconds. If you deploy our CLI, we will auto-create your SBOM without the issues of the SCA tools. And then, we will give your our report card on your SBOM. This is what your customers can also find out from your SBOM-especially if they use us to do so.</p><p>Never had a SBOM Security policy? Now is the time to create and apply one. If you ship in many countries or have to satisfy many compliance regimes, not a problem — create many policies. SBOM360 evaluates your SBOM against your policies and tell you how your software stacks up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MOeYe9WgoE-FxiED7OfyNg.jpeg" /></figure><p>Because we know more about what your software contains — including OSS and Private Source- we bring-in their transitive dependencies. And you can evaluate your entire SBOM on multiple dimensions including but not limited to Vulnerabilities, Provenance, Licensing, Security Posture, Code Complexity etc.</p><p>SBOM360 automatically validates the integrity of your SBOM — the fact that the software artifacts you think you are using is actually the software artifact you are using. And should the reputation of the artifact your developer just used, actually match the security policy you have?</p><p>SBOM360 take the long view- you can only improve what you evaluate. We enable you to manage the complete life-cycle of your SBOM from inception to Publish to new versions. To understand how well we do it, explore <a href="https://www.sbom360.com/">www.SBOM360.com</a> If we have missed something, work with us. We will make it right for you.</p><h3>One SBOM? What About the Rest?</h3><p>Most software organisations don’t really build just one application. We build hundreds or thousands. If building one correctly and evaluating one is a challenge, how do you do this at scale. Well, once you have done one; SBOM360 has already learnt how to work with you. So SBOM360 will do the rest for you — Shouldn’t that what a SBOM Manger should do? And So it does. Try it.</p><p>Comprehensive SBOM Lifecycle Management at your fingertips. Start Small. Evaluate one SBOM. Then Manage All. We will work with you. Explore <a href="https://www.sbom360.com/">www.SBOM360.com</a>.</p><h3>Introducing Lineaje</h3><p>Lineaje is focused on Software Supply Chain Integrity Management. We have much to do. However, as we worked with our initial customers it became abundantly clear that we don’t really know what’s in our software. We can’t manage and secure your Software Supply Chain if you don’t know what’s in your software. So the journey starts with SBOM360.</p><p>It’s a small step. It’s the right step. Know your Software Supply Chain first. Start with SBOM360.</p><p>—</p><p><a href="https://www.linkedin.com/in/javedhasan">Javed Hasan</a></p><p>Co-Founder &amp; CEO, <a href="https://www.lineaje.com/">Lineaje</a></p><p><a href="https://www.linkedin.com/in/arevashe">Anand Revashetti</a></p><p>Co-Founder &amp; CTO, <a href="https://www.lineaje.com/">Lineaje</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef258a609a34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lineaje/do-you-know-the-lineaje-of-your-software-ef258a609a34">Do you know the Lineaje of your software?</a> was originally published in <a href="https://medium.com/lineaje">Lineaje</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>