Contents
Offshore Advantages guide
Set a security baseline for an offshore workstation
A workstation baseline that covers the device, the account, the data, and the review.

Key takeaways
- Name the device and the account rules.
- Restrict data to approved systems.
- Review the baseline quarterly.
How to approach: Set a security baseline for an offshore workstation
A workstation baseline should tell the teammate what is required before accessing client work. Start with the device, the account, the data, and the review. A baseline that is only in a policy file will be missed.
Use the same format for every handover so the next reader can scan it. Keep the baseline practical. A rule that cannot be followed on a normal workday will be bypassed.
Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned.
Name the device and the account rules
Record the approved device, the disk encryption, and the screen lock. Record the account rules, such as named accounts and multi-factor authentication. Name the owner in the same line as the action.
Record the date and the source so the next reviewer can repeat the check. Record the update and backup expectations. An unpatched device is a risk even when the account is strong.
Review the first few notes together before the process expands. Ask whether a new reviewer could act on the record without a conversation.
Restrict data to approved systems
Write where client data may be stored and where it must not go. Record the approved transfer methods. A personal drive or a chat attachment is not an approved store.
A control that depends on memory is not yet a control. Record the clean-desk rule for paper and removable media. A paper note can defeat a strong digital control.
Keep the original note beside the corrected version. Separate what was observed from what was assumed.
Review the baseline quarterly
Check a sample of devices and accounts against the baseline. Record the exceptions and the owner.
A baseline that is not sampled is an assumption. Record the date and the source so the next reviewer can repeat the check.
Sources
- NIST Cybersecurity Framework: Connect access and change decisions with written controls and reviewable evidence.
- NIST Privacy Framework: Use a risk-based approach for personal data handled by an offshore team.
- U.S. Small Business Administration: General guidance on documenting recurring operations.
- U.S. Department of Labor: Public guidance on recordkeeping and employment practices.
- GAO Green Book: Internal control standards for operations and reporting.