acceptedWLAN IDS Sensor/Server Security Technical Implementation Guide (STIG)This STIG contains the technical security controls for the operation of a WLAN IDS Sensor and Server in the DoD environment.DISA, Field Security OperationsSTIG.DOD.MILRelease: 6 Benchmark Date: 12 Mar 20136I - Mission Critial Classified<ProfileDescription></ProfileDescription>I - Mission Critial Public<ProfileDescription></ProfileDescription>I - Mission Critial Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>Wireless IDS scanning <GroupDescription></GroupDescription>WIR0145-01The site must scan the radio frequency spectrum for unauthorized WLAN devices.<VulnDiscussion>Unauthorized WLAN devices threaten DoD networks in a variety of ways. If someone installs an access point on a DoD network, then people may use that access point to access network resources without any perimeter security controls, which significantly degrades the IA posture of that network. If someone installs an unauthorized access point in the site’s vicinity, even if not connected to a DoD network, then site users may unknowingly or inadvertently connect to it. Once this connection occurs, the user’s traffic may be diverted to spoofed web sites and other servers to capture the user’s authentication credentials and sensitive DoD data. Finally, if an unauthorized WLAN client is operating inside or near the site, it may improperly connect to the site’s WLAN infrastructure or other network devices that improperly have left open active Wi-Fi interfaces. WIDS can help counter all of these threats. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>VMS Target Wireless IDSDISA FSOVMS TargetWireless IDS1282Install and operate WIDS on a continuous or periodic basis in a manner consistent with policy requirements.Detailed policy requirements:
DoDD 8100.2 requires ALL DoD networks use a wireless IDS to scan for unauthorized wireless devices.
The WIDS sensor and server must meet the following requirements:
-For a continuous Wireless IDS (WIDS) scanning system:
--System is server-based, whereby sensor scanning results are consolidated and evaluated by a WIDS server.
--The WIDS will scan continuously 24 hours/day, 7 days/week to detect authorized and unauthorized activity.
--The WIDS will include a location sensing protection scheme for authorized and unauthorized wireless devices that will provide information enabling designated site personnel to take appropriate actions.
NOTE: While not recommended, WLAN access points that also provide WIDS scanning capability are acceptable as "continuous scanning" WIDS sensors.
- For a periodic WIDS scanning system:
--The DAA will determine how often WIDS scanning will be conducted based on the results of the wireless risk assessment. (DISA recommends at least every 90 days.)
--Periodic scanning will be conducted by using handheld or laptop WIDS scanners during a walk-through assessment of the network environment.
NOTE: The WIDS must cover all WLAN frequencies transmitted by the WLAN equipment. The WLAN frequency band can vary by country and the WIDS must cover all channels being used in a country the equipment is being used in. For example, the allowed WLAN channels are different in the U.S., Japan, and many European countries.
Check procedures:
Interview the site IAO. Determine if the scanning by a Wireless Intrusion Detection System (WIDS) is continuous or periodic. See Check V0018596 (NET-WIDS-001 / WIR0050). Verify the site’s WIDS scanning system meets the following requirements:
-For Continuous WIDS scanning:
--Verify the site has installed a continuous-scanning WIDS system (e.g., AirDefense, Airmagnet, etc.).
--Verify the WIDS is set up to scan continuously 24 hours/day, 7 days/week to detect authorized and unauthorized activity.
--Verify the WIDS includes a location sensing protection scheme for authorized and unauthorized wireless devices.
--Mark as a finding if any of these requirements have not been met.
-For Periodic WIDS scanning:
--Verify the DAA has determined the frequency of the scans. Review the DAA approved wireless risk assessment.
--Mark as a finding if any of these requirements have not been met.WIDS scan results archival<GroupDescription></GroupDescription>WIR0145-02WIDS sensor scan results must be saved for at least one year.<VulnDiscussion>DoDD 8100.2 requires ALL DoD networks use a wireless IDS to scan for unauthorized wireless
devices. If sites do not maintain scan logs, it cannot be determined if IDS findings are isolated and harmless events or a more sustained, methodical attack on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>VMS Target Wireless IDSDISA FSOVMS TargetWireless IDS1282IAO must ensure WIDS and operating procedures maintain WLAN scan results for at least one year.Detailed policy requirements:
The results of WIDS scans (logs and scan results) shall be maintained by the site for at least one year.
Check procedures:
Interview the site IAO. Verify the site has saved its scan results for at least one year, viewing one of the older logs to validate the practice. Mark as a finding if the site is not saving the logs/results or is saving them for less than one year.