Unify - Phishing Campaign Action FAQs
Q: What does the Phishing Campaign Action do?
A: The Phishing Campaign Action leverages Living Security Phishing to automatically create a risk-based scenario and send a phishing campaign immediately upon Action Plan creation. If you do not have Living Security Phishing, the campaign action will allow for a download of the identity group used to create the action; there will not be a scenario created and the campaign will need to be launched manually from your phishing tool, but you'll gain Action Plan reporting to measure impact of the Phishing Action on your group of identities.
A: The Phishing Campaign Action leverages Living Security Phishing to automatically create a risk-based scenario and send a phishing campaign immediately upon Action Plan creation. If you do not have Living Security Phishing, the campaign action will allow for a download of the identity group used to create the action; there will not be a scenario created and the campaign will need to be launched manually from your phishing tool, but you'll gain Action Plan reporting to measure impact of the Phishing Action on your group of identities.
Q: What does the action not do?
A: The Phishing Campaign Action does not retroactively apply to past campaigns or automate recurring phishing simulations.
A: The Phishing Campaign Action does not retroactively apply to past campaigns or automate recurring phishing simulations.
Q: Can I test or preview this action before using it live?
A: Yes, you can preview the scenario before it is sent. However, we recommend testing from the Living Security Phishing tool before sending a Phishing Action to ensure all whitelisting is appropriately configured.
A: Yes, you can preview the scenario before it is sent. However, we recommend testing from the Living Security Phishing tool before sending a Phishing Action to ensure all whitelisting is appropriately configured.
Q: Where can I see if the action was triggered?
A: While Risk Reporting will be available in Unify, we recommend checking the Living Security Phishing tool directly to see the sending report or other forensic data on the campaign such as timestamps, IPs captured, and bot activity.
A: While Risk Reporting will be available in Unify, we recommend checking the Living Security Phishing tool directly to see the sending report or other forensic data on the campaign such as timestamps, IPs captured, and bot activity.
Q: What are the default campaign settings for the Phishing Campaign Action?
A: The default settings for a Living Security Phishing campaign are as follows;
A: The default settings for a Living Security Phishing campaign are as follows;
- Campaign Start: Now, immediately after the Action Plan is created.
- Campaign Duration: 7 days
Q: When should i expect to see results for the phishing campaign in Unify reporting?
A: At the end of the campaign duration, which is set for 7 days post action plan creation.
A: At the end of the campaign duration, which is set for 7 days post action plan creation.
Q: How is AI utilized within the Phishing Campaign Action?
A: Our AI-powered Phishing Action Plans create phishing campaigns using an OpenAI enterprise integration inside our Unify platform. The platform calls the OpenAI API with a structured system prompt (for example, “Generate a phishing simulation email for employees in the Marketing department that work in an office in Austin, TX”). We may pass generic identity filters (department names, office locations, etc.) as inputs, but these are not personally identifiable—at most, a department name like “[Company]’s Southwest Sales” could reveal an internal naming convention.
Key Points on Data & Privacy
- No Training on Your Data: None of your data is used to train OpenAI’s models. We use a zero-shot approach where each request is a one-off API call, and the model does not learn from it.
- Enterprise-Grade Security: We use OpenAI’s enterprise API, which is SOC 2 compliant and does not store or reuse your inputs for future training.
- Controlled Personalization: Content is personalized only through merge tags (e.g., {FIRSTNAME}, {COMPANYNAME}) and targeting filters to make simulations relevant, while still protecting sensitive information.
