I think these are clear signs of a dysfunctional organization. I want to associate that with company size (larger -> more bureaucratic, counter-mission nonsense), but I've also seen large companies that don't get caught in these pitfalls. My best guess to lay blame would be at inadequate, out of touch, need-to-be-fired B.o.D and upper and mid-management deadwood. These are the people that propagate such ineffective culture.
I will forever remember the head of IT at my org exclaiming in a meeting, "I'm not here to solve problems". Blew my mind at the time, but it's emblematic and representative of company culture as a whole.
Now that said they should still try to advance the mission within that framework, and not be lazy.
Yes, their role is defense, but not insofar as to remove the profitability of the organization. In several orgs now I've seen the legal team blow contracts and the security team break the product and the IT team break development in the name of performing their role "correctly".
Brainless box checking is not part of defense, you must be willing to critically think about how to fit your role to your product or organization's profit motive.
One example is a disaster readiness organization which mandates that teams cannot deploy code in only a single datacenter. What they should really be doing is making it so code automatically runs in multiple datacenters.
Facilitate instead of forbid.
Your daily driver account should not be local admin.
Yes, we need MS Defender/S1/Crowdstrike for EDR, DNS blocking and Mandatory updates etc for security which now is actual money with cyberinsurance that won't pay unless we fulfil certain criteria. This all requires computers to be managed by an MDM.
Take it up with teh bossman.