This article summarizes the information that was presented in the February 2012 Information Technology Laboratory (ITL) bulletin, Guidelines for Securing Wireless Local Area Networks (WLANs). The bulletin, which was noted by WERB in February 2012, was based on NIST Special Publication (SP) 800-153, Guidelines for Securing Wireless Local Area Networks (WLANs): Recommendations of the National Institute of Standards and Technology. The article summarizes the bulletin for a professional technical publication, and focuses on how organizations can implement sound security practices throughout the life cycles of their WLANs. Information is provided about access to SP 500-153, and to other NIST resources that are available to help organizations improve the security of wireless local area networks, the system development life cycle and the management of risks to systems.
This article summarizes the information that was presented in the February 2012 Information Technology Laboratory (ITL) bulletin, Guidelines for Securing Wireless Local Area Networks (WLANs). The bulletin, which was noted by WERB in February 2012, was based on NIST Special Publication (SP) 800-153,...
See full abstract
This article summarizes the information that was presented in the February 2012 Information Technology Laboratory (ITL) bulletin, Guidelines for Securing Wireless Local Area Networks (WLANs). The bulletin, which was noted by WERB in February 2012, was based on NIST Special Publication (SP) 800-153, Guidelines for Securing Wireless Local Area Networks (WLANs): Recommendations of the National Institute of Standards and Technology. The article summarizes the bulletin for a professional technical publication, and focuses on how organizations can implement sound security practices throughout the life cycles of their WLANs. Information is provided about access to SP 500-153, and to other NIST resources that are available to help organizations improve the security of wireless local area networks, the system development life cycle and the management of risks to systems.
Hide full abstract
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
