<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VPN Machine Authentication in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3726967#M554509</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/303946"&gt;@fatalXerror&lt;/a&gt;: VPN does not use 802.1x. The machine credentials I was referring to was the credentials the machine uses for 802.1x prior to user login (created when machine joins the domain). You can definitely&amp;nbsp;do client certificate authentication using machine certs with the ASA and AnyConnect VPN client.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Oct 2018 12:11:38 GMT</pubDate>
    <dc:creator>Rahul Govindan</dc:creator>
    <dc:date>2018-10-17T12:11:38Z</dc:date>
    <item>
      <title>VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3200088#M554505</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;Current setup:&lt;/P&gt;
&lt;P&gt;Anyconnect clients establish VPN tunnels to an ASA and are authenticated using an OTP server and AD (primary and secondary configuration under the connection profile). For AD, the ASA sends the authentication request to ISE which is integrated with AD. Clients are associated to different group-policies depending on which AD group they belong to.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to add machine authentication to this, is is possible to additionally check that the client machine is also present and active in AD?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:36:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3200088#M554505</guid>
      <dc:creator>Terry</dc:creator>
      <dc:date>2020-02-21T18:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3201651#M554506</link>
      <description>You cannot pass machine credentials through VPN as it does not do 802.1x for VPN access. But instead, you can run posture (ASA or ISE Posture) to check for a registry key on the user machine.&lt;BR /&gt;An example using ASA posture (and DAP for enforcement) is given here:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/115947-dap-adv-functions-00.html#anc21" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/115947-dap-adv-functions-00.html#anc21&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The registry key you can use to check this is "\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain"&lt;BR /&gt;&lt;BR /&gt;You can set up the same check using ISE posture. Example here:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/adaptive-security-appliance-asa-software/117693-configure-ASA-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/adaptive-security-appliance-asa-software/117693-configure-ASA-00.html&lt;/A&gt;</description>
      <pubDate>Thu, 19 Oct 2017 13:48:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3201651#M554506</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2017-10-19T13:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3202203#M554507</link>
      <description>&lt;P&gt;Thanks for your reply Rahul.&lt;/P&gt;
&lt;P&gt;We had already tested the ASA posture / registry key option which worked fine.&lt;/P&gt;
&lt;P&gt;My customer asked the question, so I just wanted to make sure I wasn't missing an option that could be used.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Terry&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2017 08:29:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3202203#M554507</guid>
      <dc:creator>Terry</dc:creator>
      <dc:date>2017-10-20T08:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3726770#M554508</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/193294"&gt;@Rahul Govindan&lt;/a&gt;, i tried to search over the internet about VPN 802.1x for machine certificate authentication then I saw this post. Can you provide me a link that tells that 802.1x VPN with machine certificate authentication is unsupported? thanks&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2018 05:15:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3726770#M554508</guid>
      <dc:creator>fatalXerror</dc:creator>
      <dc:date>2018-10-17T05:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3726967#M554509</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/303946"&gt;@fatalXerror&lt;/a&gt;: VPN does not use 802.1x. The machine credentials I was referring to was the credentials the machine uses for 802.1x prior to user login (created when machine joins the domain). You can definitely&amp;nbsp;do client certificate authentication using machine certs with the ASA and AnyConnect VPN client.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2018 12:11:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/3726967#M554509</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2018-10-17T12:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/4758259#M579323</link>
      <description>&lt;P&gt;is there any similar solution for MAC computer?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 02:39:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/4758259#M579323</guid>
      <dc:creator>karenmar</dc:creator>
      <dc:date>2023-01-20T02:39:45Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Machine Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/4758807#M579333</link>
      <description>&lt;P&gt;What do you mean?&amp;nbsp; This thread addresses that 802.1X is not used on Remote Access VPN.&amp;nbsp; What are you trying to accomplish?&amp;nbsp; MacOS has no concept of a "Machine Account"&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 15:48:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/vpn-machine-authentication/m-p/4758807#M579333</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-01-20T15:48:22Z</dc:date>
    </item>
  </channel>
</rss>

