Using racially neutral terms in technology
In April, the UK National Cyber Security Centre (NCSC) published a blog announcing a significant change to their website, by replacing commonly used cyber security terminologies ‘whitelisting’ and ‘blacklisting’ with racially neutral terms such as ‘allow list’ and ‘deny list’.
Whitelist refers to the practice of explicitly allowing access to identified entities while blacklist is a list of entities that are considered untrusted and unacceptable.
Home Office Digital, Data and Technology to adopt this approach
This may seem like a small thing – but it’s offensive to many and we in Home Office Digital, Data and Technology support the NCSC stance and will make the same changes to our terminology.
We will also encourage people not to use terms like ‘master’ and ‘slave’ for our servers - abhorrent phrases which somehow have become normalised. Using negative or derogatory language for white meaning ‘good’ and black meaning ‘bad’ or ‘not allowed’ or making casual reference to human oppression and tyranny is just not acceptable anymore.
Our Deputy Chief Information Security Officer, Kate Stanbury, said:
We’re a strong advocate of NCSC’s decision of making this worthy change and we’ll adopt this transformation. We’ll be replacing any terminology within our own processes that’s not consistent with the ‘stamp out racism’ message.
To promote and establish an open, respectful and safe work environment, we must work together as one and replace terminologies and processes that spark discrimination amongst us.
We can’t alter all Home Office terms on our own, so we encourage our colleagues, the public and peers across the digital world to help us and be alert to phrases which could cause offense so we can take action to amend them.
Tech firms are also using racially neutral terms
Tech firms are now actively discouraging teams from using terminologies that promote racial stereotypes and stigma. For example, a popular programming language, Python, replaced terms ‘slaves’ to ‘workers’ or ‘helpers’ and ‘master process’ to ‘parent process’. In a similar way, Google Chrome has also asked their developers to avoid ‘blacklist’ and ‘whitelist’ in favour of ‘blocklist’ and ‘allowlist’.
It’s good news that organisations are taking a similar approach and we know it’s only a small step which may seem insignificant compared to the challenges presented by wider prejudice and offensive language. But it is a small step in the right direction.