# Rapid7 ASM remediation of vulnerabilities

**URL:** <https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368>\
**Category:** Surface Command\
**Created:** [July 23, 2025, 12:28pm UTC](https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368 "2025-07-23T12:28:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sul\_fazal](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/s/df788c/32.png) [@sul\_fazal](https://discuss.rapid7.com/u/sul_fazal)\
**Post date:** [July 23, 2025, 12:28pm UTC](https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368/1 "2025-07-23T12:28:52Z")

</div>

The vulnerabilities identified by CAASM (Cyber Asset Attack Surface Management) and EASM (External Attack Surface Management) are clearly visible on platforms like Command Surface. However, the question remains—what about remediation? Is it a manual process, or is there some level of automation involved?

For example, InsightIDR is integrated via a connector, which raises the question: can we take direct action from within the platform? In my environment, Microsoft Defender for Endpoint (MDE) is also deployed, which incorporates XDR capabilities. This could potentially allow for automated or semi-automated remediation workflows.

To further support this point, I’d like to reference Cortex Xpanse, which offers similar capabilities for managing and responding to vulnerabilities in external assets. It provides actionable insights and integrations that enable automated remediation, which could serve as a model for how CAASM and EASM platforms might evolve or integrate with existing XDR solutions.

---

<div class="post-metadata">

**Author:** ![Eric-Wilson](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/eric-wilson/32/2531_2.png) [@Eric-Wilson](https://discuss.rapid7.com/u/Eric-Wilson)\
**Post date:** [July 23, 2025, 1:08pm UTC](https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368/2 "2025-07-23T13:08:40Z")

</div>

Automation throughout the platform is enabled with our SOAR tool InsightConnect. With almost 300 integrations and the ability to connect to any solution with an API, the possibilities are endless for remediation given you can build the workflow. Today we have a few templates that revolve around Remediation Hub as well as Surface Command/InsightVM that can be found at the following link: [Rapid7 Extensions](https://extensions.rapid7.com/extension?product=ICON&sort=created&types=workflow)

---

<div class="post-metadata">

**Author:** ![sul\_fazal](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/s/df788c/32.png) [@sul\_fazal](https://discuss.rapid7.com/u/sul_fazal)\
**Post date:** [July 24, 2025, 12:01pm UTC](https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368/3 "2025-07-24T12:01:12Z")

</div>

Dear Eric,

Based on my understanding, external scanning is conducted using OSINT techniques, while internal vulnerabilities are identified through connectors integrated with various event sources.

When it comes to taking remediation actions, it appears that an additional solution such as a SOAR platform is required to automate and orchestrate the response. Is that correct?

I’d appreciate your confirmation or any additional insights you might have.

---

<div class="post-metadata">

**Author:** ![Eric-Wilson](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/eric-wilson/32/2531_2.png) [@Eric-Wilson](https://discuss.rapid7.com/u/Eric-Wilson)\
**Post date:** [July 28, 2025, 1:15pm UTC](https://discuss.rapid7.com/t/rapid7-asm-remediation-of-vulnerabilities/53368/4 "2025-07-28T13:15:41Z")

</div>

That is correct. Rapid7 utilizes our own SOAR platform, InsightConnect, to perform automation actions, like remediations/response, throughout the other solutions we offer.
