Última modificación: 19 de marzo de 2025

Policy No. 4204 Wireless Device Communication Procedure

Download Wireless Device Communication Procedure Document

Visión general

With the mass explosion of smartphones and tablets, pervasive wireless connectivity is almost a given at any organization. Unsecured wireless configurations can provide an easy open door for malicious threat actors.

Propósito

The purpose of this procedure is to secure and protect assets owned by PCSD. PCSD provides computer devices, networks, and other electronic information systems to meet missions, goals, and initiatives. PCSD grants access to these resources as a privilege and must manage them responsibly to maintain the confidentiality, integrity, and availability of all assets.

This procedure specifies the conditions that wireless infrastructure devices must satisfy to connect to the PCSD network. Only those wireless devices that meet the standards specified in this procedure or are granted an exception by the InfoSec team are approved for connectivity to a PCSD network.

Alcance

All employees, contractors, consultants, temporary and other workers at PCSD, including all personnel affiliated with third parties that maintain a wireless device on behalf of PCSD, must adhere to this procedure. This procedure applies to all wireless devices that connect to a PCSD network or reside at a PCSD location.

The following list includes, but is not limited to, endpoint devices such as laptops, desktops, cellular phones, and tablets. This includes any form of wireless communication device capable of transmitting packet data.

Procedimiento

General Requirements

All wireless devices that reside at a PCSD location and connect to a PCSD network, or provide access to information classified as Confidential or above, must abide by the standards specified in the Wireless Infrastructure Communication Procedure.
- Use PCSD-approved authentication protocols and infrastructure.
- Use PCSD-approved encryption protocols.
- Maintain a hardware address (MAC address) that can be registered and tracked.

Último estado de actualización:

Actualizado en enero de 2015