<?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: group-lock on Firepower in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045535#M1110125</link>
    <description>&lt;P&gt;I have exactly the same issue now.&lt;/P&gt;&lt;P&gt;The anyconnect users are able to watch all the aliasses available and the FMC/FTD is not able to limit like the ASA did woth the&amp;nbsp;&lt;SPAN&gt;group-lock value&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;is it necessary to do it on the ISE only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 20 Mar 2024 16:23:08 GMT</pubDate>
    <dc:creator>cmarin</dc:creator>
    <dc:date>2024-03-20T16:23:08Z</dc:date>
    <item>
      <title>group-lock on Firepower</title>
      <link>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/4185546#M1075948</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have multiple group policies for AnyConnect and on some of the I would like my users not to be able to choose a connection profile, much like the same way this is accomplished with the group-lock attribute in ESA.&lt;/P&gt;&lt;P&gt;Unfortunately, I cannot see something similar in FMC which manages my Firepower appliances.&lt;/P&gt;&lt;P&gt;Keep in mind that group policies are mapped to AD Groups (LDAP Mapping).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can this be accomplished somehow without the use of an external Radius Server (ISE etc) ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 21:16:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/4185546#M1075948</guid>
      <dc:creator>nickliako</dc:creator>
      <dc:date>2020-11-18T21:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: group-lock on Firepower</title>
      <link>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045535#M1110125</link>
      <description>&lt;P&gt;I have exactly the same issue now.&lt;/P&gt;&lt;P&gt;The anyconnect users are able to watch all the aliasses available and the FMC/FTD is not able to limit like the ASA did woth the&amp;nbsp;&lt;SPAN&gt;group-lock value&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;is it necessary to do it on the ISE only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 16:23:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045535#M1110125</guid>
      <dc:creator>cmarin</dc:creator>
      <dc:date>2024-03-20T16:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: group-lock on Firepower</title>
      <link>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045592#M1110128</link>
      <description>&lt;P&gt;It depends on how you do authentication and authorization. E.g. you can use AD/LDAP and assign group-policy directly to each user by mapping some LDAP attribute to group-policy name. For example, this article maps memberOf to group-policy, but you can use other attributes from LDAP schema too:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/network-management/remote-access/216313-configure-ra-vpn-using-ldap-authenticati.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/network-management/remote-access/216313-configure-ra-vpn-using-ldap-authenticati.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In this case you can have single tunnel-group (connection profile) and don't need group-lock feature.&lt;/P&gt;&lt;P&gt;Or you can map some other LDAP attribute to Tunnel-Group-Lock value (&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/740/management-center-device-config-74/vpn-remote-access.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/740/management-center-device-config-74/vpn-remote-access.html&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Or you can achieve the same with RADIUS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 17:18:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045592#M1110128</guid>
      <dc:creator>tvotna</dc:creator>
      <dc:date>2024-03-20T17:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: group-lock on Firepower</title>
      <link>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045596#M1110130</link>
      <description>&lt;P&gt;For LOCAL authentication this feature hasn't been implemented:&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;CSCvz10754&lt;/SPAN&gt; &lt;SPAN class=""&gt;ENH: RAVPN(FMC): Option to add attributes for Local use&lt;/SPAN&gt;r&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 17:21:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/group-lock-on-firepower/m-p/5045596#M1110130</guid>
      <dc:creator>tvotna</dc:creator>
      <dc:date>2024-03-20T17:21:15Z</dc:date>
    </item>
  </channel>
</rss>

