However, feeling cynical this morning, and arguably technologists need to understand "the business," is more than a black box, and product owners need to understand that "the infrastructure," is an economic factor with risks that affect the viability of their business model.
The basic problem I've encountered in large organizations is that most security tools exist to keep devops technologists entertained playing spy v. spy games while the real business instrumentalizes them as a black box of uncertainty to sandbag estimates and commitments, obstruct competing projects, obfuscate catastrophic risk exposure to investors, and externalize reckless project risk to something "nobody understands."
It's the "aw, shucks, security surprise!" game that project managers the world over use to deflect accountability for poor decisions.
I remember about 10 years ago security people discovered economics as a shallow set of metaphors for describing what they did. Today we're all about machine learning and threat hunting, technologies which I think are just more sophisticated versions of the same nonsense that keeps security people focused on externalities instead of getting real traction to effect the design and production of better products and systems.
We should ask whether the data that post-production security systems collect gives us real leverage against business risk, or if it's mainly entertainment for a tech governance group who are played as marks by the rest of their organization.
I love this field, but that also means taking a very hard look at it and asking whether it creates value beyond its hype cycle. Internet security is a disaster, and we should ask whether a new set of metaphors to help us ignore the fact we are still just doing the same thing is the right approach.