It is possible it relates to the tooling available to the security team. A team may have access to tools to manage and vet or even just report on extensions for one of the browsers but not the other at this time.

I don't think that's likely to be your situation, but it is a legitimate reason for a policy that seems to discriminate against a particular browser for no apparent reason.

It is possible it relates to the tooling available to the security team. A team may have access to tools to manage and vet or even just report on extensions for one of the browsers but not the other at this time.

I don't think that's likely to be your situation, but it is a legitimate reason for a policy that seems to discriminate against a particular browser for no other apparent reason. I know Chrome, in particular, does have an administration package available for Windows Domain administrators that allows admins to see and set a number of security options, but that doesn't mean the security team has been able to set up these tools. I suspect Firefox has something similar, but I'm not up on Mozilla's tooling for this at the moment.