<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engagements &amp; Tests on DefectDojo Documentation</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/</link><description>Recent content in Engagements &amp; Tests on DefectDojo Documentation</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2025 DefectDojo, Inc.</copyright><lastBuildDate>Fri, 30 Oct 2026 22:38:40 +0000</lastBuildDate><atom:link href="https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/index.xml" rel="self" type="application/rss+xml"/><item><title>Organizations</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__organizations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__organizations/</guid><description>&lt;p&gt;&lt;strong&gt;ORGANIZATIONS&lt;/strong&gt; → Assets → Engagements → Tests → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Organizations&lt;/strong&gt; sit at the very top of DefectDojo’s object hierarchy. Organizations are distinct from the descending objects in the hierarchy—Assets, Engagements, Tests, and Findings—because they are not technical scan targets, but rather serve primarily as organizational abstractions that compartmentalize your security efforts according to:&lt;/p&gt;</description></item><item><title>Organizations</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__organizations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__organizations/</guid><description>&lt;p&gt;&lt;strong&gt;ORGANIZATIONS&lt;/strong&gt; → Assets → Engagements → Tests → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Organizations&lt;/strong&gt; sit at the very top of DefectDojo’s Asset hierarchy. Organizations are distinct from the descending objects in the hierarchy—Assets, Engagements, Tests, and Findings—because they are not technical scan targets, but rather serve primarily as organizational abstractions that compartmentalize your security efforts according to:&lt;/p&gt;</description></item><item><title>Assets</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__assets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__assets/</guid><description>&lt;p&gt;Organizations → &lt;strong&gt;ASSETS&lt;/strong&gt; → Engagements → Tests → Findings&lt;/p&gt;
&lt;p&gt;An Asset is the thing whose security posture you want to track over time, such as an application, an API or a cloud environment. It holds every Engagement, Test and Finding for that thing, and its settings decide the SLA, permissions and deduplication scope those Findings use. To decide how broad each Asset should be, read &lt;a href="#asset-examples"&gt;Asset Examples&lt;/a&gt; and &lt;a href="#asset-boundaries"&gt;Asset Boundaries&lt;/a&gt;. To add an Asset, see &lt;a href="#create-assets"&gt;Create Assets&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Assets</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__assets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__assets/</guid><description>&lt;p&gt;Organizations → &lt;strong&gt;ASSETS&lt;/strong&gt; → Engagements → Tests → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Assets&lt;/strong&gt; sit at the center of how security work is organized within DefectDojo’s object hierarchy. Assets represent any project, program, software, or physical asset that your security team is testing, and host all of the security work and testing history related to the testing goal. Examples of Assets can include:&lt;/p&gt;</description></item><item><title>Engagements</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__engagements/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__engagements/</guid><description>&lt;p&gt;Organizations → Assets → &lt;strong&gt;ENGAGEMENTS&lt;/strong&gt; → Tests → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;In DefectDojo’s Asset hierarchy, Engagements are time- or pipeline-bound containers that represent groups of related Tests within a specific Asset. If you have a planned testing effort scheduled, whether on a routine or one-time basis, an Engagement offers you a place to store all of the related results.&lt;/p&gt;</description></item><item><title>Engagements</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__engagements/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__engagements/</guid><description>&lt;p&gt;Organizations → Assets → &lt;strong&gt;ENGAGEMENTS&lt;/strong&gt; → Tests → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;In DefectDojo’s Asset Hierarchy, Engagements are time- or pipeline-bound containers that represent groups of related Tests within a specific Asset. If you have a planned testing effort scheduled, whether on a routine or one-time basis, an Engagement offers you a place to store all of the related results.&lt;/p&gt;</description></item><item><title>Tests</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__tests/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__tests/</guid><description>&lt;p&gt;Organizations → Assets → Engagements → &lt;strong&gt;TESTS&lt;/strong&gt; → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;A Test is a container for one or more scan executions, which are used to discover flaws in an Asset. Tests are the final, most granular component of DefectDojo’s Asset hierarchy, serving as the container for the Findings that result from an execution of a security tool or manual assessment while also adding the context in which any such Findings were found (i.e., which tool reported it, when that tool was last run, etc.).&lt;/p&gt;</description></item><item><title>Tests</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__tests/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__tests/</guid><description>&lt;p&gt;Organizations → Assets → Engagements → &lt;strong&gt;TESTS&lt;/strong&gt; → Findings&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;A Test is a container for one or more scan executions, which are used to discover flaws in an Asset. Tests are the final, most granular component of DefectDojo’s object hierarchy, serving as the container for the Findings that result from an execution of a security tool or manual assessment while also adding the context in which any such Findings were found (i.e., which tool reported it, when that tool was last run, etc.).&lt;/p&gt;</description></item><item><title>Findings</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__findings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/os__findings/</guid><description>&lt;p&gt;Organizations	→ Assets → Engagements → Tests → &lt;strong&gt;FINDINGS&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Findings&lt;/strong&gt; represent the lowest level of the Asset Hierarchy where individual vulnerabilities are tracked and managed, and are the main way that DefectDojo standardizes and guides the reporting and remediation process of your security tools. Regardless of whether a vulnerability was reported in SonarQube, Acunetix, or your team’s custom tool, Findings give you the ability to manage each vulnerability in the same way.&lt;/p&gt;</description></item><item><title>Findings</title><link>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__findings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/asset_modelling/engagements_tests/pro__findings/</guid><description>&lt;p&gt;Organizations	→ Assets → Engagements → Tests → &lt;strong&gt;FINDINGS&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Findings&lt;/strong&gt; represent the lowest level of the Asset Hierarchy where individual vulnerabilities are tracked and managed and serve as the main way that DefectDojo standardizes and guides the reporting and remediation process of your security tools. Regardless of whether a vulnerability was reported in SonarQube, Acunetix, or your team’s custom tool, Findings give you the ability to manage each vulnerability in the same way.&lt;/p&gt;</description></item></channel></rss>