Eliminating Offensive Terminology in the Developer Network

Posted on July 6, 2020


We at VMware Carbon Black are working to eliminate offensive terminology from Carbon Black products and communities, including the Developer Network. Going forward, we will make the following language amendments:

  • We will use the terms “approved” and “banned” going forward rather than the terms “whitelist” and “blacklist”
  • We will use the terms “primary” and “secondary clone” or “minion” going forward rather than the terms “master” and “slave”. Original and replica will also be used in some instances.

We are reviewing and updating all of our Developer Network content. Changes to website content will occur first, and API routes that include “white_list” or “black_list” in the path or field values will be updated in the coming months. The current routes will continue to be available for 6 months after the new routes become available. Further information about the deprecation can be found here or in the Developer Community.

The following APIs will be impacted:

We are also reviewing the entire UEX site for these terms and making updates as necessary. This review will include all customer-generated content, which is one of the reasons for this post – we don’t typically edit customer content without notice. Additionally, we’ve added content filters to prevent the use of those terms in the UEX going forward.

As for the products, you will notice changes in the product interface first, in labels and messaging. For Carbon Black Cloud, TTPs and reputation names will not be changing immediately. These terms will change over time, with advanced notice to customers. See the Release Notes for more information.

Please contact us if you have concerns about this change or its impact on your organization. Thank you for your support.