> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/query/data-scan/data-scan-output.md). # Data scan output View all the results of your data scan by going to the specific workflow and viewing its execution details. In a unified view, see: * [Matches for data classifiers](#data-classifier-output) - View exact and intelligent matches with offsets, masked snippets, probability, data category, compliance standards, and full context * [Matches for regex patterns](#regex-output) - View exact and intelligent matches with offsets, masked snippets, and full context Data classifier findings are categorized by data type (security, PII, finance) for faster triage, and tagged with probability match scoring for smarter decisions.
The data scan output includes these parameters:
Data scan output parameterDescription
Workflow execution status

Number of workflow executions per status:

  • Completed
  • Warning
  • Failed
TotalTotal number of scanned assets, according to workflow execution status
Asset nameName of file that was scanned
Scan status

Number of matches found in the asset with their status:

  • Completed
  • Warning
  • Failed
Data scan assetsNumber of assets scanned in total
Data scan matchesNumber of files or Slack conversations where matches were found
ClassifierTerm that categorizes data based on sensitivity, type, or regulatory requirements
Category

Type of data found:

  • Government
  • Financial
  • PII
  • Cryptocurrency
  • Credentials
  • Medical
  • Logistics
  • Business
  • Cryptographic
  • Networking
  • Educational
Compliance

Name of compliance standard that includes the classifier:

  • GDPR
  • HIPAA
  • PCI
  • FERPA
  • LGPD
  • CCPA
  • POPI
  • PDPO
  • GLBA
Match probability

The likelihood of a data classifier appearing in an asset:

  • High - Between 71-100% likelihood there is a match
  • Medium - Between 31-70% likelihood there is a match
  • Low - Between 0-30% likelihood there is a match
DetailsClick the View icon to see details of the data scan
Regex nameThe string or pattern sequence of symbols and characters
OffsetPosition in the file or conversation where the match was found, based on the character count
DetailsClick the View icon to see details of the data classifier or regex pattern found. The context is provided for 100 characters before and after the pattern.
## Data classifier output To view the results of your data scan, go to the specific workflow and view its execution details. The context for the data classifier is displayed for 100 characters before and after the classifier. #### To view data classifier output: 1. In the **Workflow list,** click the specific workflow and go to workflow activity. 2. Click **View** to open a specific execution. 3. In the Output tab, click the **Data scan** action.
4. Next to the data classifier name, click the **Details** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fh1PTUvilwUjBiALm9QC4%2FView%20more.png?alt=media\&token=6d06e2fb-9714-4d18-b1e3-2530f04231ce) icon to see the full results.
5. Click **View asset** to open the asset. 6. Click **Copy** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FcWZvliv3SdaL4drI2LEf%2Fcopy.png?alt=media\&token=d67e829f-83b9-47de-b804-ed5f44568cbc) to copy the context or message ID of the specific conversation in Slack. ## Regex output To view the results of your data scan, go to the specific workflow and view its execution details. The context for the regex pattern is displayed for 100 characters before and after the expression. **For example**: If the regex expression `"^test*\n"` is scanned and found in the file contents, it returns this result:\ Matches: `[["index:4", "match: test run"], ["index:100", "testing"]]` This means the strings were found at character number 4 and 100 in the file contents. #### To view regex scan output: 1. In the **Workflow list,** click the specific workflow and go to workflow activity. 2. Click **View** to open a specific execution. 3. In the Output tab, click the **Data scan** action. 4. Next to the regex name, click the **Details** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fh1PTUvilwUjBiALm9QC4%2FView%20more.png?alt=media\&token=6d06e2fb-9714-4d18-b1e3-2530f04231ce) icon to see the full results.
5. Click **View asset** to open the asset. 6. Click **Copy** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FcWZvliv3SdaL4drI2LEf%2Fcopy.png?alt=media\&token=d67e829f-83b9-47de-b804-ed5f44568cbc) to copy the regex pattern or full context. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/query/data-scan/data-scan-output.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.