-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
When using Atlassian Guard Detect, an Admin might perform adjustments to the default configuration by:
- Creating a custom detection
- Changing the sensitivity of a detection
- Excluding a page from a detection
- Excluding a user from a detection
If those adjustments were the result of a test, and the alerts generated aren't needed anymore, there is currently no functionality to delete or send unnecessary alerts to an archive area.
Suggestion
Provide a new alert status to mark it for deletion or archive it.
The alert marked with this status could be sent to a temporary area, and a shorter retention period (perhaps 14 days) could be applied before it is completely deleted.
Workaround
There is no workaround at this moment, but all alerts are excluded after 180 days:
[ACCESS-2281] At this moment, alerts in Atlassian Guard Detect can't be deleted or sent to an archive area
| Support reference count | New: 1 |
| Description |
Original:
When using [Atlassian Guard Detect|https://support.atlassian.com/security-and-access-policies/docs/what-is-guard-detect/], an Admin might perform adjustments to the default configuration by:
* Using [custom detection|https://support.atlassian.com/security-and-access-policies/docs/create-a-custom-detection/] * [Changing the sensitivity of a detection|https://support.atlassian.com/security-and-access-policies/docs/get-more-or-fewer-alerts/#Change-the-sensitivity-of-a-detection] * [Excluding a page from a detection|https://support.atlassian.com/security-and-access-policies/docs/exclude-a-page-from-detection/] * [Excluding a user from a detection|https://support.atlassian.com/security-and-access-policies/docs/exclude-a-user-from-a-detection/] If those adjustments were the result of a test, and the alerts generated aren't needed anymore, there is currently no functionality to delete or send unnecessary alerts to an archive area. h3. Suggestion Provide a new [alert status|https://support.atlassian.com/security-and-access-policies/docs/track-the-status-of-an-alert/] to mark it for deletion or archive it. The alert marked with this status could be sent to a temporary area, and a shorter retention period (perhaps 14 days) could be applied before it is completely deleted. h3. Workaround There is no workaround at this moment, but all alerts are excluded after 180 days: * [How long are alerts available?|https://support.atlassian.com/security-and-access-policies/docs/view-an-alert/#How-long-are-alerts-available] |
New:
When using [Atlassian Guard Detect|https://support.atlassian.com/security-and-access-policies/docs/what-is-guard-detect/], an Admin might perform adjustments to the default configuration by:
* [Creating a custom detection|https://support.atlassian.com/security-and-access-policies/docs/create-a-custom-detection/] * [Changing the sensitivity of a detection|https://support.atlassian.com/security-and-access-policies/docs/get-more-or-fewer-alerts/#Change-the-sensitivity-of-a-detection] * [Excluding a page from a detection|https://support.atlassian.com/security-and-access-policies/docs/exclude-a-page-from-detection/] * [Excluding a user from a detection|https://support.atlassian.com/security-and-access-policies/docs/exclude-a-user-from-a-detection/] If those adjustments were the result of a test, and the alerts generated aren't needed anymore, there is currently no functionality to delete or send unnecessary alerts to an archive area. h3. Suggestion Provide a new [alert status|https://support.atlassian.com/security-and-access-policies/docs/track-the-status-of-an-alert/] to mark it for deletion or archive it. The alert marked with this status could be sent to a temporary area, and a shorter retention period (perhaps 14 days) could be applied before it is completely deleted. h3. Workaround There is no workaround at this moment, but all alerts are excluded after 180 days: * [How long are alerts available?|https://support.atlassian.com/security-and-access-policies/docs/view-an-alert/#How-long-are-alerts-available] |