<?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: Trustsec Enforcement in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547739#M4382</link>
    <description>&lt;P&gt;Hej&lt;BR /&gt;basically, u dont need to have IP-to-SGT mappings on the ENs. Only tables ENs need are SGACLs (those are delivered to ENs from ISE). from other hand, IP-to-SGT mappings are needed on the BNs to insert SRC SGT to VXLAN headers of the packets destined to ENs &amp;amp; also to enforce CTS RBAC policies on egrress from Fabric site. SXP is used for this with speakers on SXP reflectors or directly on ISE (not scalable). Effectively, if u can see IP-to-SGT mappings for external prefixes/hosts on BNs enforcement must work as defined on CatC or ISE. check if u didnt miss anything in this simplified process.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2026 15:38:25 GMT</pubDate>
    <dc:creator>Andrii Oliinyk</dc:creator>
    <dc:date>2026-04-23T15:38:25Z</dc:date>
    <item>
      <title>Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547700#M4381</link>
      <description>&lt;P&gt;Hello all:&lt;/P&gt;&lt;P&gt;Looking for some assistance with trustsec enforcement within a Cisco SDA fabric, and the best place for policy enforcement for devices external to my SDA fabric.&lt;/P&gt;&lt;P&gt;I have configured Group Based access control setup in catalyst center.&amp;nbsp; Trustsec matrix is pushed to ISE via PXGRID.&amp;nbsp; I currently have 5 VNs (VRF's).&amp;nbsp; Anything in software defined works fine from a allow/deny/sgacl perspective.&amp;nbsp; My question, is it possible to have SGT mappings for devices in my datacenter (external to SDA border), mapped into fabric edge nodes?&amp;nbsp; I know I can configure/map SGT mappings and push them to a device from ISE, but I end up seeing those mappings in the GRT/VRF/VN so systems that authenticate into a specific VN will never hit anything but "unknown" from the policy map perspective.&amp;nbsp; See role-based counters below (0 to 0 = unknown) which is where all my counters are incrementing.&lt;/P&gt;&lt;P&gt;show cts role-based counters:&amp;nbsp;&lt;BR /&gt;Role-based IPv4 counters&lt;BR /&gt;From To SW-Denied HW-Denied SW-Permitt HW-Permitt SW-Monitor HW-Monitor&lt;BR /&gt;* * 0 0 0 4758 0 0&lt;BR /&gt;0 0 0 0 42354155 149440605 0 0&lt;BR /&gt;2 0 0 0 0 0 0 0&lt;BR /&gt;3 0 0 0 0 81 0 0&lt;BR /&gt;4 0 0 0 0 0 0 0&lt;BR /&gt;5 0 0 0 0 0 0 0&lt;BR /&gt;6 0 0 0 0 0 0 0&lt;BR /&gt;7 0 0 0 0 0 0 0&lt;BR /&gt;8 0 0 0 0 0 0 0&lt;BR /&gt;9 0 0 0 0 0 0 0&lt;BR /&gt;10 0 0 0 0 0 0 0&lt;BR /&gt;11 0 0 0 0 0 0 0&lt;BR /&gt;12 0 0 0 0 0 0 0&lt;BR /&gt;13 0 0 0 0 0 0 0&lt;BR /&gt;14 0 0 0 0 0 0 0&lt;BR /&gt;15 0 0 0 0 0 0 0&lt;BR /&gt;16 0 0 0 0 0 0 0&lt;BR /&gt;17 0 0 0 0 0 0 0&lt;BR /&gt;18 0 0 0 0 0 0 0&lt;BR /&gt;19 0 0 0 0 23379 0 0&lt;BR /&gt;Any help is appreciated.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 14:22:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547700#M4381</guid>
      <dc:creator>Inq_J</dc:creator>
      <dc:date>2026-04-23T14:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547739#M4382</link>
      <description>&lt;P&gt;Hej&lt;BR /&gt;basically, u dont need to have IP-to-SGT mappings on the ENs. Only tables ENs need are SGACLs (those are delivered to ENs from ISE). from other hand, IP-to-SGT mappings are needed on the BNs to insert SRC SGT to VXLAN headers of the packets destined to ENs &amp;amp; also to enforce CTS RBAC policies on egrress from Fabric site. SXP is used for this with speakers on SXP reflectors or directly on ISE (not scalable). Effectively, if u can see IP-to-SGT mappings for external prefixes/hosts on BNs enforcement must work as defined on CatC or ISE. check if u didnt miss anything in this simplified process.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 15:38:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547739#M4382</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2026-04-23T15:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547954#M4383</link>
      <description>&lt;P&gt;Our environment (simplified) looks like Edge nodes ---&amp;gt; Intermediate Nodes (Underlay/routing) ----&amp;gt; External border nodes ----&amp;gt; Fusion Routers ------&amp;gt; Core:&lt;BR /&gt;&lt;BR /&gt;We're not doing any BGP route leaking at our fusions, we opted to hairpin inter-VN traffic at our core switch.&amp;nbsp; Please define IP-to-SGT mappings are needed on border nodes (which border, external border nodes, or fusion routers).&amp;nbsp; My goal was to try to not have to allow traffic to "unknown" for many of my fabric networks.&amp;nbsp; We have closed networks that we don't allow out to the internet, and it would be nice to be able to remove the "unknown" SGT, but because from the fabric edge, IP-SGT mappings aren't learned , I have to allow traffic to "unknown", and handle policy enforcement elsewhere.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 12:04:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547954#M4383</guid>
      <dc:creator>Inq_J</dc:creator>
      <dc:date>2026-04-24T12:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547968#M4384</link>
      <description>&lt;P&gt;look, u better incorporate learning of SGT-to-IP mapping on the BNs. with this u'll achieve 2 goals: allow BN to enforce GBAC policies on egress from Fabric site &amp;amp; provision VXLAN packets with target SGTs when those are sent to ENs. u also can do it on FNs or even Cores if u propagate SGTs downward to BNs &amp;amp; in reverse direction. But this is more complicated as u need to manually configure interlinks to carry CMD information along the packets flows &amp;amp; ensure all nodes (BN, FN, Core) handover SGTs from ingress to egress. Unless your CatC-ISE integration not migrated to CatC's "master" role, u define mappings on CatC &amp;amp; they will be propagated to ISE. From the ISE they can be delivered in either SXP or over the REST to BNs.&amp;nbsp;&lt;BR /&gt;Last but not least, whitelisting GBAC enforcement will block all Unknown (effectively SGT=0|Absent) IPs. U must be extremely precaution in doing this. I was witness to cases when customer disrupted critical applications by blocking Unknow participants of flows.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 13:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547968#M4384</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2026-04-24T13:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547991#M4385</link>
      <description>&lt;P&gt;Thank you, much appreciated.&amp;nbsp; Will look at implementing at my external border nodes.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 14:53:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5547991#M4385</guid>
      <dc:creator>Inq_J</dc:creator>
      <dc:date>2026-04-24T14:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: Trustsec Enforcement</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5548058#M4386</link>
      <description>&lt;P&gt;@ your service) as a quick followup: i dont remember that CatC provided&amp;nbsp; any workflows for SXP|OtREST mappings distribution. Most likely u'll need to do it with day-N templates for BNs.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 19:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/trustsec-enforcement/m-p/5548058#M4386</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2026-04-24T19:08:06Z</dc:date>
    </item>
  </channel>
</rss>

