Message platform for automated threat simulation, reporting, detection, and remediation
摘要
說明書
The simulated emails can be stored into a user inbox by a process of being inserted, dropped, created, or stored. While various methods may be used, and various terms may be used for this purpose, the functional end result is the same, that the simulated phishing email is stored in the user email account as a new message. The simulated emails can be inserted through an application programming interface (API) accessed by a service account.
User Activity Evidence Detection
The on-demand feature addresses two challenges that operators experience in planning and scheduling simulated phishing campaigns: ensuring that scenario emails are successfully delivered and achieving the best recipient response rate possible. Factors that can prevent scenario emails from being delivered to recipients in an organization include the presence of gateway filters that can inadvertently handle incoming scenario emails as spam, and improper whitelisting of simulation email server IP addresses
The on-demand feature eliminates the question of whether recipients received scenario emails by ensuring that scenario emails are delivered to an organization. When this feature is enabled, simulation content bypasses the whitelist and any gateway filters the organization may have in place and, by way of Microsoft Exchange Web Services (EWS), delivers scenario emails directly to the recipient's inbox when the recipient is actively using Microsoft Outlook. The on-demand feature bypasses gateway filters and whitelisting configuration only for the scenario emails, not for any other emails.
