Reflexion will be End-of-life on March 31,2023. See Sophos Reflexion EoL FAQs to learn more.
Can Sophos confirm please that SFOS 19.0.1 is still not able to detect staggered group membership of a Active Directory? Because that is what I noticed yesterday.
I tried to use a top level group that contains sub-groups for Firewall rules. If the user is member of a sub-group, SFOS does not see it's group membership.
Group A +----SubGroup B +----SubGroup C +----SubGroup D
Subgroup B Members:User 1User 2
Subgroup C Members:User 3User 4
Subgroup D Members:User 5User 6
I imported AD Group A into SFOS.
Users 1-6 restarted their Windows computers with Intercept-X and tried to use the Firewall rule but the traffic was blocked.
I checked the users in SFOS and their group membership from firewall perspective.
Both:Group andOther group memberships
do not list Group A.
If I import Subgroup B into SFOS, User 1 and User 2 show Subgroup B in Other group memberships and the users can use the firewall rule.
So unfortunately, it is very likely SFOS is still unable to read staggerd group memberships after all those years.
See posts by dirkkotte and LuCar Toni here:
Firewall rules by AD group membership does not work.
User Authentication - AD Group in Group
And the Help:
Group membership behavior with Active Directory
But that does not list limitations about staggering / nesting.
SFOS only supports the final group, not the nested groups. Nested group support would mean, the firewall would have to replicate your entire AD, which is not an easy task. Plenty of vendors are not doing this for several reasons, most likely performance and the impossible amount of combinations you can have.
Therefore most vendors, like Sophos, only query the "total group". SFOS is doing this by query the user and getting the groups of this user from AD. To get the nested groups, SFOS would have to query all groups as well to get the hierarchy, and store it in a own value. Then to query the groups against the information by the user etc. This is not an easy task to begin with, which comes with certain complications.
Another approach could be to rebuild the entire query architecture and query each group with each request. This can work but is a lot of effort and performance decrease to do this.
In the end, nested group support is something, which could be eventually better be resolved by an overlook of the architecture of the AD.
Thanks for taking your time for a detailed answer. So I made a request to the Documentation team to add something about group nesting being unsupported to the documentation.
We'll import the Subgroups into XG then.