Your comprehensive guide to seamlessly implementing Dune Security’s AI-powered Security Awareness Training platform.
Follow these essential steps to launch and optimize your organization's cybersecurity defenses.
1. User Management
Get started by configuring Dune Security to work within your existing environment. This ensures seamless integration with your identity provider and email systems.
Key Actions
Set up Single Sign-On (SSO) with providers like Microsoft Entra ID or Okta.
Enable SCIM integration for automated user provisioning.
Join the Dune Security Support channel on Slack or Teams.
Deploy the Dune Watchtower button in Outlook or Google Workspace.
Train users on proper usage.
Review and act on reported threats.
Share your organization’s abuse mailbox with your Dune Solutions team. This is configured on the Dune backend.
Important Reporting Note
If your organization does not use Dune Watchtower, please confirm that your existing reporting provider can forward reported emails as .eml attachments to secops@dunewatchtower.com.
Dune requires the reported email to be sent as an .eml attachment in order to track the reporting metric. If your provider cannot send reports in this format, Dune will not be able to capture those reports in the platform.
Google’s native “Report phishing” option is not currently supported for Dune reporting metrics due to Google’s fraud detection behavior and API limitations.
When testing phishing simulation links, each recipient should open their assigned simulation link only once, from a single browser on a single device.
Dune Security uses browser and device validation to help protect simulation integrity. If the same simulation link is opened across multiple browsers, private/incognito windows, devices, or by multiple testers, the landing page may fail to load or return a suspicious visitor mismatch error.
For the most accurate testing results:
Send each tester their own fresh simulation email.
Do not forward or share simulation links between users.
Open each link in only one browser per device.
Avoid testing the same link across normal and private/incognito browser sessions.
Troubleshooting Details
If you experience any issues during testing, please share the following details with your Solutions Engineer (support@dune.security):
HAR files for both successful and failed page loads
Tester email address
Browser and device used
Timestamp of the test
Whether VPN, SWG, ZTNA, or other network security tools were enabled during testing
Providing these details will help Dune troubleshoot more quickly and accurately.
Training Preferences & Customizations
Deliver targeted training for maximum impact.
Key Actions
Assign training based on phishing failure vectors.
Enable just-in-time training for risky behaviors.
Customize content for compliance and relevance.
Note: "Training Completion Deadline" must be configured prior to assigning trainings.
Support and Assistance
If you encounter any issues during the deployment or need assistance, please reach out to Dune Security’s support team. Our experts are here to guide you and ensure a smooth integration process.
By following these steps, you're not just deploying a tool—you’re making a critical investment in safeguarding your organization against modern cybersecurity threats.
Comments
0 comments
Please sign in to leave a comment.