Protocol Intelligence
Critical Infrastructure
Facilities and networks whose failure is felt outside their own operation. The concern is dependency and consequence rather than the perimeter of any single site.
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
What depends on this operation that its operators do not have visibility into?
02
Where do operational and information systems meet, and who owns that boundary?
03
How is a consequence-driven program different from a compliance-driven one?
Briefings go out when a piece is published, not on a schedule.
Adjacent work
Where this sits in the practice.
The capabilities closest to critical infrastructure. 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.