02-20-2023 07:03 AM - edited 02-20-2023 07:16 AM
I am making the transition to SGT/SGACL for enforcement. When I create an SGT, it auto populates in the matrix. I have found this a bit difficult to work with because I am trying to slowly phase in. So I have the following questions.
Example: I will not have Byod policy yet, but I want the tag. So I started out going into each cell for BYOD and making sure there was no SGACL applied. But then I found that by going to the source tree that I could remove BYOD completely as a source. Which is the right option?
Solved! Go to Solution.
02-20-2023 08:46 AM
hi @Josh Morris , answering your queries.
1.- If you don't have a SGACL assigned between tags X and Y , your assumption is correct , the default SGACL that you have configured in the matrix comes in that place ( in your scenario the default permit ) .
2,- Your approach is correct in both scenarios from matrix and from source tree you can configure the SGACL accordingly , while implementing this kind of enforcement a specific SGACL can be assigned from X to Y , and from Y to X , with the model you are using you need to only populate the tags you want to enforce .
Let me know if that helped you.
02-20-2023 08:46 AM
hi @Josh Morris , answering your queries.
1.- If you don't have a SGACL assigned between tags X and Y , your assumption is correct , the default SGACL that you have configured in the matrix comes in that place ( in your scenario the default permit ) .
2,- Your approach is correct in both scenarios from matrix and from source tree you can configure the SGACL accordingly , while implementing this kind of enforcement a specific SGACL can be assigned from X to Y , and from Y to X , with the model you are using you need to only populate the tags you want to enforce .
Let me know if that helped you.
02-20-2023 08:55 AM
Thanks @Rodrigo Diaz , this is helpful.
I'm thinking more from a deployment perspective now, would it make the most sense for me to remove all previously configured policy (Done initially as I thought it made sense to have it there), and start only with the policy that I'm ready to deploy. Based on my original image, I am not ready to deploy the policy I originally created. So I'm thinking I'll remove it for now, let the traffic hit the default rule of PERMIT, then add policy as I'm ready for it to be active. I also understand that I can change these policies into MONITOR state, which would allow them to report statistics but not enforce traffic.
02-20-2023 10:02 AM
That plan would work , if you enable the monitor mode for the SGACL , that will allow you to perform the testing you need without performing enforcement , but it will give you an idea if the counters for the rules you configure are receiving hits , please refer to this documentation that might help you https://community.cisco.com/t5/security-knowledge-base/trustsec-troubleshooting-guide/ta-p/3647576#toc-hId--1008668375
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide