Deploy the generated website via GitHub Actions

README.md

@@ -1 +1 @@
-Website last update: 2024-12-20 at 11:01:36.
+Website last update: 2024-12-29 at 22:13:05.

cheatsheets/Threat_Modeling_Cheat_Sheet.html

@@ -2171,7 +2171,7 @@
           <li class="md-nav__item">
   <a href="#identify-risks-early-on" class="md-nav__link">
     <span class="md-ellipsis">
-      Identify Risks Early-On
+      Identify Risks Early On
     </span>
   </a>
 
@@ -2672,7 +2672,7 @@
           <li class="md-nav__item">
   <a href="#identify-risks-early-on" class="md-nav__link">
     <span class="md-ellipsis">
-      Identify Risks Early-On
+      Identify Risks Early On
     </span>
   </a>
 
@@ -2851,7 +2851,7 @@ <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" tit
 <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>In the context of application security, threat modeling is a structured, repeatable process used to gain actionable insights into the security characteristics of a particular system. It involves modeling a system from a security perspective, identifying applicable threats based on this model, and determining responses to these threats. Threat modeling analyzes a system from an adversarial perspective, focusing on ways in which an attacker can exploit a system.</p>
 <p>Threat modeling is ideally performed early in the SDLC, such as during the design phase. Moreover, it is not something that is performed once and never again. A threat model is something that should be maintained, updated and refined alongside the system. Ideally, threat modeling should be integrated seamlessly into a team's normal SDLC process; it should be treated as standard and necessary step in the process, not an add-on.</p>
-<p>According to the <a href="https://www.threatmodelingmanifesto.org/">Threat Model Manifesto</a>, the threat modeling process should answer the following four questions:</p>
+<p>According to the <a href="https://www.threatmodelingmanifesto.org/">Threat Modeling Manifesto</a>, the threat modeling process should answer the following four questions:</p>
 <ol>
 <li>What are we working on?</li>
 <li>What can go wrong?</li>
@@ -2861,7 +2861,7 @@ <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanen
 <p>These four questions will act as the foundation for the four major phases described below.</p>
 <h2 id="advantages">Advantages<a class="headerlink" href="#advantages" title="Permanent link">&para;</a></h2>
 <p>Before turning to an overview of the process, it may be worth addressing the question: why threat model? Why bother adding more work to the development process? What are the benefits? The following section will briefly outline some answers to these questions.</p>
-<h3 id="identify-risks-early-on">Identify Risks Early-On<a class="headerlink" href="#identify-risks-early-on" title="Permanent link">&para;</a></h3>
+<h3 id="identify-risks-early-on">Identify Risks Early On<a class="headerlink" href="#identify-risks-early-on" title="Permanent link">&para;</a></h3>
 <p>Threat modeling seeks to identify potential security issues during the design phase. This allows security to be "built-into" a system rather than "bolted-on". This is far more efficient than having to identify and resolve security flaws after a system is in production.</p>
 <h3 id="increased-security-awareness">Increased Security Awareness<a class="headerlink" href="#increased-security-awareness" title="Permanent link">&para;</a></h3>
 <p>Proper threat modeling requires participants to think creatively and critically about the security and threat landscape of a specific application. It challenges individuals to "think like an attacker" and apply general security knowledge to a specific context. Threat modeling is also typically a team effort with members being encouraged to share ideas and provide feedback on others. Overall, threat modeling can prove to be a highly educational activity that benefits participants.</p>