<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asset Hierarchy on DefectDojo Documentation</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/</link><description>Recent content in Asset Hierarchy on DefectDojo Documentation</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2025 DefectDojo, Inc.</copyright><lastBuildDate>Wed, 28 Oct 2026 19:46:42 +0000</lastBuildDate><atom:link href="https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/index.xml" rel="self" type="application/rss+xml"/><item><title>Asset Hierarchy</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/asset_hierarchy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/asset_hierarchy/</guid><description>&lt;p&gt;DefectDojo Pro is extending the Product/Product Type object classes to provide greater flexibility with the data model.&lt;/p&gt;
&lt;h2 id="enabling-the-hierarchy-feature"&gt;Enabling the Hierarchy Feature&lt;/h2&gt;
&lt;p&gt;The two pieces below are separate, and are controlled by different means.&lt;/p&gt;</description></item><item><title>Assign Priority, Risk and SLAs</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/priority_sla/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/priority_sla/</guid><description>&lt;p&gt;

&lt;img
 src="https://beta-docs.defectdojo.com/images/pro_finding_priority.png"
 width="1478"
 height="492"
 decoding="async"
 fetchpriority="auto"
 loading="lazy"
 alt="image"
 id="h-rh-i-0"
 class="dd-shot dd-shot-light"
&gt;&lt;img
 src="https://beta-docs.defectdojo.com/images/dark/pro_finding_priority.png"
 width="1478"
 height="492"
 decoding="async"
 fetchpriority="auto"
 loading="lazy"
 alt="image"
 id="h-rh-i-0-dark"
 class="dd-shot dd-shot-dark"
&gt;&lt;/p&gt;
&lt;p&gt;Effective risk-based vulnerability management requires an approach that considers
both business context and technical exploitability. Using DefectDojo Pro’s Priority and Risk feature, users can automatically sort Findings into a meaningful context, ensuring
high-impact vulnerabilities can be addressed first.&lt;/p&gt;</description></item><item><title>Plan your hierarchy</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/plan_your_hierarchy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/plan_your_hierarchy/</guid><description>&lt;p&gt;&lt;span style="background-color:rgba(242, 86, 29, 0.3)"&gt;Note: parent and child Assets and the five priority fields are DefectDojo Pro features. The advice on Organizations and Assets applies to Open Source as well, which makes this a good page to read before moving from Open Source to Pro.&lt;/span&gt;&lt;/p&gt;</description></item><item><title>Change plans: review every change before it happens</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/change_plans/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/change_plans/</guid><description>&lt;p&gt;Reorganizing the hierarchy touches many Assets at once: moving an Asset to another Organization takes its subtree along, removes parent links that would cross Organizations, and recalculates priority for both Organizations. A change plan lets you see every one of those effects before anything is written.&lt;/p&gt;</description></item><item><title>Threat Intelligence</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/threat_intelligence/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/threat_intelligence/</guid><description>&lt;p&gt;DefectDojo Pro enriches your findings with &lt;strong&gt;dedicated threat intelligence&lt;/strong&gt; — exploit
availability, known exploitation, and threat-actor activity — and factors it into Priority
and Risk. This goes well beyond EPSS and the CISA KEV flag.&lt;/p&gt;</description></item><item><title>You can reorganize later</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/reorganize_later/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/reorganize_later/</guid><description>&lt;!--
Links to add once the pages for these features are on dev (each is still in review):
 * Change plans (dry-run diff, CSV upload and diff export, apply and undo):
 asset_modelling/PRO_hierarchy/change_plans.md. Link it from "Moving many Assets at once"
 and from the intro, as the way to review a large reorganization before it happens.
 * Needs Attention inbox and the onboarding-complete measure:
 asset_modelling/PRO_hierarchy/finish_onboarding.md. Link it from "Before you start moving
 things" and from "Re-mapping a Connector Record", for finding Assets still in a Connector's
 default Organization or missing priority fields.
 * Rules Engine computed destinations (place Assets by tag, connector attribute or name):
 automation/triage_engine/building_rules.md and node_reference.md. Link them from
 "Moving many Assets at once", for placement that keeps happening as new Assets arrive.
 * The Security Hub re-place action for existing Assets:
 connectors/toolreference/security_hub.md. Link it from "Re-mapping a Connector Record".
--&gt;
&lt;p&gt;The safest hierarchy plan is one you can change. DefectDojo Pro lets you get scan data in on day one with a reasonable structure, then move Assets between Organizations, change their parents, or point Connector Records at different Assets as you learn more, without losing Findings, their history or their deduplication state.&lt;/p&gt;</description></item><item><title>Finish onboarding: Assets that need attention</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/finish_onboarding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/finish_onboarding/</guid><description>&lt;p&gt;A connector can create thousands of Assets in its first sync. It cannot do two things for them: put each one in the right Organization, and say what each one is worth to your business. Until both are done, DefectDojo Pro ranks Findings and picks SLAs from defaults.&lt;/p&gt;</description></item><item><title>Framework Presets</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/framework_presets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/framework_presets/</guid><description>&lt;p&gt;Most of what a framework asks of vulnerability management is a number: patch critical flaws within 14 days, or within 48 hours when an exploit exists, and scan weekly or fortnightly. A framework preset bundles those numbers as DefectDojo Pro settings: SLA configurations, scan cadence policies, a response policy and a set of checks, named after the scheme and the version of it they encode. You apply a preset in one step after previewing exactly what it would change, and you can revert it later.&lt;/p&gt;</description></item><item><title>Asset Health Grade</title><link>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/asset_health_grade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/pro_hierarchy/asset_health_grade/</guid><description>&lt;p&gt;DefectDojo can calculate a grade for your Assets based on the amount of Findings contained within. Grades are ranked from A - F.&lt;/p&gt;</description></item></channel></rss>