Whitelisting On Known Headers Not Recommended

Stu Sjouwerman | Dec 20, 2021

We found a discussion on Twitter about this topic and we thought it would be useful to provide to provide the correct technical background related to whitelisting. 

Whitelisting purely on known headers certainly would be a non-optimum action, which is why it should be noted that the article referenced has a very large notice at the top which directs people to use an alternative method that does NOT include headers.  If someone does want to whitelist by headers we will support that but in that case we recommend using the custom header options.  This is the box at the top of the page: 

ADP-MS365

Of course another method is to whitelist is with direct message injection where the headers are effectively fictitious but that's a different discussion. Hope that clarifies this some more.  :-D

 

Topics: KnowBe4

Discover Your Organization’s Phish-prone™ Percentage

Ninety-one percent of data breaches begin with spear phishing. Launch our Free Phishing Security Test for up to 100 users to uncover your team's vulnerability and see how your security posture stacks up against industry benchmarks.

Get Your Free Phishing Security Test

Secure the Digital Workforce: Human + AI

KnowBe4 empowers the modern workforce to make smarter security decisions every day. Trusted by more than 70,000 organizations worldwide, KnowBe4 is the pioneer of digital workforce security, securing both AI agents and humans. The KnowBe4 Platform provides attack simulation and training, collaboration security, and agent security powered by AIDA (Artificial Intelligence Defense Agents) and a proprietary Risk Score. The platform leverages 15 years of behavioral data to combat advanced threats including social engineering, prompt injection, and shadow AI. By securing humans and agents, KnowBe4 leads the industry in workforce trust and defense.