Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Welcome to Keepnet! We're excited to be partnering with you on your human-risk management strategy.
This Getting Started guide will be your key resource in successfully implementing the technical setup of Keepnet and, therefore, mitigating human-related cybersecurity risks.
The steps you will follow:
(Only for customers who have Incident Responder product)
(Recommended)
(Recommended)
The document covers all aspects of , which not only addresses traditional phishing methods but also provides robust defenses against more complex attacks such as Vishing (Voice Phishing), Smishing (SMS Phishing), MFA Phishing (Multi-Factor Authentication), Quishing (QR code phishing), and Callback Phishing (Telephone Oriented Attack Delivery).
Our documentation ensures you get maximum value from our products. It comprehensively covers its core functionalities and detailed features, providing clear, step-by-step instructions for effective utilization.
Our documentation is designed for anyone who works with Keepnet products—whether you’re actively using them, selling them, or exploring their capabilities. It supports roles such as HR, IT, Compliance, and SOC teams, helping them maximize value from the platform. Whether sending targeted training, analyzing and containing email threats, or managing human risk across the organization, the resources are tailored to guide each role in achieving their objectives effectively.
The primary purpose of our documentation is to empower customers to independently use our products without relying heavily on the Keepnet support team. We provide comprehensive resources, including articles, tutorials, and troubleshooting guides, to ensure customers have the knowledge and tools to maximize our platform's capabilities.
The documentation covers an extensive scope, encompassing details about various products within the Keepnet ecosystem. It includes the Dashboard, Threat Intelligence, Awareness Educator, Phishing Simulator, Vishing Simulation, Callback Simulator, Email Threat Simulator, Smishing Simulator, Quishing Simulator, Threat Sharing, Phishing Reporter, and Incident Responder. Each product's functionalities, features, and usage guidelines are explained to help users understand and utilize them effectively.
To ensure a seamless experience, our documentation is structured in alignment with the Keepnet product interface. Starting with the Dashboard, users can navigate through each section, such as Threat Intelligence, Awareness Educator, and beyond. This intuitive structure allows users to easily find relevant information and logically progress through the documentation.
Should you require assistance using our documentation, we recommend carefully reading the instructions and guidelines. The outlined steps and best practices will help you derive the most value from available resources. If you need further support, our support team is available to address any specific queries or concerns. Reach out to us, and we will be more than happy to assist you in making the most of our documentation and achieving your desired outcomes.
Thank you for choosing Keepnet as your cybersecurity partner. Together, we can create a safer digital environment for businesses worldwide.
Build your security culture to STOP phishing!
It is essential that your employees are able to open all emails sent via Keepnet platform for you to accurately measure how your employees behave when faced with evolving social engineering threats.
To ensure emails are delivered in Google Workspace, you have 2 options:
Direct Email Creation (recommended)
You only need to do one of these options. Customers do not need to complete both.
Direct Email Creation (DEC) is a feature that connects to your O365 or Google Workspace with a few required API permissions. This feature creates the phishing simulation email directly in the user’s inbox instead of sending the emails over SMTP protocol.
Key Benefits:
Remove false positives that whitelisting tools cause when analyzing links
Eradicate maintenance and challenges of whitelisting for the purpose of email delivery (you may need to whitelist in your URL protection solutions such as Defender or ZScaler)
Very simple and quick setup (can be completed in a couple of minutes!)
Whitelisting is common practise for ensuring emails from specific domains are delivered successfully to the inboxes of your employees. Whitelisting is a method used by many organisations to ensure emails are successfully delivered.
The key challenge our customers face with whitelisting is email analysis tools often open links within emails to check for maliciousness, impacting the accuracy of your reporting data. For example, it may show that your employees have opened the phishing link when they have not. This will directly influence who receives the behavioural-based training.
Most customers choose to deploy Keepnet's highly customisable Phishing Reporter Button. Our Keepnet button is fully customisable and allows customers to set up automatic positive messages to employees to reinforce secure behaviour.
Setup is super simple:
Step 1. Configure the Phishing Reporter
Step 2. Deploy Phishing Reporter
For our full technical documentation on Phishing Reporter Button, please see below
This page is currently under construction.
Your Target Users are the people who will receive simulation emails, training emails or any other emails from the platform. They will not have a login to Keepnet or require any access to the platform.
Email addresses are required for all users even for our Vishing, Smishing and Callback tools to successfully verify your email domains
⬇️ You have several options for adding target users:
(most common: add users from your identity management provider directly into Keepnet. Automatically add people who join your business and remove people who leave)
The document show step-by-step how to synchronize users' information from the Jumpcloud identity provider to the platform.
Please log in to Jumpcloud as an admin and follow the following steps.
Please create a group and assign users to the group for synchronization.
Go to SSO > + > and then click the Custom SSO SAML.
Enter a name for the Application name.
Go to the SSO submenu and enter a number like ‘1’ into the ‘IdP Entity ID’ and ‘SP Identity ID’ fields.
Go to the Identity Management submenu and then go to the bottom of the page to fill up the following fields.
SCIM Version: SCIM 2.0
Base URL: https://scim-api.keepnetlabs.com/scim
Token Key: Please enter the secret token.
Jumpcloud configuration has been successfully finished. You can proceed with the following step.
Go to the SAML application and then select Groups that contain users that will be synchronized to the platform and then click the Save button.
The users will be synchronized to the platform in approximately a few minutes.
✅ You have now added your first Target Users. Now you need to successfully ➡️
This is only relevant for customers who have purchased the Incident Responder module or xHRM package.
The Incident Responder analyses a suspicious email, and according to the results, it takes action at the inbox level. The product also analyses the URLs, IPs, and Files with the engines of different technologies it is integrated where it enables an institution to acquire the technologies that it doesn’t have.
There are 2 steps for setting up the Incident Responder:
- Keepnet will automatically tell you whether a suspicious email is malicious or not
- Keepnet will be able to remove malicious emails from all employees inboxes
Explore our quick step-by-step videos to get the most out of the Smishing Simulator. From sending campaigns to customising templates and reviewing reports, these guides make it easy to launch & manage
Without this step, your employees will successfully receive the test phishing email but not be able to open the test phishing link without your browser security notifying the user that it may be a suspicious link. For the highest accuracy when measuring employee behaviour, you will need to whitelist domains in your browser and other security solutions.
Below are quick links for you to follow the relevant steps:
It is essential that your employees are able to receive all emails sent via Keepnet platform for you to accurately measure how your employees behave when faced with evolving social engineering threats.
To ensure emails are delivered in Microsoft 365, you have 2 options:
(recommended)
You only need to do one of these options. Customers do not need to complete both.
For successful analysis, you need to integrate one or many Threat Intel Partners. By integrating Threat Intel partners you will automate identifying malicious emails. Each email reported through the Phishing Reporter add-in will automatically be analysed for malicious content via multiple integrations.
Navigate to Incident Responder > Integrations. Click the blue New button. You can find all our Threat Intel partners under Integration Type.
The Targeted Approach is ideal for organisations that want to focus on specific threats or high-risk areas. With this method, you choose exactly which scenarios to send, giving you complete control over your campaign content and timing.
You can run campaigns in one of two ways:
Distribute scenarios across your target group
Distribute several specific scenarios to employees at the same time.
The Hyper-Personalisation feature allows you to send phishing simulation scenarios in each recipient’s preferred language. If a preferred language is not set, the system will default to the company's preferred language.
Before launching a campaign with this feature, you must assign preferred languages to users:
Navigate to Company > Target Users.
Callback Phishing
With over 250 callback scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts.
Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites!
Please Contact Support Team
IT: Temporary IT support changes
Amazon: Order Confirmation
Slack : Reset your password
Microsoft Defender: Thank you for your auto-payment
Employee Survey Reminder
Google: Google Workspace Account Recovery
The Randomised Approach is ideal for organisations looking to raise awareness broadly while collecting meaningful data on employee responses. Each employee receives a unique, randomly selected scenario from categories you’ve chosen, keeping campaigns relevant to their role or department.
You can automate campaigns to run weekly, bi-weekly, monthly, or quarterly, keeping your approach scalable without additional manual work. This ensures you consistently gather data on how employees respond to phishing threats, without the risk of employees alerting each other.
Key benefits:
Broad awareness: Employees receive different scenarios from selected categories, making training realistic and engaging.
SMS Phishing
With over 6,500 smishing scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts.
Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites!
New Device Policy
Company Survey
Update MFA MS
Dropbox Verification Notice
LinkedIn Profile Notification
LinkedIn Unusual sign-in detected
Apple Apple ID login
Suspicious Login Detected
Amazon Delivery Failed
Voice Phishing
With over 5,000 vishing scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts.
Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites! Get these scenarios in your local accent by duplicating the scenario and change the AI voice 🤖
CEO Message
PayPal Fraud Alert
Tax Refund Support
Your Tax Refund is Ready: Confirm Now and Get Your Money!
Apple Gift Card Promotion
Bank Fraud Alert
Keepnet makes it simple to deliver security awareness programs that feel authentic and accessible to every employee, anywhere in the world. Our multi-language features ensure your training and phishing simulations are effective across regions, cultures, and languages -without added complexity.
– Set up enrolments so employees can choose their preferred language directly from the training email, ensuring inclusivity and higher engagement.
– Instantly adapt any phishing template into multiple languages, with AI adjusting tone, dates, currencies, and formatting for cultural accuracy. Multiple localisations can be completed at once for faster, more realistic campaigns.
Click the ‘Test Connection’ button to test the connection and then please click the ‘Activate’ button next to the ‘Test Connection’ button.
Edit the SSO rule and then go to the SSO menu to Disable the SSO at the bottom of the page.
Also note, you will need to ensure the Keepnet domains are whitelisted in other security solutions such as Defender and ZScaler who manage the security of URLs in the inbox and browser.
Direct Email Creation (DEC) is a feature that connects to your O365 or Google Workspace with a few required API permissions. This feature creates the phishing simulation email directly in the user’s inbox instead of sending the emails over SMTP protocol.Key Benefits:
Remove false positives that whitelisting tools cause when analyzing links.
Eradicate maintenance and challenges of whitelisting for the purpose of email delivery (you may need to whitelist in your URL protection solutions such as Defender or ZScaler)
Very simple and quick setup (can be completed in a couple of minutes!)
Whitelisting is common practise for ensuring emails from specific domains are delivered successfully to the inboxes of your employees. Whitelisting is a method used by many organisations to ensure emails are successfully delivered.
The key challenge our customers face with whitelisting is email analysis tools often open links within emails to check for maliciousness, impacting the accuracy of your reporting data. For example, it may show that your employees have opened the phishing link when they have not. This will directly influence who receives the behavioural-based training.
Together, these features give you the flexibility to run global programmes that resonate locally—helping you strengthen security awareness across your entire workforce.
On the first settings page, Add-in Settings, is where you can customise how the Phishing Reporter appears in your employees inbox including:
Logo
Button labels
Messages users receive when reporting emails
Your Email Settings page is where you select who will be notified about suspicious emails and the email you want them to receive. You can add as many emails as you would like here.
Proxy: If users are accessing the internet through a proxy, you can enable the plugin to detect the proxy configuration of the computer where it will be installed.
API: If you require any changes to be made to the API settings, please let our support team know on [email protected].
Enterprise Vault: When selected, the suspicious email can be searched in the user's backup emails during the investigation. (Only for MSI phishing reporter add-in)
The Diagnostic Tool provides information about the status of the add-in. For example, if the add-in has been disabled by a user, the Diagnostic Tool can be used to ensure automatic activation or make system admins aware.
The Diagnostic Tool is designed only for use on Outlook Desktop add-in with the MSI extension. When the add-in is distributed over Office 365 or Google Workspace, it is automatically installed and active for all users.
✅ You have now customised the Phishing Reporter.
Now, go to Deployment ➡️

