---
title: "Applying your Risk Score: Where it Belongs & Where it Doesn’t"
url: "https://www.armorcode.com/podcast/applying-your-risk-score-where-it-belongs-where-it-doesnt"
markdown_url: "https://www.armorcode.com/podcast/applying-your-risk-score-where-it-belongs-where-it-doesnt.md"
llm_canonical: "https://www.armorcode.com/podcast/applying-your-risk-score-where-it-belongs-where-it-doesnt.md"
canonical_for_llm: true
entity_type: "Article"
primary_entity: "Applying your Risk Score: Where it Belongs & Where it Doesn’t"
citation_value: "Published on ArmorCode; canonical URL https://www.armorcode.com/podcast/applying-your-risk-score-where-it-belongs-where-it-doesnt."
last_updated: "2025-02-21T08:01:11-08:00"
---

<h1>Applying your Risk Score: Where it Belongs &amp;#038; Where it Doesn&amp;#8217;t</h1>

#LTAPod is back for a new season of 5-minute AppSec with Mark Lambert and Luis Guzmán in the ArmorCode studio. On the table today: risk scores. We take a turn from last month’s episode on risk prioritization/scoring to delve into how risk scores are utilized by teams—and when their use might backfire. As a standalone metric, one’s overall score can be helpful for posture-at-a-glance; but as a measure or goalpost for team performance, security leaders may find their score too volatile or reductive. This should track when considering that a risk score’s purpose isn’t to quantify a team’s efforts, but to prioritize them.