4.1. Cloud console

MetaAccess 2.6.0: February 11, 2020

1. Enhanced User Profile page to show usage of accounts (s)he is managing.

2. Added a new setting to notify end-users who is running outdated on-demand agent. This setting is disabled by default.

3. Administrators can now set a trigger to send an email notification to configured emails when an account runs out of license. This trigger is disabled by default.

4. Minor enhancements:

  • Added a column, Group, into a Device Event Logs report to indicate what group a device was associated to at that timestamp

  • Added more missing patch categories: definition_update, feature_pack

5. Bugs fixed:

  • Device ID is now fully shown on the remediation page instead of being shortened if its length is long

  • Device Details v3.1, v3.2, v3.3 now returns timestamp for the parameter infection.metascan .last_scan in GMT format as the API documents instead of UNIX format

  • Applications inventory couldn't be loaded sometimes

MetaAccess 2.5.0: January 07, 2020

1. MetaAccess enhanced policy configuration to allow administrators to configure more granular policies for each operating system and focus on security requirements at an organization. With this enhancement, admin can hide categories that they don't want to monitor.


2. Minor changes:

  • added "Enrolled At" information into a device report when an administrator exports devices from the MetaAccess console

MetaAccess 2.4.2: November 26, 2019

1. Administrators can monitor only OS updates in specific categories. All policies will be set with "any missing patches" as a default option when this release is rolled out.

2. Administrators can configure OPSWAT Client to delay the collection of compliance data after it starts. This way, it gives other applications time to start before the OPSWAT Client reports compliance data to reduce false-positive detection.

3. Enhancement:

  • Device reports will be put in a queue to be processed against a policy. The OPSWAT Client will receive a compliance result in the next check-in, up to a minute.

4. Bugs fixed:

  • MetaAccess will not send an unknown devices report if there is no unknown device found

  • A device was able to enroll in an account even the account limit is reached. The system will change status of a device to Out-of-license-usage if a device was enrolled after the limit reach.

MetaAccess 2.4.2: October 22, 2019

1. Administrators can now perform an on-demand compliance check on devices from the management console


2. Added new APIs:

3. Administrators can now monitor the progress of an on-demand threat scan from the management console


4. Bugs fixed

  • Device Details API didn't return data for some categories such as Unclassified applications, detected patches, mobile apps

  • The last reboot time of a mobile device was not shown correctly

  • Installed applications on Linux devices were not listed on the Applications inventor

5. Minor enhancement

  • Remove OPSWAT Client SDK on "Add Devices" popup

MetaAccess 2.4.1: September 17, 2019

1. Administrators can now configure different encryption state requirements for additional local volumes and additional removable volumes. These settings will be set based on the "Additional volumes are not encrypted by an approved application" setting in a policy before the release

Before Release

After Release

Additional volumes are not encrypted by an approved application

Additional local volumes are not encrypted by an approved application

Additional removable volumes are not encrypted by an approved application








2. The date time on the console UI now reflects the local timezone

3. Bugs fixed

  • Device Policy Check API returned a device was not found if the MAC Address is in uppercase. The API now accepts MAC address in either lowercase or uppercase.

MetaAccess 2.4.0: August 06, 2019

1. Whitelist Vulnerabilities: Administrators can now whitelist vulnerabilities for policies or entire accounts after reviewing risks and assess impact of vulnerabilities. By whitelisting vulnerabilities, vulnerabilities associates to a device will not be counted for issues if they are whitelisted on a policy the device is assigned to.


2. Enhanced vulnerabilities view: provides administrators a better view on what applications,OS patches and CVEs are associated, and what policies it is whitelisted on


3. The system will not send a threat summary report if the system doesn't detect any threat in the last report duration.

4. Added new OAuth APIs:

  • Device Action API v3.2 supports a new action , scan_threats, to allow administrators to send an on-demand threat scan to devices

  • Get Reports API v3.1 supports administrators to retrieve a result for on-demand threat scan action.

5. Bug fixed: the system didn't send a request to the agent to open a remediation page if the device reports issues in N consecutive reports and N is greater than the non-compliant threshold.

6. Minor enhancement:

  • Added an agent type information under System Information on Device Details view

  • The system will keep MAC address information of devices which registered or reported duplicated MAC address. By this way, administrators can search for devices which reports the same MAC address

  • Added a new default rebranding package with Japanese language

MetaAccess 2.3.1: June 25, 2019

1. "Managed By" information on remediation pages will be shown with Account Name instead of an email address of the account.


2. Enhanced performance to process requests.

MetaAccess 2.3.0: June 04, 2019

1. Enhanced threat detection to allow administrators to configure how a file is considered a threat. Criteria can be based on the number of engines and trusted engines when a device scans threats against MetaDefender Cloud. Admins can configure a policy to leverage MetaDefender Core for Threat Detection, when used this way, MetaAccess respects scan results from MetaDefender Core: only files with a BLOCKED status will be considered as threat.

