Vector
Vector

Choose your topics

Blogs
How to Prioritize Your Third-Party Risks

How can you prioritize effectively and enhance your organization’s security posture? Here are our top tips for setting up realistic, sustainable processes.

Third-Party Risk Management GRC
Blogs
Top Tips to Save Time When Assessing Third-Party Risks

Is assessing third-party risks taking up too much of your time? How can you make the process more effective and efficient? Find out in the latest post from SureCloud.

Third-Party Risk Management GRC
Blogs
The GRC Trends to Look Out for in 2024

Our GRC experts at SureCloud share their 2024 predictions for the world of governance, risk and compliance.

GRC
Blogs
The Top 5 Challenges of Third-Party Risk Management

With the supply chain now seen as a legitimate attack path, what can your organization do? Let’s explore 5 challenges of TPRM and how to overcome them.

Third-Party Risk Management GRC
Blogs
What is Third-Party Risk Management?

What is third-party risk management and how should you approach it? Find out in this post.

Third-Party Risk Management GRC
Blogs
The Top 4 Challenges of Risk Management

What are the top four challenges of risk management today and how can you overcome them? Find out in this post from SureCloud.

Third-Party Risk Management GRC
Blogs
Transform Compliance into Your Competitive Advantage

In GRC, compliance is often viewed as a cost that makes it harder to pursue growth. Here's how to make it your competitive advantage.

Compliance Management GRC
Blogs
Questions You Should Ask when Preparing For Your First Pen Test

Understand the processes that you and your chosen pentest provider will travel through for your first pen test, from the initial point to the day the test starts.

Penetration Testing
Blogs
TPRM Blog 6-Writing Clear Questions

Our GRC Practice Director explores the importance of clear communication and how to achieve it in your third party questionnaires. Read more here.

Third-Party Risk Management GRC
Vector (7)
Vector-1
Adversary Services

Network Segmentation Part 4 – Mitigating Threats from Wirelessly-Connected Devices

Network Segmentation Part 4 – Mitigating Threats from Wirelessly-Connected Devices
Written by

Ellie Owen

Published on

30 Oct 2019

Network Segmentation Part 4 – Mitigating Threats from Wirelessly-Connected Devices

 

Segmentation is the practice of dividing or separating something into different parts or sections. In the case of IT systems, this typically involves splitting a network into sub-networks, where each one is a separate network segment. Segmented networks can then be isolated from each other, increasing the security of the network. Network segmentation is an important consideration for any robust cybersecurity risk management posture – SureCloud’s IT Risk Management services and risk management software products can help you put together a programme that reflects your business needs. This series of blog posts will describe the different types of segmentation, the benefits of each, and applicable controls to maximize the security they provide.

 

Segmentation of Wireless Networks

So far in this series, we have reviewed controls to protect against attacks from outside the corporate network, or with direct access to corporate networks. This final article will review controls that aim to protect against threats from wirelessly-connected devices.

 

Wireless networks provide a convenient method to allow computers to connect to a network. Still, unfortunately, this very convenience makes it easier for unauthorized or inappropriate devices to connect unless suitable controls are implemented. The very nature of wireless technologies also means that an attacker might not need physical access to an office or another environment or potentially not even need to be near to connect to the network.

 

Types of Wireless Device

This article discusses controls for three common categories of wireless devices:

  • Corporate devices – devices provided, supported and controlled by the organization
  • Bring Your Own Device (BYOD) – employee-owned devices
  • Unknown devices – all other devices where the ownership and status may be unknown

 

How do security concerns differ for corporate devices?

Corporate devices refer to those which are provided by an organization and which are usually configured with appropriate security and management tools. Because of this, these are the most trusted devices. As such, they are often allowed to make the same connections via the wireless connection as when physically connected to the network. As a result, businesses should take steps to ensure that only approved and trusted corporate devices can connect via any high-access wireless network. The connection should identify the connecting device, ideally using a centrally managed and controlled mechanism such as a Domain-issued computer certificate to mitigate against unknown or unapproved devices connecting.

 

Optionally, the connection authentication could also confirm the device’s user, to ensure that they are an approved organization user and not an attacker using a stolen or otherwise compromised device.

 

Once connected to the wireless network, devices should be isolated from each other to prevent cross-device exposure or compromise, and all connections should use the strongest encryption available to prevent eavesdropping.

 

What are the risks of Bring Your Own Device (BYOD)?

