STIGhubSTIGhub
STIGsSearchCompare

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
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Forescout Network Access Control Security Technical Implementation Guide

V-233324

CAT II (Medium)

Forescout must off-load log records onto a different system. This is required for compliance with C2C Step 1.

Rule ID

SV-233324r1113796_rule

STIG

Forescout Network Access Control Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-001851, CCI-000172

Discussion

Having a separate, secure location for log records is essential to the preservation of logs as required by policy. Satisfies: SRG-NET-000492-NAC-002110, SRG-NET-000334-NAC-001350

Check Content

If DOD is not at C2C Step 1 or higher, this is not a finding.

1. Go to Tools >> Options >> Syslog.
2. Verify a syslog server's IP address is configured.

Or

1. Go to Tools >> Options.
2. Navigate to the extended module (e.g., Splunk) that offloads log records to a separate device. 
3. Verify the connection is successful.

If each Forescout device does not offload log records to a separate device, this is a finding.

Fix Text

Configure Syslog server with TCP, as well as configure Syslog to alert if the communication between the Syslog server and the Forescout appliance loses connectivity.

1. Go to Tools >> Options >> Syslog.
2. Click "Add/Edit".
3. Configure the Syslog:
- Navigate to Syslog Server IP address >> Server Port >> Server Protocol set to TCP.
- Check the Use TLS setting.
- Configure the Identity, Facility, and Severity.
4. Click "Ok".
5. Click "Apply".

Or

Configure external module (e.g., Splunk) per instructions to send appliance logs from each Forescout appliance to the separate destination.