Most developers should travel without standing production access. Give the few who must stay reachable, such as on call engineers, short lived, narrowly scoped access that expires when the trip ends, and keep a break glass route for everyone else. Start from what the person must do while away, not from what they usually do.
Why trips change the risk
At the office, a laptop sits on a managed network. On the road it sits in bags, hotel rooms and shared networks. The chance of loss or theft goes up, and so does the chance of using a less trusted network. NIST SP 800-46 Revision 2 notes that organizations and their staff use telework and remote access from external locations and that all components, including client devices, should be secured against threats identified through threat models. A trip is a different threat model from a desk.
Questions to ask first
- Will this person be on call during the trip?
- Is the task something a colleague at home can do instead?
- What is the worst a stolen laptop could do with the access carried?
- Can the access be time limited, read only or approval based?
- Can the person work from a hosted dev environment with no local secrets?
Decision table
| Situation | Suggested approach |
|---|---|
| Attending a conference, no on call | No production access carried; read only dashboards if needed |
| On call while away | Time boxed access, hardware key MFA, hotspot only |
| Release owner away | Delegate the release, or approve via a second person |
| Contractor travelling | Same as staff, with a shorter expiry |
| Visiting a high risk location | Loaner device with no production access, see below |
Options in order of preference
First, no access. A person who does not hold a credential cannot lose it.
Second, access through a hosted environment. If code and secrets live in a remote workspace, the laptop holds little. See Remote dev environment or local laptop: a decision guide.
Third, short lived, narrow access. Grant a role for the dates of the trip, review it on return, and let it expire on its own. The AWS steps show why a short duration matters, since temporary credentials remain valid until they expire.
Fourth, a break glass account. Keep emergency access held by a small group at home, with alerts whenever it is used.
Loaner devices
For trips where you worry about device seizure, loss or tampering, a clean loaner laptop with no production credentials is common. Wipe it on return, and do not reconnect it to the company network until checked. Set this policy before the trip, not at the airport.
What to record
Write down who has what access, for which dates, and who approved it. This is also useful evidence for access reviews. See Access review evidence: what auditors look for.
Safeguard's compliance and evidence automation and policy gates support the paper trail and the guardrails on what can ship, but the grant and revoke steps happen in your identity and cloud tools. Try a free scan to see what your code depends on.
Quick check
Is a VPN enough to allow production access from hotel Wi-Fi?
A VPN helps with the network path, but it does not reduce what a stolen laptop can do. Limit the access itself too.
Who should approve production access for a trip?
The person's manager and the system owner, with the request and expiry date recorded.
Sources
Last reviewed: 19 October 2026.
