Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/docs/data-localization/compatibility.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ The table below provides a summary of the Data Localization Suite product's beha

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| ----------------- | --------------- | ----------------- | -------------------------- |
| Access | 🚧 [^14] | 🚧 [^15] | 🚧 [^16] |
| Access | 🚧 [^14] | 🚧 [^15] | [^16] |
| Browser Isolation | ⚫️ | 🚧 [^17] | ✅ |
| CASB | ⚫️ | ⚫️ | ✘ |
| Cloudflare Tunnel | ⚫️ | 🚧 [^18] | ⚫️ |
Expand Down Expand Up @@ -142,7 +142,7 @@ The table below provides a summary of the Data Localization Suite product's beha

[^15]: Can be localized to US FedRAMP Moderate Domestic region only.

[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region. EU customers must use Logpush to retain logs.

[^17]: Currently may only be used with US FedRAMP region.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,6 @@ Be aware that if you enable CMB for a dataset that does not support your region,
| Network Analytics Logs | Account | ✅ | ✅ | ✅ |
| Device Posture Results | Account | ✘ | ✅ | ✘ |
| Audit Logs | Account | ✘ | ✅ | ✘ |
| Access Requests | Account | ✅ | ✅ | |
| Access Requests | Account | ✅ | ✅ | |

[^1]: Customer Metadata Boundary does not apply in this case, as these logs are sent directly from the processing location to your configured destination.
Loading