How do I integrate MetaAccess to Symantec Secure Access Cloud?

This guide shows you how MetaAccess can be easily and seamlessly integrated into Symantec Secure Access Cloud (TM) to implement Zero Trust Network architecture when accessing any corporate resource deployed in any datacenter (on-premises or in a private or public cloud) from any device. Learn more.

By integrating MetaAccess to Symantec Secure Access Cloud (TM) , administrators are able to check remote devices for:

  • Vulnerabilities - Detect vulnerabilities on endpoints in installed applications and operating systems.

  • Enhanced Compliance - Get greater visibility into the status of installed security applications such as hard disk encryption and system information such as password protection to ensure devices are compliant with existing policies.

  • Unwanted Applications - Detect and remove non-compliant or unwanted applications such as peer-to-peer applications from a remote device.

  • Advanced Threat Detection - Utilizing two methods of advanced threat detection, MetaAccess helps identify potential threats that existing anti-malware software might not protect against.

  • Portable media scanning and access control - Protect organizations against threats from portable media on the endpoints, a common attack vector for malware.

  • Anti-screen capture - P revent keyloggers and advanced malware from accessing sensitive data.

  • Screen capture protection - P revent unauthorized or accidental screenshots and recording by users, VDI, web collaboration tools, and malicious applications.


You can set up a MetaAccess account to manage up to 50 devices with free of charge. Start Trial Now


  • If your devices sit behind a firewall or a proxy, you need to whitelist domains to make sure devices are able to talk to OPSWAT MetaAccess cloud. See more details at How do I configure OPSWAT Client to work with a proxy or outbound firewall?

  • You need to enable Cross-domain API settings (Settings > Integrations) on your account at the port 11639 and please make sure that there is no application which used the port 11369 on your endpoints.

This article was last updated on 2020-06-25