Sign in
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

ME Vulnerability Manager Plus Enterprise (100 Computers and single User)

ZOHO Corporation | 11_1_2239_2

Windows, Windows Server 2019 Base 2022.01.01 - 64-bit Amazon Machine Image (AMI)

Reviews from AWS Marketplace

0 AWS reviews
  • 5 star
  • 4 star
  • 3 star
  • 2 star
  • 1 star

External reviews

1 review
from G2

External reviews are not included in the AWS star rating for the product.

    Steve S.

ManageEngine is revolutionizing vulnerability scanning and management

  • November 30, 2022
  • Review verified by G2

What do you like best about the product?
Most vulnerability scanning solutions follow the Nessus/OpenVas, CVE-centered approach where security personnel must wade through a hip-deep list of detected issues to solve, each one requiring research and many duplications in the mix. ME has turned this on its head by taking the CVE's under the hood and delivering an agent-based settings audit that returns most detected issues in the form of automated fixes that can be approved en masse or individually and once per device. Then they also seamlessly integrate CIS benchmarks and both OS and 3rd party software patching for a complete system hardening and INvulnerability maintenance solution that cuts down on so much extra security work. All this is wrapped up in competitive licensing tied to users rather than devices, so a growing company can afford to achieve mass, cost-effective hardening across their infrastructure, Windows and Linux in my case (I haven't tested Macintosh).

Automated patching in the form of highly-customizable test & approve-after-x-days cycles keep systems current and automated reports show continuous state of compliance. Out of the box, various locations and custom groups allow MSP-level partitions for customized security levels.

Support is excellent and responsive.
What do you dislike about the product?
The only thing I think is missing is an ability to roll back settings. I can understand patches can't necessarily be rolled back easily by 3rd party software, but a record of settings should be kept so when I harden a system I can quickly roll it back if functionality is lost. In one case I hardened a Ubuntu system so completely I couldn't get into it in any way even through root-level recovery.

I've worked around this issue by taking images of systems I'm hardening, and by pre-hardening my deployment templates rather than building fully-functional systems and then hardening. I also have dev/test systems I deploy hardening principles to first in order to minimize any production impact.
What problems is the product solving and how is that benefiting you?
Before ME Vulnerability Manager, our vulnerability scanning was always a scramble to stay on top of, and never seemed to be fully complete. Demonstrating our management was also problematic as reporting on sampled systems required gleaning information out of the mass of detail rather than a clean report showing a system's concise and specific history.

showing 1 - 1