It’s important to note that network access control requires extensive training, the right certifications, and experience working with the software. If you aren’t confident about this part, there’s always the possibility of hiring someone who is, and will be able  help you digitizing your HR operations too . It’s also likely that you’re working with companies that are new to Windows, or have failed to properly configure basic security settings, and there are  services from sites such as https://www.fortinet.com/solutions/enterprise-midsize-business/network-access/application-access.
The first three areas to address are as follows:
I. Ensure your network administrators are security-aware of the risks involved with operating the network with Windows 8.
Let’s start with why your network would need network access, what steps you need to take to ensure that it’s properly configured and secured, and how you can build a list of steps that you can use when configuring it,.
Here’s the basics for network administrators on Windows 8:
(1) Ensure that they understand the risks involved with operating the network with Windows 8
This is because of the changes made to the way Windows 8 is designed and implemented. There are two major architectural changes (which I’ll cover in future posts) that result in the new network experience:
The new, simpler, WAN architecture: This one’s pretty easy: before Windows 8, you connected to a Windows PC with a wired Ethernet connection. Then, you connected to your company’s network, at a company-supplied network hub.
What changed in Windows 8 is the simplified WAN architecture. Now, if you have a wired Ethernet network, you connect to your Windows PC using an internet connection (using your PC’s wireless network). If you connect to your company’s network using your wireless network (or the Internet if your company has set up access to it on its network) then you connect to your company’s network via the WAN, the new, simplified network architecture. This means there are only two physical connections to a network. One connects you to your company’s network using the WAN, and the other connects to the company’s network via a wireless connection. This means there are only three network protocols that you need to work with, rather than the four or five that you used to deal with when working with old school Windows. This significantly reduces the number of steps you need to take to get to a Windows 8 network.
The new, redesigned Windows Firewall, RADIUS, Windows NGFW and WinRM interfaces: This is more complex. That’s because the network has changed so much, so the Windows Firewall, the “web router” inside the Windows 8 machine, must be re-designed to understand the new, simplified network architecture.
There are a number of security controls built into Windows 8 to address these security issues. If you’re familiar with the “old way” of working with Windows Firewall, it should feel familiar.
A full list of security changes can be found at http://msdn.microsoft.com/en-us/library/windows/hardware/jj777704(v=vs.85).aspx. Microsoft has provided a lot of details in this post so I’m going to go over each of them in detail: Windows Firewall “Windows Firewall for Internet Explorer” has moved from “full site filter support” to a “proximity site filter support” model. This means that in addition to full site-by-site filtering and “third-party support” for websites that require this capability, you can use RADIUS or NAT scanning to automatically add the “proximity site filter” capability.