Scan Source

Before The Release

After The Release

MetaDefender Cloud

Threat Scan

  • Filter threats based on trusted engines. A file is detected as threat if at least one trusted engine detects it as a threat

Device Issue

  • Considered an issue if a file is detected as threat by N engines if enabled

  • Considered a critical issue if a file is detected as threat by M engines if enabled

Threat Scan

  • Filter threats based on number of trust engines. A file is detected as threat if at least N trust engines detect it as threat

Device Issue

  • Considered an issue if a device reports any threats if enabled

  • Considered a critical issue if a threat detected by M engines if enabled

MetaDefender API (Core)

Threat Scan

  • Filter threats based on trusted engines. A file is detected as threat if at least one trust engine detects it as threat

Device Issue

  • Considered an issue if a file is detected as threat by N engines if enabled

  • Considered a critical issue if a file is detected as threat by M engines if enabled

Threat Scan

  • A file is detected as threat if MetaDefender API (Core) scan result is BLOCKED

Device Issue

  • Considered an issue if a device reports any threats if enabled

  • Considered an issue if a device reports any threats if enabled


2. Administrators can now enable OPSWAT Client to auto-block mobile PTP/MTP devices when a user inserts a mobile PTP/MTP devices to an endpoint. This option is disabled by default. If you wish to enable it, please log into MetaAccess console and update policies.


3. If OPSWAT Client reports free hard disk space as not supported, MetaAccess does not consider this as an issue. This affects macOS 10.13+ devices

MetaAccess 2.2.1: May 24, 2019

  • Fixed issues

    • couldn't download agents from the download pages

    • couldn't fetch agent log

MetaAccess 2.2.0: May 14, 2019

1. Administrators can now configure agents to upload allowed/blocked files to a MetaDefender Vault when a user unblocks or copies files from portable media drives. This setting is disabled by default.


2. Administrators now have an option to exclude CD/DVD from auto-blocking portable media drives. This setting is disabled by default.


3. Administrators can see a timestamp when a device is enrolled to an account


4. MetaAccess adds a Live Chat snippet on the console to help users reach out to our support for help in less time

5. Add new APIs, Get Devices v3.3 and Device Details v3.3, to return a timestamp, enrolled_at, when a device is enrolled to an account,

6. Minor changes:

  • Increased Nickname length limit to 100 characters

  • Re-organized the left navigation menu: moved the "Group" menu out of the "Inventory" menu

MetaAccess 2.1.1: April 17, 2019

1. Fixed: when a user downloads an installer from a download link that contains a tag name/group id, the Cloud does not generate the installer with the tag name/group id

2. Fixed: the link to go to the OPSWAT support portal on Help Center

MetaAccess 2.1.0: April 02, 2019

1. MetaAccess now enables administrators to detect advanced threats within file systems in addition to active running processes powered by MetaDefender technologies. Administrators can schedule scans with multiple options such as a Full System Scan or a Custom Scan (memory, system volume, additional volumes, a specific path).


2. Administrators can also perform an on-demand scan on selected devices and obtain a threat report remotely.


3. Added oAuth API Device Information v3.0 to return pre-processing data for a device

MetaAccess February 26, 2019

1. Enhanced dashboard to provide a consolidated view of your security and device landscape across your organization . Beside an overview dashboard, administrators now can access detailed security view for Secure Access, Vulnerabilities, Compliance, and Threat Detection.


2. Administrators can do localization and globalization for each device group by customizing the remediation page for groups. Administrators can add a customized package for remediation pages at Settings > Rebranding and assign it in Group details


MetaAccess January 22, 2019

1. MetaAccess now returns parameters in the response header to indicate API rate limits (X-RateLimit-Limit), how many calls left (X-RateLimit-Remaining), when the rate limit is reset (X-RateLimit-Reset-Time)

2. Added new OAuth APIs:

  • Account Details v3.1: return details about device status, device with vulnerabilities by severity, devices with issues by severity

  • Device Action v3.1: support more actions to allow administrators retrieve OPSWAT Client log on devices

  • Get Reports v3.0: support download OPSWAT Client log if available

3. Bugs fixed

  • A co-administrator could not invite another user to manage the co-admin account

MetaAccess December 26, 2018

Release Type: Major Release

1. Administrators can configure policies to grant users following actions for portable media devices:

  • Block all access

  • Allow one-way access

  • Allow bi-directional access


2. Administrators can enable Media Manifest validation to expedite portable media file processing


3. Administrators can monitor portable media activities on devices from the MetaAccess console management


4. Administrators can configure policies to scan files on Windows and macOS agent against their own MetaDefender API servers


MetaAccess November 27, 2018

