Feature 1
Prepare a realistic authorised exercise
Choose a suitable scenario, audience and delivery plan before launching the simulation.
- Choose a template
- Select recipients
- Review and launch
Capability
Phishing Campaigns
Run authorised phishing simulations and use recipient outcomes to guide safer behaviour and follow-up learning.
The outcome
Identify where staff need more support and turn realistic practice into focused learning rather than blame.
How it helps
How Phishing Campaigns works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Turn outcomes into learning
Review recipient behaviour and use the result to focus future guidance and training.
- Compare outcomes
- Review reported messages
- Target follow-up learning
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Template and vendor library
- Staff targeting
- Campaign builder
- Immediate and scheduled delivery
- Phishing Autopilot
- Recipient outcomes and reporting
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Awareness Training
Assign practical security learning to staff and maintain clear completion records over time.
Explore capabilityCompromise Monitoring
Check whether staff email accounts appear in known breach data and keep the exposure visible for follow-up.
Explore capabilityAvailable in:Human Risk Management
Questions and answers
Questions about Phishing Campaigns
Practical answers to common questions about managing this responsibility well.
Why does phishing campaigns matter?
Identify where staff need more support and turn realistic practice into focused learning rather than blame.
What should phishing campaigns include?
It should cover template and vendor library, staff targeting, campaign builder, immediate and scheduled delivery and phishing autopilot, with enough context to support action and explain decisions.
Who should be responsible for phishing campaigns?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep phishing campaigns current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for phishing campaigns?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Phishing Campaigns in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.