Manage detection alerts and their frequency

Attachment scanning functionality is part of an early access program. You may see a difference between the information below and your Guard administration experience.

Every organization is different. A detection that’s vitally important in one organization or industry, may be less important to another.

You can fine tune alerts in several ways.

  • Enable or disable scanning of images that may contain humans.

  • Change the sensitivity of a user activity detection.

  • Enable or disable detection alerts to suit your needs.

  • Exclude certain pages a from content scanning detection.

  • Exclude users from a user activity detection.

Who can do this?
Role: Organization admin, Guard Detect admin
Atlassian Cloud: Atlassian Guard Premium
Atlassian Government Cloud:Available

Manage your detection settings for content scanning

Enable or disable scanning of images that may contain humans

You can enable or disable settings to control whether real-time optical character recognition scans can extract text from images containing humans. We do not perform facial recognition or biometric identification.

When enabled, this setting extends scans to include text embedded within images that may contain humans. These images are also processed for text extraction and scanned for sensitive data, with any findings flagged via alerts.

When disabled, this setting minimizes scanning by skipping images that may contain humans.

By default, this setting is disabled.

To enable or disable scanning for images with humans:

  1. In Guard Detect, select Detections in the header.

  2. Select Content scanning.

  3. Select the Settings tab.

  4. Under Scanning attachments with images of humans, select the appropriate option to suit your needs.

  5. Click Update to save the settings.

Change the sensitivity of a detection

For some user activity detections you can increase or decrease the number of alerts you receive by changing the sensitivity.

For example, if you change the sensitivity of the page crawling detection to receive fewer alerts, more pages need to be crawled before the alert is fired. This can be useful if you are getting a lot of alerts for expected behavior.

To customize a detection:

  1. In Guard Detect, select Detections in the header.

  2. Select User activity.

  3. Expand the detection you want to customize. You can use the filters to show only detections that can be customized.

  4. Select Fewer alerts or More alerts.

User activity detections screen showing a detection customized to send fewer alerts

Enable or disable a detection alert

You may want to disable content scanning detection alerts that don’t apply to your location, or that create too many false positives for your industry or work context.

You can enable or disable a detection alert at any time by toggling its switch. If a detection alert is available for both Confluence and Jira apps, you’ll see a toggle for Confluence and a toggle for Jira apps.

To enable or disable a content scanning detection alert:

  1. In Guard Detect, select Detections in the header.

  2. Select Content scanning.

  3. Expand the detection you’re interested in.

  4. Select the appropriate toggle to suit your needs.

The rule will be marked as off for the selected app in the list, and you’ll no longer get alerts for this rule.

If you don’t want to turn off a detection entirely, you can exclude pages that frequently generate false positive alerts. How to exclude a page from a detection

Enable or disable a user activity alert

You can enable or disable a user activity alert at any time by selecting the Alerts toggle. Each user activity alert is specific to an app, so make sure you check the full list of detections in case a similar detection exists for another app.

To enable or disable a user activity alert:

  1. In Guard Detect, select Detections in the header.

  2. Select User activity.

  3. Expand the detection you’re interested in.

  4. Select the appropriate toggle to suit your needs.

If you don’t want to turn off a detection entirely, you can exclude users that frequently generate false positive alerts. How to exclude a user from a detection

The alert will be marked as off in the list, and you’ll no longer get alerts for this rule.

Still need help?

The Atlassian Community is here for you.