What is a Critical Issue on MetaAccess policy?

MetaAccess reports many different types of information about a device. Some of these items can be considered ISSUES if a MetaAccess administrator decides it is an unwanted condition.

E.G. If an organization's security regulations require all hard drives to be encrypted, the MetaAccess administrator would set Is Issue? to true for 'No encryption application is installed' by checking on that setting.

In some cases, an admin may want to consider a particular issue as more severe than another. To do so, the admin would also set Is Critical Issue? to true for that particular issue by checking on Critical checkbox.

An example policy:

images/download/attachments/336363/image2018-9-5_11-35-26.png

To see a list of all devices with critical issues, apply the Critical filter in the device list view on the MetaAccess console.

images/download/attachments/336363/image2017-10-25_15-18-28.png

Why?

By declaring some issues as critical and others are regular severity, differing levels of access can be allowed via integration with a secure access solution or MetaAccess API. For example, you may wish to use regular issues to trigger a warning or placement in a remediation VLAN, whereas a critical issue may result in full network disconnect.



This article was last updated on 2019-09-05
EA