The head of the development org should also have an appreciation for mitigating security risks as they are often born out of bugs so it isn't all just security theater if one is zapping application breaking bugs.
The head of the security org should accept that not all security bugs will be squashed and should focus on risk ranking and prioritizing the most feasible and high impact bugs first while avoiding hypothetical scenarios unless the red-team / penetration teams can prove they are not hypothetical.
I’ve worked with security idiots whose life’s work is monk like transcription of NIST 800-53 publications into local policy. I’ve also worked with a couple who are the smartest engineers that I’ve met.
I think that the ideal security team would be like brakes on a car - they let you go faster. Unfortunately, I’ve never really seen that happen, and the culture of security people is this weird cop-like thing that comes from the Feds.