{
  "video": {
    "id": "Bz1HFxQA1o8",
    "title": "Shipping AI Into 5 Major Banks Without a 12-Month Compliance Wait — Al Chen, Cisco",
    "duration": 1062,
    "upload_date": null,
    "channel": "AI Engineer",
    "source": "AI Engineer",
    "event_format": ""
  },
  "analysis": {
    "video_id": "Bz1HFxQA1o8",
    "title": "Shipping AI Into 5 Major Banks Without a 12-Month Compliance Wait — Al Chen, Cisco",
    "one_liner": "To cut bank AI deployments from a year to a couple of weeks, show the evidence behind every compliance claim: prove a CVE exploit is actually gone, prove the restored data is correct, and prove your LLM judges aren't un-redacting PII. Saying you bumped a version or ran a backup isn't enough.",
    "summary": "Al Chen compares bank compliance and risk teams to his 10th-grade math teacher Mr. Huff, who gave most of the credit for the proof, not the answer. He argues that 'showing your work' is the real lever on compliance velocity when deploying production, customer-facing AI into air-gapped banks. He covers three pillars: the build pipeline and CVE remediation, disaster recovery for ClickHouse-backed observability, and leakage of sensitive data through LLM-as-judge reasoning. He ends by saying the factors that push timelines out are mostly human and organisational, not technical.",
    "key_points": [
      "Standard SaaS AI doesn't work at a bank because outbound egress to the internet can leak sensitive information. On-prem deployment into air-gapped banks means a more complicated flow: how images are pulled into the bank's cluster, data resiliency if a region fails mid-request, and keeping sensitive data from leaking to internal employees or outside the VPC.",
      "CVE remediation is a problem across many banks at once. The banks run different image versions with different CVEs, use different scanners, and set their own severity and remediation-SLA policies. Some want a newer package version (e.g. 3.8) while others want an older one with fewer CVEs. Transitive open-source dependencies carry CVEs the team cannot fix, so they read upstream release notes to explain to bank security teams why.",
      "The team built an automation (transcribed as 'a scale') that does the CVE research and reporting. It outputs a table telling engineering what to fix and giving bank security teams explanations for what can't be fixed.",
      "Scanners like Sysdig, Wiz and Prisma only check whether a package was bumped to a given version. They say nothing about whether the exploit is still reachable in the application code.",
      "To get that evidence they use a Harbor task: instructions, an environment containing the app's Docker images, and tests. An agent is told that version 2.6.2 supposedly fixes the CVE, writes an exploit against the older version, then writes a test for whether the new version is still exploitable. Many trials run in parallel in Docker, Modal or Daytona sandboxes.",
      "ClickHouse, the main database behind most AI observability tools, has no managed cross-region failover, unlike Redis or Postgres. Chen's DR pattern: a primary-region ClickHouse, a job that backs up to a bucket, and a job that restores to a DR region with replica pods, built on the open-source clickhouse-backup maintained by Altinity. A 'backup succeeded' status says nothing about whether the data is correct now, so he also checks row counts across tables and whether replicas have converged.",
      "Backup and restore design is also a data residency decision. A bucket doesn't care which region it's in, but residency law cares where each record lives. His fix: replicate only IDs and trace metadata across regions, and keep core trace data in one region.",
      "PII/MNPI can be redacted at the SDK, gateway or middleware level and the UI still looks clean, but an LLM judge's reasoning can un-redact it. One innocent-looking prompt line asking for an explanation a human reviewer can verify can be enough. His fix: always persist the score, and persist the reasoning only if a check finds no sensitive data in it. Optionally, a second judge runs on redacted input so its reasoning is safe to show."
    ],
    "takeaways": [
      "Prove that a CVE exploit is actually gone, for example with agent-written exploits and tests in parallel Harbor sandboxes. A version bump reported by a scanner is not proof.",
      "Check data correctness after DR jobs (row counts, replica convergence), not just backup/restore job status. Decide data residency deliberately, e.g. replicate only IDs and metadata across regions.",
      "Read your LLM-as-judge system prompts and traces for PII/MNPI leaking through the reasoning. Persist scores, gate or suppress the reasoning, or pay for a second judge call on redacted input.",
      "Before giving a bank a timeline, check how images are approved and pulled into its registry, whether GPUs are sourced, and whether there are formal security reviews or a custom LLM gateway or RBAC config. These organisational factors push timelines out by months."
    ],
    "topics": [
      "compliance",
      "financial services",
      "on-prem deployment",
      "cve remediation",
      "disaster recovery",
      "data residency",
      "llm-as-judge",
      "pii redaction"
    ],
    "tools": [
      "Cisco",
      "NVD",
      "CISA",
      "MITRE",
      "Sysdig",
      "Wiz",
      "Prisma",
      "Harbor",
      "Docker",
      "Modal",
      "Daytona",
      "Redis",
      "Postgres",
      "ClickHouse",
      "clickhouse-backup",
      "Altinity"
    ],
    "quotes": [
      {
        "text": "it's not enough just to say we bumped the package version up to a specific number.",
        "at": "06:46",
        "url": "https://www.youtube.com/watch?v=Bz1HFxQA1o8&t=406s"
      },
      {
        "text": "When you're replicating to a bucket, the bucket doesn't care if it's in Oregon or Virginia.",
        "at": "09:33",
        "url": "https://www.youtube.com/watch?v=Bz1HFxQA1o8&t=573s"
      },
      {
        "text": "having zero leakage and data sovereignty is not free.",
        "at": "12:52",
        "url": "https://www.youtube.com/watch?v=Bz1HFxQA1o8&t=772s"
      },
      {
        "text": "showing your work. That is the real lever that you have on compliance velocity when working with a bank.",
        "at": "14:40",
        "url": "https://www.youtube.com/watch?v=Bz1HFxQA1o8&t=880s"
      }
    ],
    "words": 3167
  },
  "summary_url": "/#Bz1HFxQA1o8",
  "transcript": {
    "html": "/transcripts/Bz1HFxQA1o8.html",
    "txt": "/transcripts/Bz1HFxQA1o8.txt",
    "vtt": "/transcripts/Bz1HFxQA1o8.vtt"
  }
}