<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Federal Compliance on DefectDojo Documentation</title><link>https://beta-docs.defectdojo.com/federal_compliance/</link><description>Recent content in Federal Compliance on DefectDojo Documentation</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2025 DefectDojo, Inc.</copyright><atom:link href="https://beta-docs.defectdojo.com/federal_compliance/index.xml" rel="self" type="application/rss+xml"/><item><title>Compliance Profile</title><link>https://beta-docs.defectdojo.com/federal_compliance/compliance_profile/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/compliance_profile/</guid><description>&lt;p&gt;The Compliance Profile enrolls an Asset as a system and holds the facts that appear on every
deliverable it produces. Open the Asset that represents your system boundary, go to the
&lt;strong&gt;Compliance&lt;/strong&gt; tab, then &lt;strong&gt;Profile&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>The POA&amp;M Ledger</title><link>https://beta-docs.defectdojo.com/federal_compliance/poam_ledger/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/poam_ledger/</guid><description>&lt;p&gt;POA&amp;amp;M items are created and updated automatically from findings. The sync runs shortly after
imports and finding changes, and a nightly sweep catches anything that slipped through. You can
also add items by hand, for weaknesses that no scanner reports.&lt;/p&gt;</description></item><item><title>ConMon Snapshots</title><link>https://beta-docs.defectdojo.com/federal_compliance/conmon_snapshots/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/conmon_snapshots/</guid><description>&lt;p&gt;On the &lt;strong&gt;Snapshots&lt;/strong&gt; tab, &lt;strong&gt;Generate Snapshot&lt;/strong&gt; produces the deliverables for a reporting period.
A snapshot &lt;strong&gt;freezes the ledger&lt;/strong&gt; as of that moment: later edits never change a deliverable you
have already generated.&lt;/p&gt;</description></item><item><title>Remediation Deadlines</title><link>https://beta-docs.defectdojo.com/federal_compliance/remediation_slas/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/remediation_slas/</guid><description>&lt;p&gt;Two ready-made SLA configurations ship with the feature. Assign either to your Assets from SLA
configuration settings, or copy one and adjust it.&lt;/p&gt;</description></item><item><title>Potential Agency Impact (PAIN) Ratings</title><link>https://beta-docs.defectdojo.com/federal_compliance/pain_ratings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/pain_ratings/</guid><description>&lt;p&gt;FedRAMP&amp;rsquo;s Vulnerability Detection and Response standard does not set one deadline per severity. It
sets a deadline per &lt;em&gt;combination&lt;/em&gt; of how exploitable a vulnerability is, whether it is reachable
from the internet, and how much damage its exploitation would do to the agencies using your service.
That third factor is the &lt;strong&gt;Potential Agency Impact N-rating&lt;/strong&gt;, or PAIN.&lt;/p&gt;</description></item><item><title>Setting Up PAIN Ratings</title><link>https://beta-docs.defectdojo.com/federal_compliance/pain_ratings_setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/pain_ratings_setup/</guid><description>&lt;p&gt;&lt;a href="../pain_ratings"&gt;Potential Agency Impact (PAIN) Ratings&lt;/a&gt; explains what the rating is and how a
deadline is derived from it. This page is the procedure: the order to do things in, what to check at
each step, and what the deadline should read when you get there.&lt;/p&gt;</description></item><item><title>CMMC Level 2 Assessments</title><link>https://beta-docs.defectdojo.com/federal_compliance/cmmc_assessments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/cmmc_assessments/</guid><description>&lt;p&gt;The Compliance tab can score a CMMC Level 2 self-assessment against NIST 800-171 Rev 2, using the
DoD Assessment Methodology point weights.&lt;/p&gt;</description></item><item><title>CRA and DORA Evidence Packs</title><link>https://beta-docs.defectdojo.com/federal_compliance/eu_evidence_packs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/eu_evidence_packs/</guid><description>&lt;p&gt;DefectDojo Pro includes authored catalogs for vulnerability-related obligations in the Cyber
Resilience Act (CRA) and Digital Operational Resilience Act (DORA). A regulatory assessment
collects the operational facts DefectDojo already holds, gives an assessor space to document the
remaining evidence, and produces a dated evidence pack.
To set up an instance and your products for the CRA step by step, see
&lt;a href="../eu_cra_setup"&gt;Setting Up EU CRA&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Control Coverage</title><link>https://beta-docs.defectdojo.com/federal_compliance/control_coverage/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/control_coverage/</guid><description>&lt;p&gt;The control coverage view answers a simple question: which 800-53 controls do my scanners actually
test, and where are the open weaknesses per control?&lt;/p&gt;</description></item><item><title>Setting Up EU CRA</title><link>https://beta-docs.defectdojo.com/federal_compliance/eu_cra_setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/federal_compliance/eu_cra_setup/</guid><description>&lt;p&gt;This page takes a DefectDojo Pro instance from its first login to being ready for the EU Cyber
Resilience Act (CRA): the settings to turn on once, what to record on each product in scope, what
to load for each release, how to handle an Article 14 report, and how to produce evidence each
period. Each step says where to click, starting from the left menu, and what you should see when
it worked.&lt;/p&gt;</description></item></channel></rss>