You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/pipelines/audit_log.md
+139Lines changed: 139 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -105,3 +105,142 @@ USER_UPDATED
105
105
```
106
106
107
107
You can also set up [Amazon EventBridge](/docs/integrations/amazon-eventbridge) to stream Audit Log events.
108
+
109
+
110
+
## Audit Logs for Secrets
111
+
112
+
>📘 Audit logs for secrets do not contain the value or sensitive information the secret.
113
+
114
+
115
+
Audit logs record information of transactions in which secrets are accessed or modified. The following events will be logged:
116
+
*`SECRET_CREATED` This triggers an audit log when a user of an organization that initiated the creation of a secret. Secrets can only be created by a User. Below are the fields captured in the audit log for this event.
*`SECRET_DELETED` This triggers an audit log when a secret is deleted by a user of an organization. This is only for when a secret is destroyed, and there is no handling for events such as "revoked" or "expiry". Below are the fields captured in the audit log for this event.
*`SECRET_READ` This triggers an audit event when an actor accesses or reads the value of a secret. Secrets can be read by an agent running a compute job, or read by a user belonging to an organization. Below are the fields captured in the audit log for this event.
*`SECRET_QUERIED` This triggers an audit event when a user belonging to an organization or system identity (such as an agent) when a query is performed to find a secret (or secrets). This event will still trigger if a secret is searched for but does not exist or is not found. Below are the fields captured in the audit log for this event.
*`SECRET_UPDATED` This triggers an audit event when the value or properties of a secret is updated by a user belonging to an organization. As secrets can have many versions, audit logs keeps track of the version identifiers and updates. Below are the fields captured in the audit log for this event.
0 commit comments