Amazon Q’s MCP Flaw Is an Industry Warning: AI Tools Still Lack Workspace Trust Standards

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: quarantine-CVE-2026-12957
  namespace: production
  labels:
    security.isharestuff.com/quarantine: "true"
    cve.mitigation/id: "CVE-2026-12957"
spec:
  podSelector:
    matchLabels:
      app.kubernetes.io/vulnerable-cve: "CVE-2026-12957"
  policyTypes:
    - Ingress
    - Egress
  ingress:
    # Restrict ingress solely to authorized security scanners & bastion pods
    - from:
        - namespaceSelector:
            matchLabels:
              kubernetes.io/metadata.name: soc-monitoring
      ports:
      - port: 443
        protocol: TCP
  egress:
    # Allow DNS only (isolate lateral movement)
    - to:
        - namespaceSelector: {}
          podSelector:
            matchLabels:
              k8s-app: kube-dns
      ports:
        - port: 53
          protocol: UDP

aws ec2 revoke-security-group-ingress --group-id sg-0123456789abcdef0 --protocol tcp --port 443 --cidr 0.0.0.0/0

(http.request.uri.path contains "CVE-2026-12957" or http.request.body.mime contains "exploit" or cf.threat_score gt 20)