Forescout must generate log records when successful attempts to access privileges occur.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-230936FORE-NM-000080SV-230936r960885_ruleCCI-000172low
Description
Without generating log records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Log records can be generated from various components within the information system (e.g., module or policy filter).
STIGDate
Forescout Network Device Management Security Technical Implementation Guide2025-06-12

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
AU-12
1.00
  • DISA · V2R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.3.1
1.00
  • DISA · V2R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.3.2
1.00
  • DISA · V2R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000172
1.00
  • DISA · V2R3 · disa_xccdf · related

Details

Check Text (C-230936r960885_chk)

Verify the syslog trigger is configured. 1. Log on to Forescout Administrator UI with admin or operator credentials. 2. From the menu, select Tools >> Options >> Modules >> Syslog >> Syslog Triggers. 3. Under "User Operations", verify "Include user operations" is checked. If Forescout does not generate log records when successful attempts to access privileges occur, this is a finding.

Fix Text (F-33839r603648_fix)

Configure the syslog trigger. 1. Log on to Forescout Administrator UI with admin or operator credentials. 2. From the menu, select Tools >> Options >> Modules >> Syslog >> Syslog Triggers. 3. Under "User Operations", check "Include user operations".