Solutions
Organizations
Security architecture for organizations whose risk has outgrown their arrangements.
Audience overview
The environment.
Most organizations acquire security in pieces: an IT provider, an access control installer, a compliance requirement, a policy written for an audit. Each was reasonable when it was purchased. Together they are not a program.
Protocol works with organizations to establish what is actually being protected, design an architecture that covers it, and coordinate the systems and people that deliver it.
A collection of purchases fails at the joints, silently, and is discovered by an event.
Typical challenges
What usually needs solving.
01
Physical and digital security are owned by different functions that rarely meet.
02
Access is granted at onboarding and rarely reviewed.
03
Vendor and third-party access is undocumented.
04
Incident response exists as a document, not a practiced procedure.
05
Nobody owns the whole picture.
The Protocol approach
How a program is built.
The four stages are the same for every audience. What changes is the environment being assessed and the architecture that follows from it.
- Assess
- Establish what the organization is protecting, what it currently has in place, and where responsibility sits.
- Design
- Produce a security architecture spanning facilities, systems, identity, third parties, and response.
- Integrate
- Coordinate internal functions and external providers onto shared standards and procedures.
- Manage
- Maintain the program through growth, staffing change, and changing risk.
The environment
Protocol begins with a written description of what is being protected — the properties, entities, people, and systems in scope — because an architecture designed against an assumption protects an assumption.
Relevant capabilities
The work involved.
Relevant products
The systems being built for it.
Each product below is in development. None is available to purchase today.
Protocol works with organizations as the coordinating party, not as one more vendor.
Example engagement models
How the work is scoped.
Engagements are named and scoped rather than priced. Pricing follows a conversation about the environment, not a page.
Security Posture Assessment
A review across physical, digital, human, and operational security with prioritized findings.
Integrated Security Blueprint
A designed architecture with a sequenced implementation plan.
Managed Security Oversight
Continued monitoring coordination, review, and program oversight.
Illustrative scenarios
Shapes the work takes.
The following are constructed illustrations of common situations. They are not client engagements, and no client is described anywhere on this site.
Illustrative scenario.
01
Growth outpacing arrangements
An organization that tripled headcount still runs on access and identity practices designed for a single office. The work re-establishes a baseline and rebuilds access on role rather than on request.
Illustrative scenario.
02
A first serious incident
An organization with no practiced response discovers this during the event. The work afterward is reconstruction: documented procedure, defined responsibilities, and rehearsal.
Related intelligence
Related analysis.
Start with the environment.
Speak with Protocol about a organizations requirement, an assessment, or a program that has grown past the arrangements holding it together.