Here you can find all the Hoxhunt deployment guides for setting up Hoxhunt in Office 365, on-premise Exchange or Google environment. This page is updated as new deployment guides become available.
Deployment for Office 365 & Exchange
1. Allow/whitelisting and ensuring mail flow
Reason for implementation
Ensuring that Hoxhunt phishing simulations can be delivered to end users focused inboxes. Any mail filtering or phish detection should be allow/whitelisted to ensure uninterrupted email delivery.
Mandatory for all Office 365 & Exchange customers
- Allowing Hoxhunt training emails to be delivered uninterrupted to Microsoft 365 / On-premise Exchange mailboxes
- Configuring Advanced Delivery for Hoxhunt
Optional as relevant for Office 365 & Exchange customers
-
Bypassing Defender/ATP links and attachments scanning for Hoxhunt training emails
- Allow/whitelisting of additional mail filtering systems
2. Installing Hoxhunt add-in
Reason for implementation
Ensuring that all employees who should participate in the Hoxhunt Awareness training have the Hoxhunt plugin integrated to their inbox.
Prerequisites
Client requirements for using Hoxhunt
For O365, Hybrid and Mobile
Centralized Deployment of Hoxhunt Outlook add-in
For On-premise Exchange
Distributing Hoxhunt Outlook add-in
3. Allow/whitelisting proxies and VPNs
Reason for implementation
Ensuring that the Hoxhunt plugin can open the popup where the employee can go through the microtraining either after successfully reporting or failing a Hoxhunt simulation.
Allow/whitelisting proxies and VPNs overview
4. (Optional) SSO configuration
Reason for implementation
Allowing admins and end users can log into the Hoxhunt dashboard through SSO.
Read more here: Single sign-on (SSO) overview
Alternative
If SSO is not implemented, Magic Links will be used instead.
5. (Optional) SCIM (automated user provisioning) configuration
Reason for implementation
Allowing admins to manage users automatically (we currently support Azure AD and OKTA).
User Management: Automatic user provisioning (SCIM) overview
Alternative
If SCIM is not enabled, users can be managed through CSV List uploads in the Hoxhunt Admin Portal. Read more here: Admin Portal: User Management through User Import Tool or CSV Lists
Deployment for Google
1. Whitelisting and ensuring mail flow
Reason for implementation
Ensuring that Hoxhunt phishing simulations can be delivered to end users focused inboxes. Any mail filtering or phish detection should be allow/whitelisted to ensure uninterrupted email delivery.
Mandatory for all G-suite customers
Optional as relevant for G-suite customers
Allow/whitelisting of additional mail filtering systems
2. Installing Hoxhunt plugin
Reason for implementation
Ensuring that all employees who should participate in the Hoxhunt Awareness training have the Hoxhunt plugin integrated to their inbox.
Prerequisites
Client requirements for using Hoxhunt
Installation guide
Distributed installation of Gmail plugin
4. (Optional) SSO configuration
Reason for implementation
Allowing admins and end users can log into the Hoxhunt dashboard through SSO.
Read more here: Single sign-on (SSO) overview
Alternative
If SSO is not implemented, Magic Links will be used instead.
5. (Optional) SCIM (automated user provisioning) configuration
Reason for implementation
Allowing admins to manage users automatically (we currently support Azure AD and OKTA).
User Management: Automatic user provisioning (SCIM) overview
Alternative
If SCIM is not enabled, users can be managed through CSV List uploads in the Hoxhunt Admin Portal. Read more here: Admin Portal: User Management through User Import Tool or CSV Lists