• Documentation

Review your content scan results

Before you take any action based on your content scan results, make sure you understand how to read the results. Your CSV file contains a number of fields that will help you to take action either through redaction APIs or other options.

To ensure you can take further action, avoid manually deleting anything in the CSV file. Also avoid deleting any of the content detected during the content scan from the current version of the Confluence pages or Jira work items listed in the file.

The following table shows the fields your CSV file contains and how you can use them to manage your data. We don’t share your content in the CSV file.

Field

Description

Values

Finding ID

The unique string identifier per occurrence of high-risk data

UUID format

Detection type

The type of content detected

More info: What sensitive data is detected?

Plain text format, showing the name of the detection type. For example:

  • CREDIT_CARD

  • ATLASSIAN_TOKEN

  • CUSTOM (for all custom detections)

Detection ID

Used to further identify any CUSTOM detection types using a unique string identifier.

For standard detection types, the contents of this field aren’t used for any purpose.

 

For CUSTOM detection types:

  • UUID format

For standard detection types:

  • text

Detection version

The internal versioning for detection results, used only by Atlassian for traceability or debugging, if required

  • 1, 2, 3 and beyond

App

Identifies the Atlassian app where the data was found

  • jira

  • confluence

Content ARI

The Atlassian resource identifier (ARI) of the object where the data was found

More info: Build your ARI

Jira work item:

  • ari:cloud:jira:{siteId}:issue/{issueId}

Jira work item comment:

  • ari:cloud:jira:{siteId}:issue-comment/{issueId}/{commentId}

Confluence page:

  • ari:cloud:confluence:{siteId}:page/{pageId}

Confluence blogpost:

  • ari:cloud:confluence:{siteId}:blogpost/{blogpostId}

Confluence comment:

  • ari:cloud:confluence:{siteId}:comment/{commentId}

Data field

The field that contains the high-risk data

For Confluence:

  • confluence_page_title

  • confluence_blog_title

  • confluence_page_body

  • confluence_blog_body

  • confluence_comment

For Jira

  • field ID for work items

Data location: first node

The starting location of the data when detected in Atlassian Document Format (ADF). You'll need this field if you want to use the Redactions API

Sensitive content may be spread to consecutive ADF nodes. If this occurs, the sensitive data can't be redacted

More info: Atlassian Document Format

See also in this table: Sensitive data location: last node

For ADF content:

  • A JSON pointer to the first ADF node that contains high-risk data

For non-ADF (plaint text) fields:

  • text

Data location: start position

The first character where the data was found. You'll need this field if you want to use the Redactions API

For ADF content:

  • The first character that contains high-risk data within the first ADF node

For a plain text field:

  • The first character that contains high-risk data within the entire field string

Data location: last node

The ending location of the data when found in ADF. You'll need this field if you want to use the Redactions API

Sensitive content may be spread to consecutive ADF nodes, and this occurs, the sensitive data can't be redacted

More info: Atlassian Document Format

For ADF content:

  • A JSON pointer to the last ADF node that contains high-risk data

For non-ADF (plaint text) fields:

  • text

Data location: end position

Last character where the data was found. You'll need this field if you want to use the Redactions API

 

For ADF content:

  • The last character that contains high-risk data within the last ADF node

For a plain text field:

  • The last character that contains high-risk data within the entire field string

Data hash

A hash of the high-risk data that is compatible with the Redactions API

A hash

Container ARI

The Confluence or Jira space identifier

Confluence:

  • ari:cloud:confluence:{spaceId]

Jira:

  • ari:cloud:jira:{spaceId]

Created by

The Atlassian account ID of the user who created the content

This may sometimes be empty for Jira

  • ari:cloud:identity::user/{userId]

Last updated by

The Atlassian account ID of the user who last edited the content

This may sometimes be empty for Jira

  • ari:cloud:identity::user/{userId]

Created at

The date that the item was created.

  • YYYY-MM-DDTHH:mm:ss.msZ

Updated at

The date that the item was updated.

  • YYYY-MM-DDTHH:mm:ss.msZ

Depending on how you want to handle the data, you can use the CSV file to redact content, import the data into Jira, or do a combination of both.

Read:

Still need help?

The Atlassian Community is here for you.
Ask the Community
CommunityQuestions, discussions, and articles