Secure Mobile Access 12.4 Deployment Guide
- Secure Mobile Access
- About this Guide
- About SonicWall Secure Mobile Access
- Planning Your VPN
- Common VPN Configurations
- About the Configurations
- Deployment Scenario: Remote Access for Employees and Partners
- Customizing WorkPlace
- Testing the Deployment Scenario
- Other Remote Access VPN Scenarios
- Additional Partner VPN Scenarios
- End Point Control Scenarios
- Access Policy Scenarios
- Application-Specific Scenarios
- Authentication Scenarios
- Access Component Provisioning
- SonicWall Support
Communities
Communities are a cornerstone of the appliance’s approach to deployment and security. They are used to aggregate users and groups for the purpose of deploying access agents and controlling the end point, and can also be referenced in access control rules.
You can create communities for specific types of users, such as remote employees or business partners, or take a more granular approach and create communities of users in a particular department or location.
For example, employees who require broad access to resources and applications on your network could be assigned to a community that offers the network tunnel client as an access method. To make sure that they are using laptops managed by your IT department, specify which End Point Control zones are available to users in this community.
You may have another group of users who require only limited access to resources because they’re logging in from public kiosks or other non-secure locations. To give these two different groups access to your network resources, you could create separate communities, each configured to deploy the appropriate access agents, and (in the case of users with non-secure devices) use End Point Control (EPC) to prevent sensitive data from being left on a device.
Was This Article Helpful?
Help us to improve our support portal