{
  "id": "topic:memory-security",
  "_kind": "Topic",
  "_file": "domain/topics/topics-knowledge-patterns.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Memory Security",
    "description": "Memory Security as a cross-cutting topic — protecting agent memory from\ninjection attacks, credential leakage, and unauthorized access. Covers\npath validation (Claude Code rejects traversal, UNC, null-byte, and\ndrive-root paths), privacy filtering (agentmemory strips secrets and\nPII before persistence), scope isolation (memories from one project\nshould not leak to another), and prompt injection via memory (an\nattacker plants instructions in a file that gets ingested as memory,\nhijacking future sessions). Memory security is particularly critical\nfor auto-memory systems where the agent decides what to persist —\na compromised extraction step could persist attacker-controlled content.\n"
  },
  "outgoingEdges": [
    {
      "from": "topic:memory-security",
      "to": "domain:software-engineering",
      "kind": "applies_to"
    },
    {
      "from": "topic:memory-security",
      "to": "specialization:ai-agents-conversational",
      "kind": "applies_to"
    },
    {
      "from": "topic:memory-security",
      "to": "topic:auto-memory",
      "kind": "related_topics"
    },
    {
      "from": "topic:memory-security",
      "to": "topic:memory-scoping",
      "kind": "related_topics"
    },
    {
      "from": "topic:memory-security",
      "to": "topic:knowledge-access-control",
      "kind": "related_topics"
    }
  ],
  "incomingEdges": [
    {
      "from": "domain:knowledge-management",
      "to": "topic:memory-security",
      "kind": "contains"
    },
    {
      "from": "topic:krate-agent-memory-update",
      "to": "topic:memory-security",
      "kind": "applies_to"
    },
    {
      "from": "tool:agentmemory",
      "to": "topic:memory-security",
      "kind": "relates_to_topic",
      "attributes": {}
    }
  ]
}