How to identify integrations that are running outdated versions of Python

[vaskenh]

As part of the routine management of your SecOps platform, you should ensure that any configured integrations that are running an outdated version of Python get updated.  In this post, I'll show you how to identify whether these integrations are present in your SecOps platform, and how to go about upgrading them.

First, navigate to the Marketplace.  The first clue that you are running an integration with an outdated version of Python is that you'll see a banner similar to the one below showing up toward the top of the Marketplace.

From this banner, we can see that there are some affected integrations, and that there is an associated documentation link which I've included here for completeness.  Our goal is to identify which of our integrations are affected by this issue, so let's now navigate to Integrations from within the Marketplace and use the Status: Installed filter to only show installed integrations.

For each installed integration that is running an outdated version of Python, you'll see the below red triangle icon showing up next to the integration.  This means we need to follow the referenced upgrade playbook for this integration.

Once you have identified the subset of installed integrations that are running an outdated version of Python, you can proceed to follow the upgrade procedure playbook referenced as part of the status message, and linked above.