{"id":4006,"date":"2017-02-06T00:17:42","date_gmt":"2017-02-06T00:17:42","guid":{"rendered":"http:\/\/www.abrahamsconsulting.com\/blog\/?p=4006"},"modified":"2017-02-06T00:32:00","modified_gmt":"2017-02-06T00:32:00","slug":"network-access-control-objections","status":"publish","type":"post","link":"https:\/\/www.abrahamsconsulting.com\/blog\/network-access-control-objections\/","title":{"rendered":"3 Network Access Control objections: a.k.a ‘alternative facts.’"},"content":{"rendered":"

I have heard my share of Network Access Control objections (NAC), but these three (3) have a following; a movement of sorts:\"Network<\/a><\/p>\n

    \n
  1. “We have a firewall-so we don’t need to worry about NAC.”<\/li>\n
  2. “Our wireless controller already has a built-in system like this.”<\/li>\n
  3. “We already use Mobile Device Management\u00a0 (MDM) to ensure security of our devices.”<\/li>\n<\/ol>\n

    There is nothing better than a movement for a worthy cause. Consider the Women’s march in DC<\/a>\u00a0on January 21, 1017?<\/p>\n

    I stand with those women.<\/p>\n

    However, the focus of this post, is Network Access Control objections. [Further reading: Critical Security Controls:What’s NAC got to do with it].<\/strong><\/a><\/em><\/p>\n

    The truth, \u00a0neither knows, nor has it e-v-e-r known\u00a0an\u00a0alternative, except, for its opposite—<\/p>\n

    A Lie.<\/em><\/p>\n

    There are, however,\u00a0 alternatives to Network Access Control, a.k.a \u00a0consequences to negligence and or poor decisions<\/strong>.<\/em><\/a><\/p>\n

    Here are some considerations for the Network Access Control objections stated above:<\/p>\n

    Firstly, even Next Generation firewalls cannot perform access control on guests or BYODs. They can only do so on managed\/Active Directory devices. Furthermore, firewalls are built to focus on the traffic coming in from the outside. The inside threat, an organization’s own users, pose the greatest risk to their network.<\/p>\n

    Imagine that? \u00a0Your allies are also your enemies. A conundrum, if ever there was one.<\/em><\/p>\n

    Secondly, NAC handles your wired and VPN networks as well. It also focuses on the enhancement of\u00a0 the devices on your network, in ways that wireless controllers do not. For example, can wireless controllers check for anti-virus software or can they check on OS patch level policies?<\/p>\n

    And thirdly, Mobile Device Management\u00a0 (MDM) software will not ensure the security of your devices.<\/p>\n

    Here are three (3) reasons why:<\/p>\n

      \n
    1. \u00a0MDMs cannot take action on a device that is deemed a security threat?<\/li>\n
    2. \u00a0MDMs will not address the Windows and OSx machines on your network?<\/li>\n
    3. Have you considered the outcome if someone removes the MDM client from your phones, which would cause a blind spot? What policy do you have in place to address this occurrence?<\/li>\n<\/ol>\n

      Are\u00a0 you now willing to vet Network Access Control solutions? If so, please contact us. <\/a><\/p>\n

      If not, consider the current Security Climate<\/strong><\/a>. Are you able to identify the Internet of Things (IoT) devices<\/strong><\/a> that connect to your network?<\/p>\n

      Beyond these recommendations to implement a sound Network Access Control solution, ‘alternative facts,’ may<\/em> be the ‘right’ alternative for you.<\/p>\n

      Sources:\u00a0<\/em><\/p>\n