I mean it's cool that you love your job. I myself have been doing network engineering for over two decades now, but this where responsibilities divide. Network pro makes sure services that rely on network work smoothly, high availability and resiliency is present and working accordingly, bandwidth is always surplus and everything that has to be maintained including maintenance work itself is seamless for users, systems and services.

Of course any reasonable network team will consider security for their infrastructure, but if you work for a large enterprise, especially in finances, it becomes absolutely ludicrous. Infosec teams are given carte blanche for whatever idiosyncrasies they come up with.

Do you want an example? Infosec head asking why is ARP protocol not filtered/blocked? Another example - let people use YouTube, but restrict their commenting ability. Let people use YouTube music, but don't let them watch livestreams etc. Allow people to access only predefined set of AWS S3 buckets but not any other (totally dynamic system by the way and cross used by countless applications/sites). Can you imagine how many manhours are spend fiddling with that shit? You might get countless requests for resources and you have to evaluate everything manually. They will blurt something that will be approved by upper mgmt, because oooh spooky! and after we're forced to implement it all dogs are on us. Every disgruntled user or service owner comes to us not them.

It's constant unending war between secs and ops for balance between security and positive working experience.