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: mission-control/docs/guide/audit/access-logs.mdx
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ When `full` mode is enabled, the scraper expects each configuration item to pote
96
96
97
97
## Entra ID Audit Logs
98
98
99
-
Entra ID generates sign-in logs and directory audit logs that can be scraped as access logs. There are three approaches depending on your infrastructure and latency requirements:
99
+
Entra ID generates sign-in logs and directory audit logs that Mission Control scrapes as access logs. There are three approaches depending on your infrastructure and latency requirements:
100
100
101
101
||[HTTP + MS Graph](/docs/integrations/azure-ad/audit-logs/http-scraper)|[Logs Scraper](/docs/integrations/azure-ad/audit-logs/logs-scraper)|[Event Hub](/docs/integrations/azure-ad/audit-logs/event-hub)|
102
102
|---|---|---|---|
@@ -113,6 +113,10 @@ For longer retention (beyond 30 days), export logs via Azure Monitor Diagnostic
113
113
114
114
## Example: Custom Scraper with Access Logs
115
115
116
+
:::note
117
+
The `config_id` and `user_id` fields reference UUIDs in the database, but scrapers resolve them by matching on external identifiers (names, aliases, or scraper-assigned IDs). The example below uses human-readable strings to show the scraper input format — Mission Control resolves these to UUIDs internally.
118
+
:::
119
+
116
120
```json title="config-with-access-logs.json"
117
121
{
118
122
"id": "db-prod-001",
@@ -124,7 +128,7 @@ For longer retention (beyond 30 days), export logs via Azure Monitor Diagnostic
124
128
"access_logs": [
125
129
{
126
130
"config_id": "db-prod-001",
127
-
"external_user_id": "user-123",
131
+
"user": "user-123",
128
132
"created_at": "2025-01-08T10:30:00Z",
129
133
"mfa": true,
130
134
"properties": {
@@ -134,7 +138,7 @@ For longer retention (beyond 30 days), export logs via Azure Monitor Diagnostic
Copy file name to clipboardExpand all lines: mission-control/docs/guide/audit/backups.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Use [scraper transforms](/docs/guide/config-db/concepts/transform) to extract ba
61
61
62
62
## Backup Events from Changes
63
63
64
-
Track backup-related events by mapping [change types](/docs/guide/config-db/concepts/changes) in your scraper. CloudTrail events like `CreateDBSnapshot`, `DeleteDBSnapshot`, and `RestoreDBInstanceFromDBSnapshot` can be mapped to named change types for clearer audit reporting:
64
+
Track backup-related events by mapping [change types](/docs/guide/config-db/concepts/changes) in your scraper. You can map CloudTrail events like `CreateDBSnapshot`, `DeleteDBSnapshot`, and `RestoreDBInstanceFromDBSnapshot` to named change types for clearer audit reporting:
Copy file name to clipboardExpand all lines: mission-control/docs/guide/audit/change-tracking.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,8 @@ Mission Control provides an immutable audit trail of all configuration modificat
13
13
14
14
Changes are recorded in two ways:
15
15
16
-
-**Diff changes**: Mission Control compares each scrape result with the previous version and records the diff automatically. No additional configuration is needed beyond setting up a scraper.
17
-
-**Event-based changes**: External events (CloudTrail, Kubernetes events) are ingested as named change types, providing richer context about who made a change and why.
16
+
-**Diff changes**: Mission Control compares each scrape result with the previous version and records the diff automatically. You don't need additional configuration beyond setting up a scraper.
17
+
-**Event-based changes**: Mission Control ingests external events (CloudTrail, Kubernetes events) as named change types, providing richer context about who made a change and why.
18
18
19
19
See [Changes](/docs/guide/config-db/concepts/changes) for details on change types, severity mapping, and retention.
Copy file name to clipboardExpand all lines: mission-control/docs/guide/audit/concepts.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Mission Control's audit system stores four categories of data: identities (who),
15
15
16
16
## How Entities Relate
17
17
18
-
**Identity providers** (Entra ID, AWS IAM, Kubernetes RBAC, databases) are scraped into **users**, **groups**, and **roles**. Users belong to groups, and roles define permission sets.
18
+
Mission Control scrapes **identity providers** (Entra ID, AWS IAM, Kubernetes RBAC, databases) into **users**, **groups**, and **roles**. Users belong to groups, and roles define permission sets.
19
19
20
20
**Permissions** link users, groups, and roles to specific **resources** — the infrastructure items in your catalog (AWS accounts, Azure subscriptions, Kubernetes clusters, databases, etc.). This answers "who _can_ access what."
0 commit comments