Skip to content

Playbook · for Engineering, Security

AI supply chain: models, packages and tools

Models, LLM frameworks and MCP servers are dependencies. Inventory them, pin them, scan them and keep their keys out of code.

By Mr.DLast reviewed 2 min read

What the AI supply chain is

Most of an AI feature is code and data you did not write: the model, its weights and tokenizer, an LLM framework, vector database clients, MCP servers, datasets, and the API keys that connect them. OWASP lists supply chain risks as LLM03. In practice, the most common entry points we see are vulnerable agent frameworks and MCP servers, and leaked model API keys.

1. Know what you run

Build an inventory, the same way you would for any dependency:

  • models and their sources (vendor API, hosted, self-hosted weights);
  • LLM frameworks, inference servers and their versions;
  • MCP servers and plugins used by agents and coding assistants;
  • datasets used for fine-tuning or retrieval, with their origin and licence;
  • every API key and who owns it.

A software bill of materials (SBOM) from your build covers the code part. The EU Cyber Resilience Act will expect one for products sold in the EU.

2. Pin and verify

  • Pin exact versions of LLM frameworks and MCP servers, and update deliberately.
  • Download model weights only from trusted publishers, verify checksums or signatures, and prefer safe formats such as safetensors over formats that can execute code when loaded.
  • Mirror critical packages and models in your own registry, so a deleted or hijacked upstream does not change what you deploy.

3. Scan continuously

  • Scan dependencies for known vulnerabilities in every pull request, and again on a schedule, because new CVEs land on old versions.
  • Watch advisories for the frameworks you use. Agent frameworks, inference servers and MCP servers have had a steady stream of critical flaws in 2026.
  • Scan container images for the inference and agent runtimes too.

4. Keep keys out of code

Leaked model keys are resold for LLMjacking: attackers run inference on your account and you get the bill.

  • Store keys in a secrets manager and inject them at run time.
  • Scan commits and history for secrets in every pull request, and add a pre-commit hook.
  • Rotate keys automatically, and immediately when one was ever committed, even briefly.
  • Set spend limits and alerts on every model provider account.

5. Check your AI vendors

For each AI provider, record where data is processed, how long it is retained, whether it is used for training, and how the vendor will tell you about an incident. AI platform breaches in 2026 exposed customer datasets and secrets, so plan how you would rotate everything a vendor held.

6. Isolate what you cannot fully trust

Run third-party models and MCP servers with network isolation and minimal permissions, so a compromised component cannot reach the rest of your environment.

What WardBee checks

With code scanning turned on for a GitHub or GitLab repository, WardBee finds secrets in code and recent history, vulnerable dependencies and insecure infrastructure code. On AWS it checks for secrets in Lambda and CodeBuild environment variables and Secrets Manager rotation. Results map to ISO 27001, SOC 2 and the EU CRA.

What WardBee checks for this playbook

  • Lambda function environment variables do not contain secretsawslambda_function_no_secrets_in_variables
  • CodeBuild project has no sensitive credentials in plaintext environment variablescodebuild_project_no_secrets_in_variables
  • Secrets Manager secret has rotation enabledsecretsmanager_automatic_rotation_enabled

Runs on each AWS sync while a framework it maps to, such as ISO 27001, is enabled. Run it on your account

Related standards: OWASP Top 10 for LLM Applications · EU Cyber Resilience Act · ISO/IEC 27001

More playbooks

Check this playbook against your own AWS account.

WardBee connects read-only to AWS and, if you choose, to GitHub or GitLab, and shows which of these controls pass, fail or still need a person, as ISO 27001 and SOC 2 evidence.

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.