Respect, too. I've lost count of how many times I've been stuck waiting for somebody in the network group to grant me access to some resource I need to do my job until somebody that they actually respect (that is, a manager) tells them that they have to.
Though arguably the manager should have arranged for an easier process if this happens more than a few times.
There’s a difference between needing to ask for access to shared resources and asking for someone else to do work. So many corporations silo there teams so deeply that PRs from outside members aren’t even considered. Collaboration isn’t given anything more than lib service.
If you're legitimately concerned about internal adversaries you start by finding and catching them. Once you've set up effective mechanisms for doing that you can start to introduce stricter controls around sensitive data/operations based on what you've learned about how your internal adversaries operate. You use a light touch when doing this, because you understand that every extra control you put in place introduces inefficiency into the organization.
I feel like at very senior levels, you can't really say "it's not my job". You're looking out for the whole organization, not just your direct team, and it's your responsibility to help everyone move ahead - even the ones who don't report to you.
If they're on the network team, it's literally their job description to make sure everybody has the network access they need.
If their job is to manage access, it slowly morphs into "controlling access" and then "wanting justification in granting access" which is not the same thing. There's no benefit to someone pointing this out for a long time. Eventually (hopefully) this perversion is identified as the cause of why processes went from efficient to gridlock, grinding a large company to a halt.
None of these are directly relevant to the power imbalance.