Protocol Intelligence
Insights
Shorter arguments about how the security field is organized and where that organization produces failure. Insights make one point and stop.
Under examination
The questions this topic works through.
Protocol publishes when there is something worth reading rather than on a schedule. These are the questions this topic exists to answer — an agenda, not a set of conclusions.
01
Why do competent components keep producing incoherent programs?
02
Which industry conventions exist because they work, and which because nobody revisited them?
03
What is the difference between a program that is believed to be working and one that is known to be?
3 pieces
Filed under this topic.
Briefings go out when a piece is published, not on a schedule.
Adjacent work
Where this sits in the practice.
The capabilities closest to insights. Writing and practice inform each other, which is the reason Protocol publishes at all.
Discuss this subject.
Speak with Protocol about a security requirement, a program under review, or the analysis behind any of this writing.