Run different versions of Twistlock defender

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Run different versions of Twistlock defender

L1 Bithead



We are planning to upgrade our Twistlock console from 22.12.415 to 30.03.122

We have 2 environments which we would like to stagger the twistlock defender upgrade.

Is it possible to have 2 different versions of twistlock defender connecting to the new console version 30.03.122?





L1 Bithead

Yes, you are okay to upgrade from 22.12.415 to 30.03.122 if you make a console backup first.


If you run into trouble with the upgrade, deploy a 22.12.415 console and restore a backup. 



The general recommendation is that the defender version is within N-2 of the console version. In your example, the major version is Maxwell (30.**.***) so N-2 support would look like this:


N       == 30.00.*(Maxwell)

N-1    == 22.12.* 

N-2    == 22.06.* 

N-3+  == EOL



If the defender is outside of N-2 then the defender would not be able to communicate with the console until it is upgraded. 





For other situations here, is the console upgrade path. 

20.09.* -> 20.12.* -> 21.04.* -> 21.08.* -> 22.01.* -> 22.06.* -> 22.12.585 > Maxwell (30.0*)


If you are running a Prisma Cloud console version 22.06 or earlier, you must first upgrade the console to 22.12.585 and then to 22.12.694.








  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!