{"resourceId":"prisma-airs-november-2026-k8s-ip-tag-harvesting-fpfn-auto-remediation","versions":[{"version":"external-5546eb8dbd83ad03de6e16544b9799075ff971b6d8b9f311e73b61ea4a5356a3","resource":{"id":"prisma-airs-november-2026-k8s-ip-tag-harvesting-fpfn-auto-remediation","title":"Prisma AIRS November 2026 notes: public Kubernetes IP-tag harvesting for runtime firewalls and FP/FN reporting with auto-remediation on API Intercept","organization":"Palo Alto Networks","sector":"AI runtime security / Kubernetes and API guardrails","geography":"Multi-cloud (Amazon EKS, Azure AKS, Google GKE) and API Intercept customers","publishedAt":"Prisma AIRS documentation, New Features November 2026 (release date November 2026)","publicationDate":"2026-11-01","eventDate":null,"sourceName":"Palo Alto Networks TechDocs","sourceLabel":"New Features - Prisma AIRS - November 2026","sourceUrl":"https://docs.paloaltonetworks.com/prisma-airs/new-features/by-date/prisma-airs/november-2026","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","infrastructure","data-security"],"finding":"Prisma AIRS November 2026 release notes describe two capabilities. First, AI Runtime Security can harvest IP-tag mappings from public and hybrid Kubernetes clusters (EKS, AKS, GKE) into Dynamic Address Groups via Strata Cloud Manager, so Prisma AIRS AI Runtime Firewalls (VM-Series) can enforce policy on ephemeral pod and inference-endpoint labels instead of static CIDRs. Administrators onboard cloud accounts with read permissions, configure an IP-Tag Collector profile and assign the firewall as a redistribution agent. Second, AI Runtime Security API Intercept gains false-positive and false-negative reporting with auto-remediation: operators dispute verdicts from scan logs and AI violation dashboards, triggering exception patterns and local rule adjustments, with reported verdicts also fed into Palo Alto's detection pipeline for model retraining. Documentation only; no measured false-positive reductions or SLED deployments.","sledRelevance":"Universities and state agencies running containerized AI inference on public cloud Kubernetes, and those already using API Intercept guardrails, get concrete operational features. Interpretation: tag-based policy helps when research workloads churn IPs; FP/FN auto-remediation can cut alert fatigue but needs change control so exception patterns do not quietly weaken protections for FERPA or HIPAA prompts.","evidence":"Opened and read the full November 2026 new-features page for both feature sections, including deployment steps and auto-remediation description.","architectureImplications":"Needs Strata Cloud Manager cloud onboarding, IP-Tag Collector profiles and VM-Series redistribution; API Intercept console becomes a feedback loop into local exceptions and vendor model retraining.","governanceImplications":"Interpretation: FP/FN disputes and auto-created exceptions should require dual control or periodic audit in regulated environments.","securityPrivacyImplications":"Cloud read permissions for cluster metadata expand the control-plane attack surface; exception patterns can reopen previously blocked prompt classes.","caveats":"Vendor documentation; month-level dating only; no quantitative FP/FN results; auto-remediation effects on detection quality not independently tested.","streamIds":["palo-alto-networks"],"roles":{"sales":"Sales framing: these November notes are incremental product maturity for existing Prisma AIRS runtime customers, not a net-new platform story. They matter when a prospect already runs Kubernetes AI workloads or complains about false positives on API Intercept. A bounded engagement could be enabling IP-tag harvesting in a non-prod cluster and defining an FP dispute workflow. Do not claim measured alert reductions the docs do not provide.","engineering":"Engineering framing: IP-tag harvesting depends on cloud account onboarding, collector profiles and firewall redistribution into Dynamic Address Groups; policy should target workload tags, not CIDRs. For API Intercept, engineers must decide which roles can file FP/FN disputes and whether auto-created exception patterns require review before enforcement. A proof of value is spinning a labeled inference pod and showing the firewall DAG update, plus filing a synthetic FP and confirming the exception.","delivery":"Delivery framing: treat November features as configuration and governance work on an existing AIRS estate. Delivery should stage K8s harvesting in non-production, document required cloud IAM read roles, and put FP/FN auto-remediation behind an approval checklist. Proposed acceptance criteria include tag-based allow rules covering a test workload within an agreed time and dual control on exception patterns. Risks include over-broad cloud permissions and silent weakening of guardrails."},"roleDetails":{"sales":{"customerProblem":"Ephemeral Kubernetes AI workloads break static IP policies, and noisy API Intercept verdicts create operational friction.","stakeholders":["Cloud platform lead","AI application owner","Security operations","Compliance officer"],"discoveryQuestions":["Are inference workloads on public EKS, AKS or GKE?","Is AI Runtime Firewall (VM-Series) already deployed?","How are false positives on API Intercept handled today?","Who may authorize exception patterns?"],"valueHypothesis":"Interpretation: tag-based runtime policy plus a controlled FP/FN loop could stabilize guardrails for dynamic AI workloads.","potentialEngagement":"A non-production IP-tag harvesting pilot plus an FP dispute runbook review.","unsupportedClaims":["Measured FP rate reduction","Automatic coverage of private-only clusters without onboarding","Compliance certification from these features alone"]},"engineering":{"fit":"Fits Prisma AIRS runtime customers with public/hybrid Kubernetes AI workloads or API Intercept noise problems.","architectureIntegration":"Strata Cloud Manager collectors feed Dynamic Address Groups on AI Runtime Firewalls; API Intercept console feeds local exceptions and vendor retraining.","prerequisites":["Cloud account onboarding with cluster read permissions","IP-Tag Collector profile and redistribution agent","API Intercept console access"],"constraints":["Public/hybrid cluster focus as documented","Auto-remediation can change local policy quickly","Month-level release dating only"],"security":"Limit cloud read roles; require review of exception patterns that weaken prompt-injection or DLP rules.","proofOfValue":["Observe DAG update when a labeled pod starts","File a synthetic FP and inspect created exception","Confirm policy uses tags rather than static CIDRs"]},"delivery":{"work":"Onboard cloud accounts, configure collectors, author tag-based AI Security Profiles, and stand up FP/FN governance.","dependencies":["Cloud IAM approvals","VM-Series runtime firewall capacity","SecOps change-control process"],"ownership":"Platform networking owns IP-tag pipelines; SecOps owns verdict disputes and exceptions.","skillsAdoption":"Staff need training on Kubernetes labels and AIRS violation dashboards.","governanceCheckpoints":["Cloud read permissions reviewed","Exception-pattern dual control enabled","Monthly audit of FP/FN changes"],"acceptanceCriteria":["Proposed: test workload protected by tag-based rule within agreed window","Proposed: FP dispute creates a reviewed exception, not a silent allow","Proposed: rollback path for auto-remediation documented"],"risks":["Over-privileged cloud collectors","Exception patterns reopening blocked content classes","Tag hygiene failures leaving workloads unprotected"]}},"retrievedAt":"2026-11-06T04:11:32Z","enrichedAt":"2026-11-06T04:16:24Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Security teams need Kubernetes tagging literacy and a workflow for verdict disputes.","procurementImplications":"Confirm AI Runtime Firewall (VM-Series) and API Intercept entitlements separately; features are release-note claims, not new public pricing.","operatingModelImplications":"Platform and SecOps must agree who owns IP-tag pipelines and who approves FP/FN exceptions.","sourceVerification":{"openedUrl":"https://docs.paloaltonetworks.com/prisma-airs/new-features/by-date/prisma-airs/november-2026","referenceExcerpt":"administrators can submit verdict disputes directly from the console to trigger automated remediation workflows","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}