Overview
When Rapid7 InsightVM or Nexpose customers want to detect vulnerabilities like missing patches and old operating systems in their AWS EC2 instances, one option is to use this scan engine. This listing is for a version of our standard scan engine that has been modified specifically for use in AWS environments. It leverages the Dynamic Discovery feature of InsightVM, which continuously detects when EC2 instances are added or removed from your AWS environment. The engine uses this information to ensure it scans every active EC2 instance and only EC2 instances that belong to you.
Customers can use this scan engine to scan across multiple VPCs, as long as traffic can flow between the scan engine's VPC and the target (e.g. VPC peering). If your VPCs are isolated, you will need to install a separate engine in each VPC you want to scan. This version of the scan engine can only be used to conduct internal scans of AWS infrastructure.
Highlights
- Easily run scans and detect vulnerabilities in your EC2 instances
- Designed specifically for AWS environments. Will only scan assets in your AWS account(s).
Pricing
Additional AWS infrastructure costs
Type | Cost |
|---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
Please see the seller website for refund details.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
The Rapid7 Scan Engine must be paired with an existing InsightVM or Nexpose Console via EC2 User Data. No direct access to the Scan Engine via SSH is allowed. Other than user data, all configuration is controlled via an InsightVM or Nexpose Console.
- Use the manual "Launch with EC2 Console" to launch in the appropriate region.
- Generate a shared secret from from the Scan Engine Administration page of your InsightVM or Nexpose console.
- Provide the following EC2 User Data (available under the advance section in instance details) to the Scan Engine, replacing the bracketed sections with information about your console:
NEXPOSE_CONSOLE_HOST=
NEXPOSE_CONSOLE_SECRET= NEXPOSE_CONSOLE_PORT=40815 - We recommend at least an m5.large (8GB of RAM) and at least 10GB of disk space.
- Launch the instance.
- Once the image boots, it can take 10-15 minutes to pair with the console.
- Check the Engines page in the Console to see if the engine paired successfully. For troubleshooting and more information consult the InsightVM or Nexpose docs at help.rapid7.com
Resources
Support
Vendor support
Rapid7 Customer Support services provide rapid resolution of issues. We include telephone and email support, 24 hour vulnerability service level agreement, 24 hour incident response time, and a reliable testing guarantee. http://www.rapid7.com/support/ ; 866-390-8113; support@rapid7.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Scan Engine is easy to configure but...
The InsightVM scan engine is easy to install and configure with the security console. However, after a few months of regular scans the scan engine EBS volume is completely filled. This wouldn't be a problem if the scan engine allowed ssh access into it so that we can re-size the EBS volume correctly. Instead you have to delete and re-setup the scan engine with a bigger EBS every so often.
There is also no means to delete older logs from the scan engine in an automated fashion which is the main cause of this issue.