Skip to main content

AST-09.1: Dynamic Host Configuration Protocol (DHCP) Server Logging

AST 3 — Low Identify

Mechanisms exist to enable Dynamic Host Configuration Protocol (DHCP) server logging to: (1) Improve asset inventories; (2) Assist in detecting unknown systems; and (3) Provide support during troubleshooting or forensic analysis activities.

Renumbered: Formerly AST-02.6 in SCF 2025.4.

Control Question: Does the organization enable Dynamic Host Configuration Protocol (DHCP) server logging to: (1) Improve asset inventories; (2) Assist in detecting unknown systems; and (3) Provide support during troubleshooting or forensic analysis activities?

General (4)
Framework Mapping Values
CIS CSC 8.1 1.4 1.5
CIS CSC 8.1 IG2 1.4
CIS CSC 8.1 IG3 1.4 1.5
NIST 800-207 NIST Tenet 7
US (1)

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Asset Management (AST) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with AST domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Asset management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel.

Level 2 — Planned & Tracked

Asset Management (AST) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with AST domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Asset management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The IT department establishes, maintains and updates an inventory that contains a listing of all organizational-owned TAASD, at a minimum covering common devices (e.g., laptops, workstations and servers).

Level 3 — Well Defined

Asset Management (AST) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with AST domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are well-documented and kept current by process owners. ▪ An IT Asset Management (ITAM) team, or similar function, is appropriately staffed and supported to implement and maintain AST domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of ITAM operations (e.g., ITAM platform, (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to enable Dynamic Host Configuration Protocol (DHCP) server logging to improve asset inventories and assist in detecting unknown systems.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. AST-09.1_A01 Dynamic Host Configuration Protocol (DHCP) server logging is implemented.
  2. AST-09.1_A02 DHCP server logging is utilized to detect unknown systems.
  3. AST-09.1_A03 Dynamic Host Configuration Protocol (DHCP) server logs are used to improve asset inventories.
  4. AST-09.1_A04 Dynamic Host Configuration Protocol (DHCP) server logs are retained and available to support troubleshooting or forensic analysis activities.

Evidence Requirements

E-MON-04 Rogue Devices

Documented evidence of rogue device identification is included as part of the centralized event log collection and review/analysis process.

Event Log Monitoring

Technology Recommendations

Micro/Small

  • Centralized log collector
  • Security Incident Event Manager (SIEM)

Small

  • Centralized log collector
  • Security Incident Event Manager (SIEM)

Medium

  • Security Incident Event Manager (SIEM)

Large

  • Security Incident Event Manager (SIEM)

Enterprise

  • Security Incident Event Manager (SIEM)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.