Whitelisting On Known Headers Not Recommended
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:
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. 😀
Free Phishing Security Test
Would your users fall for convincing phishing attacks? Take the first step now and find out before bad actors do. Plus, see how you stack up against your peers with phishing Industry Benchmarks. The Phish-prone percentage is usually higher than you expect and is great ammo to get budget.
Here’s how it works:
- Immediately start your test for up to 100 users (no need to talk to anyone)
- Select from 20+ languages and customize the phishing test template based on your environment
- Choose the landing page your users see after they click
- Show users which red flags they missed, or a 404 page
- Get a PDF emailed to you in 24 hours with your Phish-prone % and charts to share with management
- See how your organization compares to others in your industry
PS: Don’t like to click on redirected buttons? Cut & Paste this link in your browser: https://info.knowbe4.com/phishing-security-test-partner?partnerid=001a000001lWEoJAAW