STIGQter: STIG Summary: Palo Alto Networks Prisma Cloud Compute Security Technical Implementation Guide Version: 2 Release: 3 Benchmark Date: 01 Apr 2026:

Prisma Cloud Compute must run within a defined/separate namespace (e.g., Twistlock).

DISA Rule

SV-253547r1137646_rule

Vulnerability Number

V-253547

Group Title

SRG-APP-000431-CTR-001065

Rule Version

CNTR-PC-001380

Severity

CAT II

CCI(s)

• CCI-002530 - Maintain a separate execution domain for each executing system process.

Weight

10

Fix Recommendation

Deploy the Prisma Cloud Compute Console and Defender containers within a distinct namespace.

Check Contents

Inspect the Kubernetes namespace in which Prisma Cloud Compute is deployed:

$ kubectl get pods -n twistlock
NAME READY STATUS RESTARTS AGE
twistlock-console-855744b66b-xs9cm 1/1 Running 0 4d6h
twistlock-defender-ds-99zj7 1/1 Running 0 58d
twistlock-defender-ds-drsh8 1/1 Running 0 58d

Inspect the list of pods.

If a non-Prisma Cloud Compute (does not start with "twistlock") pod is running in the same namespace, this is a finding.

Vulnerability Number

V-253547

Documentable

False

Rule Version

CNTR-PC-001380

Severity Override Guidance

Inspect the Kubernetes namespace in which Prisma Cloud Compute is deployed:

$ kubectl get pods -n twistlock
NAME READY STATUS RESTARTS AGE
twistlock-console-855744b66b-xs9cm 1/1 Running 0 4d6h
twistlock-defender-ds-99zj7 1/1 Running 0 58d
twistlock-defender-ds-drsh8 1/1 Running 0 58d

Inspect the list of pods.

If a non-Prisma Cloud Compute (does not start with "twistlock") pod is running in the same namespace, this is a finding.

Check Content Reference

M

Target Key

5473