Vulnerability Management - Rapid7 InsightVM typical architecture

I was bored by repeatedly using low end applications, so today, I thought to use a very sophisticated and complex application .. MS Paint 😁 .

So, a typical Rapid7 InsightVM high level architecture looks like as depicted in the attached image.

1. InsightVM agents reports to Rapid7 platform.
2. Scan engines reports to security console.
3. Scan engine communication methods (https://docs.rapid7.com/insightvm/scan-engine-communication-methods/)
4. InsightVM agent requirements - Network traffic and connectivity (https://docs.rapid7.com/insight-agent/network-traffic-and-connectivity-requirements/)
5. Security console system requirements (https://docs.rapid7.com/insightvm/system-requirements/)
6. Security console is always in sync with Rapid7 platform as it has to upload data collected by scan engines to the platform and download agent data from the platform.
7. Rapid7 platform endpoints can be more specific depending on the data storage region for a particular organization.
8. Agents receives product and content updates from *https://endpoint.ingress.rapid7.com/. Scan engines and security console receives product and content updates from updates.rapid7.com.


Happy Learning !!
hashtag#VulnerabilityManagement hashtag#CyberSecurity hashtag#Rapid7