Prisma Cloud Compute Edition is a security scanner. It scans containers, hosts, and packages to find vulnerabilities and compliance issues.
The Prisma Cloud Compute Edition check is included in the Datadog Agent package, so you do not need to install anything else on your server.
To configure this check for an Agent running on a host:
-
Edit the
twistlock.d/conf.yaml
file, in theconf.d/
folder at the root of your Agent's configuration directory to start collecting your twistlock performance data. See the sample twistlock.d/conf.yaml for all available configuration options.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
twistlock |
<INIT_CONFIG> |
blank or {} |
<INSTANCE_CONFIG> |
{"url":"http://%%host%%:8083", "username":"<USERNAME>", "password": "<PASSWORD>"} |
If you're using Kubernetes, add the config to replication controller section of twistlock_console.yaml before deploying:
apiVersion: v1
kind: ReplicationController
metadata:
name: twistlock-console
namespace: twistlock
spec:
replicas: 1
selector:
name: twistlock-console
template:
metadata:
annotations:
ad.datadoghq.com/twistlock-console.check_names: '["twistlock"]'
ad.datadoghq.com/twistlock-console.init_configs: "[{}]"
ad.datadoghq.com/twistlock-console.instances: '[{"url":"http://%%host%%:8083", "username":"<USERNAME>", "password": "<PASSWORD>"}]'
ad.datadoghq.com/twistlock-console.logs: '[{"source": "twistlock", "service": "twistlock"}]'
name: twistlock-console
namespace: twistlock
labels:
name: twistlock-console
Available for Agent versions >6.0
Collecting logs is disabled by default in the Datadog Agent. To enable it, see Kubernetes Log Collection.
Parameter | Value |
---|---|
<LOG_CONFIG> |
{"source": "twistlock", "service": "twistlock"} |
-
Collecting logs is disabled by default in the Datadog Agent. Enable it in your DaemonSet configuration:
#(...) env: #(...) - name: DD_LOGS_ENABLED value: "true" - name: DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL value: "true" #(...)
-
Mount the Docker socket to the Datadog Agent. See the Datadog Kubernetes example manifests.
-
Make sure the log section is included in the Pod annotation for the defender, where the container name can be found just below in the pod spec:
ad.datadoghq.com/<container-name>.logs: '[{"source": "twistlock", "service": "twistlock"}]'
-
Collecting logs is disabled by default in the Datadog Agent. Enable it with the environment variable:
DD_LOGS_ENABLED=true
-
Add a label on the defender container:
ad.datadoghq.com/<container-name>.logs: '[{"source": "twistlock", "service": "twistlock"}]'
-
Mount the Docker socket to the Datadog Agent. More information about the required configuration to collect logs with the Datadog Agent available in Docker Log Collection.
Run the Agent's status subcommand and look for twistlock
under the Checks section.
See metadata.csv for a list of metrics provided by this check.
Prisma Cloud Compute Edition sends an event when a new CVE is found.
See service_checks.json for a list of service checks provided by this integration.
Need help? Contact Datadog support.