# Checklist: weekly asset discovery and 14-day vulnerability enumeration under CISA BOD 23-01

Twelve steps for federal civilian agencies: what the directive’s scope takes in, the 7-day, 14-day, 24-hour and 72-hour requirements, CISA’s on-demand requests, performance data, and how BOD 26-04 now starts remediation clocks from BOD 23-01 results.

Checklist · Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## What the directive requires and where it stands

Binding Operational Directive 23-01, Improving Asset Visibility and Vulnerability Detection on Federal Networks, is dated October 3, 2022 on CISA’s website. It binds Federal Civilian Executive Branch agencies and does not apply to national security systems or to certain Department of Defense and Intelligence Community systems. Its required actions applied by April 3, 2023 [1]. CISA’s implementation guidance answers agencies’ common questions about scope and method, and CISA says it expects agencies at a minimum to meet or exceed it [2].

As checked on November 14, 2026, the directive is not marked as revoked on CISA’s website [1]. BOD 26-04, Prioritizing Security Updates Based on Risk, dated June 10, 2026, revoked BOD 19-02 and BOD 22-01 [4] and relies on BOD 23-01: its remediation timelines can start when an agency enumerates a vulnerability under BOD 23-01 and updates the CDM dashboard [3]. That makes the speed and coverage of discovery and enumeration matter for remediation deadlines as well. Our [BOD 26-04 explainer](https://insights.moraph.com/cisa-bod-26-04-risk-based-remediation-explained) covers that directive.

## Using the steps

Each step names the required action or guidance it rests on; where a step is our suggestion, it says so. The owner under each step is a typical role; the directive assigns actions to agencies. Agencies that operate systems through contractors remain responsible for them, since the scope includes systems operated by another entity on an agency’s behalf [1]. This page explains the directive; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Write down the scope: every non-ephemeral IP-addressable asset on agency systems, in every environment, and the few exclusions.** (CISO with the CDM program manager) The directive covers all IP-addressable networked assets reachable over IPv4 and IPv6, whether information technology or operational technology, including servers, workstations, virtual machines, network devices and printers in on-premises, roaming and cloud deployments. It excludes ephemeral assets such as containers and third-party-managed SaaS, and it reaches systems operated by another entity on an agency’s behalf [1]. CISA’s guidance puts IaaS, data center collocation and some PaaS assets in scope, treats physically segmented guest networks as out of scope, brings BYOD devices in where allowed on enterprise networks, and counts only truly physically air-gapped systems as out [2].
2. **Run automated asset discovery at least every 7 days, covering at a minimum the entire IPv4 space the agency uses.** (Network security operations) The directive requires automated asset discovery every 7 days, covering at a minimum the entire IPv4 space used by the agency [1]. The guidance distinguishes asset discovery, which checks the network for active and inactive hosts and finds unmanaged devices, from asset management; inventories from endpoint and mobile device management tools may feed into a comprehensive discovery effort [2].
3. **Start vulnerability enumeration across all discovered assets every 14 days, including laptops and other roaming and nomadic devices.** (Vulnerability management lead) The directive requires enumeration to be initiated every 14 days and accepts that a full enterprise scan may not finish in that time [1]. The guidance explains that agencies must start a new scan every 14 days even if the previous one has not completed, and must feed available results from the previous scan three days after the new scan starts [2].
4. **Use privileged credentials or agents for enumeration on managed endpoints and network devices wherever the technology allows, with least privilege on the scanning accounts.** (Vulnerability management lead with identity and access management) The directive requires enumeration on managed endpoints and network devices to be conducted with privileged credentials to the maximum extent possible; credentialed network scans and client- or agent-based detection both count [1]. The guidance says administrators must apply least privilege and separation of duties to the accounts used for enumeration, which attackers target [2].
5. **Keep vulnerability detection signatures no more than 24 hours behind the vendor’s latest release.** (Vulnerability management lead) The directive requires all detection signatures to be updated at an interval no greater than 24 hours from the last vendor-released update [1]. Logging each update’s timestamp, so the interval can be shown, is our suggestion and also feeds the performance data in step 10 [2].
6. **Extend enumeration to iOS, Android and other devices outside agency networks where the capability exists.** (Endpoint and mobility team) The directive requires the same type of vulnerability enumeration on mobile devices and other devices outside agency on-premises networks where the capability is available [1].
7. **Get CISA approval for any alternative discovery or enumeration method, and keep the approvals with the system records.** (CISO) The directive requires all alternative asset discovery and vulnerability enumeration methods, such as for specialized equipment or systems that cannot use privileged credentials, to be approved by CISA [1]. Filing the approvals with each system’s authorization records is our suggestion.
8. **Automate ingestion of enumeration results into the CDM Agency Dashboard within 72 hours of discovery completion.** (CDM program manager) The directive sets 72 hours from discovery completion, or from the start of a new cycle if the previous full discovery has not completed [1]. BOD 26-04 requires assets reported in the CDM Federal Dashboard to include all associated IP addresses, including RFC 1918 and RFC 4193 private addresses [3].
9. **Be able to start on-demand discovery and enumeration within 72 hours of a CISA request and return results within 7 days.** (Security operations center manager) The directive sets both clocks and says the enumeration must still be initiated within the period even when a full enterprise scan cannot finish, because partial results give situational awareness [1]. Rehearsing a request once a year is our suggestion.
10. **Report vulnerability enumeration performance data to the CDM Dashboard in CISA’s common data schema.** (CDM program manager) Within 6 months of CISA publishing requirements for this data, agencies must start collecting and reporting it; the directive page links the BOD 23-01 Common Data Schema [1]. The guidance describes the data as scanning logs, such as records of successful credentialed enumeration, timestamps of enumeration activity and signature update timestamps [2].
11. **Feed BOD 26-04 from the same results: tag externally reachable assets and treat each enumerated vulnerability as a possible start of a remediation clock.** (Vulnerability management lead with system owners) BOD 26-04 starts its remediation timelines when CISA adds a vulnerability to the KEV Catalog or when, under BOD 23-01, the agency enumerates or identifies it on an asset and updates the CDM dashboard, whichever is first [3]. Its Phase III, within 180 days of issuance, requires agencies to identify and tag continuously all agency-owned assets reachable from outside the agency network with a routable IP address, with organization, environment, exposure and asset type [3].
12. **Keep evidence of cadence, coverage and signature currency, and be ready for CISA’s oversight.** (CISO) The directive’s goals include tracking how often the agency enumerates its assets, what coverage it achieves and how current its signatures are. CISA reports annually to the Secretary of Homeland Security, the Director of OMB and the National Cyber Director, reports quarterly progress to OMB and monitors compliance [1]. Keeping a monthly coverage figure for each system is our suggestion.

## Sources

1. Cybersecurity and Infrastructure Security Agency. BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks (October 3, 2022). <https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks> Checked November 14, 2026.
2. Cybersecurity and Infrastructure Security Agency. BOD 23-01: Implementation Guidance for Improving Asset Visibility and Vulnerability Detection on Federal Networks. <https://www.cisa.gov/news-events/directives/bod-23-01-implementation-guidance-improving-asset-visibility-and-vulnerability-detection-federal> Checked November 14, 2026.
3. Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk (June 10, 2026). <https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk> Checked November 14, 2026.
4. Cybersecurity and Infrastructure Security Agency. Cybersecurity Directives. <https://www.cisa.gov/news-events/directives> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-cisa-bod-23-01-asset-discovery-and-vulnerability-enumeration>
Publisher: Moraph Insights
