STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to F5 BIG-IP Device Management Security Technical Implementation Guide

V-217416

CAT II (Medium)

The BIG-IP appliance must be configured to audit the enforcement actions used to restrict access associated with changes to the device.

Rule ID

SV-217416r984111_rule

STIG

F5 BIG-IP Device Management Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-001814

Discussion

Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.

Check Content

Verify the BIG-IP appliance is configured to audit the enforcement actions used to restrict access associated with changes to the device.

Navigate to the BIG-IP System manager >> Logs >> Configuration >> Options.

Review configuration in the "Audit Logging" section.

Verify that "MCP" is set to Debug.

If the BIG-IP appliance is not configured to audit the enforcement actions used to restrict access associated with changes to the device, this is a finding.

Fix Text

Configure the BIG-IP appliance to audit the enforcement actions used to restrict access associated with changes to the device.