Aruba Networks Remote Access Points

Aruba's Virtual Branch Network (VBN) solution dramatically simplifies the complexity and cost of deploying a remote solution at branches with one to many users. Complex configuration, management, software updates authentication, intrusion detection, and remote site connectivity tasks are handled by powerful data center-based Aruba controllers running new Aruba software. Centralizing these services in the controllers enables the branch office equipment to be greatly simplified and cost reduced. The virtualized functions are transport-independent, so any wide-area network - including 3G cellular and DSL - can be used to connect the branches offices.

Enquire about this product

User access to network services, applications, and resources is governed by IT-defined policies that are disseminated network-wide. This results in a more uniform and secure user experience, regardless of where the network is accessed.

Typical uses include:

• Branch offices;
• Business continuity applications;
• Business partner network access;
• First responder and disaster recovery operations;
• Instantly deployed, mesh wireless branch offices;
• Kiosks and store-in-a-store retailers;
• Remote campuses or clinics;
• Telecommuters;
• Telemedicine;
• Temporary workers;
• Virtual call centers.

VBN offers equal or higher security than traditional remote networking solutions at a far lower price point and without infrastructure complexity.

Compliance Standards

Requirement 1: Install and maintain a firewall configuration to protect cardholder data 

Requirement 2 Do not use vendor-supplied defaults for system passwords and other security parameters

(See 2.1.1)  For wireless environments connected to the cardholder data environment or transmitting cardholder data, change wireless vendor defaults, including but not limited to default wireless encryption keys, passwords, and SNMP community strings. Ensure wireless device security settings are enabled for strong encryption technology for authentication and transmission.

Requirement 4 Encrypt transmission of cardholder data across open, public networks 

4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data environment, use industry best practices (e.g., IEEE 802.11i) to implement strong encryption for authentication and transmission.

• For new wireless implementations, it is prohibited to implement WEP after March 31, 2009.
• For current wireless implementations, it is prohibited to use WEP after June 30, 2010.

Requirement 9 Restrict physical access to cardholder data

9.1.3 Restrict physical access to wireless access points, gateways, and handheld devices.

Requirement 11 Regularly test security systems and processes

11.1 Test for the presence of wireless access points by using a wireless analyzer at least quarterly or deploying a wireless IDS/IPS to identify all wireless devices in use

GCSX No 9 Intrusion Detection 

GCSX No 11 Wireless Networks