# See which agent read which secret and when

> See which agent read which secret and when: 1 companies fully do it, 11 with a limit, 12 carry the tag. Every listing in Secrets & credential vaults with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/secrets.audit-reads/
- Markdown: https://www.anchorterminal.com/niches/secrets.audit-reads/index.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/niches/secrets.audit-reads/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/secrets.audit-reads/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 11 | 12 | 9 | 3 |

## What counts as done

Every read is in an exportable log with the identity, secret name, time and source, kept at least 30 days on the plan in use.

Measured, for our own tests: each read is in the log within 5 minutes.

How agents ask for it: which agent used the prod key; show me secret access for last night's run; prove the agent didn't read the payment key

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **AWS Secrets Manager (Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location))**: CloudTrail records GetSecretValue with the caller, and the console keeps 90 days of event history; a trail to S3 keeps more. The page states no delivery delay, so the 5-minute bar is unconfirmed. acc-07 recommends it for precisely this.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **1Password service accounts, SDKs and Environments MCP (AgileBits Inc. (doing business as 1Password))**: The Events API itemusages endpoint logs item views by user or service account for SIEM export, but needs Business, usage reports can take hours to sync, and retention per plan was not stated.
- **Akeyless (SecretlessAI and MCP server) (Akeyless Security Ltd.)**: Audit logs record access_id, get_secret_value actions and item, and can be forwarded to Splunk and others, but the free plan keeps 3 days and has no event forwarding; Enterprise retention was not stated.
- **Azure Key Vault (Microsoft Corporation)**: AuditEvent logs record SecretGet with the caller's identity, but logging is off until a diagnostic setting is created, and logs arrive up to 10 minutes after the operation, past the 5-minute bar.
- **Bitwarden Secrets Manager (Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.))**: Event 2100, Accessed secret, is logged per machine account, exportable as CSV and kept indefinitely, but event logs need Teams or Enterprise and no delivery delay is stated.
- **Doppler (Doppler Technologies, Inc.)**: Secret access logs show each actor with the first and most recent read, not every read, and access history depends on the plan; Developer activity logs keep 3 days.
- **Google Cloud Secret Manager (Google LLC (Google Cloud EMEA Limited and other regional entities by billing address))**: AccessSecretVersion is logged as DATA_READ with the caller, but Data Access audit logs must be enabled first, and the page states no delivery delay.
- **HashiCorp Vault + Vault MCP Server (HashiCorp, Inc. (an IBM company))**: Audit devices record every request and response, and Vault refuses requests it cannot audit, but auditing is disabled on a new cluster and retention is whatever your file, syslog or socket target keeps.
- **Infisical (Infisical, Inc.)**: A get-secret event records the actor, environment, path, key and version and can be streamed out, but Free has no audit logs and Pro keeps 30 days; no delivery delay is stated.
- **Keeper Secrets Manager (Keeper Security, Inc.)**: app_client_access logs that a device read from an application, not which secret, and events go to the Advanced Reporting and Alerts Module with SIEM export, sold separately; retention not stated.
- **Phase (Phi Security Inc.)**: Secret read events name the service account and token, path and version, and Log Streams ship them every 30 seconds, but Log Streams are Enterprise only, and Free keeps audit logs 24 hours.
- **Pulumi ESC (Pulumi Corporation)**: Environment Open and Environment Decrypted events are logged and exportable, but audit logs need Pro or Enterprise, automatic export needs Enterprise, and retention and delay were not stated.

## What stops agents finishing

- audit log off until enabled (Google Data Access logs, Azure diagnostic setting)
- no audit on free plans or kept 1 to 3 days
- reads through a shared token cannot be told apart by agent

## Around it

Before: secrets.scoped-read. After: agent-observability.trace-calls, security-intelligence.siem-export.

## Where this comes from

Weight 9 of 100 in Secrets & credential vaults: 3 of 27 accounts (cloud access logs, credwrap audit, runtime supervision); buyer check 3 asks for it

As data: https://www.anchorterminal.com/api/v1/use-cases/secrets.audit-reads.json, or the MCP tool get_use_case with id secrets.audit-reads. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
