<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Incident-Response on Security Blueprints</title>
    <link>https://securityblueprints.io/tags/incident-response/</link>
    <description>Recent content in Incident-Response on Security Blueprints</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>user@example.com (Niels Provos)</managingEditor>
    <webMaster>user@example.com (Niels Provos)</webMaster>
    <copyright>Security Blueprints, LLC</copyright>
    <lastBuildDate>Sun, 06 Sep 2026 23:57:45 +0000</lastBuildDate>
    <atom:link href="https://securityblueprints.io/tags/incident-response/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Supply Chain Aging</title>
      <link>https://securityblueprints.io/security-invariants/supply-chain-aging/</link>
      <pubDate>Fri, 01 Nov 2024 00:00:00 +0000</pubDate><author>user@example.com (Niels Provos)</author>
      <guid>https://securityblueprints.io/security-invariants/supply-chain-aging/</guid>
      <description>Overview Supply Chain Aging is a security invariant that mandates all third-party open-source software to be aged by a specified number of days before it can be imported into the production environment. This aging period allows the community to identify and mitigate any malicious backdoors or vulnerabilities that may have been introduced into the software.&#xA;Benefits Increased Detection of Malicious Code: Significantly increases the likelihood that malicious backdoors inserted into open-source packages have been found and removed.</description>
    </item>
  </channel>
</rss>
