Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-172 Enhanced CUI Protection Center

03.13.12E — Denial-of-Service Protection

Read the official CUI requirement and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect it to implementation, evidence, and sustained operation.

3Parameters
1Source controls
2Assessment objectives
3Assessment methods

03.13 — System and Communications Protection · NIST SP 800-172 Revision 3

Active
Official NIST requirement content

Security requirement

  1. a.[Organization-defined: types of denial-of-service events] the effects of the following types of denial-of-service events: [Organization-defined: SELECTED PARAMETER VALUE].
  2. b.Employ the following safeguards to prevent the denial-of-service events [Organization-defined: safeguards].
Official NIST discussion

Discussion

Denial-of-service events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of denial-of-service events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of denial-of-service attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to denial-of-service events. This requirement is sourced to a control tailored out of the SP 800-53B .13 moderate baseline in SP 800-171.

Official organization-defined parameters

Tailoring decisions required

Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.

types of denial-of-service eventsorganization-defined types of denial-of-service eventsthe types of denial-of-service events to be protected against or limited are defined.
SELECTED PARAMETER VALUE
safeguardsorganization-defined safeguards by type of denial-of-service eventthe safeguards to prevent the denial-of-service objective by type of denial-of-service event are defined.
Official protection strategy classifications

Protection strategies supported

These classifications are carried from the official SP 800-172 OSCAL record and help explain the enhanced requirement’s defensive purpose.

PS-CRSCyber Resiliency
PS-PRAPenetration-Resistant Architecture
Bare Metal Cyber interpretation

Implementation perspective

Treat Denial-of-Service Protection as an enhanced CUI protection outcome for elevated threat conditions that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to secure architecture, boundary protection, communications security, cryptography, and isolation of CUI processing.

  1. Confirm the federal agency selected this enhanced requirement for the critical program or high-value asset and identify the CUI system components, services, users, and external connections in scope.
  2. Resolve every organization-defined parameter through an approved governance and tailoring process.
  3. Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
  4. Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
  5. Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

  • Which critical-program or high-value-asset CUI, data flows, users, and services are protected by this enhanced requirement?
  • Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
  • Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
  • What change, incident, or threshold should trigger reassessment?

Evidence and validation

  • network and trust-boundary diagrams
  • firewall and gateway configurations
  • cryptographic configuration and key records
  • segmentation and isolation test results

Common failure patterns

  • diagrams omitting cloud and third-party paths
  • encryption enabled without key governance
  • flat trust zones permitting unnecessary lateral movement
  • boundary rules accumulating without owner review
Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (2)
  1. a.

    the effects of [Organization-defined: types of denial-of-service events] are [Organization-defined: SELECTED PARAMETER VALUE].

  2. b.

    [Organization-defined: safeguards] are employed to protect against or limit the effects of denial-of-service events.

Examine

  • System and communications protection policy
  • procedures addressing denial-of-service protection
  • list of denial-of-service attacks requiring employment of security safeguards to protect against or limit effects of such attacks
  • system design documentation
  • list of security safeguards protecting against or limiting the effects of denial-of-service attacks
  • system configuration settings and associated documentation
  • system audit records
  • system security plan
  • other relevant documents or records

Interview

  • System/network administrators
  • personnel with information security responsibilities
  • personnel with incident response responsibilities
  • system developers

Test

  • Mechanisms protecting against or limiting the effects of denial-of-service attacks
Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-172 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source record

Authoritative sources