If curl returns an HTTP response status code of 200, you have connectivity to Console.
If you customized the setup when you installed Console, you might need to specify a different port.
Log into Console.
Manage > Defenders > Deploy
In the first drop-down menu (1), select the way Defender connects to Console.
A list of IP addresses and hostnames are pre-populated in the drop-down list.
If none of the items are valid, go to
Manage > Defenders > Names
, and add a new Subject Alternative Name (SAN) to Console’s certificate.
After adding a SAN, your IP address or hostname will be available in the drop-down list.
Selecting an IP address in a evaluation setup is acceptable, but using a DNS name is more resilient.
If you select Console’s IP address, and Console’s IP address changes, your Defenders will no longer be able to communicate with Console.
In the second drop-down list (2), select the Defender type.
Both Linux and Windows platforms are supported.
In the final field (4), copy the install command, which is generated according to the options you selected.
On the host where you want to install Defender, paste the command into a shell window, and run it.
Verify the install
Verify that Defender is installed and connected to Console.
Defender can be deployed and run with full functionality when dockerd is configured with SELinux enabled (--selinux-enabled=true).
All features will work normally and without any additional configuration steps required.
Prisma Cloud automatically detects the SELinux configuration on a per-host basis and self-configures itself as needed.
No action is needed from the user.
In Console, go to
Manage > Defenders > Manage
Your new Defender should be listed in the table, and the status box should be green and checked.