<?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: SGT - Extend to VMware in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664526#M576569</link>
    <description>&lt;P&gt;You've run across a limitation that exists with TrustSec. As you pointed out, this used to be possible with the 1000v, but that isn't viable anymore. TrustSec shines in the facility/LAN/edge, but it's really not a DC technology.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Adam already brought up Secure Workload and it's probably the most viable solution at the moment. The solution would leverage Cisco Secure Workload (Tetration) agents on the application servers, integrate ISE and Secure Workload, then write application scopes with facility/endpoint SGTs. This moves the enforcement point to the application servers native firewall. This does have its own scale considerations because firewall policy is written on IP and not SGT, Secure Workload is doing that translation based on the ISE sessions context it receives.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Aug 2022 17:48:01 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2022-08-05T17:48:01Z</dc:date>
    <item>
      <title>SGT - Extend to VMware</title>
      <link>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664490#M576567</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;What options are there for enforcing SGT policy as close to the Virtual machine/application as possible in a VMware environment? I know previously we could have used the Nexus 1000V but with that no longer being solved, is there a solution for this?&lt;/P&gt;
&lt;P&gt;Many thanks&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 15:57:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664490#M576567</guid>
      <dc:creator>Aileron88</dc:creator>
      <dc:date>2022-08-05T15:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: SGT - Extend to VMware</title>
      <link>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664521#M576568</link>
      <description>&lt;P&gt;Cisco Secure Workload:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/products/security/tetration/index.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/security/tetration/index.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Or integration ISE with ACI and ACI into VM-Ware.&amp;nbsp; Not sure if there is a newer integration doc than this:&amp;nbsp;&lt;A href="https://content.cisco.com/chapter.sjs?uri=/searchable/chapter/content/en/us/td/docs/ios-xml/ios/sec_usr_cts/configuration/xe-16-7/sec-usr-cts-xe-16-7-book/cts-aci-intgn.html.xml" target="_blank"&gt;https://content.cisco.com/chapter.sjs?uri=/searchable/chapter/content/en/us/td/docs/ios-xml/ios/sec_usr_cts/configuration/xe-16-7/sec-usr-cts-xe-16-7-book/cts-aci-intgn.html.xml&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 17:24:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664521#M576568</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-08-05T17:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: SGT - Extend to VMware</title>
      <link>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664526#M576569</link>
      <description>&lt;P&gt;You've run across a limitation that exists with TrustSec. As you pointed out, this used to be possible with the 1000v, but that isn't viable anymore. TrustSec shines in the facility/LAN/edge, but it's really not a DC technology.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Adam already brought up Secure Workload and it's probably the most viable solution at the moment. The solution would leverage Cisco Secure Workload (Tetration) agents on the application servers, integrate ISE and Secure Workload, then write application scopes with facility/endpoint SGTs. This moves the enforcement point to the application servers native firewall. This does have its own scale considerations because firewall policy is written on IP and not SGT, Secure Workload is doing that translation based on the ISE sessions context it receives.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 17:48:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4664526#M576569</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2022-08-05T17:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: SGT - Extend to VMware</title>
      <link>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4665587#M576588</link>
      <description>&lt;P&gt;Thank you both for the answers!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 08:19:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sgt-extend-to-vmware/m-p/4665587#M576588</guid>
      <dc:creator>Aileron88</dc:creator>
      <dc:date>2022-08-08T08:19:15Z</dc:date>
    </item>
  </channel>
</rss>

