Companies
Protect source code, processes, suppliers, prototypes, customer leverage, and employee know-how across commercial and personnel boundaries.
Leadership playbooks
Make sensitive access deliberate, observable, and reversible.
The objective is resilient collaboration—not isolation. Strong controls protect assets and people while preserving legitimate exchange.
01
Choose your context
Start with the institution you lead.
The playbooks translate recurring case patterns into governance questions, technical controls, and steps leaders can assign and test.
Universities and research institutions
Reconcile openness with contractual duties, disclosure, export controls, sample custody, intellectual property, and fair process.
Incident response
Preserve evidence, stabilize access, protect legal privilege and people, assess notification duties, and avoid premature public claims.
02
Board-level test
Five questions worth asking now
A leader should be able to get a concrete answer, an accountable owner, and evidence that the control works.
- 01
What are the crown jewels?
Name the smallest set of technologies, processes, data, samples, supplier relationships, and tacit knowledge whose loss would compress a competitor’s timeline or materially harm the institution.
- 02
Who can reproduce them?
Map not only file permissions, but also the people, equipment, settings, vendors, and troubleshooting knowledge needed to rebuild the capability elsewhere.
- 03
Which relationships create access?
Connect customers, suppliers, visitors, collaborators, travel, outside appointments, recruiters, and departing staff to the assets they can reach.
- 04
What would trigger escalation?
Define observable conduct and access thresholds before an incident. Do not make nationality, ethnicity, or viewpoint a proxy for risk.
- 05
Can we prove what happened?
Test logging, retention, sample custody, source provenance, device preservation, and decision records through a realistic tabletop exercise.