Skip to main content
NetApp Knowledge Base

Scanned databases do not report any sensitive info in the Investigation page

Views:
16
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
netapp_console
Last Updated:

Applies to

  • Classification
  • Investigation report

Issue

  • Scanning a MySQL Server database, the Map and Classify mechanism is failing to identify known personal identifiable and other sensitive information, resulting in server errors during API calls.
  • The Investigation Report tab shows 0 hits in both the Personal and Sensitive Personal columns after scanning the database that contains phone numbers, addresses, and other sensitive information.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.