AI API key not managed

warningai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

Severity: warning
Selects: every node of kind ai-service
Components in scope: 126

What it checks

It looks at every node of kind ai-service, and fires when:

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Message

AI service '{{node.id}}' is called with an API key, the key is not held in a key-management component, and the design has none.

{{node.id}} style paths are filled in from the node, the edge or the design the finding is about.

Applies to · 126 components

AI service ai-service

Tripped by · 2

Reference designs whose broken twin names this rule in its header. The gate reads the same header, and fails when a rule no design trips.

linear-syncreference llm-gatewayreference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# An AI vendor reached with an API key, called from the team's own servers, workers or clients,
3# with the key not declared as held in a key-management component and no key-management node in
4# the design. The key then lives in configuration or code, unrotated, and one leak bills the account.
5# Tripped by: designs/reference/llm-gateway/design.broken.yaml and designs/reference/linear-sync/design.broken.yaml
6schemaVersion: "1"
7type: "rule"
8id: "ai-api-key-unmanaged"
9severity: "warning"
10select:
11  node:
12    kind: "ai-service"
13when:
14  all:
15    - prop: "auth"
16      equals: "api-key"
17    - prop: "keyStore"
18      equals: false
19    - hasEdge:
20        direction: "in"
21        peerKind: ["app-server", "worker", "client"]
22    - not:
23        hasNode:
24          kind: "key-management"
25message: "AI service '{{node.id}}' is called with an API key, the key is not held in a key-management component, and the design has none."

The same page as markdown, for an agent: /catalogue/rules/ai-api-key-unmanaged.md