home

Mobile Endpoint Security

Lookout Product Documentation

Find answers about using and optimizing Lookout products.

Configure Phishing and Content Protection

These procedures are for new customers enabling Phishing and Content Protection for the first time. Existing customers with Phishing and Content Protection refer to Migrating Existing Users to Secure DNS to enable Secure DNS for their users.

  1. Navigate to the Protections module and click the Phishing and Content Protection tab.
  2. In the Manage settings for: dropdown, select the device group you will apply the settings to.

    Phishing and Content Protection settings are per-group, facilitating a controlled rollout to the organization.

  3. Enable the Enable Phishing and Content Protection toggle:
  4. Existing customers with advanced features (see Appendix C for details) can configure the

    Deployment Type option as Secure DNS or On-Device VPN or both.

    On IOS 14 or above, selecting the Secure DNS deployment type shows only the DNS setup instructions to the user. Selecting the On-Device VPN shows only the VPN setup instructions to the user. Selecting both shows both DNS and VPN instructions to the user.

  5. Optionally, enable Phishing and Content Protection enforcement by setting the Make Phishing and Content Protection mandatory toggle to ON.
    This prevents end users from disabling the feature on their Lookout for Work app.
  6. Customers with advanced features (see Appendix C for details) can configure Secure DNS Corporate Domain Skip List. Admins can specify a list of domains that should not be resolved by Lookout DNS resolver.
    Those domains will be resolved by the default DNS resolver of the network to which the device is connected.
    • Typically admins can configure their internal domains using this option. When the device is connected to a corporate network, those internal domains will be resolved by the corporate DNS resolver.
    • You can also add ‘in-flight’ airline Wi-Fi domains so users using Secure DNS can connect to airline Wi-Fi. Otherwise, Lookout for Work will wait for Secure DNS resolution of the Wi-Fi domain which never comes because no other internet connections exist in-flight. See Using a Skip List to Allow In-Flight Wi-Fi Connection.
  7. Optionally, configure Allowlisted Content. Such domains will always be trusted and never be blocked.
  8. Optionally, configure Denylisted Content. Such domains in the Denylist will not be trusted and always enable policy action on.
  9. Click Save changes.
  10. Navigate to the Policies tab directly or by clicking Configure content policies in the Phishing and Content Protection tab.
  11. Find the Unauthorized Content classification.

    When Lookout detects unauthorized content (for example, a site known to distribute spyware), it either alerts the user or blocks access to the URL based on the responses you configure.

  12. Choose a Risk Level of None, Advisory, Low, Medium, or High.
    Risk LevelPossible Response
    NoneLookout does not detect a threat or notify or block the users from accessing the content.
    AdvisoryLookout alerts the user but does not log a threat in the console.
    Low, Medium, HighLookout alerts the user and may also block the users depending on the response settings.
  13. Click the gear icon next to the Risk Level dropdown.

    The Configure Unauthorized Content Protection dialog appears.

  14. Select the checkboxes of unauthorized content you want to respond to.

    Content subcategories are described here: Reference: Unauthorized Content Policy Categories.

  15. Click Save Changes.
  16. Choose the response from the Response dropdown.
  17. Click Save Changes on the Policies tab.
  18. Set a severity and response for the Phishing and Content Protection Disabled classification.
    This classification indicates that the end user has disabled the PCP feature in their Lookout for Work app.
  19. Set a severity and response for the VPN Permission Not Accepted issue types.

    This classification indicates that the end user has not accepted VPN permissions, so Lookout cannot create a local VPN for PCP or On-Device Threat Remediation.