Early rate$2,400 of senior audit time for $500. Early members keep the rate as it climbs.$2,400 of senior audit time for $500See how →
Checklists/AI Security/Long-Lived Agent Security

Long-Lived Agent Security Checklist

22 audit checks for persistent autonomous agents covering memory poisoning, temporal privilege re-entry, identity drift, delegated authority, scheduler abuse, and forensic durability.

🚨 Long-Lived Agent Threat Landscape

Persistent agents accumulate state, authority, and context over time. The core risk is not one bad prompt, but a tainted write that survives until a later privileged read.

• Temporal attack chains a low-trust write today can trigger a high-trust action days later

• Persistent memory summaries, notes, queues, caches, and files all become attack surfaces

• Standing authority scheduled jobs and recurring approvals create latent execution power

• Identity drift agents can slowly inherit broader roles, repos, channels, or operational assumptions

• Delegated autonomy subagents and background workers amplify blast radius if authority is copied transitively

• Forensics decay compressed context and mutable logs often erase the sequence needed for incident reconstruction

📄
Need the long-lived agent checklist as PDF? Message Carlos on Telegram.DM me on Telegram →
Showing 22 of 22 vulnerabilities
#1

Persistent State Inventory

Critical
▼

All durable accumulators are enumerated, including memory stores, summaries, notes, task queues, caches, files, transcripts, and external tickets

#2

Write-Retrieve-Execute Mapping

Critical
▼

The audit maps whether a low-trust write can later be retrieved in a higher-trust decision context

#3

Trust Labels Survive Persistence

Critical
▼

Trust level and source provenance persist with stored memories, summaries, and artifacts

#4

Memory Poisoning Resistance

Critical
▼

External inputs cannot silently create durable instructions, behavioral rules, or operator preferences

#5

Summary Integrity Checks

High
▼

Compressed summaries and rollover context are reviewable, attributable, and protected against instruction laundering

#6

Shared State Isolation

High
▼

Shared files, vector stores, task boards, and cross-agent scratchpads are isolated by tenant, project, and role

#7

Forgetting and Rollback Controls

Medium
▼

Operators can delete, revert, or quarantine poisoned state with clear scope and verification

#8

Runtime Identity Pinning

Critical
▼

The agent remains pinned to the correct user, workspace, repository, account, and delivery channel across long runs

#9

Standing Approval Review

Critical
▼

Persistent approvals are minimized, scoped, and visible to the operator

#10

Credential Freshness Boundaries

High
▼

Scheduled or resumed runs do not inherit stale tokens, wallets, or cloud credentials beyond their intended window

#11

Destination Identity Validation

High
▼

Messages, commits, PRs, ticket updates, and webhook deliveries validate the intended destination at execution time

#12

Delegated Authority Attenuation

Critical
▼

Child agents, workers, and helper automations receive less authority than the parent by default

#13

Scheduled Trigger Governance

High
▼

Cron jobs, webhook triggers, and event-driven runs are inventoried, reviewed, and bounded by task-specific policy

#14

Re-Authorization on Synthesis

High
▼

Combined outputs from multiple workers require fresh validation before high-impact execution

#15

Queue and Backlog Poisoning Controls

High
▼

Task queues and pending work items cannot be poisoned into privileged execution paths

#16

High-Risk Tool Rechecks

Critical
▼

Shell, wallet, deployment, publishing, and external write actions re-validate context and approval immediately before execution

#17

Economic Abuse Controls

Medium
▼

Runaway loops, repeated retries, and expensive model routing are detected and capped

#18

Network Egress Boundaries

High
▼

Long-lived agents cannot freely exfiltrate accumulated memory, logs, or secrets over normal outbound channels

#19

Tamper-Evident Action History

High
▼

Commands, approvals, memory writes, delegation events, and external actions are durably logged

#20

Compression and Retention Policy

Medium
▼

The system retains enough pre-compression evidence to support incident review

#21

Containment Controls

Medium
▼

Operators can pause schedules, revoke delegated workers, quarantine state, and rotate credentials quickly

#22

Owner-Harm Scenarios Tested

Critical
▼

The audit tests whether the agent can betray its operator through covert memory exfiltration, destructive action, or unauthorized external execution

Need a long-lived agent security audit?

Zealynx audits persistent agent systems with a temporal lens: what gets written, what survives, what is later trusted, and what authority that trust can unlock.