AnyDesk Security Checklist

1. Define approved business use

Document why AnyDesk is being deployed and which business processes it will support.

Trending

Zoom Room Certified Integration Partner

Examples include:

• Employee IT support
• Server administration
• Branch device maintenance
• Remote working
• Customer technical support
• Approved supplier maintenance

Avoid allowing different departments to install and configure remote access software independently without IT oversight.

2. Use an appropriate business licence

The AnyDesk free version is intended for private, non-professional use. Organisations should use an appropriate professional licence for work-related activities.

3. Identify authorised administrators

Maintain a list of employees and approved service providers who can initiate remote sessions.

Access should be removed promptly when:

• An employee changes role
• An administrator leaves
• A supplier contract ends
• A temporary project is completed
• Access is no longer required

4. Enable two-factor authentication

Two-factor authentication adds another authentication layer to supported AnyDesk access scenarios and the my.anydesk account.

It should be considered especially for administrators and Unattended Access.

5. Apply the minimum required permissions

Not every support session requires full keyboard control, file transfer, clipboard access or administrative privileges.

Use permission profiles to define what each user or support role can do.

6. Restrict incoming access

AnyDesk Access Control Lists can be used to define which devices are permitted to contact an endpoint.

Restricting access reduces exposure compared with allowing connection requests from any source.

7. Protect Unattended Access

Use strong, unique credentials and avoid sharing them through insecure channels.

Where supported, combine Unattended Access with:

• Two-factor authentication
• Access Control Lists
• Restricted permissions
• Approved administrator accounts
• Session monitoring

8. Review session logs

Session logs can support monitoring, investigation and audit requirements.

Define who reviews the logs, how often they are reviewed and what activities should be escalated.

9. Train employees to recognise scams

Employees should never accept unexpected remote access requests, even when the person claims to represent a bank, software company, government department or well-known technology provider.

Users should verify support requests through the organisation’s approved help desk channel.

10. Standardise deployment

Use approved deployment methods and configuration standards. Depending on the plan, AnyDesk supports MSI packages, device management tools, batch scripts and Windows Group Policy.

11. Keep endpoints protected

Remote access security also depends on the security of the underlying devices.

Maintain:

• Operating system updates
• Endpoint protection
• Secure administrator accounts
• Device encryption
• Firewall policies
• Backup procedures
• Physical device security

12. Review the deployment regularly

Remote access requirements change as the organisation opens branches, adds employees or appoints new suppliers.

Conduct periodic reviews of users, devices, permissions, licences, logs and security settings.