Guard Premium & data residency/BYOK — does it work on pinned product data?

[Paul Roche Val]

Hey community,

The Guard Detect FAQ confirms that Guard Premium's own data (alerts, detection logs) is not subject to data residency or BYOK: https://support.atlassian.com/security-and-access-policies/docs/guard-detect-faq/

What I'm trying to understand is the other direction: when Guard Premium operates on Jira/Confluence product data that is pinned to a data residency region (e.g. Switzerland) and/or encrypted with BYOK, does it still have full visibility to scan, classify and detect sensitive content within that data?

Put differently — do DR and BYOK constraints on the underlying product data in any way limit Guard Premium's effectiveness?

Anyone who has tested this in a similar setup would be very helpful. Thanks!

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Paul Roche Val 

Pinned location + Guard Premium: yes, generally fine

Pinned location + BYOK/CMK: yes, but only by provisioning the encrypted app in that chosen location

Existing pinned app + later add BYOK/CMK: not the normal supported path today

Guard Premium feature data itself: check feature by feature, because Guard Detect is a known exception.