Niches · Secrets & credential vaults

See which agent read which secret and when

One company's docs show a full fit.

1companies, full fit
11companies, fit with a limit
12companies carry the tag
9share of the category's work
3first-hand accounts

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. No docs we read state these figures, so they don't count against a listing here.

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 1

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

ListingWhy
AWS Secrets Manager A
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. source

Does the job, with a limit 11

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.

ListingWhy
1Password service accounts, SDKs and Environments MCP BB
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. source
Akeyless (SecretlessAI and MCP server) BB
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. source
Azure Key Vault BB
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. source
Bitwarden Secrets Manager C
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. source
Doppler BB
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. source
Google Cloud Secret Manager BB
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. source
HashiCorp Vault + Vault MCP Server C
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. source
Infisical AA
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. source
Keeper Secrets Manager B
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. source
Phase B
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. source
Pulumi ESC BB
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. source

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

The same as data: /api/v1/use-cases/secrets.audit-reads.json, or the MCP tool get_use_case with id secrets.audit-reads. Other jobs in this category: /api/v1/niches?category=secrets.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.