If you have deployed a Defender to scan an Artifactory registry, there are several caveats to look out for.

This most likely means that you have a self-signed certificate that the underlying docker daemon on the defender host does not trust. This can also happen if you have set up Artifactory as an insecure registry.

If you go to the host that the Prisma Cloud Defender is running on and try to pull your Artifactory images, you should receive the same error

You will need to add your trusted self-signed cert to the docker daemon. Specify the URL of the insecure registry on the machine where the registry scanning Defender runs, then restart the Docker service. For more information, see the Docker documentation.