Guard Detect frequently asked questions

We’re gradually transitioning Guard Detect into Atlassian Administration. We’ll support Guard Detect until the Atlassian Administration experience includes all the same features (and new ones!).

The Findings page in Atlassian Administration is the first step in the transition.

Go to Findings documentation

Guard Detect is part of Atlassian Guard Premium.

Is Guard Detect supported for data residency?

Data residency gives you control over where your in-scope app data is hosted. Understand data residency

Data residency is not currently available for Guard Detect.

Guard Detect is designed to store minimal data. Alert data is stored for 1 year, which is consistent with the Atlassian Administration audit log retention. All other data is referenced from Atlassian administration audit logs and services that primarily belong to Jira and Confluence.

Is Guard Detect supported for BYOK?

Customer Managed Keys (CMK) encryption lets you encrypt app data for Jira, Confluence, or Jira Service Management (EAP only) with keys hosted in your external AWS account. What is CMK encryption

BYOK encryption is not currently available for Guard Detect.

Is Guard Detect available in Atlassian Government Cloud?

Yes, Guard Detect is currently available in Atlassian Government Cloud.

Is there an API?

Yes, APIs are available for Guard Detect. Get started with Guard Detect APIs

You can also send alerts to your SIEM or other tool using one of our integrations or webhooks. How to send alerts to your own tools

Does it monitor individual sites or your whole organization?

Guard Detect monitors the entire organization. It functions at the organization level and tracks user activity across multiple sites in the same organization.

If you are trying Guard Detect, and don’t want alerts to be generated for your production data, you will need to use a test organization.

Does it impact performance or functionality of other Atlassian apps?

Guard Detect doesn’t touch any of the Atlassian app suite architecture. It’s a layer of intelligence that observes events happening within your Atlassian organization.

Guard Detect is not installed or running any code in your production site like an app or integration. It passively listens to app and administrative events and is completely detached from the actual features, therefore it will not affect your Atlassian app's performance.

What are findings?

We’re gradually transitioning Guard Detect into Atlassian Administration. We’ll support Guard Detect until the Atlassian Administration experience includes all the same features (and new ones!).

The Findings page in Atlassian Administration is the first step in the transition. More about findings

Is the Findings page same as the Alerts page in Guard Detect?

The Findings page is similar to the Alerts page in Guard Detect but not the same.

Guard Detect is available outside of Atlassian Administration, so your Guard Detect admins can access it. They can continue to use Guard Detect and its existing features. Most functionality remains in Guard Detect at the moment, and we’ll continue to maintain Guard Detect.

The Findings page is located within Atlassian Administration, where organization admins can access it. This is the first step to moving Guard functionality into Atlassian Administration. We'll continue to add new and existing functionality there. Key differences between the Findings page and Guard Detect

Is the Findings page available in Atlassian Government Cloud?

Yes, the Findings page is available in Atlassian Government Cloud.

 

Still need help?

The Atlassian Community is here for you.