Mend is an automated application security and remediation platform. It can be used to drive insights into static & software composition analysis. Both Mend SAST and SCA products are supported.
In order to connect Cortex to your Mend instance, you’ll need to create an API token, and add it under Settings → Mend SAST. Additionally, you'll need your organization name, which can be found in the SAST interface under Administration → Organizations.
In order to connect Cortex to your Mend instance, you’ll need the Organization API Key which can be found in the SCA interface under the Integrate tab. Once located, add it under Settings → Mend SCA.
If you do not see the Settings page you're looking for in the sidebar, you likely don't have the proper permissions and need to contact your admin.
We route our requests through a static IP address. Reach out to support at email@example.com to receive details about our static IP. If you're unable to directly whitelist our static IP, you can route requests through a secondary proxy in your network that has this IP whitelisted, and have that proxy route traffic to your Mend instance.
If you’re unable to expose your Mend instance to be reachable by Cortex, you can set up a Custom Integration Webhook.
By default, Cortex will use your associated Git repository (e.g.
repo-name) as the "best guess" for the Mend application name for SAST and Mend project name for SCA.
If your repository names don’t cleanly match the Mend SAST application names or Mend SCA project names, you can override this in the Cortex Service Descriptor.
If you need to override the automatic discovery, you can define the following block in your Cortex Catalog Descriptor.
The application IDs can be found in the Mend SAST web interface. The project IDs can be found in the Mend SCA web interface.