Allowing uncontrolled and unmanaged devices to have full access to the corporate network without any restrictions or verifying the state of the device could lead to a malware infection being introduced onto the network, or it could provide an attacker with access to the network through a compromised device.

 

Bring Your Own Device (BYOD) provides a particular challenge: how to allow unknown and untrusted devices to connect to the corporate network without impacting the security of that network. These devices typically belong to an organization’s employees, who are subject to corporate policy and standards, and where there is a level of trust in place. This trust does not, however, signify that their devices are sufficiently secured to be permitted to join the network; it only suggests that the user’s intent is known and non-malicious.

 

All BYOD devices that connect to a corporate network should do so via a dedicated, segregated, and authenticated connection. The authentication should occur at the network layer during the initial connection, not after the connection. This will permit the use of encrypted connections and help to prevent eavesdropping. Protocols such as WPA2-Enterprise can be configured to require users to authenticate using RADIUS or equivalent – rather than via an unencrypted, open connection and web form authentication or a shared password/key. To further enhance the authentication, Multi-Factor Authentication can mitigate attacks from compromised user credentials.

 

BYOD Devices

Devices such as smartphones and tablets should be placed in a further restricted network which permits access to only the services which are appropriate to these devices. This might allow access to an Intranet and proxied Internet access, but not to systems which would not typically be used by these types of devices, such as file servers.

 

Employee-owned laptops, if permitted, should only be allowed to connect after the IT and/or IT Security department confirms that appropriate protections such as anti-virus are present and that devices are patched and updated to a suitable level. This could alternatively be managed as part of the connection itself with systems such as Network Access Control which can interrogate the devices; this could place the devices in a restricted network if the security level is not appropriate, allowing them to be remediated before allowing a full connection.

 

As with corporate wireless, devices connecting to the BYOD wireless network should be isolated from each other to prevent cross-device issues.

 

How should we handle unknown devices?

As discussed in the first Network Segmentation article, unknown or untrusted “guest” wireless devices should be isolated completely from the corporate network. This could provide guests with access to external systems such as the Internet, or the means by which to connect to their own VPN while protecting the corporate network from possible compromise from these devices. The difference between a “guest” or unknown device and a BYOD device is that the owner or user of that device is typically unknown to the organization; there would be no contractual or other obligations against them regarding their conduct on any organization network. The Cisco BYOD Design Guide states:

 

“Guest wireless traffic from the campus or a branch location is configured to be auto-anchored (tunneled via Ethernet-over-IP or CAPWAP) from the internal wireless controllers to the guest wireless controller. This may provide a somewhat higher level of security, in that guest wireless devices are not terminated on the “inside” of the corporate network. This is often desirable from a customer perspective because the security posture of guest devices cannot be determined.”

 

To achieve this, a dedicated Wireless LAN Controller or similar can be placed inside a dedicated, isolated DMZ segment. Traffic would be tunnelled from the wireless access points through internal Wireless LAN Controllers and onto the Guest controller before finally exiting the network. This efficiently segregates the traffic from the corporate network as it transitions to the exit point without requiring additional access points.

 

Guest access should also require users to authenticate, either during the connection itself or after connection via a web form. This could be using temporary credentials provided to the guest on request, which would provide a level of accountability to any actions conducted by connected devices and also discourage potential misuse by guests.

 

Once again, devices connecting to the Guest wireless network should be isolated from each other to prevent cross-device issues.

 

 

Corporate and Guest Wireless Segmentation Infographic

 

Improving Your Business Cyber Security

With this knowledge of threats from corporate, BYOD, and unknown wirelessly-connected devices in mind, businesses can begin to improve their cybersecurity processes. With guidance from SureCloud’s Cyber Risk Management experts, you can develop a segmentation plan that accounts for BYOD devices and guest device connections. This ability is particularly relevant in the face of remote working trends, where facilitating maximum productivity outside of formal workspaces is more important than ever. Take a look at our risk management software offerings for more information.

 

About SureCloud

SureCloud is a provider of cloud-based, Cybersecurity services and Integrated Risk Management products, which reinvent the way you manage risk.

SureCloud also offers a wide range of Cybersecurity testing and assurance services, where we stay with you throughout the entire test life-cycle, from scoping through to vulnerability discovery and remediation. Certified by the National Cyber Security Centre (NCSC) & CREST and delivered using the innovative Pentest-as-a-Service (underpinned by a highly configurable technology platform), SureCloud acts as an extension of your in-house security team and ensures you have everything you need to improve your risk posture.