Your license model determines which widgets are available on the dashboard.
The Top Posts box shows the five messages shared on the Threat Sharing platform that have generated the most interaction. Click on the title of a post to see more information.
The All button at the top right of the box will take you to the Threat Sharing section.
The Recently Posted Threats box displays the title of the last five posts shared on the Threat Sharing platform, the name of the malicious content in the post, and the name of the community where it was shared.
The All button at the top right of the box will take you to the Threat Sharing section.
The widgets available will vary depending on your license type, role, and permissions.
Any actions you take will only be valid for your system users. Other users will see their own settings.
You can add, remove, or relocate a widget by clicking on the Edit Dashboard button at the top right. Once you have made the change, click Save Changes.
Select the widget you want from the Edit Dashboard > Add Widgets menu and click Save Changes to confirm the action.
When you click Edit Dashboard, an ‘X’ icon will be visible at the top right of each widget. Click the ‘X’ to delete a widget and click Save Changes to confirm the action.
Click the Edit Dashboard button and drag and drop the widget to the desired location. Click Save Changes to confirm the action.
Responding swiftly to email attacks is significant, as each passing minute escalates the threat. On average, it takes 9 hours to detect and remove a malicious email, significantly amplifying the risk. Keepnet's automated phishing incident response tool allows businesses to identify and respond to email attacks in minutes
Setup RequiredDefault Behaviour of Incident ResponderPopular CustomisationsWith thousands of ready-to-use simulations across phishing, quishing, callback, vishing, and smishing, you have a wealth of options when shaping your organisation’s security awareness strategy. To make things easier, our Customer Success team has hand-picked their favourite and most effective scenarios from each simulator. These recommendations highlight the scenarios most loved by customers across industries and use cases, helping you quickly identify impactful options and streamline your process as you get started with Keepnet.
PhishingQuishingCallbackSmishingVishingYou can install free threat intel partners or if you already have subscriptions for paid versions, you can integrate these too! All links to install all free and paid for intel threat partners below
Free Intel Threat Partners
Paid Intel Threat Partners
Add as many Threat Intel Partners as you would like. The more you integrate, the more thorough your analysis of suspicious emails.
Please follow the steps for Mail Configuration for your email provider:
Pre-schedule a campaign for the year
Select all scenarios you want to use in advance.
Run them monthly (e.g., scenario 1 in month 1, scenario 2 in month 2, etc.).
Saves time by automating the campaign while ensuring full coverage of targeted threats.
Key benefits:
Focused impact: Target high-risk employees or departments with scenarios that matter most.
Industry-relevant exposure: Ensure every employee has experienced and seen examples of the most common phishing threats in your industry — for example, DocuSign, Microsoft notifications, or reset password scams — so your team recognises these threats in real life while you collect valuable response data.
Actionable insights: Collect data on responses to specific threats, helping to prioritise training and awareness efforts.
Getting started:
Manual Upload: Assign a preferred language to each user via CSV or manually add for each employee
Sync with Entra ID / AD: Populate the Preferred Language property in Entra ID and Keepnet will pull this through automatically
To launch a campaign using this feature:
Navigate to Phishing Simulator > Campaign Manager.
Click the + NEW button to create a new campaign.
In the Hyper-Personalization section, select:
"Send in the target users’ preferred language" → The system will send scenarios in each recipient’s preferred language. If no preferred language is set, the company's default language will be used.
Click Next to proceed through scenario selection, target groups, and delivery settings.
Click Launch to start the campaign.
If a scenario template is available in the user's preferred language, they will receive that version.
If a scenario template is not available in the user’s preferred language, the system will send the scenario in the company’s default language.
If no scenario template matches either the user's preferred language or the company’s default language, the system will prompt you to select appropriate language versions before launch.
This ensures that users receive scenarios in the most relevant language for them, improving the effectiveness of phishing simulations.
Data-driven: Collect consistent insights into employee behaviour to inform future campaigns.
Suspicious Activity on Your Google Account
Slack Security Alert
MS Teams Invite
The document show step-by-step how to synchronize users' information from the Okta identity provider to the platform.
Please make sure to set up the mandatory settings from the ‘Getting Started’ page in this document before proceeding to the following step.
Please log in to https://www.okta.com/ as an admin user.
Click on Applications and go to Applications from the left menu.
Click on the Browse App Catalog and search SCIM 2.0 Test App (OAuth Bearer Token) and then click Add button.
Enter a name for the application like My SCIM Integration and click on the Next button.
Choose SAML 2.0 with the default settings and click on the Done button.
The application is now created successfully, go to the Provision menu and click the Configure API Integration button and then enable the API Integration option.
Tenant URL: https://scim-api.keepnetlabs.com/scim
Secret Token: Enter the token which was created on the platform.
Okta configuration has been successfully finished. You can proceed with the following step.
Go to the Assignments menu and click on the Assign button to assign Users or Groups to this SCIM application which will be synchronized to the platform.
To import user(s) or group(s), click on the Assign button to synchronize users or groups to synchronize to the platform.
✅ You have now added your first Target Users. Now you need to successfully ➡️
This video tutorial shows the documentation steps for synchronizing users' information from the Okta identity provider to the platform.
By setting up a SCIM integration, you can ensure all new employees are added in auto-enrolled training and phishing simulations. There are 2 key steps to setting up your SCIM integration:
Get your secret token
Complete setup in your AD portal
Go to Company > Company Settings > SCIM Settings page. Click the ‘+New’ button to create a SCIM setting.
Some of our customers add custom fields to add information in addition to email, first name, last name, department and phone number. If you would like to set this up click here, otherwise you can skip.
Group Name: If you would like to synch all users to one target group please select the group here. You can leave empty and group by department instead.
Grouping Criteria: You must select one of these
Select a SCIM field to determine user groups: Group users by department (or a custom mapped field such as location). This will group all users by the Entra ID property "Department"
Synchronise groups with identity management platform: Groups are mirrored directly from Entra ID. If you select a group called "Keepnet UK" on Entra ID, this group will be named exactly the same in Keepnet and contain the exact same users.
Click Save and make sure to copy the unique token information.
✅ You can now use the following shortcuts to complete the final settings on your identity provider platform.
Welcome to the Customer Success Hub—your one-stop destination for guidance, best practices, and resources to help you get the most out of Keepnet. This self-service model is designed to put success at your fingertips, so you can find the answers you need quickly and start seeing results right away.
Inside, you’ll find:
🎥 How-to Videos – Quick, practical walkthroughs to guide you through common tasks.
🎯 Campaign Strategy Guide – Expert advice on planning and running effective security awareness campaigns.
💙 – Hand-picked simulations from our Customer Success team, showcasing the scenarios customers love most.
🌍 – Tools to run global programmes with local impact through training, localisation, and hyper-personalisation.
Our goal is to make it easy for you to achieve success—whether you’re just getting started or scaling your awareness efforts globally.
Keepnet utilizes a tracking pixel to monitor when users open phishing simulation emails. This tracking pixel is embedded in all phishing simulation emails sent through the platform. When the email is opened, the pixel sends a response to Keepnet, logging the open event.
It is important to note that opening a phishing simulation email is not considered a failure and does not impact the user’s gamification score. However, phishing emails may be marked as "opened" automatically in the following scenarios:
Email Reported: If a user reports the phishing email using the Reporter Button, the email is automatically logged as opened.
Phishing Failure: If a user clicks on a phishing link or opens a malicious attachment within the simulation email, the system will mark the email as opened, even if the tracking pixel does not load.
This tracking mechanism ensures accurate monitoring of user interactions while maintaining fair evaluation criteria in phishing awareness programs.
In some organizations, email client settings prevent images from being automatically downloaded. When this occurs, Keepnet's tracking pixel cannot load, and email opens will not be recorded in phishing simulation reports.
If your organization blocks automatic image downloads, you can enable email open tracking using one of the following methods:
You can add phishing email senders to a safe senders list to allow all email images to load. This method is not recommended for the following reasons:
There is a limit to the number of safe senders you can add, and Keepnet sends simulations from many different email addresses. Our phishing simulation email addresses are also subject to change without notice.
Your users may be able to identify phishing simulation emails due to all of the images loading, while other external, non-Keepnet emails would not load images.
You can create a Group Policy Object in Active Directory to update the Trusted Zone in Outlook to allow tracking pixels to load without allowing all other phishing simulation email images to load. The steps to complete this are detailed below:
Navigate to your Local Group Policy Editor.
You will find the correct Group Policy to edit by navigating to User Configuration > Windows Settings > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Security Page.
Double-click the Site to Zone Assignment List policy to modify the policy.
We recommend sending a phishing test campaign to yourself once these settings are saved so you can ensure opens are being tracked successfully.
Explore our quick step-by-step videos to get the most out of the Phishing Simulator. From sending campaigns to customising templates and reviewing reports, these guides make it easy to launch & manage
We have over 16,000 templates you can start using immediately. However, many customers love to customise the templates available for their own business. Alternatively, some customers have emails they want to import to Keepnet to use as a Phishing scenario.
These step-by-step quick tutorials show you how to send training, how employees access training, how to view reports, deliver in multiple languages and automating training for new users or groups.
In order to use the Phishing Reporter add-in in the Exchange environment, your platform must meet the following requirements.
Exchange 2013 - version (15.0.847.32) or above
Exchange 2016 - version (15.1.225.42) or above
Exchange 2019
To deploy the Phishing Reporter add-in, follow the steps below.
Log in to the Exchange Admin interface.
Go to Exchange Admin Center > Organization > Add-ins (called Apps in some versions)
Click the (+) button and select Add from file. Install the Phishing Reporter .xml file that you previously downloaded and click Next.
It may take up to 12 hours for the add-in to be displayed on users' email applications. Users may need to relaunch their email applications.
✅ You have now deployed the Phishing Reporter. Next step is to (only for customers who have purchased the Incident Responder or SOC package)
Keepnet makes it simple to deliver training in the languages your employees are most comfortable with. This guide will walk you through setting up training enrollments that allow employees to choose their preferred language directly from the enrollment email. You’ll also learn how to configure which languages are available for each training, ensuring a seamless experience that supports inclusivity and accessibility across your organisation.
Go to Company > Company Settings > Notification Templates
Search "Enrollment" to bring up all 7 Enrollment templates
Learning Path Enrollment Reminder
Learning Path Enrollment
Infographic Enrollment
Poster Enrollment
Duplicate each one to be able to edit and add the Language Selector option
Replace the "Enroll" button with the "Training Language Selection" merge tag
Repeat for all 7 enrollment templates
Top Tip: Some customers use this opportunity to customise with their logo and branding!
Go to Awareness Educator
Select the training module you would like to send (work best for multi-language modules)
Click on the 3 dots & click "Send Training"
Under Content Language:
An employee reports a suspicious email using the Keepnet Reporter Button or Native Microsoft Report button
Keepnet analysis the reported email for malicious content in seconds using 5+ integrations simultaneously
Keepnet automatically shares the analysis result with the employee via email
When analysis result is “Malicious”, Keepnet starts an automatic investigation to find all instances of the malicious content
Once investigation is complete, Keepnet System Admins receive Investigation Report
Keepnet System Admin can then log into Keepnet and delete all instances of malicious emails in a few clicks
Traditional URL Phishing via Email
With over 16,000 phishing scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts.
Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites!
Policy Announcement – Microsoft Teams
Microsoft: SETTINGS EXPIRE TODAY
New Message on Teams
Someone Sent a Document
Sharepoint: IT Support shared “To be completed” with you
Microsoft Teams: Director added you to a project team!
Google Docs: You were mentioned in a comment
Google: Suspicious sign-in prevented
Google: Shared Spreadsheet
DocuSign: Your Document Has BeenCompleted
DocuSign: Signature Request
IT: Back Up Your Emails
LinkedIn: Deactivation Request
Support Desk Alert
HR: All Employee Meeting
Mimecast: You have new held messages
Your Benefit Program Account has invalid information
New Employee Impersonation
Action Required: Storage Quota Exceeded
CEO Fraud: Supplier Payment Approval
CEO Fraud - Payroll confirmation
CEO Fraud - Request IT Help, Locked Out
CFO: Financial Report
HR: Annual Employee Growth Report
Sharepoint: New shared document
Sharepoint: IT Support shared “To be completed
OpenAI: Invited to a ChatGPT Team
This section explains how to structure phishing awareness campaigns using Keepnet. It introduces three approaches — Randomised, Targeted, and The Blend — showing how each helps you:
Deliver relevant scenarios to employees
Scale campaigns efficiently
Collect meaningful data on how employees respond to phishing threats
To help you hit the ground running, our Customer Success team has hand-picked the most popular and effective phishing campaigns. These examples give you tried-and-tested inspiration to build an engaging programme that develops employee awareness from day one.
You can explore each approach in detail using the links below, including step-by-step guidance and tutorial videos for setting up campaigns:
Quick visual summary:
Use this page as your starting point to decide which approach works best for your organisation and to access tutorials for each campaign type.
Platform administrators must whitelist dash.keepnetlabs.com and api.keepnetlabs.com on content filtering proxy solutions to use the products successfully.
If you have completed white labeling, it is sufficient to whitelist the platform domain name that will be used to access to platform and api.keepnetlabs.com address.
The domain names of the should be whitelisted with content filtering (proxy) solutions to make sure that the domains can be accessed by the target users. If the target users can't access the phishing link in the network, the simulated phishing campaign might not be successful.
You can find the phishing simulation domains by logging into the platform and then go to Phishing Simulator > Settings > Domains page.
System administrators may upload the target users' first name, last name, email address, department, or such other information to the platform; however, because can be very sensitive, the platform domain information should be whitelisted to ensure DLP allows you to upload these pieces of information to the platform.
✅ You have now Whitelist Domains so your target users can successfully open Keepnet email links. Please also Whitelist in your security solutions if you haven't already.
Next step is to ➡️
Phishing Reporter is an add-in that allows users to easily report a suspicious email to cyber security teams. Quick, comprehensive analysis and response can be provided when used in conjunction with the Incident Responder.
Integrate the Native Microsoft Reporter Button with Keepnet
Use your existing reporter button whilst capturing who is showing secure reporting behaviour across your phishing simulations
Use our highly customisable Keepnet Reporter Button
Customise the language employees see when reporting and set up positive reinforcement messages for employees whilst still being able to redirect reported emails to your SOC team
We have a you can use to share the key benefits and expectations of your employees using this tool.
Using the platform's APIs, target users may be effortlessly migrated. The API endpoints that are required are detailed below.
Instructions for adding target users using an API
POST /api/target-users
Go to the Swagger .
Click the Authorize button on the top right side of the page.
Complete the authorization step with the Client ID and Client Secret key that you created on the platform.
Make sure that the api1 option is checked (✓) on the Scopes section.
Then use this endpoint to add a new target user to the platform.
Searching for a user using API
POST /api/target-users/search
Go to the Swagger .
Click the Authorize button on the top right side of the page.
Complete the authorization step with the Client ID and Client Secret key that you created on the platform.
Make sure that the api1 option is checked (✓) on the
Editing Target Users using API
PUT /api/target-users/{resourceId}
Go to the Swagger .
Click the Authorize button on the top right side of the page.
Complete the authorization step with the Client ID and Client Secret key that you created on the platform.
Make sure that the api1 option is checked (✓) on the
✅ You have now added your first Target Users. Now you need to successfully ➡️
This document provides a step-by-step guide on how to synchronize users' information, such as First Name, Last Name, Email Address, Department Name, etc., from the Google Workspace email server to the platform.
You must have an admin account to set up the Google Workspace integration.
Please follow the steps below.
Go to Company > Company Settings > Google User Provisioning page.
Click the CONNECT TO GOOGLE button.
Click Continue and then click the Allow button to grant the requested permissions.
After successful integration, please proceed with the following configurations.
In the Select Sync Source field, choose one of the following options:
Sync Organizational Units (OU): Sync users from the organizational units. Select all organizational units or choose the ones you wish to sync users from.
Sync Groups: Sync users from group(s) that are from your Google Workspace. Select all groups or choose the ones you wish to sync users from.
In the Select Sync Method field, choose one of the following three options:
Sync all users to target users: This will sync all users from the selected organizational units or groups.
Sync all users to a target group: This will sync all users from the selected organizational units or groups and add them to the selected target group on the platform.
Sync users and create a matching group:
Now, click the START SYNC button to begin synchronization.
The synchronization may take some time depending on the number of target users. Once the synchronization is complete, you can view the synced users on the Company > Target Users page.
The synchronization automatically repeats every 24 hours to ensure all users are updated with the latest information from Google Workspace, or to remove any target users who are no longer available in Google Workspace.
If you wish to sync the user's latest information to the platform immediately without waiting 24 hours, please click the SYNC NOW button.
If you no longer need to sync users from Google Workspace to the platform and wish to remove the integration, you can follow the steps below.
Once the integration is removed, the synced users will be deleted from the platform.
Go to Company > Company Settings > Google User Provisioning page.
Click the Unlink Integration button to remove the integration.
The integration is now successfully deleted.
Customers can take any of our 16,000+ phishing templates - or your own custom scenarios -and localise them into any language of your choice. Keepnet doesn’t just translate; it adapts the entire email, including subject lines, body text, currencies, dates, and tone, to feel natural and authentic for the target region. Multiple localisations can be completed at once, making it simple to launch truly global campaigns in minutes.
With optional human review for added quality assurance and unified reporting across all languages, you can scale phishing simulations faster, more cost-effectively, and with greater realism than ever before.
For example:
Go to Phishing Simulator > Phishing Scenarios > Email Templates
Duplicate or Edit any Phishing Template
On the Email Settings page, click on the Localize button
Select one or many languages you'd like the template to be localised in
Once complete, use the drop-down on the top left hand side to review the localisation of each language
Save
Top Tip: Add this template to a Scenario to send to your employees
To complete this procedure, you must have security administrator privileges with the Microsoft Security & Compliance Center or be a member of the Microsoft Exchange Online Organization Management administrator group.
Note the IP addresses to be allowed.
Log in to your exchange admin center.
From the left sidebar menu, go to Mail flow > Connectors.
Click Add a connector.
Select Partner organization in the Connection from the section.
Give the connector a name and click Next.
In the Authenticating sent email window, select the option that states By verifying that the IP address of the sending server matches one of the following IP addresses that belong to your partner organization.
Enter the IP addresses and click Next.
Uncheck the TLS option stating Reject email messages if they are not sent over.
Click Next, then click Save to complete the process.
You must complete the following steps once the connector is defined.
Go to the Mail flow > Rules page in the left sidebar menu.
Click the + icon on the screen and select Bypass spam filtering.
In the New rule window, give the rule a name and select The sender is ... > IP address is in any of these ranges or exactly matches.
Enter the IP addresses and click
✅ You have now Whitelist Domains so your target users can successfully open Keepnet email links. Please also Whitelist in your security solutions if you haven't already.
Next step is to ➡️
Our customer success team have collected some common customer queries and added all the answers to these queries here in this section!
Q: When I try to log-in, I get a "invalid token" error
A: This error message appears when customers try to access keepnet using their "account creation" link on the original email you received when joining Keepnet. Instead, navigate to dash.keepnetlabs.com to login and you won't have any issues!
Q: I added the new Just-in-time Red Flags landing page as a 2nd landing page for a data submission campaign. However, the email template didn't pull through when I tested.
A: Great idea! When you copy the HTML of the Red Flags landing page to use as a 2nd step, you will also need to copy the custom javascript code. This is the code which loads the email template use in the campaign with the red flags highlighted. Below is a 5 minute video on how to resolve this!
https://www.loom.com/share/79889043685147479f35c80696442723
We're also going to be improving the customer experience for adding 2nd landing pages which will allow you to select an existing landing page for page 2 without copying HTML at all!
Q: What is Bot Activity and why might I see it on my Campaign Report?
Bot Activity means something has scanned the link on your phishing email. This could be a security tool, a chrome extension or an analysis engine. Keepnet has highly sophisticated methods of detecting bot activity to ensure your reports only include the human activity of your employees. Here is an explainer deck which covers each Bot Activity type in more detail 👇
Q: How do I remove users from the platform if I've used SCIM to pull in from Entra ID?
To remove users from Keepnet when connected to Entra ID, please go to portal.azure.com and find the Enterprise Application you made for Keepnet SCIM. Navigate to Users & Groups and manage users from here. Add and remove users to Keepnet from this application. Microsoft updates Keepnet every 40 minutes!
Our video guides walk you through customising the Phishing Reporter button, testing deployment, and rolling it out across your entire organisation with ease.
The Blend Approach combines the strengths of both the Randomised and Targeted methods, giving organisations a balanced, scalable, and highly effective phishing awareness programme.
With this approach, you run:
Monthly randomised campaigns
All employees receive unique, randomly selected scenarios from categories you choose.
Keeps awareness broad and realistic while preventing employees from alerting each other.
Quarterly targeted campaigns
Focus on high-risk users, departments that need extra awareness, or key functions such as HR, Finance, and IT.
Ensure everyone in these groups experiences and sees examples of the most relevant phishing threats for their role.
Key benefits:
Comprehensive coverage: Combines broad awareness with focused attention on high-risk areas.
Scalable: Automate randomised campaigns while scheduling targeted campaigns at key intervals.
Industry-relevant exposure: Employees see the most common phishing threats in your industry — for example, DocuSign, Microsoft notifications, or reset password scams — reinforcing recognition and response skills.
Actionable insights:
Getting started:
This document will provide information on how to start an Email Threat Simulator scan to the email inbox using a Google Workspace account.
To use the Email Threat Simulator with a Google Workspace email account, the app requires a password.
Follow the steps to create the app password for the Google Workspace account.
Go to your (for test mail address)
Select Security.
Under “How to sign in to Google”, select 2-Step Verification.
At the bottom of the page, select App passwords.
Enter a name to help you remember where to use the app password.
Select Create.
Copy and save the app password for use in the Keepnet interface.
The app password is a 16-character code generated on your device.
Select Done.
This section describes the steps to start a scan with Google Workspace in the Email Threat Simulator product.
Go to Email Threat Simulator > Scans page from the left menu on the platform.
Click on the +NEW button to start a new simulation.
Read the warning message and then click on the “I Understand” button.
Fill in the Test Email Address field.
Use the document to understand the details of the scan report.
The Dashboard is the first page that the system administrator sees after logging into the platform. This section explains how to use the Dashboard widgets to enhance functionality to suit your needs.
Click the AI-Powered Assistant icon (...) at the bottom right of the Dashboard to get help about any information.
The following video tutorial contains information about how to manage dashboard.
By integrating Threat Intel partners you will automate identifying malicious emails. Each email reported through the Phishing Reporter add-in will automatically be analysed for malicious content via multiple integrations.
There are 2 steps to Integrating Threat Intel Partners:
Create a new integration
Follow relevant steps to install each threat intel partner
Navigate to Incident Responder > Integrations. Click the blue New button. You can find all our Threat Intel partners under Integration Type.
You can install free threat intel partners or if you already have subscriptions for paid versions, you can integrate these too! All links to install all free and paid for intel threat partners below
Free Intel Threat Partners
Paid Intel Threat Partners
Add as many Threat Intel Partners as you would like. The more you integrate, the more thorough your analysis of suspicious emails.
This section will help you comprehend and utilize the fundamental features within the Phishing Scenarios page. Below, we have provided shortcuts to the parameters within the Phishing Scenarios page.
Our Email Threat Simulator is an easy way to see how many real threats are currently able to bypass your email security. Quickly review which ones aren't blocked and take action to block these in the future. Each time there is a new threat vector, we will add this to Email Threat Simulator so you can consistently stay informed about which active threats can bypass your current SEGs.
Our Customer Success team have put together a page of resources to help you hit the ground running with Keepnet. Learn how to setup your campaigns and enrollments to align with you business goals!
Our collection of short, step-by-step video guides is designed to help you get the most out of Keepnet’s security awareness tools. From setting up and running phishing simulations, to delivering engaging training, through to deploying the Phishing Reporter button, each video provides clear, practical guidance to make every stage simple and effective.
To complete this procedure, you must have security administrator privileges with the Microsoft Security & Compliance Center or be a member of the Microsoft Exchange Online Organization Management administrator group.
Note the to be allowed.
Log in to your exchange admin center.
QR Code Phishing
With over 5,500 quishing scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts.
Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites!
Microsoft: SharePoint has been set up for your account
Microsoft: Re-authenticate your account
LinkedIn Your organization can join LinkedIn Learning
DocuSign: Your Document Has Been Completed
Microsoft Teams : Urgent: Video Meeting Request
Microsoft: SharePoint has been set up for your account
Google Account Security Verification Required
Congratulations! You've Won a Reward as an Active Google User
This article section describes how to integrate the module with Google Workspace, Exchange, or Microsoft Office 365 email services. It's important to follow the steps accurately. Please contact your email server administrator if you don’t have the required permissions to make these configurations.
The Incident Responder module investigation tool can detect malicious emails in user inboxes and remove them automatically or can be removed by the admin as well.
Server-based integration with your email service provides the most comprehensive protection. While email investigations can be conducted with the Phishing Reporter plug-in, the user must have Outlook open and the plug-in active for the investigation to be successful. If the Outlook application is closed for any reason, a complete investigation can only be performed using a server-based integration.
Our requires a test account for making and reporting the tests listed here. This document contains sample configurations for making possible security and reliability checks with this test account.
The test account will only receive email and will not be able to send mail to any internal or external email address except us. This is a safe configuration option that will prevent potential violations.
Customers who use an Exchange email server must create a restricted email account. Customers who use Google Workspace, Microsoft 365, or other services may skip this step.
Use the Exchange Server PowerShell administrative interface to create a test account with the command below.
Our allows institutions to defend against major attack vectors. In recent years, the number of target-oriented attacks has increased significantly. Most often, the targets of attacks are large corporations, government agencies, and political organizations. However, any institution that collects data seen as valuable faces a risk of cyberattack. Awareness of potential exposure and preparation to resist an attack are critical in today’s world.
Your license model determines which widgets are available on the dashboard.
This widget shows a summary graph of the overall performance of your phishing campaign for the last 6 months. The graph is organized by the number of users(Y-axis) and date(X-axis). The widget represents how many users have fallen to the phishing campaign for Click Only, Data Submission, and Attachment types of campaigns.
You can view your phishing campaign reports by clicking on the Campaign Reports shortcut.
It is essential that your employees are able to receive all emails sent via Keepnet platform for you to accurately measure how your employees behave when faced with evolving social engineering threats.
To ensure emails are delivered in Microsoft 365, you have 2 options::
Enable the policy by selecting the Enabled option.
Under the Options area, click Show.
From the Show Contents window, enter the phish link domain used in your test in the Value Name. You can also use wildcards in your entry to indicate a phish link subdomain.
For a complete list of phish link domains, navigate to the Phishing > Settings > Domains tab in the Keepnet Platform.
For the Value, enter "2", which corresponds to "Trusted Zone".
Click OK.
Navigate to Outlook.
Select Options > Trust Center > Trust Center Settings. Click the check mark to Allow downloads from Websites in this security zone: Trust Zone.
Note the IP addresses to be allowed.
Sign in to Google Admin.
Select Apps > Google Workspace > Gmail from the left sidebar menu.
Go to the Spam, Phishing, and Malware page.
Select the Email allowlist tab and click the Edit button.
Add the IP addresses that are listed here.
Click the Save button.
Go back to the Spam, Phishing, and Malware page.
Select the Inbound Gateway option and click Enable, if not enabled.
Add the IP addresses and click Save.
Select Automatically detect external IP if not already selected.
WARNING: Leave the option of Reject all mail not from gateway IPs unchecked.
This option must be 'unchecked'. Do not enable this option!
Select the option of Require TLS for connections from the email gateways listed above.
Click Save to complete the process.
✅ You have now Whitelist Domains so your target users can successfully open Keepnet email links. Please also Whitelist in your security solutions if you haven't already.
Next step is to Setup your Phishing Reporter ➡️
This widget shows the name of the last five phishing campaigns, the launch date of the campaign, and the current stats (no response, clicked, opened, submitted). You can go to report the campaign by clicking on the name of the campaign.
You can click ALL shortcuts to go to the campaign reports page to view all phishing campaigns.
This widget shows the names of the top five phished users for all the time, their email addresses, and the number of times they’ve been phished. The number of times is unique. As an example, if it says five that means the user received five unique phishing campaigns and phished to all five campaigns.
This widget shows the names of the last five phishing campaigns that have the most successfully phished users and the number of phished users. You can view the campaign report by clicking on the name of the campaign.
This widget shows the names of the top five users that report phishing simulation emails, the email of the user, and the number of reported emails. It won’t matter if the user phished and then reported the email or not phished and reported the emails, both actions will be shown on the widget.
The campaign reports which has been Marked As Test will not be included in the widgets.
Randomised
Unique, randomly selected scenarios
Capture realistic employee responses while preventing alerting
Targeted
Specific scenarios selected for impact
Focus on high-risk areas and key threats
The Blend
Combination of both approaches
Broad awareness plus targeted focus on critical users and departments
In the Do the following section, select Set the message header to this value ... > Set a message header and enter “X-MS-Exchange-Organization-Bypass Clutter” in the text field, and click OK.
Set the value information to true with the enter text option on the right.
Click Save to complete the process.
Check 'Automate with password' under Choose an Option.
In the Password field, enter the app password value you created before.
Click on the Next button.
In the Scan and Delivery step, set the delivery speed as desired.
Click on the Next button.
Confirm the User Agreement.
Start the simulation by clicking on the Save button.
Search ‘SCIM Provisioner with SAML (SCIM v2 Enterprise)' and click on the Add button.
Enter a name for the application like My SCIM Integration and click on the Save button.
Once you have successfully created the application, enter the application details and go to the Configuration menu and enable the API Connection.
Tenant URL: https://scim-api.keepnetlabs.com/scim
SCIM JSON Template: Please fill up this field with the following code.
{ "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": { "department": "{$parameters.department}", "manager": { "managerId": "{$parameters.external_manager_id}", "displayName": "{$user.manager_firstname} {$user.manager_lastname}" } }, "active": "{$user.active}", "emails": [ { "value": "{$user.email}", "type": "work", "primary": true } ], "meta": { "resourceType": "User" }, "name": { "familyName": "{$user.lastname}", "givenName": "{$user.firstname}", "formatted": "{$user.display_name}" }, "userName": "{$parameters.scimusername}", "id": null, "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ] }
SCIM Bearer Token: Enter the token which was created on the platform.
Click on the Save button the proceed.
Go to the Provisioning menu and enable the following options under the Workflow title.
Enable Provisioning.
Create User
Delete User
Update User
OneLogin configuration has been successfully finished. You can proceed with the following step.
You can find how to synchronize users or groups from here under the ‘Provisioning Users into Groups’ title.
✅ You have now added your first Target Users. Now you need to ensure they are able to receive emails from Keepnet successfully ➡️
Select Incident Responder > Mail Configurations from the left sidebar menu of the dashboard to create a new mail configuration or view the details of an existing configuration.
To set initial configurations, select the appropriate email server integration:
Office 365
Exchange
Google Workspace
The integration details are:
Name
Name of the configuration
Platform
Email service name to be integrated: Exchange EWS, Office 365, or Google Workspace
An active email address is required for testing purposes
Status
Status of the configuration: (running/not running)
Date Created
Integration start date
Action
Edit/remove the integration
Direct Email Creation (DEC) is a feature that connects to your O365 or Google Workspace with a few required API permissions. This feature creates the phishing simulation email directly in the user’s inbox instead of sending the emails over SMTP protocol.Key Benefits:
Remove false positives that whitelisting tools cause when analyzing links.
Eradicate maintenance and challenges of whitelisting for the purpose of email delivery (you may need to whitelist in your URL protection solutions such as Defender or ZScaler)
Very simple and quick setup (can be completed in a couple of minutes!)
Whitelisting is common practise for ensuring emails from specific domains are delivered successfully to the inboxes of your employees. Whitelisting is a method used by many organisations to ensure emails are successfully delivered.
The key challenge our customers face with whitelisting is email analysis tools often open links within emails to check for maliciousness, impacting the accuracy of your reporting data. For example, it may show that your employees have opened the phishing link when they have not. This will directly influence who receives the behavioural-based training.







This text has been prepared for customers to use who want to inform their users that Keepnet will be their new cybersecurity awareness training provider.
Replace [Company Name] with your company name
Dear [Team Name],
We’re excited to announce that your cybersecurity awareness training will now be delivered through Keepnet! This is part of our ongoing efforts to make training simple, effective, and easy to complete.
Here’s what to expect:
Emails from Keepnet: Look out for training invitations coming from [email protected].
One-click access: Simply click the “Enroll” button in the email—you’ll go straight into the training. No logins or passwords required.
Quick and interactive: Each session is interactive and takes only 3–5 minutes on average to complete.
Seamless experience: We’ve designed the process to make completing training as smooth and hassle-free as possible.
By completing these sessions, you’ll be helping to strengthen our company’s cybersecurity posture and stay ahead of potential threats—all in just a few minutes.
Thank you for taking the time to stay informed and proactive. Together, we can make [Company Name] safer for everyone.
This text has been prepared for customers to use who want to inform their users about the Phishing Reporter add-in.
Replace [Company Name] with your company name
Replace "Suspicious (Phishing) E-mail Reporter" with the name of your add-in
Dear Employees,
We’re excited to introduce a brand-new tool that puts the power of cybersecurity right at your fingertips: the “Suspicious (Phishing) E-mail Reporter”
What is it? This handy add-in adds a “Suspicious (Phishing) E-mail Reporter” button directly to your email menu bar. With a single click, you can report suspicious emails for our Information Security Team to investigate - helping us protect the company from potential threats before they become problems.
Why it matters:
Protect yourself and your colleagues: Reporting suspicious emails helps prevent security incidents that could affect everyone.
Strengthen our company’s cybersecurity: Timely alerts mean our security team can act quickly, keeping our systems safe.
Stay cyber-savvy: Each report helps you recognise phishing attempts and sharpen your awareness.
How to use it:
Spot a suspicious email.
Click the “Suspicious (Phishing) E-mail Reporter” button in your email menu.
Choose whether you’d like to delete the email.
That’s it! The Information Security Team will analyse the email and send you a quick update on what we found.
Thank you for helping us keep [Company Name] safe and secure. Spotting and reporting suspicious emails protects the whole team.
Stay alert and stay safe,
Organization administrator permissions are required to use the Exchange Management Shell.
New-Mailbox -UserPrincipalName “UserPrincipalName” -Alias “Mail Alias” -Name “Mailbox Account Name” -Database “Database Name” -OrganizationalUnit “” -ResetPasswordOnNextLogon $false –password (ConvertTo-SecureString -String “Password” -AsPlainText -Force)While on the Provisioning menu, go to the ‘To App’ menu and click the Edit button to enable the following fields. Please make sure to click the Save button after enabling the following fields.
Create Users
Update User Attributes
Deactivate Users.
Make this add-in available to users in your organization
Mandatory is always enabled
Users can't disable this add-in.
Click Save to complete the process.
Enrollment after Failed in a Simulation
Enrollment Reminder
Enrollment
To send in all available languages: tick "All Languages"
To send in only relevant languages: untick "All Languages" and tick only the languages of your choice
On the Summary Page - review the languages you have selected and the enrollment template
Then use this endpoint to search for a target user on the platform.
Then use this endpoint to edit a target user on the platform.
From the left sidebar menu, go to Mail flow > Connectors.
Click Add a connector.
Select Partner organization in the Connection from the section.
Give the connector a name and click Next.
In the Authenticating sent email window, select the option that states By verifying that the IP address of the sending server matches one of the following IP addresses that belong to your partner organization.
Enter the IP addresses and click Next.
Uncheck the TLS option stating Reject email messages if they are not sent over.
Click Next, then click Save to complete the process.
You must complete the following steps once the connector is defined.
Go to the Mail flow > Rules page in the left sidebar menu.
Click the + icon on the screen and select Bypass spam filtering.
In the New rule window, give the rule a name and select The sender is ... > IP address is in any of these ranges or exactly matches.
Enter the IP addresses and click OK.
In the Do the following section, select Set the message header to this value ... > Set a message header and enter “X-MS-Exchange-Organization-Bypass Clutter” in the text field, and click OK.
Set the value information to true with the enter text option on the right.
Click Save to complete the process.
✅ You have now ensured your target users will receive emails through Keepnet. Now you need to Whitelist Domains so your target users can successfully open Keepnet email links ➡️
The following video tutorial contains information about how to whitelist in Exchange 2013 or 2016 environment.
Your Dropbox Storage Is Almost Full
Action Required: Identity Verification
AnyDesk – Remote Desktop Solutions
You need to be an authorized admin to create a system user in this menu.
By clicking the + New button in the upper right corner, you can create a new system user.
For more information on some of the fields, see below:
This information is required for MFA purposes for System Users
Set users as active to allow them to access Keepnet Labs. Set system users as inactive to stop their access to Keepnet Labs.
Company Admin: Full admin access across the environment user has been added to.
Reseller: Full admin access across company they user has been added to AND all subsidiary companies.
You can create custom roles for your users and limit their access to various products on the platform. Please click here for more information
✅ You have now added your first System User! Now you need to Add your Target Users ➡️
This video tutorial will cover how to start scan, view report on the Email Threat Simulator.
Select Add users manually to add target users one by one. Alternatively, select Import from file to upload a CSV or XLS(x) file.
Select Group: If you haven't added any users yet, you will need to create a new group. Some suggested User Groups our customers use:
Test Group - for your cyber team to test phishing campaigns
All Users - to easily send campaigns to all employees
Department Specific e.g. Finance - to easily send targeted campaigns to specific departments
Step 4.
Field Mapping: Ensure the fields you are adding in are matched with the correct heading. For example, the user's first name matched with the heading, 'First Name'. Click Next once complete.
Step 5.
Import Users: Either pick the users you wish to add and click Import Selected, or click Import All to add all the users.
✅ You have now added your first Target Users. Now you need to ensure users are able to receive emails from Keepnet successfully ➡️


You can integrate your EWS environment with the Incident Responder product by following the steps below.
First, you must have or create a Microsoft user identity with either impersonation or delegation permission.
The user must have exchange admin permissions to configure these options.
Please refer to this document for information on how to create a service/admin user.
The impersonation option is recommended for setting up email server integration.
Impersonation gives one service account access to every mailbox in a database. This enables quick and easy investigation and response to an incident.
Restrictions may also be designated for the impersonation account, depending on the policies of the organization.
The following command can be used in the Exchange Management Shell to grant the impersonation privilege to a service account. This example assigns the service account [email protected] full access permission to all user mailboxes in the company.com organization.
The delegation privilege requires that permissions be added individually to each mailbox. The platform can access the mailboxes within the Exchange designated by the organization.
Restrictions may also be designated for the account, depending on the policies of the organization.
The following command can be used in the Exchange Management Shell to grant delegation privilege to a service account. This example assigns the service account user [email protected] full access permission to the specified ‘TargetUserName’ user mailbox.
To make sure that the integration is working, you can test it on the platform. Go to Incident Responder > Mail Configurations on the left sidebar menu of the dashboard and then click + NEW and choose the mail provider - in this case, Exchange EWS. Complete the following fields in the configuration table:
The integration details are:
The new configuration will now appear in the list of mail configurations if the test was successful.
If an X appears, it indicates there was a problem and the email server integration failed; please review the instructions.
Throttling policy is a control mechanism designed to preserve server reliability and functionality by limiting the resources consumed by a single user or application.
The Microsoft Exchange throttling policy is a default setting that restricts users on various client access protocols, such as MAPI, Activesync, OWA, POP3, etc., intended to prevent a potential crash or denial of service (DoS) via repeated requests.
A successful integration between Exchange and the Incident Responder will lead to hundreds of connections on the Exchange server when an investigation begins.
The investigation may be obstructed by the throttling policy. Therefore, the default throttling policy rights of the service user defined in the Incident Responder product should be expanded to avoid this problem.
You can use the command below in Exchange Management to view all of the available throttling policies.
Open the Exchange Management Shell and use the command below to create a new throttling policy.
Once you have added a new throttling policy, please enter the following command to set the permissions of the new policy.
User Use the command below to assign a throttling policy to a specific user. Replace “[email protected]” with the service user you designated in the Incident Responder.
This document shows how to synchronize users' information from the Azure AD identity provider to the platform. Please make sure to set up the mandatory settings from the ‘SCIM Integration’ page before following the below steps:
Log in to as an Azure Admin.
Click on Microsoft Entra ID.
Click on +Add at the top left hand side.
On the drop down select Enterprise Application.
Click on +Create your own application.
Enter a name for the application.
Select ‘Integrate any other application you don't find in the gallery (Non-gallery)’ option.
Click the Create button to create the application.
Select the ‘Provisioning’ menu from the left side.
Click the ‘New Configuration’ button and then enter the following information.
Tenant URL: https://scim-api.keepnetlabs.com/scim
Secret Token: Enter the token which was created on the Keepnet platform.
Click the ‘Test Connection’ button to test your configuration. If it’s successful, click the Save button to save settings.
When synchronizing users, customers have 2 options:
Synchronize all users in Entra-ID
Synchronize only assigned users and groups
Within the provisioning section, use the Settings drop down
You will notice it defaults to 'Synchronize only assigned users and groups'
Click on 'Synchronize all users and groups'
Save
Click on Users and Groups in the left hand menu under Manage
Click on 'Add users/groups'
Click on 'None Selected' on the left hand side
On the right, you will see a list of your users and groups populate
The final step is to start provisioning. Simply go to Overview on the left hand menu and select Start Provisioning on the top of the page.
Your users will sync from Microsoft to Keepnet every 40 minutes, ensuring any new employees who belong to one of your assigned groups is automatically added to Keepnet
✅ You have now added your first Target Users. Now you need to successfully ➡️
This video tutorial shows the documentation steps for synchronizing users' information from the Azure AD identity provider to the platform.
A
Customize Phishing Reporter for your organization's needs
Go to Phishing Reporter > Manage and Download section and click “Connect Account”
Log in to your Microsoft 365 account using your admin credentials.
Once you log in, the Permissions requested pop-up window will display. Read the permissions, then click Accept.
Once you accept the permissions, the GRAPH Authorization Successful window will display.
Click the Download icon below the Microsoft Ribbon Phishing Reporter option to download the PhishingReporterRibbon.xml file.
In a new tab of your browser, log in to your Microsoft 365 admin center.
From the menu on the left side of the page, click Settings.
From the Settings drop-down menu, select Integrated apps.
Click Add-ins at the top-right corner of the page. The Add-ins page will open
On the Add-ins page, click Deploy Add-In. The Deploy a new add-in pop-up window will open.
In the pop-up window, click Next.
Click Upload custom apps.
Select the I have the manifest file (.xml) on this device option. Then, click Choose File and select the PhishingReporterRibbon.xml file that you downloaded in step 6.
Click Upload to install the Phishing Reporter. The Configure add-in pop-up window will open.
From the pop-up window, select which users will have access to the Phishing Reporter and which method you would like to use to deploy the Phishing Reporter.
Click Next, and additional app permissions will display.
Once you have read the permissions, click Save. The Deploy Phishing Reporter pop-up window will open.
The expected timeframe for the Phishing Reporter to deploy is 24 hours, but timeframes can vary. For more information about deploying add-ins, see Microsoft's article.
Once the pop-up window displays a confirmation that the add-in successfully deployed, click Next. The Announce add-in pop-up window will open and display a message about announcement recommendations from Microsoft.
Click Close to close the pop-up window.
"We were unable to process this item. Please try again later." message in the Ribbon Phishing Reporter in Outlook.
The suggested solution is to ""
This video tutorial shows the documentation steps for deploying Microsoft Ribbon Phishing Reporter add-in on M365.
Some customers like to customise the default behaviour of the Incident Responder and the relevant Notification Templates associated with the default workflow. Below are some popular customisation our customers request and how to achieve each one:
Customers can fully customise notifications employees and system admins receive when they report an email for Analysis Results & Investigation Updates. You can view the default notification template
To make customisations, please go to:
Company > Company Settings > Notification Templates
Filter Category by "Incident Responder"
Click on the 3 dots to the right then select "Duplicate" to be able to edit
Make all the customisations you would like, including:
Please note: If you have not purchased the Incident Responder, you will not be able to see Notification Templates for the Incident Responder module.
As you will have seen, the automatically analyses reported email and then automatically runs an investigation for all emails which are found malicious. To take this one step further, you can automate the deletion of all instances of malicious emails.
This is not enabled by default, allowing system admins to decide whether emails should be deleted - especially in rare cases where a safe email may be incorrectly flagged as malicious.
To set this up, please follow the below instructions:
Incident Responder > Playbook
Create a new Playbook by click on the blue +NEW button
Rule Info: Name the playbook and add a description
Conditions: Set to From > exists (this will cover all reported emails)
Top Tip: if you have multiple Playbooks running, set the priority for this one as Very High to ensure this rule will supersede the other rules you have in place
The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting Sender IPs in the Google Workspace environment.
To complete this procedure, you must have security administrator privileges with Google Workspace.
Note the to be allowed.
Sign in to
Select Apps > Google Workspace > Gmail from the left sidebar menu.
Go to the Spam, Phishing, and Malware page.
✅ You have now ensured your target users will receive emails through Keepnet. Now you need to so your target users can successfully open Keepnet email links ➡️
The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting Domains in the O365 environment in the Safe Links feature.
This step is suggested to prevent any false clicks on training or phishing reports.
Find the list of the domains in Phishing Simulator > Settings > Domains.
Sign into the Microsoft Security & Compliance Center.
Click Policies and rules from the left sidebar menu, click Threat Policies and select Safe Links.
✅ You have now Whitelist Domains so your target users can successfully open Keepnet email links. Please also Whitelist in your security solutions if you haven't already.
Next step is to ➡️
Direct Email Creation (DEC) is a feature that connects to your O365 with a few required API permissions. This feature creates the phishing simulation email directly in the user’s inbox instead of sending the emails over SMTP protocol.Key Benefits:
Remove false positives that whitelisting tools cause when analyzing links.
This integration allows your employees to continue using Microsoft’s Phishing Reporting button to report suspicious emails to your SOC team or Microsoft Defender. Along with that, this integration adds new benefits by forwarding reported emails to Keepnet’s Incident Responder. This ensures deeper analysis and tracking capabilities while maintaining your existing reporting process.
Key Benefits:
Dual Reporting: Emails reported via the Microsoft Phishing Reporting Button are sent to both Microsoft Defender and Keepnet's Incident Responder product for advanced analysis.
This guide explains the Threat Intelligence product and how to use it.
This includes:
What is Threat Intelligence?
How to export a list of breached accounts?
Add a name and description for your safe links policy and click Next.
Select your company domain to be included in this policy and click Next.
Deselect the Track user clicks option.
Add the phishing domains by using *.domain.com/* wildcard syntax to the Do not rewrite the following URLs section.
Click the Next button and select Submit to complete the process.






An active email address to be used for testing purposes
X-Anchor Mail Box Header
Check this box if the platform needs to use the X-Anchor MailBox header in connections to the Exchange server.
Target Groups
Selection of the users to be subjects of investigation
All Groups: All user inboxes
Specific User Groups: Selected group of user inboxes
Test Connection
Perform a test of the configuration
Name
Name of the configuration
Service URL
Exchange URL information
Exchange Version
Exchange version information
Account Type
Account type of the service user
Username
Username of the service user
Password
Password of the service user
Test Email Address
[PS] C:\Windows\system32> Get-Mailbox -ResultSize unlimited -Filter "(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne 'Admin')" | Add-MailboxPermission -User [email protected] -AccessRights FullAccess -InheritanceType All[PS] C:\Windows\system32> Add-MailboxPermission -Identity "TargetUserName" -User "[email protected]" -AccessRights FullAccess Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}New-ThrottlingPolicy KeepnetUnlimitedPolicyNameSet-ThrottlingPolicy KeepnetUnlimitedPolicyName -RCAMaxConcurrency Unlimited -Exchange EWSMaxConcurrency Unlimited -Exchange EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -Exchange EWSCutoffBalance Unlimited -Exchange EWSMaxBurst Unlimited -Exchange EWSRechargeRate Unlimited -Exchange EWSFindCountLimit UnlimitedSet-Mailbox “[email protected]" -ThrottlingPolicy KeepnetUnlimitedPolicyNameMost customers find it useful to use Groups - if you select a Group, any new members of this group will automatically be added to Keepnet
Click Select then Assign on the bottom of the page


Email Delivery (select Direct Email Creation if setup)
Subject Line
From Name
From Email Address (must be keepnetlabs.com unless you have selected Direct Email Creation or setup your own SMTP)
Body of the Email
Once you're happy with your edits, Save the template
Set this template as default by click on the 3 dots and selecting "Make Default" - don't forget this step!
Actions: Create a new workflow
Select "Analyse" from the drop down
Select all Integrations (if you don't have any setup, please follow these steps)
Tick the box - "Investigate according to analyze results"
Select Sources > Select the you have setup
Actions > Delete Email
SAVE

Select the Email allowlist tab and click the Edit button.
Add the IP addresses that are listed here.
Click the Save button.
Go back to the Spam, Phishing, and Malware page.
Select the Inbound Gateway option and click Enable, if not enabled.
Add the IP addresses and click Save.
Select Automatically detect external IP if not already selected.
WARNING: Leave the option of Reject all mail not from gateway IPs unchecked.
This option must be 'unchecked'. Do not enable this option!
Select the option of Require TLS for connections from the email gateways listed above.
Click Save to complete the process.
Eradicate maintenance and challenges of whitelisting for the purpose of email delivery (you may need to whitelist in your URL protection solutions such as Defender or ZScaler)
Very simple and quick setup (can be completed in a couple of minutes!)
This page explains how to use the Direct Email Creation feature in Google Workspace. Please follow the steps below to set up DEC settings within your Google Workspace.
Please follow the steps below to make the necessary settings on the platform for the Direct Email Creation feature to be connected within your Google Workspace.
Log in to the platform
Go to Company > Company Settings > Direct Email Creation page.
Click the + NEW button and select Google Workspace.
Fill in the following fields.
Configuration Name: Give a name for your DEC settings.
Client ID: Copy the Client ID ( 102720780747216042586 ).
Select your domain(s) under the Domains field.
IMPORTANT: The selected domain(s) must be Verified on the Allowed Domains page and must be used in your Google Workspace. Otherwise, the selected domain will not work with this DEC configuration.
Do not close this tab. The Save button will remain disabled until the configuration works. Please proceed to the following section.
Please follow the steps below to make the necessary settings for the Direct Email Creation feature to be connected to your Google Workspace.
Log in to https://admin.google.com/ your Google Workspace admin panel.
On the left-hand side, go to Security > Access and Data Control > API Controls.
From the API Controls page, click on the "Manage Domain-wide Delegation" button under the "Domain-wide Delegation" field.
Click on the Add New button.
Enter the Client ID ( 102720780747216042586 ) into the Client ID field.
Enter the following URLs into the OAuth Scopes field.
https://mail.google.com
https://www.googleapis.com/auth/gmail.insert
https://www.googleapis.com/auth/gmail.modify
Click on the Authorize button.
Now, we will complete the process in this section, test the connection between Google Workspace and the Direct Email Creation feature, and see if we can successfully create an email in the user's inbox.
Go to your Company > Company Settings > Direct Email Creation settings page.
Click on the "Send Test Email" button to test the email creation.
To: Enter the recipient's email address who will receive the test email in their inbox.
The email domain must be the domain that was selected previously in the Domains field.
From: Enter an email as a from address.
Sender Name: Enter a sender name.
Message: Enter a message for test purposes.
Click on the Send button to create the email in the user's inbox. If successful, please click the Save button to complete the configuration.
If the test is not successful, please see the Troubleshoot section.
Go to Phishing Simulator > Campaign Manager from the main menu. Click on + NEW to create a phishing campaign and launch it to your target users.
Please complete the first, second, and third sections step by step. For more information about how to use each menu, see here.
When you get to the Delivery Settings page, inside of the Email Delivery field, select your DEC settings.
Set up the rest of the settings as you wish, and then click on Next to go to the last page.
Review all of your settings and click the Launch button to create phishing simulation emails in the selected target user's inbox.
✅ You have now ensured your target users will receive emails through Keepnet. Now you need to Whitelist Domains so your target users can successfully open Keepnet email links ➡️
This video tutorial explains how to configure direct email creation settings and launch a campaign with these settings to create phishing emails directly in the user's inbox instead of launching with the SMTP option.
If you test the DEC configuration and the test is not successful, please try the following options.
Please make sure the domain you selected in DEC settings is Verified in the Allowed Domains page. If it is not, please verify it.
Please ensure the domain you selected in DEC settings is used in the employee's email address as main domain in Google Workspace.
Please try to launch a phishing campaign to the test emails with DEC settings via Campaign Manager. Then, go inside the campaign report and go to the Sending Report menu. You can see more technical information if you hover your mouse over the delivery Error status.
If the options above are not resolved, please contact the support team for further assistance.
Simulation Tracking: During phishing simulation campaigns, Keepnet tracks employees who report simulated phishing emails, helping administrators measure awareness and provide training.
If you don’t already have a shared inbox for phishing reports:
Log into the Microsoft Exchange Admin Center.
Navigate to Recipients > Mailboxes > Add a Shared Mailbox.
Enter a Display Name and Email Address for the shared mailbox.
Click the Create button to create a shared mailbox.
Forward reported phishing emails to Keepnet using a mail flow rule:
Please contact the support team of Keepnet to get the Keepnet email address for forwarding.
Log into the Microsoft 365 Admin Center and open the Exchange Admin Center.
Go to Mail Flow > Rules and click Create New Rule.
Configure the rule:
Name: Enter a name such as "Forward Reported Emails to Keepnet".
Set Apply this rule if: Select the "The recipient" and then select the "is this person" option. Please enter the shared mailbox email address that you created in the previous section.
Do the following: Select the "Add Recipients" and then select the "to the To box" option. Please enter the email address that you got from the Keepnet Support Team.
Leave the "Except if" option as default and then click Next.
Leave the "Set rule settings" page settings as default and then click Next.
Click Finish to create the rule.
Open User Submission Settings in your Microsoft 365 portal.
Ensure “Monitor reported messages in Outlook” is active.
Choose “Use the built-in Report button in Outlook”.
Set “Reported message destinations” to “Microsoft and my reporting mailbox” or “My reporting mailbox only”.
Add your shared mailbox that you created at the beginning of the document to the "Add an exchange online mailbox to send reported messages to:" field and save.
If not already installed:
Visit Microsoft AppSource and search for “Report Phishing”.
Click Get it now and follow the installation instructions.
Wait up to 12 hours for the add-in to appear in Outlook.
Launch a phishing simulation campaign through Keepnet.
Report a simulation email using the Microsoft Phishing Reporting button. Then, go to your campaign report and click the Reporters menu to verify that you reported the simulation email.
Verify the email is also visible on Keepnet’s Incident Responder page.
Reporting Delays: When Microsoft forwards reported emails to the specified email destination, there may be a delay caused by Microsoft’s internal processing. For example, some emails may appear immediately whilst other emails may take 10 minutes to get reported to Keepnet from Microsoft.
Blocked Emails: Emails flagged as phishing might be quarantined by Microsoft or other security solutions, causing delays in forwarding.
Interference: External security solutions, such as Data Loss Prevention (DLP) systems, may interfere with email forwarding from Microsoft to Keepnet. This can result in delays or prevent emails from being reported altogether.
Email Quarantine: Emails flagged as phishing might be quarantined by Microsoft or other security solutions, causing delays in forwarding.
Policy Conflicts: Custom email policies on the customer’s Microsoft tenant could block or redirect reported emails, affecting Keepnet’s tracking.
Server Downtime: Temporary unavailability of Microsoft or Keepnet’s email servers can result in reporting delays.
If your organisation doesn't prefer to send all reported emails via the Microsoft button to Keepnet for analysis and reporting, you can only send simulation emails to Keepnet.
To do this, please follow the steps below.
Log in to the Microsoft 365 Admin Centre and open the Exchange Admin Centre.
Go to Mail Flow > Rules and edit the rule that you recently created.
Click the + button next to 'Apply this rule if' condition to create an AND condition.
Select 'The subject or body' and then select 'subject or body matches these text patterns' option.
Add this 'x-keepnet-tid: [0-9a-zA-Z]+' to the text field.
Click the Save button to apply the changes.
Here is a screenshot reference of the above rule:
Now, when an employee reports an email by using the Microsoft Phishing Reporter button, only simulation emails will be sent to Keepnet; any other emails will not be sent to Keepnet.
The Threat Intelligence product scans the web, searching for signals and data that may represent a breach of your data security and a threat to your business. The constant vigilance afforded to you by the Threat Intelligence product shortens the time between the potential data breach and defensive response, reducing the opportunity for fraudulent activity.
In the Threat Intelligence product, you can check for data leaks for your previously allowed email domains in the Domain Allowlist menu.
Please find the documentation for the domain allowlist here.
Go to the Threat Intelligence menu from the left menu on the dashboard to review the following functions.
This table contains all breached email accounts. This table includes information such as breached account, the source of the breach, the password type of the email account, and the leak date.
The components of the Breached Accounts page are explained in the table below.
Breached Account
Information about the breached email account is located in this column.
Source
This column shows from which source the account was leaked or under what name it was leaked.
Password Type
Indicates the status of the password information contained in the data leak. eg. Cleartext, hash, MD5, etc.
Leak Date
This column shows the information about the date when the data leak was disclosed.
You can take manual actions on breached accounts table. You can click the buttons top of the data table for the appropriate steps you want to perform.
Download
The list of the breached accounts can be downloaded. You can click the button to download all pages or the current page and download the data in the table in XLSX, CSV and PDF formats.
Refresh
By clicking this button, you can reload the page and view it if new data has been added.
Table Settings
With the table settings button, you can show and hide the columns or freeze the columns.
Sorting
According to which column you want to sort, you can change the order when you click on the relevant column heading.
This tutorial explains the Threat Intelligence product and how to use it.
A: No, you can only list, copy to clipboard and download the list of the breached accounts.
A: You can perform almost every operation in the Threat Intelligence product using API. You can refer to our Rest API document to see the details.
Log in to your Microsoft 365 account using your global admin credentials.
Once you log in, the Permissions requested pop-up window will display. Read the permissions, then click Accept.
The Microsoft Page View Phishing Reporter requires specific Microsoft Graph API permissions to function effectively within an organization’s Microsoft 365 environment. These permissions allow the application to interact with users’ emails, retrieve necessary details for reporting phishing attempts, and ensure smooth integration with the email infrastructure.
Below is a breakdown of the permissions required and their purpose:
1. Mail Permissions
Mail.Read: Allows the Phishing Reporter to read the user’s email to retrieve necessary email details such as headers, attachments, and content.
Mail.Read.Shared: Extends read access to shared mailboxes, ensuring that the application can retrieve phishing emails reported from shared accounts.
Mail.ReadWrite: Provides both read and write access to the user’s mailbox, enabling modifications or tagging of emails as needed.
Mail.ReadWrite.Shared: Extends read and write permissions to shared mailboxes for better handling of phishing reports.
Mail.Send: Enables the application to send emails, which may be necessary when forwarding reported phishing emails.
Mail.Send.Shared: Allows the application to send emails from shared mailboxes when the user has the appropriate permissions.
2. User Profile Permissions
profile: Allows the Microsoft Page View Phishing Reporter to retrieve basic user profile information, ensuring accurate reporting and tracking.
Once you accept the permissions, the GRAPH Authorization Successful window will display.
Click the Download button for the Page View button under the Microsoft 365 to download the Microsoft365PhishingReporterAddin.xml file.
Log in to Microsoft 365 Admin Center and go to Add-ins.
Select Deploy Add-in and click Next.
Under Deploy a custom add-in, click Download custom apps.
Select I have the manifesto.xml file.
Click Upload.
Assign the users who will have access to the add-in. We recommend selecting Everyone so the add-in will be installed on every user under the Microsoft 365 tenant.
Select Deployment Method. We recommend selecting Fixed which is the default option.
Click Deploy.
You will receive an email notification confirming your successful deployment. It may take up to 24 hours for the add-in to be displayed on the users' email applications. Users may need to relaunch email applications.
✅ You have now deployed the Phishing Reporter.
Next step is to Setup Incident Responder (only for customers who have purchased the Incident Responder or xHRM package)

















If you've installed the Phishing Reporter on the Microsoft Outlook Desktop version successfully but are unable to see the Phishing Reporter button, here are some steps you can follow to troubleshoot the issue.
First, confirm that you are using a version of Outlook that is compatible with Phishing Reporter. It might be possible that your current Outlook version is outdated and not supported by the add-in. Phishing Reporter usually supports the most recent versions of Outlook, but you can double-check the specific versions from here.
Make sure the Phishing Reporter Add-in was installed correctly. If the installation was interrupted or not completed, it could result in the button not appearing.
Press the Win+S button combination on your keyboard, and find ‘Installed Apps’.
Locate 'Phishing Reporter Outlook AddIn' in the list of installed programs.
If you cannot find it, try reinstalling the software.
Sometimes, the add-in might not be enabled, or it may have been disabled. Here's how to check:
In Outlook, go to 'File' > 'Options' > 'Add-ins'.
In the 'Manage' dropdown, select 'COM Add-ins', then select 'Go'.
If 'Phishing Reporter' is listed but not checked, tick the checkbox to enable it.
If 'Phishing Reporter' is not listed, it means the add-in is not installed correctly. Try reinstalling.
In some cases, the button may not be visible because it's not added to your Outlook ribbon, or it's located under a different tab.
Right-click on the ribbon and select 'Customize the Ribbon'.
Look for 'Phishing Reporter Add-in Name' in the list. If it's there, make sure it's ticked and placed under the Home tab.
Sometimes, Outlook or the add-in may be experiencing issues that could be found in the Windows Event Logs.
Type 'Event Viewer' in the Start menu and open it.
On the left side, navigate to 'Windows Logs' > 'Application'.
Look for any recent warnings or errors related to Outlook or the Phishing Reporter Add-in around the time you last launched Outlook. Pay particular attention to Event ID 45 and 59, which might be related to this issue.
When examining your Windows Event Logs, you may encounter a log entry indicating that the Phishing Reporter add-in has been disabled by Outlook. This typically occurs when the add-in takes too long to load at startup. Once identified, the disabled add-in can be enabled again, as outlined in Step 3 of this guide. If the issue continues after this action, please refer to Step 8 for further troubleshooting assistance.
Microsoft Outlook Desktop may occasionally deactivate add-ins to prevent the application from crashing. By leveraging the Windows Event Logs, you can acquire valuable insights about the loading times of all add-ins. This knowledge helps identify add-ins exceeding the optimal loading time of 1000 milliseconds.
Outlook loaded the following add-in(s):
This log indicates a network connectivity error during an HTTP request.
This error usually stems from the following situations:
The network connection dropped or there is a temporary problem in the network. In this case, the network connection should be checked and, if necessary, the network may need to be restarted or the network settings may need to be checked.
The client side is using an incorrect IP address or port number. In this case, the target and parameters of the request should be checked.
The connection is being blocked due to a firewall or other network security settings. In this case, the security settings should be checked.
Error Log:
This log represents a network error situation.
This error usually stems from the following situations:
Network connection problems. In this case, the network connection should be checked, and it should be ensured that the computer has general access to the internet.
The DNS server is not functioning correctly. In this case, the DNS server should be checked, if necessary, restarted, or DNS settings should be reviewed.
Error Log:
If the above steps don't resolve your issue, it's suggested to ask for assistance from the Keepnet support team. There are two primary ways to get in touch with them:
Email: You can send an email to . Make sure to include all relevant details about your problem, such as your Outlook version, OS version, and any other pertinent information about your system.
Support Portal: Alternatively, you can submit a ticket directly via the Keepnet support portal at .
For additional information on how to contact support, please refer to our documentation.
To deploy the Phishing Reporter add-in to users in Google Workspace, follow these steps.
Go to and click on the New Project button.
The new script file that is opened is saved with a project name.
In the Code.gs, paste the script code provided by the platform and save it.
Go to the settings icon and click Project Settings.
In the project settings, click: Show "appsscript.json" manifest file in editor.
Save the appscript.json file. Copy and save the manifest code.
Go to and create a new project.
Name your project and select the location. Then click on Create to start your project.
Go to the API & Services page. Open the OAuth content screen page from the left menu and select your project.
Please make sure the
On the OAuth content screen, fill in the App Name, User Support Email, App Logo and Developers Contact Email Address. Then click Save and Continue.
After that, click the Save and Continue button again on the Scope screen without making any changes. Then click Back to Dashboard.
Go to API & Services, open the Library page to search Gmail API, and then enable it.
Go to Project Settings, find the "Cloud Platform Project" title, and click on the Change Project button on
Paste the Project Number in the designated field and click Set Project.
Confirm the project change.
The change is enabled once the project change is confirmed.
If you don't want to test the add-in in your Gmail account, please go to the "Enable Google Workspace Marketplace SDK" part to distribute the add-in to the organization.
If you want to test and see the add-in functionality, logos, add-in name, description, and more information, you can deploy the add-in to your Gmail account for test purposes and remove it anytime.
Go to
Select the add-in project.
Click on Deploy >Test Deployments > Install button.
Click Done.
The add-in will appear on your Gmail account shortly.
From the Library page, search for the Google Workspace Marketplace SDK and click on it.
Click the Enable button and activate Google Workspace Marketplace SDK.
Go back to and click on the Deploy > New Deployment button.
Please follow up the following steps to deploy the add-in to your target users.
To deploy the add-in, go to and click on the Google Apps icon in the top right-hand corner of the screen.
Scroll down to and click on it.
Click Internal Apps and find the add-in
Click the Admin Install
It may take up to 24 hours for this app to be installed for your entire Google Workspace domain or organizational unit.
✅ You have now deployed the Phishing Reporter.
Next step is to (only for customers who have purchased the Incident Responder or SOC package)
This section describes the capabilities and features of the threat simulation reports that can be generated using the Email Threat Simulator > Scan > Report button.
The components of the Scan Reports page are explained below.
The Summary provides a brief synopsis of the threat scan and options for further action.
The score is calculated based on the number of emails determined to be insecure and the severity value of the risk posed by these emails.
The attack vectors are listed by attack type or by email status: Malicious Attachments, Ransomware Samples or Insecure Emails.
This section provides a summary report of the attack vectors exploited to target an email address.
A: Yes, you can download a detailed report of the launched attack vectors in .xls, .pdf, or .csv format using the Download button.
A: Yes. You can transfer all of our reports through an API. This flexibility allows you to use the information as needed to suit your business.
You can integrate your Microsoft 365 environment with the Incident Responder product to start an investigation on users' email accounts by following the steps below.You must use an account with global administrator permission.
Select App Registration on the Microsoft Azure portal.
Click +New registration.
In the Register an application section, enter the name of the new application (required field).
Select supported accounts from the Accounts in this organizational directory only option (auth secure login only - single-tenant).
Select Public client/native (mobile & desktop) from the dropdown menu to enter a Redirect URL.
Click Register. (Leave the myapp://auth field section blank).
The new application will now appear in the list of app registrations; click on the name of the new application.
Under Essentials, you will see the following displayed:
Application (client) ID
Directory (tenant) ID
Please take note of these as you will need this information later to set up the new configuration.
Now you are ready to proceed to the next step: the application secret key.
An application secret key must be created for the new registration.
Under Manage from the left-side menu, select Certificates & Secrets.
Select Client secrets.
Select +New client secret.
Enter the description and expiration date and click Add.
The last step is to add application permissions.
Select Manage > API Permissions and click +Add permission.
Click Microsoft Graph and a new window called Request API permissions will appear.
Click Application permissions and then choose Application Permission and in the Select permissions field, find and select the following required permissions:
You can find more information about these permissions at “”.
You can test the integration on the platform to make sure that it is working. Go to Incident Responder > Mail Configurations on the left sidebar menu of the dashboard and then click + NEW and choose the mail provider - in this case, Office 365.
Complete the following fields in the Microsoft Office 365 configuration table. The integration details are:
If the test was successful, the new email server integration will be shown in the list of mail configurations.
If an X appears, it indicates there was a problem and the email server integration failed; please wait a few minutes (5-10+min) for O365 to successfully complete the integration, and then if not work still, please review the instructions.
This permission allows the app to read data in your organization's directory, such as users, groups, and apps. Note: Users may consent to applications that require this permission if the application is registered with their organization’s tenant.
The platform uses this permission to retrieve the client's user list when an investigation is initiated and then to access the email addresses. For example, when a user finds a suspicious email, the platform can scan all users in the list retrieved.
This permission allows the app to create, read, update, and delete email in user mailboxes. It does not include permission to send mail. The platform uses this permission to scan and filter users' emails. For example, when the “From” filter is selected as a parameter to be used in an investigation, this authorization enables the creation of a list of the emails that meet this criterion. It is also used to send a warning message to users. This permission also allows the platform to scan the contents of the emails to find and match the designated investigation parameters. For example, specific filters such as regex, keywords, etc.
This permission allows the app to create, read, update, and delete the user's mailbox settings. It does not include permission to send mail directly, but allows the app to create rules that can forward or redirect messages. The platform uses this permission to mark emails that will receive a warning message.
This permission allows the app to read the full set of profile properties, reports, and managers of other users in your organization on behalf of the signed-in user. The platform uses this permission to read and filter user information during the scanning process. If user-related filters, such as specific users, are selected as scan criteria, the user information may need to be read. For example, an organization may elect to initiate an investigation of employees in a particular department.
A: Yes. The platform’s flexibility allows you to start an investigation at any time and specify how long it is to run, or to create a continuous, automatic search for harmful e-mails. Server-based integration with your email service provides the most comprehensive protection.
A: Yes. The Phishing Reporter plug-in can be used to conduct investigations and mitigation. However, the user must have Outlook open and the plug-in active. Email server integration eliminates this limitation.
The Phishing Simulator allows you to create a realistic simulated phishing email that is sent to employees in order to assess their ability to recognize suspicious emails and their response to attacks that could compromise organizational data and systems.
The product provides the capability to customize and target a phishing campaign suited to your organization and to evaluate the results.
A: Currently, no - it’s mandatory to see the campaign tested before making any mistake. You will receive the email on the Delivery Settings page. The system automatically sends a test email and notifies you about this action
A: If the microsoft name is used in a subdomain there are many threat intelligence services, chromium based browsers, URL filtering tools easily detect and block this domain. If you need this, please reach out to
A: We can only host domains verified through Cloudflare. Please refer to for more information.
A: You can easily create a customized phishing scenario to suit your organization. You will find the instructions .
A: The System templates can't be deleted by the admin users. The admins are able to delete their custom templates.
A: The platform automatically generates unique tracking links for attached files for each target user for Attachment type campaigns. The domain that is used for the attachment type campaign are dynamics. Please make sure you whitelist all the simulation domains.
A: The delivery status can be checked on Sending Report menu in the campaign report to see if the emails have been delivered successfully to the users. If the emails are successfully delivered, please check your .
A: If the campaign contains an HTML page where it contains any words, pictures or links related to Google, Facebook, Twitter, Apple, Microsoft or other such major companies, Google will easily identify it as suspicious and as a result, the user will see red screen after click the link in the simulated phishing email.
Please make sure not to use real words, pictures or links that are related to major companies.
The platform offers approximately fifty domains to be used in campaigns. The admin can also try to change the phishing domain to a new one and then launch the campaign with the new domain.
A: The Outlook Desktop application doesn't read CSS styles which cause sometimes the email not to look properly as it was seen on the platform. You may contact the support team to check if the phishing email could be optimized.
A: The difficulty level of email templates and landing pages is determined based on several factors, including but not limited to:
Sophistication of Phishing Techniques: The use of advanced spoofing methods, such as display name spoofing, domain similarity, and the inclusion of personalized information, can make a phishing attempt more difficult to recognize.
Quality of the Content: The presence of grammatical errors, unusual requests, or other indicators typically associated with phishing can vary. Templates with fewer errors and more realistic scenarios are considered more difficult.
Design and Presentation: For landing pages, the visual design and how closely it mimics legitimate websites play a crucial role. High-quality designs that closely resemble real sites increase the difficulty level.
Easy: These attempts may contain obvious signs of phishing, such as poor spelling and grammar, generic greetings, or implausible requests. They are typically easier for users to identify with basic awareness training.
Medium: These attempts are more sophisticated, with fewer obvious errors and more believable scenarios. They might have email addresses and websites that look like they are real, but if you look closely, you can still find some mistakes.
Hard: These are highly sophisticated attempts that closely mimic legitimate emails and websites, often using personalized information and current events to create convincing scenarios. Recognizing these requires advanced awareness of identity phishing tactics.
A: If you can't see the X-Keepnet-TID header in phishing simulation emails, it's likely due to how the email was forwarded. If the simulation email was forwarded using the "Forward as Attachment" or "Normal Forward" options in Outlook, Microsoft may alter the email headers.
When a message is forwarded as an attachment in the Outlook desktop application, the attachment is often compressed to reduce its size. This compression can strip the original message headers, including the EOP headers we need to analyze.
To ensure the original message and its headers remain intact, save the message to your desktop first, compress it (we recommend adding it to a .zip archive), and then send the compressed file as an attachment. The Outlook Desktop client will not modify the message within a zip file, ensuring that the complete message with all headers arrives at its destination.
For more details, please refer to the following article:
Your license model determines which widgets are available on the Dashboard page.
The Investigations widget displays a summary of the number of automated and manual investigations your company has launched.
Click the (icon symbol) button in the upper right corner of the widget to see detailed information about all of the investigations.
You can visit this document for detailed information about investigations.
This widget summarizes the estimated return on investment, or savings achieved using the Incident Responder product.
For this feature to produce accurate results, you will need to enter the time and cost information specific to your business.
Go to the Incident Responder > Incident Responder page and click the Settings button at the top right of the ROI Summary window and provide the following elements for the calculation:
The Phishing Reporter widget shows the number of people who have the plugin installed and the number of users who have been active in the previous 4 minutes. Visit this to learn more detailed information about the technical structure of the Phishing Reporter plugin.
The Incident Analysis widget displays the total number of suspicious emails reported and the number of emails confirmed to be malicious. Visit this for detailed information about the process used to analyze suspicious emails.
The Reporter Email Trends widget provides a monthly analysis of the previous 6 months that includes the total number of malicious, phishing, or undetected emails, and the recent trend in activity.
The Recently Reported Incidents widget shows the subject line, the status of the analysis (open, closed, in-progress, false-positive), and the result of the analysis (undetected, phishing, malicious, simulation) of the last five suspicious emails reported.
You can click on the title of each reported email to see specific summary information.
Click the All button on the top right of the widget to display all of the reported emails in detail.
The Recent Investigations widget shows the subject of the last five investigations, the progress of the investigations (%), and the current status (running, canceled, finished, expired). You can view a summary of the investigation by clicking on an investigation title.
Click the All button at the top right of the widget to go to the Investigations page.
The Reporters widget shows the five most reliable users who report suspicious emails to the platform. The reliability score improves when the reported email is confirmed to be a phishing or otherwise malicious message. The reliability score will drop if the reported suspicious email does not contain irrelevant and/or harmful content.
Reliability status is classified as follows:
You can click the All button at the top right of the widget to see a list of all of the users who have reported suspicious activity to the platform.
This widget shows the last five reported email incidents and their results. You can access to the last five reported email incidents with their status and you can click on the related incident to access details.
The Rules box displays the top 5 playbook rules, the criteria used to analyze emails, defined in the Incident Responder platform that was met the most often.
You can integrate your Google Workspace environment with the Incident Responder product by following the steps below.
Log into https://console.cloud.google.com/ using an account that has administrative permissions.
Click Select a project > New Project.
Click on the related new project.
On the left-side menu, go to APIs and Services > Library, search for Admin SDK API, and click Enable.
Return to the previous page and search for Gmail API, then click Enable to activate the API.
Select IAM & Admin > Service Accounts from the left-side menu.
Click Create Service Account, name it, and click Create and Continue.
Select Service Directory > Service Directory Admin as the role and click Continue > Done to complete the process.
After creating a service account, click on the related user and go to the user details page.
Go to the Keys tab, click Add Key > Create new key.
Select JSON as the key type and click Create. Save the JSON file.
Go to the Details tab and copy Unique ID information. Save this information for the next step.
Next, log in to .
Go to Security > Access and data control > API controls on the left-side menu.
Scroll down to Domain-wide delegation and click Manage Domain-Wide Delegation.
Click Add New.
For Client ID, enter the Unique ID
https://mail.google.com/,https://www.googleapis.com/auth/admin.directory.user,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/gmail.labels,https://www.googleapis.com/auth/gmail.modify
Click Authorize to complete the process.
To make sure that the integration is working, you can test it on the platform. Go to Incident Responder > Mail Configurations on the left sidebar menu of the dashboard and then click + NEW and choose the mail provider - in this case, Google Workspace.Complete the following fields in the configuration table:
The new configuration will now appear in the list of mail configurations if the test was successful.
If an X appears, it indicates there was a problem and the email server integration failed; please review the instructions.
API scopes identify the information an application will be able to access on a user’s behalf.
This permission allows the app access to emails in user mailboxes. Please note, it is only used to enable investigative searches; we do not create, read, edit, or send emails using this permission.
The platform uses this permission to scan and filter users' emails. For example, when the “From” filter is selected as a criterion for investigation, this authorization enables the creation of a list of the emails that meet the specified parameter. Other uses include regex and keyword searches.
This permission enables quick deletion of malicious content without compromising user privacy.
This permission allows the app to read data in the organization's user directory. The platform uses this access to retrieve a client's user list and their email addresses when an investigation has been initiated.
This permission allows the app to create, read, update, and delete labels. The platform uses this authority to mark emails in the user's inbox with a warning message when the client deems this appropriate. For example, after running an investigation, you may choose to warn the user rather than delete the email results.
A: No. In order to be able to start an investigation and take action on emails, integration with Google Workspace is required.
The Threat Sharing Community platform is an early warning system deployed across a network that provides inbox-level incident response and investigation capability, giving users maximum agility and reducing response time. Users have the ability to expand their threat intelligence reach by using their collective network knowledge, as well as reduce their costs and accelerate implementation of a response. Users can also preemptively initiate inbox investigations before suffering a malicious attack, which provides proactive protection.
You can access the Threat Sharing product from the left-hand panel after logging in to the platform.
A: Yes. If you do not want to disclose your name and organization when posting an incident, you can select the anonymous option offered in the preview section.
A: When you see an incident posted and shared by a fellow member of a community, you can easily begin an investigation to determine potential risk to your firm by selecting the Investigate option. You will be prompted to add the criteria, target users, duration, and other details to be used as part of the investigation.
For more information, go to How to Edit, Investigate, Share, or Delete an Incident.
A: No. Community membership is limited to employees of organizations that have registered to the platform. Once an organization has registered, all registered users of that organization are eligible to participate, if they choose to do so.
For more information about invitations, go to Invitations or Invite New Members.
A: Shared incidents will be maintained in the database
A: A user must accept terms and conditions before a post will be accepted in order to ensure maximum reliability of the shared information.
A: No, they are not verified. However, threat sharing communities are peer-to-peer networks formed and built on trust. This can be used to verify the posts/incidents.
A: No. You can share as many as you want to.
A: Yes. The owner of a community may transfer ownership to another member of the group. Select the name of the member to become the new owner, click on the three dots next to their name, and you have the option to Assign as Owner.
If you do not wish to assign a new owner, you also have the option to delete the community, however, please all posts and the data of the community will be erased.
A: A user must accept terms and conditions before a post will be accepted in order to ensure the maximum reliability of the shared information.
The best solution would be to post anonymously. The poster’s profile details – including the name of the individual and that of the organization - are withheld. It is also possible to select the attributes of the incident that will be visible or hidden in the Header field or Body or Attachment to provide additional confidentiality.
When setting up a community, the owner has a high degree of control about who can access and view that community information. The public, private, and hidden types of community offer different levels of disclosure and participation. Only public communities have unrestricted membership.
The owner of a private or hidden community has administrator rights and controls membership.
The name of a private community is displayed on the Communities homepage; however, membership is restricted.
The search option on the Communities page allows you to locate established groups in industries or sectors most relevant to your interests. For example, a user who works in financial services can search for communities concerned with banking, brokerage, investment banking, or private equity and, if the privacy options allow, become a member of those communities. It is also possible to search for industries and sectors according to the privacy option.
The Treat Sharing page also suggests communities that may be of potential interest.
If there are no existing communities of interest to join, this is an opportunity to create a new community for members of an unrepresented industry or sector.
This could be a great way to establish a presence for your community and become a thought leader within your industry or sector.
The Incidents section offers several ways to search for a particular incident to determine if it may have already impacted your organization. The keyword, company, and threat fields can be used to filter the results.
This can provide excellent insights into past, present, and future threats to an organization, as well as guidance for targeted awareness training and to address any vulnerabilities in information security systems and networks.
Community members can see which incidents are and have been considered the most harmful. The most dangerous attributes are flagged in the post, and members can immediately access the specific details and take the appropriate action for their organization.
Invitations are an invaluable way to expand and enrich communities. A large community has greater resources and expanded ability to improve cyber resilience. The member organizations will be better prepared for attacks based on the knowledge shared by others in the community.
There is no limit to the number of invitations to a public community, and all members may invite a colleague to join. The owner of a hidden or private community serves as a gatekeeper to membership and is the ultimate decision-maker of how many invitations are issued and to whom.
The best way to make a community successful is the proactiveness of the membership, and in particular, the community owner. The larger the community, the more useful and valuable it will be for everyone, but the integrity and caliber of the membership provides additional strength, trust, and reliability.
The intended vision and goals of a community are provided when it is created and serve as a guide to activities and membership.
Users have a range of options to choose from in response to a posted incident according to their own organization’s cybersecurity protocols and incident response procedures. Valuable information is provided related to both actual and potential threats and may be used according to individual needs.
Priorities always change in an organization, and the same is true in the threat sharing world of communities. If the owner of a community no longer feels that it is functional, relevant or the purpose no longer exists, then the community can be deleted, and all incidents reported and which members were part of it will be destroyed as well.
Click Create
Go to Project Settings and copy the Project Number.
Go back to the Console Cloud. Go to the API & Services page, find “Google Workspace Marketplace SDK” and click on it.
Go to the App Configuration tab and enable the Google Workspace add-on option and check Deploy using Apps Script Deployment ID.
Then paste the Deployment ID to the deployment field on the page and then fill in the following fields.
Developer Name with Keepnet.
Fill in the Developer Website URL with https://keepnetlabs.com
Fill in the Developer Email with [email protected].
Before saving, do not forget to select the Private option and then click Save.
Go to the Google Workspace Marketplace SDK page and click the Manage button to see the Store Listing menu.
Select the Category as "Web Project".
Select the Language as "English".
Upload your company logos. If you prefer, you can use the default logos below.
Fill in the Terms of Service URL, Private Policy URL, and Support URL with https://keepnetlabs.com for the add-in.
Under Distribution, select the Region that you will be deploying the add-in to and click Publish.
Click Continue to start the distribution of the extension.
Accept the required permissions to complete the deployment.
Context and Relevance: Attempts that leverage current events, believable scenarios, or target specific job roles can be harder to identify as phishing, especially if they align closely with the recipient's expectations or experiences.
Average hours saved per reported email
The average time spent investigating a reported suspicious email manually (per email)
Average total cost per hour
The average cost to investigate a reported suspicious email manually (per hour)
Very Low
Reliability score of 0-20
Low
Reliability score of 20-40
Medium
Reliability score of 40-60
High
Reliability score of 60-80
Very high
Reliability score of 80-100
For OAuth Scopes, paste the scope information below:
Name
Name of the configuration
Credential JSON
Open the JSON file with a text editor and copy/paste all of the information
Test Email Address
An active email address to be used for testing purposes
Test Connection
Perform a test of the configuration

Result
The results of the attack: Secure, Insecure or Unchecked.
Secure: The attack vector was sent successfully but not delivered.
Insecure: The attack vector was sent successfully and delivered to the inbox.
Unchecked: The attack vector might be sent successfully but delivery is not checked.
Email Sent Date
Date and time that attack vector email was sent to the target email address.
Total Attacks Sent
The number of emails sent to the target email address.
Secure Endpoints
The number of emails successfully blocked by email security solutions.
Insecure Endpoints
The number of emails that could not be blocked by email security solutions
Unchecked Emails
The number of emails not checked by the platform because the automated scan was not enabled or authentication of a target email account failed
Start Date
The date and time the scan of a target email address was initiated
Status
The status of the scan: completed, continuous or in progress
The attack vector target email address
Attack Vector
The name of the attack vector
Extention
The extention of the file.
Category
The type of the attack vector
Hash
The hash of the file.
SHA256
The SHA256 of the file.
Severity
The risk level of each attack, shown as a severity rating from 1 (lowest risk) to 10 (highest risk).
Status
Send status of the attack vector: in progress, successful, or error
In Progress: The attack vector email is in the queue to be sent.
Successful: The attack vector email was sent successfully.
Error: An error occurred in the delivery of the attack vector.
Make sure to save the secret key value before you move on to the final step.
Directory.Read.All
Mail.ReadWrite
MailboxSettings.ReadWrite
User.Read.All (under User)
Click Add permissions.
Click Grant admin consent for (user).
Perform a test of the configuration
Name
Name of the configuration
Application (client) ID
Application ID information is provided on the azure portal under the Overview menu.
Application Secret
Application Secret information is provided on the azure portal under the Overview menu.
Directory (tenant) ID
Directory ID information is provided on the azure portal under the Manage > Certificates & secrets menu.
Test Email Address
An active email address to be used for testing purposes
Domain Selection
Authorized domain(s) to start investigations on
Test Connection
Event ID:59
Source:Outlook
Log:Application
Message:Outlook disabled the following add-in(s):
ProgID: PhishingReporter.Outlook.Addin
GUID: {D0F2562C-3BC1-42E3-B34E-8A735974A173}
Name: PhishingReporterAddIn
Description: AddinModule
Load Behavior: 2
HKLM: 1
Location: C:\Program Files (x86)\Phishing Reporter\Phishing Reporter Outlook
Threshold Time (Milliseconds): 1000
Time Taken (Milliseconds): 1875
Disable Reason: This add-in caused Outlook to start slowly.
Policy Exception (Allow List): 0Name: Microsoft Exchange Add-in
Description: Exchange support for Unified Messaging, e-mail permission rules, and calendar availability.
ProgID: UmOutlookAddin.FormRegionAddin
GUID: {F959DBBB-3867-41F2-8E5F-3B8BEFAA81B3}
Load Behavior: 3
HKLM: 1
Location: C:\Program Files\Microsoft Office\root\Office16\ADDINS\UmOutlookAddin.dll
Boot Time (Milliseconds): 0
Name: Skype Meeting Add-in for Microsoft Office
Description: Skype Meeting Add-in for Microsoft Office
ProgID: UCAddin.LyncAddin.1
GUID: {A6A2383F-AD50-4D52-8110-3508275E77F7}
Load Behavior: 3
HKLM: 1
Location: C:\Program Files\Microsoft Office\root\Office16\UCAddin.dll
Boot Time (Milliseconds): 15
Name: PhishingReporterAddIn
Description: AddinModule
ProgID: PhishingReporter.Outlook.Addin
GUID: {D0F2562C-3BC1-42E3-B34E-8A735974A173}
Load Behavior: 3
HKLM: 1
Location: C:\Program Files (x86)\Phishing Reporter\Phishing Reporter Outlook AddIn\adxloader64.dll
Boot Time (Milliseconds): 146Request url: https://addin-api.keepnetlabs.com/api/heartbeat response content : RestHttpClient.cs : Post : 109
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'keepnetaddin.xcompany.local'Request url : https://addin-api.keepnetlabs.com/api/notify/email response content : : RestHttpClient.cs : Post : 104
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 1.1.1.1:235Request url: https://addin-api.keepnetlabs.com/api/heartbeat response content : RestHttpClient.cs : Post : 104
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'addin-api.keepnetlabs.com'


In standard Windows, the MS Outlook service does not support monitoring and reporting the functionality of the installed add-ins on it. This service has been developed in order to monitor and report whether Keepnet Outlook add-in functions properly or not.Using this service, system administrators will be aware of the potential environment-based errors which could affect the Keepnet Outlook Phishing Reporter add-in not functioning properly and be able to take action.
Go to Phishing Reporter > Settings > Diagnostic Tool to download the diagnostic tool.Configure the following settings:
Proxy Settings: Enable proxy settings for the Diagnostic Tool to go internet through a proxy.
Optional Settings: Select if you want the Diagnostic Tool to check the Phishing Reporter add-in and enable it automatically if disabled.
Once you're happy with your settings, click Download under the diagnostic tool. Then follow the steps below to install the service.
There are two options to install the service, either install it on your computer or deploy the service to thousands of users' computers using centralized software distribution tools.
Click on the MSI package to install it on your computer.
Click the Next button and continue with the default settings.
Click the Yes button to finish the installation.
You can use the following commands for silent installation and removal.
Once the installation is complete, you can confirm that the diagnostic tool has been installed by going to Phishing Reporter > Users and looking under the Diagnostic tool column.This column will show one of the following in the table below.
To view the Diagnostic Tool information, go to Phishing Reporter > Users and look under the Add-in Status column. When hovering the mouse over this column under the desired user, you will see the following information below.
The Diagnostic Tool has been successfully installed, operated and can communicate with the platform to help you obtain Phishing Reporter status information for all target users.
For troubleshooting purposes, you can provide the support team with the log and configuration files, which can be found in the following path on the user's computer.
C:\Program Files (x86)\Keepnet Labs\KeepnetLabs Phishing Reporter Diagnostic Service
✅ You have now deployed the Phishing Reporter
Next step is to (only for customers who have purchased the Incident Responder or SOC package)
This video tutorial explains how to customize the Diagnostic Tool service and download it.
A: If the add-in is installed and active, but seems Offline, then the Outlook application is closed. If Outlook is still running, but it is still Offline, it means that there is a communication problem between the add-in and the platform. You can easily detect this problem from the logs created by the add-in on the user's computer or get support from our support team.
A: If you see the “Inactive" notification, then it is disabled by the user. If it says “Disabled", it means that it is disabled by Outlook. You can also verify this from the interface of user’s Outlook Desktop in the File > Options > Add-Ins window.
A: With the feature, you can authorize your users with custom permissions.
Direct Email Creation (DEC) is a feature that connects to your O365 with a few required API permissions. This feature creates the phishing simulation email directly in the user’s inbox instead of sending the emails over SMTP protocol.Key Benefits:
Remove false positives that come from email delivery.
Eradicate maintenance and challenges of whitelisting for the purpose of email delivery (you may need to whitelist in your URL protection solutions such as Defender or ZScaler)
Very simple and quick setup (can be completed in a couple of minutes!)
Go to Company > Company Settings > Direct Email Creation from the main menu. Click on + NEW to create a direct email creation setting.
Click on Connect Account button to connect your O365 with the Direct Email Creation (DEC) application to create a configuration.
Name your DEC, select which domains you will send phishing simulation emails to and Send Test Email.
Send Test Email To: Enter the email of the person receiving the test email.
Sender Email Address: Enter any email - you can now send emails from any email address!
Sender Name: Enter a sender name.
Message: Enter a message.
Make Direct Email Creation your Default Delivery Method - this will save you lots of time and remove delivery errors when you start sending phishing campaigns.
Keepnet follows for third-party applications and has received approval from Microsoft. The app uses permissions solely to create simulated phishing emails in users' inboxes. It does not include permission to read, send email or access other mailbox functionalities.
The following permissions are required for customers using the Microsoft 365 email server.
Microsoft bundles permissions together. The following Microsoft screenshot shows a 'Mail' permission group. There's no separate Write permission — only the Mail.ReadWrite permission, which handles Write actions.
The following permissions are required for customers using the Microsoft Exchange Online email server.
In summary, customers only need to share the necessary permissions based on their specific environment, whether they use Microsoft 365, Microsoft Exchange Online, or a hybrid of both. Keepnet requests these permissions to create simulation emails in the user's inbox across any of these environments.
For example, if you use just only Microsoft Exchange Online, then Keepnet only uses the related permission groups for Exchange Online, other permissions are not used.
To view the activity of the DEC application created by the platform and confirm that it is only creating simulation emails (and not reading any emails), please follow these steps:
Log in to the .
Navigate to the Audit menu.
If not already enabled, click to Enable Audit Logging.
Set up the DEC configuration successfully on the platform, and send a test email using the DEC settings to generate activity logs.
In the logs, you should see activities such as "Created mailbox item", confirming the application's behavior. For example:
This log indicates that the application is only creating mailbox items and not accessing or reading mailboxes.
✅ You have now ensured your target users will receive emails through Keepnet. Now you need to so your target users can successfully open Keepnet email links. ➡️
This video tutorial explains how to configure direct email creation settings and launch a campaign with these settings to create phishing emails directly in the user's inbox instead of launching with the SMTP option.
A: Click for more information.
A: No, you can only launch a campaign with DEC settings using Campaign Manager. If you launch a campaign with Fast Launch, the campaign will be started with default SMTP settings.
A: If you use only the product and use the DEC feature, you don’t need to do . If you’re using other products, such as Awareness Educator, you need to do whitelisting since the DEC feature only works for now with the product.
A: No, the users whose status shows Error means the destination email user account hasn’t been found in the O365, or there might be another problem for these users' email accounts which platform will show you as a tooltip if you hover your mouse over the error status.
A: You can check and make sure you selected the related domain addresses in the DEC configuration, and then you can try to resend the campaign to these users from the Sending Report menu in the campaign report.
A: Authorizing the DEC feature on the O365 server doesn’t involve any potential security considerations. Keepnet provides encryption to secure data and prevent unauthorized access to keep your data safe.
First, we encrypt data and apply it to our and to make data secure and prevent potential vulnerabilities.
Furthermore, we have a strict access policy and do not allow unauthorized gain access to sensitive data; please see our access policy .
Keepnet does its best to maintain rigorous security protocols such as regular audits of access rights, continuous monitoring for abnormal activities, and thorough vulnerability assessments.
You can see other data security measures on our .
Use this chart to determine which Phishing Reporter add-in is best suited for your Microsoft 365 environment. The right choice depends on how your employees access Outlook—whether through desktop apps, web browsers, or mobile devices.
A: You can try to re-deploy the add-in. If it still does not appear, you should contact the support team of the email service provider.
A: The platform uses “Code Signing with Microsoft Authenticode” to protect tools against hacking attempt. For more information, please .
A: Yes, it is. Many institutions manage the add-in (install, uninstall, enable, disable) with central administration tools, such as Microsoft SCCM, IBM Bigfix.
A: Yes, if you distribute the Phishing Reporter Add-In as an XML package (Microsoft 365), it will be available in both OWA/Outlook applications and will also function within the Outlook application on iOS.
A: The add-in works in shared mailboxes in the Outlook Desktop Application. However, it is not supported in shared mailboxes in OWA (Outlook Web Access).
A: No, the new Outlook application on Windows 11 does not support MSI-based add-ins. It is designed to work primarily with web-based add-ins such as . If you need MSI-based add-ins, we recommend using the classic Outlook for Windows desktop application. For more information, please find information under the "Extensibility" section in this .
A: No, you can't use the add-in if you open OWA in a mobile browser. Microsoft 365 does not support third-party add-ins in mobile browsers for OWA. Please use the Outlook app instead.
This document will provide information on how to start the Email Threat Simulator scan to the email inbox by using the “Continue with Microsoft Office 365” feature.
Microsoft O365 requires extra configuration steps in order to use the Email Threat Simulator with an O365 email account.
Follow the steps to create and configure the application on Microsoft Azure.
Login to .
From the Home page, go to the App Registrations menu from the Azure Services page
Create a new application by clicking on the +New Registration button.
Fill in the following fields on the Register an Application page and then click the Register button.
Name: Enter a name for your application.
Supported account types: Select the “Accounts in this organizational directory only (Single tenant)” option.
After creating the application, copy the “Application (client) ID” and “Directory (tenant) ID” from the Overview page to use it in the platform later.
Follow the steps to assign the required permission to the application that has been created on Microsoft Azure.
To assign EWS.AccessAsUser.All permission;
Click API Permissions from the left menu and click the +Add a permission button.
Click APIs my organization users title on the Request API
Click the Grant admin consent for “CompanyName” button to successfully grant these permissions to the application.
Follow the steps to configure Authentication configuration in order to start a simulation from the platform.
Set permissions on the Web Applications field from the Authentication menu;
Click on the Authentication from the left menu and then click on the +Add a platform button from the Platform Configurations page.
From Configure Platforms page, under the Web Applications title, click on the Single-page Application button.
Under the Configure Single-page Application
Set permissions on the Mobile and Desktop Applications field from the Authentication menu;
Click on the +Add a platform button from the Platform Configurations page.
From Configure Platforms page, under the Mobile and Desktop Applications title, click on the Mobile and Desktop Applications button.
Under the Configure Desktop + Devices title, find Redirect
Set permissions on the Advanced Settings field from the Authentication menu;
From the Authentication menu, under the Advanced Settings title, find Allow Public Client Flows field and activate the “Enable the following mobile and desktop flows:” option.
Click the Save button to finish this configuration steps.
Please make sure that the 2FA authentication is disabled on the email account before starting a simulation on the platform.
Azure might need approximately 30-60 minutes to apply the changes on their side. If you see an error while starting a simulation, please wait a few hours and then try again.
Follow the following steps to start the simulation from the platform.
Go to Email Threat Simulator > Scans page from the left menu on the platform.
Click on the +NEW button to start a new simulation.
Read the warning message and then click the “I Understand” button.
You can find more information about the Email Threat Simulator .
Click on the Next button to go to the next page and customize the options as wished on “the “Scan and Delivery Settings” page and then go to the last page to agree on the “User Agreement” to start the simulation.
If you’re unable to start an ETS scan on an O365 email account, follow these steps to troubleshoot:
Check Sign-In Logs: Navigate to the User Sign-In logs for the email account used for the ETS scan. Review the logs to identify any technical issues preventing Keepnet from connecting to the account.
Verify MFA/2FA Settings: Ensure that Multi-Factor Authentication (MFA) or Two-Factor Authentication (2FA) is disabled for the email account used for the ETS scan.
Allow Time for Settings to Apply: After configuring the account settings according to the documentation, wait at least 60 minutes before initiating the ETS scan. Microsoft may require some time to apply the changes across your organization.
If you still can't start an ETS scan on the email account, please for further assistance.
Go to the Email Threat Simulator page from the left menu on the dashboard to see the following fields.
The components of the scans page are explained in the table below.
Date Created
The date and time the scan was created
You can delete or duplicate a scan as well as to view detailed reports of a scan.
The Email Threat Simulator has only one mandatory component: the test email address. Follow the steps below to start a new scan:
Click the +NEW button in the upper right corner of the Email Threat Simulator > Scans page.
Test Email Address: Enter your ETS test email address to which you want all attack vectors to be sent.
Choose an Option: Please select one of the following suitable options for your ETS scan.
The Attack Vectors page lists all available attack vectors that can be sent to your test email inbox to test your email security gateway infrastructure.
Here are the fields for each attack vector:
These settings give you the ability to edit, enable/disable, or delete attack vectors.
.Click on the three dots “︙” button under the Action heading to adjust the following
A: No. You may not duplicate continuous scans for the same domain; however, you are able to start multiple scans without selecting the continuous scan option.
A: No. You cannot edit a scan, but you can delete a previous scan and start a new scan.
A: You are not permitted to add new attack vectors or take action on existing attack vectors.
It's suggested to use all the methods explained in this documentation step by step for whitelisting successfully. The customer may skip the related step if there is no feature in their O365 environment due to the license.
Redirect URI: Leave this field blank.
Select Delegated permissions option on the Office 365 Exchange Online page.
Enable the EWS.AccessAsUser.All permission in the EWS field and then click Add Permission button.
To assign Mail.Read permission;
Click API Permissions from the left menu and click the +Add a permission button.
The Microsoft APIs field will appear by default on the Request API Permission page.
Click on Microsoft Graph and select Delegated Permissions option.
Enable the Mail.Read permission in the Mail field and after that click Add Permission button.
Under the Implicit Grant and Hybrid Flows title, enable the Access tokens (used for implicit flows) and ID tokens (used for implicit and hybrid flows) options.
Click on Configure button to finish this configuration steps.
Click on Configure button to finish this configuration steps.
Test Email Address
The email address that the simulation will be started on.
Choose an Option
Select the “Continue with Microsoft Office 365” option.
Password
The password of the email address that will be used in the simulation
Application (Client) ID
The Application (Client) ID information that is visible in the application that is created in the Azure platform.
Directory (Tenant) ID
The Directory (Tenant) ID information that is visible in the application that is created in the Azure platform.
Automate with password: The malicious emails will be sent to your email inbox, and the automated check, such as how many emails have reached the inbox or not, will be performed automatically.
OWA: If your Microsoft 365 email inbox is accessible from the internet, click the OWA option and define your Outlook Web Access URL and Username information.
Google Workspace: If you want to use your Google Workspace email inbox with a password, please use this document for more information.
Continue with Microsoft Office 365: The malicious emails will be sent to your inbox, and the automated checks, such as how many emails have reached your inbox or not, will be performed automatically. Please learn how to start a scan on a Microsoft 365 email account here.
Click the Next button and check the Continuous Scan box if you want it to be included in this scan automatically when a new attack vector is added.
Define the delivery interval for emails in the Distribution section and click the Next button.
Accept the User Agreement and click the Start button.
Status
Current status of the scan
Domain
Domain address of the email used to initiate the scan
View Report
Access detailed reports of a scan. You can find more information about the report details here
Delete
Delete the scan
Duplicate
Create a copy of the scan
Attack Vector Name
The display name of the attack vector.
Type
The category of the attack vector, such as malware, malicious, or other categories.
Hash
The hash of the attack vector.
SHA256
The SHA-256 hash value of the attack vector.
Severity
The severity level of the attack vector. Enter a number from 1 to 10 (1 = lowest severity, 10 = highest).
Status
When set to active, this attack vector will be sent to the test email inbox.
Date Created
The date and time when the attack vector was added.
Edit
Change the settings of the relevant attack vector
Enable/Disable
Enable or disable existing attack vectors. Disabled attack vectors will not be sent in new scans.
Delete
Delete the attack vector

✅ Supported
Outlook on MacOS (Microsoft 365)
✅ Supported (Version 16.81 (23121700) or later)
✅ Supported
❌ Not Supported
Outlook on MacOS (Exchange)
❌ Not Supported
❌ Not Supported
❌ Not Supported
Outlook on Web MacOS (Exchange)
❌ Not Supported
✅ Supported
❌ Not Supported
Outlook on the Web (Microsoft 365)
✅ Supported
✅ Supported
❌ Not Supported
Outlook on the Web (Exchange)
❌ Not Supported
✅ Supported
❌ Not Supported
Outlook on iOS (Microsoft 365)
❌ Not Supported
✅ Supported
❌ Not Supported
Outlook on Android (Microsoft 365)
❌ Not Supported
✅ Supported
❌ Not Supported
Outlook on iOS (Exchange)
❌ Not Supported
❌ Not Supported
❌ Not Supported
Outlook on Android (Exchange)
❌ Not Supported
❌ Not Supported
❌ Not Supported
Shared Mailboxes (Outlook Desktop)
❌ Not Supported
❌ Not Supported
✅ Supported (only within Classic Outlook)
Shared Mailboxes (Microsoft 365)
❌ Not Supported
❌ Not Supported
❌ Not Supported
Mobile Browser (OWA)
❌ Not Supported
❌ Not Supported
❌ Not Supported
Installation Method
Deploy via Microsoft 365 Admin Center (Manifest XML)
Deploy via Microsoft 365 Admin Center (Manifest XML)
Manual deployment via GPO or SCCM Tools
User Experience
Ribbon button
Side panel in reading view
Ribbon button (Classic Outlook interface only)
Outlook on Windows (Classic)
✅ Supported (only version 2404 build 17530.15000)
✅ Supported
✅ Supported
Outlook on Windows (New)
✅ Supported
✅ Supported
❌ Not Supported
Outlook Classic 2016+ on Windows (Exchange)
❌ Not Supported
✅ Supported



Click SAVE to create configuration settings.
Go back to the Audit menu and search for logs related to the user who sent the test email with DEC settings. Also, you may copy the Application ID of the DEC application and paste it under the Keyword Search field to search logs.
Read and write all applications
It is used only when the customer uses a custom domain instead of dash.keepnetlabs.com to access the platform. This ensures that the customer can successfully configure the DEC settings on the platform while using the custom whitelabeled domain.
Read domains
It is used to fetch the domains that the customer owns in Microsoft 365 and allows the customer to select the relevant domains so the platform can create simulation emails in the user's inbox under the selected domains.
Read and write mail in all mailboxes
It is used to create a simulation email in the user's inbox. Please see following screenshot for more information about this permission
Read all users' full profiles
It is used to read the user's profile information, retrieve email account details (e.g., email address), and switch to the user's profile to create simulation emails in their inbox.
Sign in and read user profile
It is used to read basic company information of the signed-in user who grants permission.
Access mailboxes as the signed-in user via Exchange Web Services
It is used to access user's mailbox in order to create simulation email in the inbox.
Use Exchange Web Services with full access to all mailboxes
It is used to create a simulation email in the user's inbox without using a sign-in account.
Manage Exchange As Application
It is used to allow the app to manage the organization's Exchange environment without any user interaction.




The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting Sender IPs in the O365 environment in the Phishing Simulation feature.
Note the IP addresses to be allowed.
Sign in to the Microsoft Security & Compliance Center.
Click the Policies & rules item on the left sidebar menu.
Go to Threat policies > Advanced delivery.
Click the Phishing simulations tab and click Edit.
Add the IP address to Sending IP section.
Add the Domain address (also known as the MAIL FROM address) used in the phishing campaign into the Domains section.
Add the phishing domains by using *.domain.com/* wildcard syntax to Simulation URLs to allow section.
Click Save to complete the process.
The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting Sender IPs in the O365 environment in the Threat Policies feature.
Note the IP addresses to be allowed.
Sign in to the Microsoft Security & Compliance Center.
Click the Policies and rules > Anti-Spam under the Policies. To go directly to the Anti-spam policies page, use https://security.microsoft.com/antispam
Click the Connection Filter Policy and select the Edit connection filter.
Add the IP addresses to the section labeled Always allow messages from the following IP addresses or address range.
Enable the Turn on safe list option.
Click Save to complete the process.
The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting the Sender IPs in the O365 environment in the Bypass Spam Filter feature.
Sign in to the admin portal.
Go to Exchange > Mail flow > Rules and click the + Add a rule button.
Select the Bypass Spam Filter option.
Enter a name for your whitelisting rule.
Scroll down to the "Apply this rule if..." section and select "The sender" and then select "IP address is in any of these ranges or exactly matches"
To the right you'll see "Enter text...", click "Enter Words" to bring up a new window labeled specify IP address ranges, and enter the IPs listed and then click the Save button.
Scroll down to the "Do the following" section.
Select the "Modify the message properties" option and then select the "Set the spam confidence level(SCL)" option.
And then click the Set the spam confidence level (SCL) to '-1' option and select "Bypass spam filtering" and click the Save button.
Next to the "Do the following" field, click + button to create a new rule.
Select the "Modify the message properties" option and then select the "set a message header" option.
Click "Enter Words" and type "X-MS-Exchange-Organization-BypassClutter" and then click the Save button.
We recommend leaving the rest of the rule settings the same. Once you have completed these steps, click Save to save your whitelisting rule.
Make sure the whitelisting rule's status is enabled. If it's disabled, click on it and Enable it and click the Edit Rule Settings button on the opened page to save it.
The below instructions will show you how to whitelist the emails such as notification, training, or phishing simulation emails that will be sent from the platform to users by whitelisting the Sender IPs in the O365 environment with the "SkipSafeLinksProcessing" rule.
This step is suggested to prevent scanning phishing simulation links by O365 sent by the platform.
Sign in to the admin portal.
Go to Exchange > Mail flow > Rules and click the + Add a rule button.
Click on the Create a new rule option.
Enter a name for your whitelisting rule.
Scroll down to the "Apply this rule if..." section and select "The sender" and then select "IP address is in any of these ranges or exactly matches"
To the right, you'll see "Enter text...", click "Enter Words" to bring up a new window labelled specify IP address ranges, and enter the IPs listed and then click the Save button.
Scroll down to the "Do the following" section.
Select the "Modify the message properties" option and then select the "Set a message header" option.
Set the message header to "X-MS-Exchange-Organization-SkipSafeLinksProcessing" and set the value to "1".
We recommend leaving the rest of the rule settings the same. Once you have completed these steps, click Save to save your whitelisting rule.
Make sure the whitelisting rule's status is enabled. If it's disabled, click on it and Enable it and click the Edit Rule Settings button on the opened page to save it.
The below instructions will show you how to whitelist the attached files in the emails that will be sent from the platform to users by whitelisting the Sender IPs in the O365 environment with the "SkipSafeAttachmentProcessing" rule.
This step is suggested to prevent scanning phishing simulation attachment files by O365 sent by the platform.
Sign in to the admin portal.
Go to Exchange > Mail flow > Rules and click the + Add a rule button.
Click on the Create a new rule option.
Enter a name for your whitelisting rule.
Scroll down to the "Apply this rule if..." section and select "The sender" and then select "IP address is in any of these ranges or exactly matches"
To the right, you'll see "Enter text...", click "Enter Words" to bring up a new window labelled specify IP address ranges, and enter the IPs listed and then click the Save button.
Scroll down to the "Do the following" section.
Select the "Modify the message properties" option and then select the "Set a message header" option.
Set the message header to "X-MS-Exchange-Organization-SkipSafeAttachmentProcessing" and set the value to "1".
We recommend leaving the rest of the rule settings the same. Once you have completed these steps, click Save to save your whitelisting rule.
Make sure the whitelisting rule's status is enabled. If it's disabled, click on it and Enable it and click the Edit Rule Settings button on the opened page to save it.
If the emails sent by the platform somehow is not delivered to the user's inbox, the admin can use the following steps to see why it's not delivered and find a solution for it.
Sign in to the admin portal.
Go to Exchange > Mail flow > Message Trace and click the + start a trace button.
Enter the from address to the "Senders" field which is expected to be delivered from the platform and click the Search button.
The O365 will list the emails that is delivered from the specified email address and then you can click on the emails to see more information.
✅ You have now ensured your target users will receive emails through Keepnet. Now you need to Whitelist Domains so your target users can successfully open Keepnet email links ➡️
The following video playlist tutorial contains information about how to whitelist in O365 environment.
Silent Installation
C:\Windows\System32\msiExec.exe -i "KeepnetPhishDiagInstaller.msi" /QN /norestart
Silent Removal
C:\Windows\System32\msiExec.exe -x "KeepnetPhishDiagInstaller.msi" /QN /norestart
Product Guid Detection
get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize
Remove with Product Guid
C:\Windows\System32\msiExec.exe -x {product-guid} /QN /norestart
Not Installed
The diagnostic tool has not been installed
Online
The diagnostic tool has been installed, and the user is online
Offline
The diagnostic tool is installed, but the user is offline
Error/Uninstalled
There is an error with the diagnostic tool installation or the tool has been removed
Add-in is installed and
User is online
User is offline
HKLM Number
List of possible values:
1: Active: Don't load automatically
2: Disabled: Load at startup
3: Active: Load at startup
Boot time
How long it takes for the add-in to start
Outlook version
Version information of Outlook application
Outlook Architecture
Either:
X32
X64
OS version
User’s operating system version information
This document explains the functionality of the LDAP feature as well as how to set up an LDAP to synchronize target users information such as Name, Surname, Email, Department, Phone Number or other information to the platform automatically.
LDAP is a standard protocol that allows the platforms to access an active directory to fetch target user’s information such as Name, Surname, Email, Department, Phone Number, and other information to synchronize these user’s information to the platform automatically.
Go to Company > Company Settings > LDAP from the platform menu to access the following LDAP configuration.
If the test connection is successful, you will see that it’s successful, if not please see the detailed pop-up message.
Usually, a whitelist rule is needed to access to the local Active Directory from the platform's IP address. You can contact support team to get IP address of the platform.
This is where you can see your scheduled LDAP rules. This means LDAP will automatically scan daily for new users to add/update/delete to your specified target group.
The components of the Scheduled Syncs page are explained in detail in the table below.
This is where you can choose which information that will be fetched and imported to the specific column on the platform. The admin can fetch specific information from the active directory such as the Manager, Country, City, or other attributes and synchronize this information of the users.
The components of the Field Mapping page are explained in detail in the table below.
While the Email, First Name, Last Name, or Department attributes are the most popular field mapping categories, you can have the option to synchronize Display Name, Office, Telephone Number (Mobile or Home), Address (Street, City, State, P.O Box, Country, Zip Code), Company, and more.
Go to Target Users > People menu and then click the Table Settings button on the right top of the screen to click the EDIT FIELDS button.
Create a custom field and then click the Save button.
To map this custom field with LDAP, go to Company Settings > LDAP > Field Mapping and map any listed active attributes to a created custom field.
Do not forget to save changes by clicking the Save Changes button and then proceed to the following title.
Follow the steps below to import target users to the platform from the integrated Active Directory by using the LDAP.
Go to Company > Target Users from the platform menu.
Click the + NEW button on the top right of the page and then select the ‘Import users from LDAP’ option.
There is two following option to import users.
This option fetches all unique email users in your active directory, no matter what active directory groups they are in.
If this option is selected, please choose a target group that all users will be imported to on the platform.
If the target group is not selected, all users will be imported as a single member on the platform without being assigned to a target group. No worries, all users can be imported to a single target group later.
There are three options to import users.
This option fetches unique email users that are in certain groups in your active directory.
If this option is selected, please choose LDAP groups which users that are inside will be imported to the platform.
If the target group is not selected, all users will be imported as a single member on the platform without being assigned to a target group. No worries, all users can be imported to a single target group later.
There are three options to import users.
✅ You have now added your first Target Users. Now you need to successfully ➡️
The following video shows how to set up an LDAP connection and import or synchronize users to the platform.



Next, click Enter Words under the "header value" and type "true".
Saves the changes
Choose ‘Sync All Users’ if all users need to be synchronized automatically.
This process repeats every 24 hours automatically to fetch new users or update changes on the users.
Choose ‘Sync By Query’ if all users need to be synchronized users by criteria.
This process repeats every 24 hours automatically to fetch new users or update changes on the users that match the criteria.
Use the filters to create criteria to filter users out of all users to synchronize and then use the View Users button to see filtered users that will be synchronized.
Choose ‘Sync All Users’ if all users need to be synchronized automatically.
This process repeats every 24 hours automatically to fetch new users or update changes on the users.
Choose ‘Sync By Query’ if all users need to be synchronized users by criteria.
This process repeats every 24 hours automatically to fetch new users or update changes on the users that match the criteria.
Use the filters to create criteria to filter users out of all users to synchronize and then use the View Users button to see filtered users that will be synchronized.
Click ‘+ Add Condition’ to add more conditions for filtering the users.
Server URL
URL and Port number to access the active directory.
Bind Username
Read-only access account name in the active directory.
Bind User Password
Password of the read-only account.
Base DN
The starting point for searches in the LDAP directory server. Example of DC=company and DC=domain.com.
Relative DNS
A relative search will be conducted on the subbranches of base DN for LDAP users whose objectType=user. You can enter a different relative DN on each line.
Status
Disable the LDAP is no need to use more.
Connection
Test your configuration if successful to connect the active directory.
Name
Name of target group
Status
Disables the scheduled rule if you don’t want the rule to work anymore.
Date Created
Date and time that the scheduled rule was created.
Last Run
The last time LDAP was scanned for new changes.
Next Run Time
The next time LDAP will be scanned for new changes.
Edit
Edit the scheduled rule to change the settings.
Delete
Delete LDAP synchronization if the LDAP rule shouldn’t work anymore.
User’s Email Address that will be imported
First Name
User’s First Name that will be imported
Last Name
User’s Last Name that will be imported
Department
User’s Department that will be imported
Phone Number
User's Phone Number that will be imported.
Timezone
User's Timezone that will be imported.
Save Changes



The Phishing Simulator > Phishing Scenarios > Scenarios page provides a selection of ready-to-use phishing campaigns. These standard system scenarios are available to all clients and can be launched with just a few clicks. You also have the option to customize a scenario to your needs or to create a unique phishing campaign.
The components of the Scenarios page are explained below.
Scenario name
The name of the phishing template
Category
Category is used to classify phishing scenarios by threat type.
Method
The phishing technique.
Data Submit: Used to detect target users who submit data on the landing page
Attachment: Used to detect target users who download the attachment in the phishing simulation email
Click-Only: Used to detect target users who click unknown links in the phishing email.
This section explains how to initiate a phishing campaign.
Once you have selected a phishing template for your campaign and identified the targets, click on the Launch '➤' button in the Actions menu on the far right of the page.
You will be presented with options to specify or modify various elements of the campaign.
Once you designed the proposed campaign and clicked the Next button, you will be provided with a summary. The components are explained below.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Edit button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Preview button to view what will be sent to the targeted users.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Duplicate button to recreate a previous campaign.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Delete button to delete a phishing campaign.
This option gives you an overview of phishing templates on the platform, grouped by region (e.g., EMEA, NAM), brand (e.g., Microsoft, Google), industry (e.g., finance, IT), attack type (e.g., click-only), language, and emotional triggers (e.g., urgency, excitement). It helps you explore and select the most relevant templates for your campaigns.
To access it, go to Phishing Simulator > Scenarios and click the "Scenario Statistics" button at the top-right of the scenarios page.
The Scam of the Week category highlights phishing scenarios that are based on the most recent and trending cybersecurity threats. These scenarios are updated weekly and curated by security experts to help you quickly launch timely and realistic phishing simulations.
To view scam of the week scenarios, go to Phishing Simulator > Phishing Scenarios, select Scam of the Week from the Category filter.
Phishing scenarios have two components: the phishing email template and the landing page. Follow the steps below to add a new phishing scenario:
Click the +NEW button in the upper right corner of the Phishing Simulator > Phishing Scenarios page.
Complete the required fields on the first page, then click Next.
Scenario Name: Enter a name for your scenario.
Now you can click the Save button to create your scenario. Now, you are ready to launch your scenario either using or .
The Just-in-time Learning Page is an intelligent feature that automatically highlights warning signs (red flags) in simulated phishing emails. It provides employees with instant, contextual training at the exact moment of risk.
To set this up, you first need to create both the Just-in-time Learning Page and the Red Flag Email Template. Once completed, you can combine them to build a phishing scenario and launch it to your employees.
If you are ready, please follow the steps to create a scenario.
Before you proceed with this section, please make sure you have created the and .
Click the +NEW button in the upper right corner of the Phishing Simulator > Phishing Scenarios page.
Complete the required fields on the first page, then click Next.
Scenario Name: Enter a name for your scenario.
Now you can click the Save button to create your scenario. Now, you are ready to launch your just-in-time learning page scenario either using or .
This tutorial will cover the Scenarios that are created by combining the Email Template and/or Landing Page and making the campaign ready to send to the target users.
You must either a) create a community, or b) become a member of an existing community. You can access the Communities page by Dashboard > Threat Sharing > Communities. The sub pages of the community page are explained below.
Your Communities
The communities you are enrolled in
The fields of the community page are explained below.
A search window is available to help quickly find a name on the community homepage.
Go to Dashboard > Threat Sharing > Communities and click on the Create Community button.
Next, you will be asked to enter the following from the table below:
Please read and accept the terms and conditions. Then click on Create to complete the process.
After creating your community, you will be directed to the new Threat Sharing Community homepage.
You will now be able to post your first incident.
Go to Dashboard > Threat Sharing > Communities and click on the Three Dots. You will be able to edit the interaction with the fields in the table below.
If you no longer wish to be the owner of a community, you have the option to transfer ownership to a fellow member.
Go to the Communities dashboard
Select the community for which ownership is to be transferred
Go to Members menu
Select the member who will be the new owner
Invite new members to your Community
Once a community has been established, you are able to invite members to join the group. A maximum of five can be invited at one time.
To invite new members;
Go to the right-hand pane of the community homepage
Under About Community, click +Invite and enter the email address of the invite
Click Invite to send your request
Requests
Individuals who are not currently members of the community can request to join. These requests are visible under the Requests option on the community homepage.
The names of the members of your threat sharing community are visible under the Members page. You wil be able to see the following information.
A search window is available to help quickly find a name on the community homepage.
Incidents Page
The names of the incidents of your threat sharing community are visible under the Incidents Page. You will be able to see the following information.
A search window is available to help quickly find a name on the community homepage.
Click on the three dots to the right of the member’s name and click 'Assign as owner' button
Confirm that you are willing to give admin privileges (includes rights to remove users and delete the community) to the new owner
Click Accept to complete the transfer of ownership
A message will appear to confirm that the transfer of the community’s ownership has been successful.
All
All Communities on the platform
Invitations
Invitations waiting for you to accept or decline
Community Name
The name of the post
Users
Number of users in the community
Industry
The industry for to the community
Last Update
The date and time the last post was made
Three Dots (Actions)
Edit Community
Notification Settings
Leave
Delete
Community Name
The name for your community
Community Description
A description of the community with its rules and goals (max. 300 words)
Industry
The industry most relevant to the community
Privacy
Public: Anyone can find the community and see posted threats
Private: Only members invited by the community owner can see posted threats, but the name of the community is listed publicly in the communities list
Hidden: Only members can see posted threats and the name of the group is not displayed in the list of communities
Edit Community
Edit the general information and settings of the community.
Notification Settings
Enable Email notifications
Disable Email notifications
NOTE: If you disable the first notifications setting, no notifications will be sent out to the community to inform them of posted incidents.
Leave
To withdraw from the community. NOTE: You will no longer be able to post incidents to this community; you will have to rejoin or be re-invited.
Delete
To delete the community
Company
The Company that created the threatsharing community
Users
The number of users
Industry
The industry for the community
Posts
The number of posts made
Three Dots (Actions)
See posted incidents
Incident Name
The name of the post
Created by
The name of the user that created the post and the company that the user belongs to
Date Created
The date and time the post was made
Security Label
Security labels to inform recipients about how to share sensitive information. Please visit Traffic Light Protocol for more information.
Details
A preview of the reported threat
Three Dots (Actions)
See posted incidents
Description: Describe the template briefly for your reference.
Category: Select the threat type that classifies your phishing scenario.
Method: Choose the appropriate phishing strategy for your scenario.
Click-Only: Redirect users to a specific landing page, and see who clicks the phishing link within the report.
Data Submission: Redirect users to a page where they must enter requested credentials and see who submits this information in the report.
Attachment: Redirect users to download a file attached within the simulated email, and see who opens the file within the report.
MFA: Redirect users to a Multi-Factor Authentication (MFA) page where they must input a received MFA code to continue, and see who submits MFA codes in the report.
Roles: Add roles to the scenario that fit specific roles.
Tags: Define tags for the scenario.
Make Available For: Make your scenario available to be used by the other customers under your organization. This feature is only available to admins who have Reseller permissions.
Click Next to go to the Email Template page.
On the Email Template page, select the e-mail template you want to use and then click the Next button.
Select the Landing Page template you want to use and then click the Next button to move on to the Summary page.
If the MFA method is selected, you'll find a sub-menu titled "MFA Settings" on the Landing Page. Here, you can customize the "Sender Phone Number" and the text for the "SMS Verification Message".
The Summary page provides you with an overview of the proposed phishing campaign, including the type of campaign, the targeted users, and other important details.
Category: Select the threat type that classifies your phishing scenario.
Method: Choose the appropriate phishing strategy for your scenario. Please make sure the method is the same as your email template and landing page category.
Click-Only: Redirect users to a specific landing page, and see who clicks the phishing link within the report.
Data Submission: Redirect users to a page where they must enter requested credentials and see who submits this information in the report.
Attachment: Redirect users to download a file attached within the simulated email, and see who opens the file within the report.
MFA: Redirect users to a Multi-Factor Authentication (MFA) page where they must input a received MFA code to continue, and see who submits MFA codes in the report.
Roles: Add roles to the scenario that fit specific roles.
Tags: Define tags for the scenario.
Make Available For: Make your scenario available to be used by the other customers under your organization. This feature is only available to admins who have Reseller permissions.
Click Next to go to the Email Template page.
On the Email Template page, select the red flags email template you created and then click the Next button.
On the Landing Page page, select the just-in-time learning page and then click the Next button to move on to the Summary page.
If the MFA method is selected, you'll find a sub-menu titled "MFA Settings" on the Landing Page. Here, you can customize the "Sender Phone Number" and the text for the "SMS Verification Message".
The Summary page provides you with an overview of the proposed phishing campaign, including the type of campaign, the targeted users, and other important details.
MFA: Used to detect target users who enter their MFA codes on the landing page
Languages
Filter scenarios based on your preferred languages.
Roles
Filter scenarios based on the roles.
Tags
Tags can be added to the phishing scenario to enable viewing using related tag lists.
Difficulty
The level of difficulty to recognize a phishing attempt (Easy, Medium, Hard). Please click here to see how the difficulty level is determined.
Created By
System: Standard phishing scenario templates provided with the product.
Custom: Phishing scenarios created or customized by system users.
Date Created
The date and time the phishing scenario was created.
Campaign Name
The name used to identify the phishing campaign and the name that will be used on the report generated at the conclusion of the campaign
Target Groups
The group(s) selected to receive the phishing campaign message
Mark as Test
The phishing report can be removed from other reporting areas of the platform
Limit Recipients
The phishing campaign can be designed to be sent to random users in the target group according to a percentage or user count.
Scenario Info
Basic information about the phishing campaign
Settings
Settings information of the phishing campaign
Other
Any other additional information about the campaign
Target Users
The users to whom the phishing campaign will be sent
Email that will be sent to users
Preview of the phishing email that will be sent
Landing page for users who click the phishing link
Preview of the landing page when a user clicks the phishing link used in this campaign
The Phishing Simulator > Phishing Scenarios > Email Templates page provides you with system default phishing email templates. You can use them as they are or customize them as needed for your phishing campaign.
The components of the Email Templates page are explained below.
Template name
Name of the email template
Method
The phishing technique employed.
Data Submit = Used to detect target users who submit data on the landing page
Attachment = Used to detect target users who download the attachment in the phishing simulation email
Click-Only = Used to detect target users who click unknown links in the phishing email
Languages
Filter email templates based on your preferred languages.
Tags
This section explains how to edit, preview, clone, or delete an e-mail template.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Edit button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Preview button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Duplicate button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Delete button.
Follow the steps below to create a new email template for use in a new or existing phishing campaign:
Click the +New button in the upper right corner of the Phishing Simulator > Phishing Scenarios > Email Templates page.
Complete the required fields on the first page, then click Next.
Complete the sections below on the Email Settings page:
Follow the steps below to create a new email template with red flags for use in a new or existing phishing campaign:
Click the +New button in the upper right corner of the Phishing Simulator > Phishing Scenarios > Email Templates page.
Complete the required fields on the first page, then click Next.
Complete the sections below on the Email Settings page:
Once you save your email template, now click to learn how to create and use the email template with just-in-time learning page.
Follow the steps below to effortlessly create custom email templates with the help of AI Ally. Once your template is ready, it can be used in a new or existing phishing campaign:
Click the +New button in the upper right corner of the Phishing Simulator > Phishing Scenarios > Email Templates page.
Complete the required fields on the first Template Info page, then click Next.
Click on Use AI Ally and describe the scenario and key details for the email template you want to generate.
Here are some helpful ready-to-use AI prompts for creating email templates.
Here's a list of merge tags to help you make your email template more personal. Adding these tags can make your phishing campaign more tailored to the recipient.
The Email Templates page provides you with system-default phishing email templates. You can use them as they are or customize them as needed for your phishing campaign.
Landing pages direct the user to a specific page, and can be used for a variety of purposes, such as requesting login credentials or other sensitive information.
The Phishing Simulator > Phishing Scenarios > Landing Page Templates page contains standard default landing pages you can select and use for your phishing scenario or customize according to your preferences. You also have the option to create an entirely new landing page.
The components of the Landing Page Templates page are explained below.
Template name
The name of the landing page template
Method
The phishing technique employed.
Data Submit: Used to detect target users who submit data on the landing page
Attachment: Used to detect target users who download the attachment in the phishing simulation email
Click-Only: Used to detect target users who click unknown links in the phishing email
Languages
This section explains how to edit, preview, clone, or delete a landing page.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Edit button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Preview button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Duplicate button.
Click on the three dots '⋮' button in the Actions option on the far right of the relevant page, and then click the Delete button.
Follow the steps below to add a new landing page that you can use in a new or existing phishing scenario:
Click the +New button in the upper right corner of the Phishing Simulator > Phishing Scenarios > Landing Page Templates page.
Complete the required fields on the first Template Info page, then click Next.
On the Page Settings page, provide the Phishing Link: the URL to be used in the phishing email.
Follow the steps below to add a new just-in-time learning page that you can use in a new or existing phishing scenario:
Go to Phishing Simulator > Phishing Scenarios > Landing Page Templates page.
Search 'Just-in-time Learning Page: Email Warning Signs' and click the Duplicate button to customize.
Customize any fields on the first Template Info page, then click Next.
Once you create your just-in-time learning page, now click to learn how to combine your red flag email template and just-in-time learning page in a scenario to be able to launch to your employees.
Follow the steps below to effortlessly create custom landing page templates with the help of AI Ally. Once your landing page template is ready, it can be used in a new or existing phishing campaign:
Click the +New button in the upper right corner of the Phishing Simulator > Phishing Scenarios > Landing Page Templates page.
Complete the required fields on the first Template Info page, then click Next.
On the Page Settings page, provide the Phishing Link: the URL to be used in the phishing email.
Here are some helpful ready-to-use AI prompts for creating landing pages.
JavaScript enhances landing pages with dynamic behavior and interactivity. This capability helps you create more engaging and realistic phishing simulations by enabling features such as:
Real-time content manipulation Example: Add a countdown timer that shows “You have 30 seconds left to complete this form.” This creates urgency and makes the simulation feel more realistic.
Form validation Example: When a user tries to submit a form without entering an email address, JavaScript can show a warning like: “Please enter your email before submitting.” This mimics real websites that check inputs.
Conditional content display Example: Show a hidden message only if a user types in a certain keyword or clicks a specific button, such as “Access Granted” after filling a field correctly.
Please follow the steps below to use the JavaScript code editor feature.
Go to Phishing Simulator > Phishing Scenarios > Landing Pages
Click + NEW to create a new landing page
Complete the required fields on the first page, then click Next
Click Edit at the bottom center of the page to open the landing page editor
You can now with your email template and landing page and then it to your email inbox to test the landing page to confirm if everything works as you expect.
Here's a list of merge tags to help you make your landing pages more personal. Adding these tags can make your phishing campaign more tailored to the recipient.
Landing pages direct the user to a specific page and can be used for a variety of purposes, such as requesting login credentials or other sensitive information. This tutorial will walk through the steps of creating/editing a landing page.
A: Yes! You can direct users to your own URL instead of using a standard Keepnet landing page. To set this up, select a Keepnet landing page, and replace the URL in the provided HTML code with the URL of your hosted landing page. Here’s how you do it:
Choose a Keepnet landing page for your phishing scenario.
Insert the following HTML code, substituting https://www.google.com with your own landing page URL:
This setup will automatically redirect anyone who clicks on the link to your chosen landing page after 1 second, allowing us to track the click-through.
Subject: Subject line of the phishing email
From Name: Sender name that will be visible to the target recipient
From Email Address: Sender email address information that will be visible to the target recipient
CC: Add a CC email address to your phishing simulation email.
Attach File: If desired, you can attach a file to the phishing email. This option is only available if the email template method type is set to Attachment.
View/Edit Template: View and edit the available email templates in localized languages.
Localize: Localize your main email template to different languages. Click here to learn the benefits of the feature and more information.
Show Red Flags: Let AI Ally scan the email template and highlight suspicious elements—such as mismatched sender addresses, fake buttons, or misleading icons—while employees are expected to spot these red flags on their own.
Import Email: Use the three-dot button to import an MSG or EML file and customize it.
Click Edit to make any changes or Save to complete the process.
From Name: Sender name that will be visible to the target recipient
From Email Address: Sender email address information that will be visible to the target recipient
CC: Add a CC email address to your phishing simulation email. This is optional.
Attach File: If desired, you can attach a file to the phishing email. This option is only available if the email template method type is set to Attachment.
View/Edit Template: View and edit the available email templates in localized languages.
Localize: Localize your main email template to different languages.
Import Email: Use the three-dot button to import an MSG or EML file and customize it.
Show Red Flags: Click the button for AI Ally to scan the email template and highlight suspicious elements—such as mismatched sender addresses, fake buttons, or misleading icons—while employees are expected to spot these red flags on their own.
Click Edit to make any changes or Save to complete the process.
Once described, select the Language in which the email template will be created.
If you prefer a plain text email template, do not select the Enable styled HTML format option. For an HTML-formatted email template, you may choose this option.
After providing the scenario details, click the Generate Email Template button to create your template.
Once the template is generated, complete the following sections on the Email Settings page:
Subject: AI Ally will write a subject for your email template; you may customize it.
From Name: Specify the sender's name that will be visible to the recipient.
From Email Address: Provide the sender's email address that will be visible to the recipient.
CC: Add a CC email address to your phishing simulation email.
Attach File: If desired, you can attach a file to the phishing email. This option is only available if the email template method type is set to Attachment.
Click Edit to make any changes, or Save to finalize the email template creation process.
Payroll Adjustment Notification
Make a template that seems to be from the Payroll Department, informing the user of a recent adjustment to their paycheck due to an error. Include a link where they can view the updated payment details. The tone should be apologetic for the error but emphasize the need for the user to verify the correction.
Company Event Registration
Create a template that looks like it’s from the company’s event planning team, inviting the user to register for an upcoming company-wide event. The email should include a link to a registration page and stress that space is limited, so they should register as soon as possible. The tone should be enthusiastic and encouraging.
Account Deactivation Notice
Make a template that looks like it’s from the user’s account management system, warning them that their account will be deactivated if they do not confirm their details by clicking a provided link. The tone should be formal and emphasize the importance of maintaining active status.
Software Update Required
Create a template that looks like it’s from the IT department, informing the user that a critical software update is required to maintain system security. The email should include a link to start the update process and make the tone urgent, with a focus on preventing potential security vulnerabilities.
From Name
Inserts the sender's name from the associated email template for this landing page scenario.
From Email
Inserts the sender's email address from the associated email template for this landing page scenario.
Subject
Inserts the subject line from the associated email template for this landing page scenario.
Company Logo
Displays your organization's logo, sourced from the page.
Company Name
Displays your organization's name, sourced from the company profile.
Date Sent
Inserts the date when the campaign is launched.
Current Date
Inserts the current date when the campaign is launched.
Current Date Plus 10 Days
Inserts a date that is 10 days after the campaign's launch date.
Current Date Minus 10 Days
Inserts a date that is 10 days before the campaign's launch date.
Random Number One Digit
Generates and inserts a random one-digit number.
Random Number Two Digit
Generates and inserts a random two-digit number.
Random Number Three Digit
Generates and inserts a random three-digit number.
Tags can be added to the email template to enable viewing using related tag lists.
Difficulty
The level of difficulty to recognize a phishing attempt (Easy, Medium, Hard). Please click here to see how the difficulty level is determined.
Creation Type
Filter email templates based on their creation type (e.g., Manual or AI Ally).
Created By
System: Standard phishing email templates are provided with the product.
Custom: Phishing email created or customized by users
Date Created
The date and time the email template was created
IT Policy Update Request
Make a template that looks like it is coming from our organization’s IT department, notifying the user about a critical policy update that requires their immediate review. The email should contain a link to a document that they need to acknowledge by the end of the day to remain compliant. Make the tone serious, emphasizing the importance of adhering to the new policy.
Finance Department Alert
Create a template that appears to be from our Finance Department, asking the user to verify a payment that is scheduled for today. Include a link that directs them to a secure page to review the details. The tone should be urgent and professional, with an emphasis on preventing unauthorized transactions.
HR Benefits Update
Make a template that looks like it is coming from our HR department, informing the user about changes to their benefits package. They are asked to log in to the benefits portal via a provided link to review and accept the new terms. The tone should be informative yet urgent, stressing the need to complete this before the end of the week.
CEO Urgent Assistance Request
Create a template that appears to come from our CEO, requesting the user’s urgent help in reviewing a confidential document. The CEO should mention that they are relying on the user’s expertise and that a quick response is needed due to a tight deadline. The tone should be friendly but emphasize the urgency of the task.
Suspicious Login Alert
Make a template that looks like it is coming from the organization’s security team, warning the user about a suspicious login attempt on their account. The email should urge them to click a link to verify their identity and secure their account. The tone should be urgent, with a focus on protecting the user’s account from unauthorized access.
Coworker Sharing a Resource
Create a template that looks like it’s coming from a coworker, sharing a useful resource or guide related to the user’s recent project. The email should include a link that appears to be to a legitimate document-sharing service. The tone should be casual and collaborative, encouraging the user to check it out.
Full Name
Inserts the target user's first and last name.
First Name
Inserts the target user's first name.
Last Name
Inserts the target user's last name.
Phishing URL
Inserts a phishing simulation URL for the recipient to click and view the landing page.
Inserts the target user's email address.
Localize: Localize your main landing page template to different languages. Click here to learn the benefits of the feature and more information.
Click Edit to make any changes or Save to complete the process.
Review your red flag landing page, or click the Edit button to customize it.
Once you complete customization or review, click Save to complete the process.
Click on Use AI Ally and describe the scenario and key details for the landing page you want to generate.
Once described, select the Language in which the landing page will be created.
After providing the scenario details, click the Generate Landing Page button to create your landing page.
Once the landing page is generated, click Edit to make any changes, or Save to finalize the landing page template creation process.
Bank Account Login Page
Data Submission
Create a landing page that mimics a bank account login page. Include fields for "Username" and "Password", a "Forgot Username or Password?" link, and a "Sign In" button. Add a small bank logo at the top, and include links for "Enroll Now" and "Help". The design should be secure and professional, with a dark blue and white color scheme.
Subscription Confirmation Page
Data Submission
Create a landing page for subscription confirmation. Include a message saying "Thank you for subscribing!", a field for entering an email address to confirm the subscription, and a "Confirm Subscription" button. Add a small note about privacy at the bottom. The design should be clean and modern, with a focus on ease of use.
E-commerce Checkout Page
Data Submission
Create a landing page for an e-commerce checkout process. Include fields for billing information (name, address, city, state, zip code), payment information (credit card number, expiration date, CVV), and a "Place Order" button. Add a small shopping cart icon at the top, and a summary of the order on the right side. The design should be user-friendly with a focus on security.
Event Ticket Purchase Page
Data Submission
Create a landing page for purchasing event tickets. Include fields for selecting the number of tickets, seating options, and payment details. Add a "Purchase Tickets" button at the bottom, and a small banner at the top with the event name and date. The design should be vibrant and engaging, with a focus on creating excitement for the event.
Phishing Awareness Oops Page
Click Only
Create a landing page that tells the user they've clicked on a simulated phishing email. The message should say "Oops! The email you just clicked was a phishing simulation. Don't worry, this is to help you learn." Include three key rules: 1. Avoid unknown links/attachments. 2. Verify the sender's email. 3. Be cautious of too-good-to-be-true offers. The design should be clear and educational.
Security Training Oops Page
Click Only
Create a landing page that informs the user they interacted with a simulated phishing email. The message should say "Oops! You just clicked on a test phishing email for training purposes." Include three rules: 1. Avoid unknown links. 2. Verify sender legitimacy. 3. Be cautious of urgent requests. Design it to be instructional and easy to understand.
At the top of the editor, click Import to open the HTML code editor
Inside the editor, locate the notice: “Some scripts may be blocked for security reasons. Click here to add custom JavaScript code.”
Click the link to open a pop-up where you can safely insert your JavaScript
After inserting your script, click Save to apply your changes and publish the landing page
From Email
Inserts the sender's email address from the associated email template for this landing page scenario.
Subject
Inserts the subject line from the associated email template for this landing page scenario.
Company Logo
Displays your organization's logo, sourced from the page.
Company Name
Displays your organization's name, sourced from the company profile.
Date Sent
Inserts the date when the campaign is launched.
Current Date
Inserts the current date when the campaign is launched.
Current Date Plus 10 Days
Inserts a date that is 10 days after the campaign's launch date.
Current Date Minus 10 Days
Inserts a date that is 10 days before the campaign's launch date.
Random Number One Digit
Generates and inserts a random one-digit number.
Random Number Two Digit
Generates and inserts a random two-digit number.
Random Number Three Digit
Generates and inserts a random three-digit number.
User Language
Inserts the target user's Preferred Language information on the landing page
User Department
Inserts the target user's Department information on the landing page.
Filter landing pages based on your preferred languages.
Difficulty
The level of difficulty to recognize a phishing attempt (Easy, Medium, Hard). Please click here to see how the difficulty level is determined.
Creation Type
Filter landing pages based on their creation type (e.g., Manual or AI Ally).
Created By
System: Standard landing page templates are provided with the product.
Custom: Landing pages created or customized by users
Stop Bot Activity
It shows the stop bot activity feature enabled for the landing page. By default, it is enabled and cannot be disabled to ensure that the target user activities are accurately captured.
Tags
Tags can be added to the landing page to enable viewing using related tag lists.
Date Created
The date and time the landing page was created
Google Login Page
Data Submission
Create a landing page that closely resembles the Google Login Page. Ensure the design includes fields for email and password input, a "Forgot email?" link, and a "Next" button. Include a Google logo at the top and a small text link for "Help" and "Privacy Policy". The page should have a clean, minimalistic design with a white background.
Amazon Login Page
Data Submission
Create a landing page that looks like the Amazon Login Page. Include fields for email and password, a "Forgot Password?" link, and a "Sign-In" button. Add a small Amazon logo at the top and include a checkbox for "Keep me signed in". Below the login form, include a "Create your Amazon account" link. The design should have a white background with light gray borders.
Company Event Registration Form
Data Submission
Create a landing page for a company event registration. Include fields for full name, email, phone number, and a dropdown to select the department. Add a "Register" button at the bottom. The page should also include a banner at the top with the company logo and event name. The color scheme should match typical corporate branding with a professional look.
Password Reset Page
Data Submission
Full Name
Inserts the target user's first and last name.
First Name
Inserts the target user's first name.
Last Name
Inserts the target user's last name.
Inserts the target user's email address.
From Name
Inserts the sender's name from the associated email template for this landing page scenario.
Create a landing page for a system password reset. Include a field for entering the email address, a "Submit" button, and a link for "Contact Support" in case the user has trouble resetting their password. The design should be simple with a white background, and include a small company logo at the top. The instructions should be clear and concise.
htmlCopy code<meta http-equiv="refresh" content="1; URL=https://www.your-landing-page.com" />A phishing campaign can be launched to target users in two ways. The Fast Launch option allows you to initiate a phishing campaign quickly and easily, without having to designate any settings. However, if you prefer customization, advanced features are available to refine the campaign using the Campaign Manager option, such as Schedule, Multiple Target Groups, SMTP Delay, Expire Date, Multiple Scenarios, and Randomize to allow you to modify a variety of elements to suit your needs.
The components of the Campaign Manager page are explained below.
These settings give you the ability to edit, preview, or delete campaigns, as well as create new instances. You can also resend a campaign to specific users.
Click on the three dots “︙” button under the Action heading to adjust the following features.
In the Campaign Name column, the Instances option will provide details of the campaign, such as how many times it has been launched and the users targeted.
The components of the Campaign Instances page are explained below.
You can delete, pause, or resume a paused instance on the Campaign Instances page as well as you also have the option to view detailed reports of an instance or resend the campaign.
Click on "+ NEW" on the Phishing Simulator > Campaign Manager page to create a new phishing campaign to set up to launch target users in four simple steps:
Campaign Settings
Phishing Scenarios
Target Audience
Delivery Settings
Before launching a phishing campaign, you must create a .
Enter basic information about this campaign. The components of the Campaign Info page are explained below.
Select one scenario to send selected target users or select multiple phishing scenarios to distribute randomly.
Select target groups for your campaign.
Set email delivery options.
The components of the Delivery Settings page are explained below.
All of the phishing campaign details are easily accessible on one page, along with a preview of the phishing scenario and the landing page.
The components of the Campaign Summary page are explained below.
Click Start to launch the campaign.
Click Cancel to rescind all of the actions, then click Quit in the pop-up window. If you want to make additional edits, click Continue Editing.
The "Reply Tracking" feature allows system administrators to monitor and identify users who respond to phishing simulation emails. This not only helps in evaluating employee awareness but also provides valuable insights into how users engage with suspicious emails. By understanding user behavior, organizations can tailor their training efforts and mitigate potential risks more effectively.
Identify High-Risk Users: Track which employees engage with phishing emails by replying, so you can provide targeted training to address their vulnerabilities.
Gain Behavioral Insights: Understand what employees typically write when responding to phishing emails, which can reveal potential patterns of risky behavior.
Improve Security Awareness: Use the data collected to refine your awareness campaigns and educate employees on best practices for handling suspicious emails.
Follow the steps below to enable and utilize this feature:
Navigate to Phishing Simulator > Campaign Manager, then click the + NEW button.
Fill in the required fields. For more details on setting up a campaign, refer to the .
Enable the "Reply Tracking" option.
Enter a custom email name and select one of the simulation domains
Once your campaign is live, any employee who replies to the simulation email will appear in the campaign report under the Replied menu. You can review the details of their replies if you have enabled the "Save reply email content for review" option.
For more information about campaign reports, refer to the full documentation .
The Preferred Language feature allows you to send phishing simulation scenarios in each recipient’s preferred language. If a preferred language is not set, the system will default to the company's preferred language.
Before launching a campaign with this feature, you must assign preferred languages to users:
Navigate to Company > Target Users.
Assign a preferred language to each user.
Add these users into a Target Group.
Before creating a campaign that sends a scenario in your users’ preferred languages, make sure the scenario includes a localized email template and landing page. This ensures each employee receives both assets in their own preferred language.
Create or duplicate an , then add localized versions for the required languages using the localization feature.
Create or duplicate a , then add localized versions for the required languages using the localization feature.
Create a scenario and add your localized email template and landing page.
You can now proceed to the next section to launch your scenario.
To launch a campaign using this feature:
Navigate to Phishing Simulator > Campaign Manager.
Click the + NEW button to create a new campaign.
In the Hyper-Personalization section, select:
"Send in the target users’ preferred language"
If a scenario template is available in the user's preferred language, they will receive that version.
If a scenario template is not available in the user’s preferred language, the system will send the scenario in the company’s default language.
If no scenario template matches either the user's preferred language or the company’s default language, the system will prompt you to select appropriate language versions before launch.
This ensures that users receive scenarios in the most relevant language for them, improving the effectiveness of phishing simulations.
This tutorial covers the Campaign Manager options such as Schedule, Multiple Target Groups, SMTP Delay, Expire Date, Multiple Scenarios, and Randomize to allow you to modify various elements to suit your needs.
A: Yes. The Incident Responder investigation feature gives you the capability to delete the phishing simulation email.
A: No. You can only cancel the campaign before the launch date.
A: Yes. You can adjust the campaign settings at any time before the launch date.
A: Yes. On the Advanced Settings tab, the Exclude from reports feature provides this capability.
A: When multiple scenarios are selected for a campaign, the distribution of emails will be calculated based on the number of users divided by the number of scenarios. For example, if you have 100 users and 4 scenarios, each scenario will be sent to 25 users.
A: This header prevents Microsoft Defender from analyzing links in phishing simulation emails, ensuring accurate test results and preventing false positives.
A: This status occurs because the user clicked the simulation link and was redirected to the training enrollment page but did not click the 'START TRAINING' button to begin the training.
Until the user actively starts the training by clicking this button, their status will remain as 'In Queue'. Once they start the training, the status will automatically update accordingly.
List the phishing campaigns that were launched with training content.
Created By
The source of the phishing campaign (system, custom)
Email Delivery
The selected email delivery option, or rule.
Date Created
The date and time the campaign was created
Last Launch
The date of the most recent use of the campaign
Campaign Summary
Select training and send the training via email or redirect it immediately once the user falls for a phishing campaign.
Enrollment: Users can either be redirected to the training immediately with the "Start Training Immediately" option or opt to receive the training later through an email with the "Enroll via Email Notification" option.
Click Only: The users who click the phishing link will be redirected to the training immediately, or a training email will sent later.
Data Submission: The users who submit their credentials will be redirected to the training immediately, or a training email will sent later.
By enabling the frequency feature, you can view the date and time when the scenarios will be delivered to the selected groups.
To review the content of reply emails, enable the "Save reply email content for review" option. This allows you to view the content of the replies directly in the campaign report.
Click Next and select the scenario you wish to launch for your employees.
Configure the remaining settings as needed. For detailed guidance, refer to the "Create a Campaign" section in the documentation.
Complete the remaining campaign fields and settings as needed.
Click Next to proceed through scenario selection, target groups, and other customizations.
Click Launch to start the campaign.
Campaign Name
The name of the campaign
Instance information indicating the number of times the campaign has been launched is available next to the campaign name
Target Users
The target users who will receive the phishing email
Status
Status information of the campaign. (idle, running, completed, paused, canceled, error)
Idle = The campaign is launched and has not started yet
Running = The campaign is in progress
Completed = The campaign is delivered to all target users
Paused = The campaign has been temporarily suspended
Canceled = The campaign has been withdrawn
Error = The status field displays an error message if there is a delivery problem
Scenarios
Shows how many scenarios has been launched in the campaign.
Scenario Distribution
Shows how scenarios are assigned to users (e.g., same random scenario for all, different random scenarios for each, AI Ally selects scenario for each user or manual selection).
Method
Method type of the campaign
Preview
Preview the campaign details, including the Email Template, Landing Page, and any associated training content that was selected.
Edit
Change the settings of the relevant campaign
Create New Instance
Create a copy of the same campaign and launch it to the different target groups.
Delete
Delete the campaign
Frequency
If you have selected multiple scenarios, it shows how often the system will send the selected scenarios randomly to the selected groups.
Start Time
The date and time the campaign is launched
Target Users
The total target users that the campaign was launched to.
Status
Current status of the campaign (idle, running, completed, paused, canceled, error)
Date Created
The creation date of the campaign
Launch
Resend a campaign to a selected group
View Report
Access detailed reports of a campaign You can find more information about the report details here
Delete
Delete the campaign report
Cancel
Terminate an active campaign. The system won't send the phishing email to the users who haven't received it.
Campaign Name
The name of the campaign
Hyper-Personalization
This feature allows you to tailor simulation scenarios based on the recipient’s language preferences. You can choose from two options when launching a campaign:
Send in a manually selected language: Select a specific language to send the scenario to all recipients, regardless of their preferred language settings.
Send in the target users' preferred language: Deliver scenarios in each recipient’s preferred language. If a user has no preferred language set, the scenario will be sent in the company's default language.
Smart Grouping
Users who clicked the campaign are automatically added to the selected target group.
Tracking Duration
Select the time period you want to keep this campaign active
Mark As Test
Select this box if you want to exclude the results of the campaign from the overall company score
Reply Tracking
Enter custom reply-to address to track replies. Please click here to learn more.
Scenarios
Select scenarios to be sent to selected target users.
Type
Filter scenarios according to their method type.
Language
Filter scenarios according to their language.
Difficulty
Filter scenarios according to their difficulty level.
Category
Filter scenarios according to their threat type.
Scenario Distribution
Select how scenarios will be sent to users:
Select scenarios manually: The selected scenarios by the admin will be sent to target users.
Select random scenarios for each user: The platform will randomly select scenarios from the scenarios menu for each user. Use filters (Type, Language, Difficulty, and Category) to list scenarios from which the platform will pick randomly.
Select the same random scenario for all users: The platform will randomly select one scenario from the scenarios menu for all users. Use filters (Type, Language, Difficulty, and Category) to list scenarios from which the platform will pick randomly.
AI Ally selects scenario for each user: If you filter scenarios by Type, Language, Difficulty, or Category and then proceed to select target users, the AI Ally will choose a scenario from the filtered options for each user.
The selection will be based on each user's specific attributes, such as their Phone Number, Timezone, Company Country, and Department Name to ensure the most relevant scenario is sent to each user.
As information, Personally Identifiable Information (PII) is never shared with the AI model.
Target Audience
Choose one or several recipient groups to send the selected phishing scenarios to.
Limit Recipients
Send only to users with an active phishing reporter add-in: Select this option to send the campaign only to users with an active phishing reporter plug-in.
Send this campaign to randomly selected users: Choose this option to send the phishing campaign to randomly selected users within the target group. You have the option to choose a percentage of the group or a specific number of users.
Email Delivery
Frequency
If you have selected multiple scenarios, you can choose how often you would like to send the scenarios randomly to the selected groups.
Schedule
The date and time of the campaign launch:
Save for later: Check this box if you want to send the campaign later. To send now, click the "Now" button after opening the date and time pop-up.
Schedule for: Check this box to begin the campaign on a specific date.
Enable Region-Aware Time Zone Delivery: Send phishing simulation emails based on the target users' time zones. Users without a defined time zone will receive the email based on the organization's main time zone.
Distribution
When you launch a phishing campaign to a large audience, this feature ensures that the emails are not blocked or quarantined by the recipient's email server. It achieves this by distributing the emails over a period of time rather than sending them all at once.
Send emails when the campaign starts: As the campaign begins, emails are immediately dispatched to the selected target users.
Send emails on defined days and hours: You can determine the specific days and times when emails will be delivered to the chosen target users.
Sending limit per batch: Define the quantity of emails you'd like to send to the recipients in each batch during the chosen days and times.
Send emails with delay every: Decide on the duration of the pause between sending each batch, whether it's in seconds, minutes, or hours.
The system will automatically determine and show you the duration required to send the campaign to the designated number of recipients based on your chosen settings.
Campaign Info
The name of the campaign, the difficulty level, and the phishing technique employed. (Data Submission, Click only, Attachment)
Settings
Date and time of the campaign, the number of emails to be sent, and the email delivery info
Other
Other additional enabled settings will appear here such as "mark as test" option.
Target Users
The target users who will receive the phishing email.
Click on Preview to see the target users count and target user groups.
Email that will be sent to users
The phishing email template selected for the campaign
Click Preview to see how it will be displayed in the target users’ inboxes
Landing page for users who click on the phishing link
The landing page template selected for the campaign.
Click Preview to see how it will be displayed in the target users’ browsers
Training
Training
Schedule
Attachment: The users who open the attached file will receive the training via email.
MFA: The users who submit their MFA code will be redirected to the training immediately, or a training email will sent later.
Reminder: The users who don't complete the training will receive additional reminder emails.
Certificate: The users who complete the training will receive a certificate. dit Training Redirect Page: The training redirect page is written in English by default, but it can be fully customized. The users who once fall to simulation will be redirected to the training redirection page if you selected the 'Start Training Immediately' option.
This section describes the basic functionalities of phishing campaign reports, which you can find from the Phishing Simulator > Campaign Manager and click the Instances button to access the reports of the phishing campaign.
Once you go inside the Instances of a campaign, you will see reports for that campaign; click on the View Report button under the Actions column to access the phishing campaign report.
In a campaign report, there are many sub-menus that provide valuable statistics about your phishing campaign. Here are the following menus on a campaign report:
The Summary provides a brief synopsis of the phishing scenario and options for further action.
This section provides the opportunity to display the results of the campaign in a useful pie chart presentation.
This section displays general information about the content of the phishing scenario. If you selected multiple scenarios, you can switch between them to preview.
This section displays details of the sender’s name, the difficulty level, and the phishing scenario type sent to the target users.
You can preview the email template design of the phishing scenario sent to the target users by clicking on the Preview button.
The URL, difficulty level, and scenario type of the landing page content of the phishing scenario sent to the target users are displayed here.
You can preview the landing page design of the phishing scenario sent to the target users by clicking on the Preview button.
This section displays the information of the target users who opened the phishing scenario email.
This section provides details of the target users who clicked on the phishing link.
This section displays details of a target user who submitted data on the landing page of the phishing scenario.
This section displays the details of a target user who opened the attachment file.
This section displays the details of target users who did not take any action in response to the phishing email.
This section provides details of target users who reported phishing emails using the phishing reporter add-in.
This section provides a summary report of the delivery of the phishing email to the target users.
When a user submits a form containing a password field, we evaluate the password using a scoring system that determines how strong or weak it is. This score is based on the structure and patterns used in the password.
We do not store or receive full user passwords. Before the form is submitted:
Only the first character of the password is kept.
All remaining characters are replaced with asterisks (*), e.g. P********.
Positive Scoring Factors
Negative Scoring Factors
Complexity Rating (Based on Score)
Thank you — here is the final version incorporating that bot activity may apply to both "Opened Email" and "Clicked Link" events, and still maintaining the correct documentation format with only one Heading 2 and one Subheading 3:
In phishing campaign reports, Human Activity refers to real actions taken by users, such as opening emails, clicking links, or submitting data. In contrast, Bot Activity represents automated interactions triggered by email security systems, spam filters, or sandboxing tools. These bots scan emails and follow links as part of their protective duties—sometimes even before users see the message.
Bot activity may appear in both Opened Email and Clicked Link sections of the report. For example, if a security system opens an email to analyze it, or clicks a link to test the destination, these actions may be captured and flagged as bot interactions.
To ensure accurate reporting, the platform automatically detects and labels such activity based on predefined detection rules. Any record classified as Bot Activity will carry a special tag and can be excluded from the view by clicking the “Hide Bot Activity” button. Admins can also hover over the info (ⓘ) icon in the Activity Type column to see which rule was triggered.
The detection rules are:
A1 – Unusual User-Agent Interacted: Triggered when an atypical or suspicious user-agent (browser identifier) is detected.
A2 – Honeypot Link Reused: The hidden phishing link inside of the email clicked multiple times by the same IP and user-agent within 5 minutes—indicating automation.
A3 – Same-Second Activity Spike: Multiple activities occurred at the exact same time, which is unlikely for human users.
If customers see several entries marked as Bot Activity, it typically means that their security tools pre-screened the phishing simulation links. To evaluate real user behavior, they should filter the report by Activity Type or use the “Hide Bot Activity” toggle. For better accuracy in future simulations, they may consider whitelisting Keepnet domains to reduce interference from automated systems.
By filtering out bot noise, organizations gain a clearer understanding of true user actions and risk levels.
This tutorial describes the basic functionalities of phishing campaign reports which you can find in the Campaign Reports menu.
A: Yes. You can download a report that provides details of the campaign by clicking on the Download Report button.
A: No. The information in the report cannot be changed.
A: Yes. The resend function allows you to send the phishing scenario to any user you select.
A: Yes. The Sending Report option provides you with a view of the current activity of the phishing scenario.
A: Yes. You can transfer all of our reports through an API, enabling you to use the information as needed to suit your business. Additional information on APIs is available
A: The differences are explained below.
"Only Opened Emails" will show the users who only opened the email and didn't go further, such as clicking the link.
"Only Clicked Links" will show the users who opened the email and then clicked the link and didn't go further, such as data submission.
"Opened Emails" will show the users who opened emails. It doesn't matter if user clicked the link or submitted any data.
A: Please see below how the Sandbox Activity Detection feature works to identify false positive clicks.
Rule 1: User Agent Signatures: We have a list of 10+ sandbox user agent patterns. If a user action matches these, it's flagged as sandbox activity.
Rule 2: Honeypot Link: We embed invisible "Honeypot" links in our emails. While humans can't see or click them, sandboxes often access them, revealing their presence.
Rule 3: Request Header Analysis: By examining request headers, we can identify unique characteristics that differentiate sandbox activities from real user actions.
A: If users did not receive the simulation email via DEC and show the error 'The process failed to get the correct properties' in the Sending Report section of the campaign report, it may indicate that these users have been deleted, do not have an email license, have no inbox, or have been deactivated. Please check the users in your Microsoft 365 admin panel to ensure they are all active and have a valid mailbox license.
Reply Tracking
Shows if the reply tracking feature is enabled or not for the phishing campaign.
Scenario Name
Name of the phishing scenario that is sent to user
Scenario Language
Language of the related scenario that was sent to user.
Last Opened
Date and time a target user last opened the phishing email
Times Opened
Number of times a target user opened the phishing email
Hide Sandbox Activity
If a sandbox solution has analyzed the simulated phishing email that is generated for the target user, you can choose to show or hide this false positive information in the menu.
Activity Type
List the human or sandbox activities by using one of the following options.
Human Activity: The human has opened the simulated phishing email.
Sandbox Activity: The sandbox solutions have opened the simulated phishing email.
Action
The Resend button allows you to resend the same phishing email.
The Details option shows the date and time a user opened the phishing email, the user agent, browser information, geolocation, IP information, and other information.
Language of the related scenario that was sent to user.
Last Clicked
Date and time the user last clicked on the URL in the phishing email
Times Clicked
Number of times the user clicked on the phishing link
Hide Sandbox Activity
If a sandbox solution has analyzed the simulated phishing email that is generated for the target user, you can choose to show or hide this false positive information in the menu.
Activity Type
List the human or sandbox activities by using one of the following options.
Human Activity: The human has clicked the simulated phishing link.
Sandbox Activity: The sandbox solutions have clicked the simulated phishing link.
Action
The Resend button allows you to resend the same phishing email.
The Details option shows the date and time a user opened the phishing email, the user agent, browser information, geolocation, IP information, and other information.
Name of the phishing scenario that is sent to user
Scenario Language
Language of the related scenario that was sent to user.
Last Submission
Date and time that the user last submitted data on the landing page of the phishing scenario
Times Submitted
Number of times that the target user submitted data on the landing page of the phishing scenario
Action
The Resend button allows you to resend the same phishing email.
The Details option shows the date and time a user opened the phishing email, the user agent, browser information, geolocation, IP information, and other information.
Language of the related scenario that was sent to user.
Last Opened
Date and time that the user last opened the attachment file
Times Opened
Number of times that the target user opened the attached file
Activity Type
It shows if the user has data for the campaign.
Action
The Resend button allows you to resend the same phishing email.
The Details option shows the date and time a user opened the phishing email, the user agent, browser information, geolocation, IP information, and other information.
Language of the related scenario that was sent to user.
Last Send Date
Date and time that the phishing email was sent to the target user
Action
The Resend button allows you to resend the same phishing email.
Language of the related scenario that was sent to user.
Last Reported
Date and time when a user reported the phishing email using the phishing reporter add-in.
Times Reported
Number of times that a user reported the phishing email using the phishing reporter add-in.
Action
The Resend button allows you to resend the same phishing email.
The Details option shows the date and time a user opened the phishing email, the user agent, browser information, geolocation, IP information, and other information.
Language of the related scenario that was sent to user.
Email Delivery
Which SMTP is used to deliver the simulation emails to the users.
Date Sent
The last date and time that the email has been sent to target user.
Delivery Status
Status of the phishing email sent to the target user
In Queue = The phishing email is in the queue to be sent.
Successful = The phishing email was sent successfully.
Error = An error occurred in the delivery of the phishing email.
Action
The Resend button allows you to resend the same phishing email. The Details button allows you to see the email delivery details.
Symbols
count * 6
Symbols (!@# etc.) give a strong boost
Middle numbers/symbols
count * 2
Placing numbers/symbols in the middle adds bonus
Meets requirements
# of types used * 2
Bonuses for using at least 3–4 character types
Consecutive lowercase
-count * 2
Same logic as above with lowercase
Consecutive numbers
-count * 2
Same logic with digits
Sequential letters (abc)
-count * 3
Penalizes predictable patterns
Sequential numbers (123)
-count * 3
Sequential symbols (!@#)
-count * 3
80–100
1 (Very Strong)
Excellent password
A4.1 – The phishing link was clicked, but the invisible browser javascript challenge was not passed.
A4.2 – The browser failed to load required scripts that a real user’s browser would normally execute.
Download Report
An .xls format version of the phishing scenario report is available for download by clicking the Download Report button.
Resend Campaign
Resend the phishing scenario to the same target user group with the same settings by clicking the Resend Campaign button.
Opened Email
The number and percentage of target users who opened the phishing email
Clicked Email
The number and percentage of target users who clicked on the URL in the phishing email.
Submitted Data
The number and percentage of target users who submitted data on the landing page of the phishing scenario.
Opened Attachment
The number and percentage of target users who opened the attachment file.
Phishing Reporters
The number and percentage of target users who reported the simulated phishing email by using the platform's suspicious email reporter add-in.
No Response
The number and percentage of target users who did not take any action in response to the phishing e-mail.
Target Groups
The total number of target groups selected for the phishing campaign.
Hyper-Personalization
With the 'Preferred Language' option, users will receive scenarios in their preferred language. Those without a preferred language will receive scenarios in the company's default language.
Smart Grouping
If enabled, users who fail at the phishing campaign are automatically added to the selected target group.
Target Users
The total number of users selected to receive the phishing campaign email.
Campaign Lifetime
The date and time the phishing campaign will be terminated. No additional data will be processed in the phishing report after the expired date.
Languages
Language used in the phishing scenario.
Scenario Distribution
Number of Categories
The number of categories of selected scenarios.
Languages
The number of languages of selected scenarios.
Method
The list of methods of selected scenarios.
Difficulty
The difficulty levels of selected scenarios.
Delivery Start - End
The date and time the campaign was started and was/will be ended to complete sending the email to all selected users.
Duration
It shows how long it took to send the campaign email to all selected users.
Delivery Status
Out of the total number of chosen users, it displays how many of them successfully received the campaign email and how many did not. Please go to Sending Report menu to see more information.
Name
Name of the phishing scenario.
Method
Phishing scenarios can be created in one of several forms.
Data Submit = Designed to detect target users who submit data on the landing page.
Attachment = Designed to detect users who open the attached file by opening the file attachment in the e-mail.
Click-Only = Designed to detect users who click on the phishing link in the email.
Difficulty
Difficulty level of the phishing scenario (easy, medium, hard)
Language
Language used in the phishing scenario.
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Scenario Name
Name of the phishing scenario that is sent to user
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Password Complexity
Complexity level of the password submitted on the landing page of the phishing email. (very weak, weak, medium, strong, very strong)
TIP: The platform only captures the length and the first character of a password. Click here for more information.
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Scenario Name
Name of the phishing scenario that is sent to user
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Scenario Name
Name of the phishing scenario that is sent to user
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Scenario Name
Name of the phishing scenario that the user reported.
First Name
First name of the target user
Last Name
Last name of the target user
Email Address
Email address of the target user
Department
Department of the target user
Preferred Language
User's preferred language that is set from the Target Users menu.
Scenario Name
Name of the phishing scenario that is sent to user
Length
length * 4
Longer passwords score higher
Uppercase letters
(length - uppercaseCount) * 2
More uppercase letters (A–Z) = more points
Lowercase letters
(length - lowercaseCount) * 2
More lowercase letters (a–z) = more points
Numbers
count * 4
Only letters
-length
No digits or symbols = deduction
Only numbers
-length
No letters or symbols = deduction
Repeated characters
-variable penalty
Penalized based on how often characters repeat
Consecutive uppercase
-count * 2
0–19
5 (Very Weak)
Needs major improvement
20–39
4 (Weak)
Below average
40–59
3 (Moderate)
Meets some standards
60–79
2 (Strong)
Shows which scenario distribution setting is used for the campaign. See more info about the scenario distribution feature .
Scenario Language
Scenario Name
Scenario Language
Scenario Language
Scenario Language
Scenario Language
Numbers increase the score
Sequences like "AAA" are discouraged
Good overall security
Cancelled = This user was eliminated as a target for this phishing campaign.