They can't do their jobs unless they communicate with you. And you can't do your job unless you communicate with them.

I'm still hearing this question from time to time—on Twitter, at live events, in article comments—when we write about various broad issues: "But what does that have to do with network security?" It's the Network Security Isolationist school of thought.

In our February Special Report, we take a look at the many facets of securing intellectual property (IP)—via legal safeguards, timely data destruction, social engineering prevention and more. IP protection is a broad business goal and a perfect illustration of why isolationist thinking doesn't work in security. Network defenses are a critical part of the puzzle, but only one part.

The "What does that have to do with network security?" question is a weirdly anti-intellectual, incurious thing to ask for an industry with roots in exploration and tinkering and pattern-finding. More critically, it holds back the network security profession, making security people appear to be nonparticipants in the business.
Ten years ago, this question was the norm. Five years ago, it was maybe a forgivable lapse. Now, it's just ridiculous.