Corvus
RED × BLUE

Threat Playbook

Adversary vectors paired with the defensive controls that close them. Read top-to-bottom — engagements are sorted by severity. Baseline controls below apply across the surface.

3
Severe
7
Moderate
0
Low
3
Baseline

Severe · Act Now

3 engagements

Moderate · Plan Mitigation

7 engagements

Baseline · Surface-Wide

3 controls
B-11 Baseline

Operationalize a monthly vulnerability management cadence with patch SLAs

Baseline control aligned to the recurring CVE pattern observed against PAN-OS (2019-17440, 2024-3400, 2025-0108/0111, 2026-0257/0300): operationalize a monthly vulnerability management cadence with explicit patch SLAs (critical=72h, high=7d, moderate=30d). Subscribe to PANW security advisories, CISA KEV, and Unit 42 threat bulletins as primary feeds. Maintain an asset inventory of all PANW perimeter devices including patch level.

B-12 Baseline

Pre-commit and pre-publish secret scanning across all PANW dev tooling

Baseline control: pre-commit and pre-publish secret scanning (truffleHog, gitleaks, or equivalent) across all PANW-published GitHub orgs (PaloAltoNetworks/, cdot65/, etc.), npm publishes, and CI/CD pipelines. Audit credential storage practices for the dev-rel and SDK engineering orgs. Rotate any credentials matching observed patterns.

B-13 Baseline

Zero-trust internal segmentation between Strata, Prisma, Cortex, and new Idira/AIRS

Baseline control: apply zero-trust internal segmentation between the four platform pillars (Strata, Prisma, Cortex) and the new identity (Idira) and AI runtime (AIRS) extensions. Deny-by-default across boundaries; explicit allowlisting for integration paths required by the platformization architecture. Continuous validation of segmentation policy via internal red-team exercises. Aligned with PANW's own Zero Trust commercial messaging.