OpenControls Logo

STIG Viewer

STIGViewer Support

Forescout must prevent the installation of patches, service packs, plug-ins, or modules without verification the update has been digitally signed using a certificate that is recognized and approved by the organization.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-230949FORE-NM-000220SV-230949r1018755_ruleCCI-003992low
Description
Changes to any software components can have significant effects on the overall security of the network device. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the software has not been tampered with and has been provided by a trusted vendor. Accordingly, patches, service packs, or application components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The device should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved Certificate Authority (CA). Customer portal updates file download section on the vendor website has the MD5 hashes for the updates files. Currently, this is the method used by DOD to pull down files rather than using the internal connection to the Forescout server.
STIGDate
Forescout Network Device Management Security Technical Implementation Guide2025-06-12

Related Frameworks

2 mappings across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.2Signed Components
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (13) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-2(10)Shared and Group Account Credential Change
1.00
AU-4Audit Log Storage Capacity
1.00
CM-14Signed Components
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
CM-5(3)Signed Components
1.00
CM-7Least Functionality
1.00
CM-7(5)Authorized Software — Allow-by-exception
1.00
IA-2(5)Individual Authentication with Group Authentication
1.00
SC-2Separation of System and User Functionality
1.00
SC-23Session Authenticity
1.00

+3 more (top 10 by confidence shown)

CCI2 mappings
CCI-001749
1.00
CCI-003992
1.00

Details

Check Text (C-230949r1018755_chk)

Verify by inspecting the SSP or documentation to determine if there is a procedure for validating the MD5 hash against the Forescout updates.forescout.com portal to ensure that the software has come from the Forescout server. If the site does not have a documented process to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate recognized and approved by the organization, this is a finding.

Fix Text (F-33852r997756_fix)

When Forescout updates are downloaded, whether from the DOD update server or the updates.forescout.com portal, each update consists of an MD5 hash. Manually inspect, compare, and verify the MD5 hash against the Forescout website to ensure that the software has come from the Forescout server.