Updating Your KMSAT Phishing Settings

In this article, you'll learn about the Phishing Settings section of your KMSAT account settings. In the Phishing Settings section, you can update your phishing campaign settings and enable Direct Message Injection (DMI) and Artificial Intelligence Driven Agent (AIDA).

Click the links below to learn more about the Phishing settings.

Jump to:

Phishing Settings

Direct Message Injection (DMI)

Phishing Settings

In the Phishing Settings section, you can customize your phishing settings.

See below for more information about the settings in this section:

1. Default Landing Page: To set a default landing page for all phishing campaigns, select a landing page from this drop-down menu. When you create a phishing campaign or edit an email template, you’ll have the option to override this setting and select a different landing page if you’d like.
2. Default Landing Domain: To set a default landing page domain for all email templates, select a landing page domain from this drop-down menu. When you edit an email template, you’ll have the option to override this setting and select a different landing page domain if you’d like.
3. Disable Email Open Tracking: Select this check box to remove the small tracking image that we place in each phishing email. This image tracks if and when your users open the email. For more information, see our How Do You Track Email Opens in the Phishing Security Test? article.
4. Include Archived Users In Reports: Select this check box to include data from archived users in all phishing reports. If this setting is disabled, data from archived users will not be included in phishing reports.
5. Overwrite [[domain]] Placeholder: Select this check box to change what the [[domain]] placeholder displays in phishing templates and landing pages. This setting will not affect the [[domain]] placeholder in training notifications. After you select the check box, enter a domain in the text field.
   You may want to enable this setting if your organization does not want you to spoof your users' domains or if you use spoofing prevention to prevent emails spoofing your domain from being delivered successfully.
   If you do not enable this setting, the [[domain]] placeholder will use the recipient's email domain. For information on how the [[domain]] placeholder works by default, see our How the [[domain]] Placeholder Works article.
   

   Note: If you use a look-alike domain or a domain that is similar to your organization’s real domain, we recommend that you purchase the look-alike domain. If someone else purchases the look-alike domain and your users reply to an email sent by the domain, your users may reply to the owner of the domain. Please be aware that using a real domain with anti-spoofing protection could affect email deliverability.

6. Disable Template Attack Vectors: Select this check box to disable phishing email templates that use specific attachment attack vectors. For example, if you don't want your users to receive simulated phishing attacks that include PDF attachments, you can select PDF Attachments from the drop-down menu. For more information, see our What Attachments Can I Add to My Phishing Campaign and How Are They Tracked? Article.
7. Default Phishing Language: From the drop-down menu, select the language that you’d like to use in phishing campaign emails. This language will be used in all users’ phishing emails unless a different Phishing Language has been set for a user. If a user’s language is not available, the account’s default language will be used. For more information, see our Localization Guide.
8. Overwrite Sender Address with Reply-to Address For OOO Replies: We recommend that you select this check box if you use reply-to phishing, track out of office (OOO) replies, or use Microsoft Exchange or Microsoft 365. For more information, see the Should I track out of office replies? section of our Reply-to Phishing article.
9. Overwrite Return-path Address with Reply-to Address: Select this check box to change the return-path address to the reply-to address in a reply-to phishing campaign. We recommend that you enable this setting if your mail server settings require the return-path address to match the reply-to address. For more information, see our Reply-to Phishing article.
10. Overwrite Fixed Return-path Address with Sender Address: We recommend that you select this check box if you use Google Workspace (formerly G Suite) as your mail server. If you do not enable this setting, Google Workspace users may see "via KnowBe4" text beside the sender email address when they receive phishing test emails in their inbox. For more information, see our Why does my phishing test email show “Via psm.knowbe4”? article.
11. Disable X-PHISHTEST Header: Select this check box to remove the X-PHISHTEST header from phishing emails.
12. Enable PST Header Token: Select this check box to include the generated token in an X-KB4TOKEN header in phishing emails. If you enable this setting and would like to generate a new token, click the Regenerate Token button.
13. Add Custom Header: Select this check box to add a custom header name and header value to phishing emails. If you select the check box, you must enter text in the Header Name and Header Value fields. If you whitelist our phishing emails by email header, you can enable this setting and then whitelist your custom header text for additional security.
14. Enable DKIM Signature: Select this check box to add a DKIM signature to your phishing emails for additional security. You can choose to use KnowBe4's signing domain or customize your own signature. If your organization requires DMARC/DKIM checking for incoming messages, we recommend that you select this check box. For more information, see our How to Enable and Customize DKIM Signatures article.

Back to top

Direct Message Injection (DMI)

In this section, you can enable Direct Message Injection (DMI). DMI eliminates the need to whitelist simulated phishing emails by creating a secure link between your KMSAT console and your Microsoft 365 account.

For more information about enabling DMI, see our DMI Configuration Guide.

Back to top