Skip to main content
NetApp Knowledge Base

How to remove sensitive data from AutoSupports before sending to NetApp

  1. Last updated
  2. Save as PDF
Views:
2,923
Visibility:
Public
Votes:
2
Category:
ontap-9
Specialty:
CORE
Last Updated:

​

​

Applies to

  • ONTAP 9
  • AutoSupport

Description

This article describes the procedure to remove sensitive data from AutoSupport logs. A company may need to remove or 'scrub' sensitive data from AutoSupport logs that are received by NetApp due to compliance and/or company policy. Sensitive data in this context means fields that potentially contain either customer identifying information (CII) and personally identifying information (PII).

For much more information, see:

Things to Consider

 It is important to know that there are important business workflows, support procedures, and dashboards which will stop working if this option is enabled since a lot of information which powers those things will not be transmitted to NetApp.

Examples of things which MAY not work once this option is enabled, include:

  • Automated case creation for critical problems - This could lead to dangerous situations such as data loss if disk failures are not monitored
  • Core Files Upload Processing - Essential for analyzing system issues
  • Support "Fix its" - Quick resolution tools for common problems
  • Active IQ dashboard areas - Performance, Storage Efficiency, Cloud Recommendations
  • Tech Refresh  and Add-on workflow - These internal and customer-facing workflows for customization and sizing could be impaired
  • Performance Archives – Used for getting detailed data to work performance support cases

 

How does this affect support?

  • During support cases, enabling this option will slow down the process for NetApp Support to diagnose and troubleshoot your issue.  This includes support case automation, increasing the risk of undetected hardware failures. 

 

Carefully consider setting this option before doing it:

  • NetApp does not transmit any data stored on your storage.
  • NetApp strips out sensitive data when it arrives and encrypts it in a separate database with strict access controls.
  • NetApp adheres to security best practices around secure software development lifecycle, password issues (rotation, etc.), and role-based access controls of data.

 

Please review Security and Privacy of NetApp Telemetry Data for more information and PII handling in the AutoSupport data warehouse. 

 

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.