---
title: "Factors in Prioritization"
url: "https://www.armorcode.com/podcast/factors-in-prioritization"
markdown_url: "https://www.armorcode.com/podcast/factors-in-prioritization.md"
llm_canonical: "https://www.armorcode.com/podcast/factors-in-prioritization.md"
canonical_for_llm: true
entity_type: "Article"
primary_entity: "Factors in Prioritization"
citation_value: "Published on ArmorCode; canonical URL https://www.armorcode.com/podcast/factors-in-prioritization."
last_updated: "2025-02-21T08:01:12-08:00"
---

<h1>Factors in Prioritization</h1>

Prioritizing threat/vulnerability findings takes thought, a satellite cam, and a microscope if you don’t have an AppSecOps platform at work. There’s a lot to consider: criticality variance across tools (they don’t come normalized out of the box), threat intelligence on CVEs, and tool/technique weight factors for starters. A major concept is the context around the app/sub-app/module associated with a finding. The software’s dependencies, environment, provenance, and the sensitivity of its data are just a few values that affect priority.