A process that I've heard some financial people developing (highly secret/proprietary/potentially valuable) software use when traveling is: 1. Store confidenti

A process that I've heard some financial people developing (highly secret/proprietary/potentially valuable) software use when traveling is: 1. Store confidential data on company servers or a secure/trusted/audited cloud service. 2. Protect that data with two factor authentication, ideally with an ephemeral/rotating factor. 3. Incorporate a duress code into one of the auth factors (e.g. "add one to the google authenticator result when logging in or you get fake data/get permanently locked out until you human-authenticate to regain access"), ideally both. This is far from perfect, but reasonably secure and not terribly inconvenient in practice. Additional layers of protection can be added to the duress process, like defaulting to under-duress behavior until a certain timeframe (i.e. you're being searched at the airport and not during your appointment time slot), or when from an unrecognized network location. Like all duress-code-based responses, it is vulnerable to humanity (e.g. torture/intimidation).