How to Secure Remote Workers

Summary

Remote access should be designed around identity, least privilege, device security, monitoring, and a support process users can follow.

Identity first

Use this section as a starter framework for evaluating identity first in the context of your business, users, risk level, budget, and support expectations. The best decision is usually the one your team can operate consistently after launch.

For a stronger plan, document the current state, decision owner, technical dependencies, security considerations, and how success will be measured after implementation.

Remote access design

Use this section as a starter framework for evaluating remote access design in the context of your business, users, risk level, budget, and support expectations. The best decision is usually the one your team can operate consistently after launch.

For a stronger plan, document the current state, decision owner, technical dependencies, security considerations, and how success will be measured after implementation.

Endpoint basics

Use this section as a starter framework for evaluating endpoint basics in the context of your business, users, risk level, budget, and support expectations. The best decision is usually the one your team can operate consistently after launch.

For a stronger plan, document the current state, decision owner, technical dependencies, security considerations, and how success will be measured after implementation.

Support process

Use this section as a starter framework for evaluating support process in the context of your business, users, risk level, budget, and support expectations. The best decision is usually the one your team can operate consistently after launch.

For a stronger plan, document the current state, decision owner, technical dependencies, security considerations, and how success will be measured after implementation.