Profile
Who travels, carrying what authority, to which destinations. The three inputs ISO 31030 uses to set a security profile per trip rather than per person.
Practice 03 — Operational Security
A wrench is cheaper than an exploit.
Crypto and AI teams travel to places where a laptop, a phone and a set of keys are worth more than the building they are standing in. At that point the threat model stops being technical.
- ISO 31030
- Assessed against CCSS
What sets the estimate
- People in scope
- Roles and exposure
- Devices and platforms
- Custody and key material
- Travel and jurisdictions
Scoped on the call, quoted in days, in writing.
Scope an operational security review
A short, discreet call to understand your exposure, and to explain what we would advise and what is proportionate.
Times in
Loading available times…
Why teams call
You already suspect at least one of these.
- Someone is flying to a conference next month with signing authority on their person.
- Nobody has decided what a team member hands over if they are threatened.
- Your recovery process has been written down but never rehearsed.
- Hardware wallets were bought from whichever reseller shipped fastest.
- Travel bookings are made by whoever is free, with no risk assessment.
What you get
The deliverables.
Travel and physical
- Risk assessment by destination, traveller and activity, to the ISO 31030 framework
- Defined itinerary, vetted drivers and screened accommodation
- Close protection where the risk profile calls for it, in cities your team has not worked before
- Device and communications posture for border crossings and hostile networks
Custody under coercion
- Hardware wallet initialisation with verified provenance, on devices sourced to a chain you trust
- Duress PIN mapped to a funded decoy wallet — credible enough to surrender
- Plausible deniability by design: what is handed over, and what stays invisible
- Approval policy, signing ceremonies and recovery that has actually been rehearsed
How it runs
Design and provision
Travel arrangements, device posture and custody configuration built together, because a duress wallet is only useful if the itinerary assumed someone might ask for it.
Rehearse
Recovery and surrender walked through with the people who would have to do it, under time pressure, before it matters.
QuestionsBefore you
Before you
book the call.
Do you provide the close protection yourselves?
We design the requirement and coordinate delivery through licensed providers in the destination. Protective services are a regulated activity and we will not pretend otherwise; you will know exactly who is contracted and under what licence.
Is a decoy wallet actually credible?
Only if it is funded and used. A wallet with a plausible balance and real transaction history is credible; an empty one invites a second conversation. Designing what "plausible" means for your team is most of the work.
We are a small team. Is this proportionate?
Often it is not, and we will say so. Plenty of teams need a rehearsed recovery process and a sensible device policy, and nothing else. The call is free precisely so you can find that out.
How discreet is this?
Engagements are covered by mutual NDA before scoping detail is exchanged, we do not name clients, and travel specifics stay with the people delivering that trip.
Next step
Scope an operational security review.
Thirty minutes, no obligation. We will tell you what is worth doing, including when the answer is less than you expected.