Introduction

After Field Effect MDR scans your environment, it will generate a vulnerable software ARO for every piece of vulnerable software discovered, and list all of the endpoint devices this with that vulnerable software (at the time of the scan). You can find the list of affected endpoints within the ARO's description.

Additionally, this ARO type has a supplemental data section you can take advantage of, if the feature is enabled. Once enabled, it allows you to export a list of the affected endpoints. This is helpful when dealing with large numbers of endpoints.

When resolving this type of ARO, Field Effect MDR will scan your environment again, and if any endpoint devices still have an outdated version of Chrome, a new ARO will be generated listing any affected, or missed, endpoints.

"Refreshing" this type of ARO 

This type of ARO is also "refreshed" on a monthly basis, meaning that every month, Field Effect MDR will scan for vulnerable software, and automatically close any unresolved vulnerable software AROs that have newly affected endpoints and open a new ARO for that vulnerable software, that includes all of the endpoints with vulnerable software (at the time of the scan). You should always refer to the most recent ARO for a vulnerable piece of software to see the most accurate listing of vulnerable software.

If you are working in a large environment with a large number of endpoints, you can trigger a "refresh" by resolving a vulnerable software ARO. Once the scan is complete (up to several hours), a new ARO will be generate with an up-to-date list of affected endpoints.  

Postponing the issue into the next month

If you know you will not be able to address a vulnerable software issue within a given month and want to pause the scan until next month, you can Dismiss the ARO. This will stop Field Effect MDR form scanning your environment until the next monthly scan.      

Suppressing this ARO for Data Tables  

If you prefer to work exclusively with supplemental data tables to deal with software management, and not receive any AROs for vulnerable software, See the Supplemental Data Page - Overview for more on how AROs can be suppressed.