Release Type: Minor Release

1. Added support to integrate with 3rd party SSO service: an account can provision users through their own SSO service


2. Enhanced user management with search/filter and update abilities


3. Enhanced the remediation page to show end-users an overview about the device’s issues.

4. Added number of vulnerabilities of a device into an Inventory report

5. Added a new OAuth API Account Details v3.0: added the license key to the API response

MetaAccess October 23, 2018

Release Type: Minor Release

1. Added the number of vulnerabilities of each device into an export result when a user exports device inventory

2. Removed options to download Infected Devices, Exempted Devices, Unknown Devices on Download Reports section on Reports and Notifications page. Now administrators can download these reports on the Devices page

3. Enhanced remediation guidelines to resolve vulnerability issues which were associated with missing patches

4. Added a new OAuth API Get Threats v3.0 to return detected threats on a device

5. Bug Fixed:
- On Android devices: The cloud showed the last time IP connections had scanned as the last report even when the agent had not scanned IP connections

MetaAccess September 25, 2018

Release Type: Minor Release

1. Enhance Linux policies

2. Vulnerabilities: add a policy to consider a device issue based on vulnerability severity

3. Enhanced operating system policy: allow administrators define approved OS versions

MetaAccess August 28, 2018

Release Type: Minor Release

1. Vulnerabilities enhancement

  • Detect vulnerabilities at operating system level

  • A central view for all vulnerabilities on an account

2. Added an option to automatically delete and uninstall the OPSWAT Client on devices which have not accessed to cloud applications in a certain amount of time.

Known issues

  • if an application is deleted, and a device only accessed to that application in last X days, the device will be automatically deleted and the agent will be uninstalled.

3. Added OAuth APIs:

  • Get Applications v3.0 API: support filter application installed on endpoints on an account

MetaAccess July 31, 2018

Release Type: Minor Release

1. Added support to enforce access rule for mobile devices to cloud applications

2. Introduced OPSWAT Client SDK for OEM customers

3. Vulnerabilities: enhanced dashboard to show vulnerable devices by severity level

4. Enhanced Privacy Settings to enforce agent not transfer configured privacy information to MetaAccess servers

5. Added OAuth APIs:

  • Get CVEs 3.0 API: support filter CVEs on an account

  • Get Devices 3.2 API: added filters to filter devices which install specific apps or have specific CVEs

  • Get Device Details v3.2 API: added last time a device scaned running processes against with MetaDefender Cloud and a field to indicate if a file still exists on the system for repeated threats

6. Enhanced Upgrade Account process on console to make it more convenience for customers

7. Lockscreen timeout is shown as "not supported" instead of "not set" on OS platforms OPSWAT Client doesn't have ability to check lock screen timeout

MetaAccess June 26, 2018

Release Type: Major Release

1. Application Inventory: provide visibility on applications installed on endpoints.

2. Vulnerability: scan for vulnerabilities on the endpoint system and installed applications to detect vulnerable applications installed organization-wide as well as per device

3. Compliance Assessment: use a scoring system based on OPSWAT and CVSS scores to consider an issue if a device has CVEs

4. Added OAuth APIs:

    • Device Details v3.2: support query device details with a custom ID

    • Get Applications v3.0: get applications install on endpoints

    • Application Details v3.0: get application details along with CVEs

    MetaAccess May 22, 2018

    Release Type: Minor Release

    1. Updated Terms and Conditions, Privacy Policy, and Cookie Policy

    2. Cloud Access Control: record a user who is using a device to access a SaaS application if requested

    MetaAccess May 08, 2018

    Release Type: Minor Release

    1. Added a new OAuth API, "Get Groups" v3.0, to return managed groups in an account

    2. Enhanced to show encryption state as “not supported” instead of “unencrypted” if a product is not supported to detect encryption state.

    3. Changed the text "antivirus" to "anti-malware" on console, not on API parameters/keywords

    4. Bugs fixed

    • Get Devices API v3.1, v3.0: Returns all devices in an account instead of devices assigned to a filtered group

    MetaAccess April 10, 2018

    Release Type: Minor Release

    1.Added an action to fetch agagent's logs

    2. Added a setting to skip threats in local malware log if the file no longer exists
    on the system

    3. Added a OAuth APIs, Get Devices v3.1 and Device Details v3.1, to return the last timestamp a device is rebooted

    4. Enforced rate limit for OAuth APIs

    5. Changed the text "antivirus" to "anti-malware" on console, not on API parameters/keywords

    6. Bugs fixed

    • Get Devices API v3: Got HTTP 200 in response instead of 413 when the page parameter exceeds a page limit

    • Device Action API v3: Got HTTP 400 when group id doesn't exist on an account with assign to group action

    • Device Status Change API v3: Got HTTP 400 instead of 406 if the limit parameter is greater than 50