Please review and implement the following pre-deployment requirements to ensure the optimal performance and functionality of the Inspired eLearning (IeL) platform and its components, including the iLMS, PhishProof, and associated courses.

System Requirements

Pre-Deployment Action Items: Hosted & SCORM

Please complete the following steps to ensure the iLMS platform and Inspired eLearning courses function correctly. Hosted customers using iLMS must include both the LMS and CDN domains, while SCORM customers only need to include the CDN domains for course content.

Step 1: Add Exceptions to Network Security - Intrusion Detection System (IDS) and Firewall)

Add the following domains to your allow-list:

• LMS Domains: 
  • *.inspiredlms.com
  • *.securityawarenesstraining.com
• CDNs for Course Content:
  • spa.tclcdn.com
  • inspiredcdn.s3.amazonaws.com
  • assets.tclcdn.com

Step 2: Add Exceptions for Email Communication

Add the following domains to your email filter allow-list:

• Default LMS Sender Domain: 
  • *.inspiredlms.com
  • *.securityawarenesstraining.com
• Domains used for communications from VIPRE internal teams to designated customer contacts:
  • *.inspiredelearning.com
  • *.vipre.com
• Domain used for communication with our support teams: *.inspiredelearning.zendesk.com

Step 3: Adjust Browser Settings

Add the following to the trusted sites and privacy settings in your browser:

• LMS Domains: 
  • *.inspiredlms.com
  • *.securityawarenesstraining.com
• (Only If using Skillsoft Content) Content Streaming Domain: *.skillport.com

Allow pop-ups from the following site to ensure courses launch properly:

• LMS Domains: 
  • *.inspiredlms.com
  • *.securityawarenesstraining.com

Completing these steps ensures optimal performance and functionality of the iLMS and courses.

Pre-Deployment Action Items: PhishProof

To ensure successful delivery and accurate testing of phishing simulations, add our designated IP addresses, domains, and URLs to your allow-list in your email security and network filters (IDS, firewall, client-side email filters, third-party Cloud email filters).

Step 1: Add Exceptions for Phishing Simulations

The following lists have been formatted for easy copying from here and pasting into a CSV for importing.

Requirements for Organizations Using Microsoft Email Services

If your organization uses Microsoft Email Services, the following configuration is required to ensure seamless email delivery and proper functionality of your phishing simulations.

1. Configure Allow-Listing in Microsoft 365 Defender: Set exceptions in the Microsoft 365 Defender portal to allow simulated phishing emails to bypass filtering
   • For assistance, refer to Microsoft's knowledge base articleConfigure 3rd Party Phishing Simulations in Microsoft 365 Defender Portal
2. Bypass ATP Link and Attachment Processing: Create rules in Microsoft 365 to bypass Advanced Threat Protection (ATP) processing for links and attachments in simulated phishing emails
   • Follow our process for creating rules to bypass Microsoft ATP

The following action is needed to prevent Microsoft Defender SmartScreen from misidentifying safe PhishProof educational landing pages as malicious:

1. Update Group Policy settings for SmartScreen
   • For assistance, refer to the following Microsoft knowledge base articles:
     • SmartScreen Settings
     • SmartScreenAllowListDomains

Requirements for Organizations Using Microsoft Email Services AND Third-Party Cloud Email Filters (including VIPRE Email Security Cloud)

Additional configuration is required if your organization uses Microsoft Email Services AND a third-party cloud email filter (including VIPRE Email Security Cloud). Without these adjustments, email flow issues may occur.

Why Configuration is Needed: Due to intermediary routing, Microsoft 365 may not correctly recognize simulation emails as coming from PhishProof when using a third-party cloud filter.

1. Create a Receive Connector in Office 365: A Receive Connector allows emails processed by your third-party filter to enter Microsoft's email service securely
   • If you already have a Receive Connector, skip the remainder of this step and proceed to Step 2
   • For assistance, refer to the following VIPRE articles:
     • Receive Connectors - Microsoft 365
     • Block non-VIPRE Email Sources
2. Enable Enhanced Filtering for the Receive Connector in Exchange Online: This ensures that Microsoft recognizes emails routed through your third-party filter as trusted
   • For assistance, refer to Microsoft's knowledge base article

Requirements for Organizations Using VIPRE Email Security Cloud

If your organization uses VIPRE Email Security Cloud, you don't need to make any changes within your VIPRE account. However, you must still perform allow-listing on your organization's mail server. Please allow-list the PhishProof IP addresses and domains listed above.

Filtering Bots

Some security features, such as web-security gateways, rate limiters, email filters, or Googlebot, may click on links before users do, which can cause false-positive clicks in Phishing Campaign reporting. Bots need to be filtered in the PhishProof Admin Portal to avoid this. 

Refer to the following VIPRE article for assistance: PhishProof Initial Setup.