export_campaign_data
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
export_campaign_data [2018/12/14 16:20] – add note about CSV separator lucy | export_campaign_data [2022/03/05 13:53] – lucysecurity | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== Introduction: | ===== Introduction: | ||
- | Starting with LUCY 4.0 we added a navigation item called export within the campaign overview page. The menu that opens allows you to export any campaign related data: | + | In the LUCY there' |
- | {{ exports_all.png?600 }} | + | {{ exp_cmp_data_4.png?600 }} |
You can either export [[monitor_a_campaign_statistics|ALL data that gets monitored]] in LUCY or only specific data: | You can either export [[monitor_a_campaign_statistics|ALL data that gets monitored]] in LUCY or only specific data: | ||
- | {{ export_types.png?600 }} | + | {{ exp_cmp_data_2.png?600 }} |
===== Export into CSV ===== | ===== Export into CSV ===== | ||
- | :!: Reports in the CSV format are generated using the delimiter | + | :!: Reports in the CSV format are generated using the separator |
- | The default | + | The default |
* **Export recipients to CSV (1)**: allows to export recipients to a CSV file (can be opened in excel) based on different criteria | * **Export recipients to CSV (1)**: allows to export recipients to a CSV file (can be opened in excel) based on different criteria | ||
- | {{ export_csv.png?600 }} | + | {{ exp_cmp_data_3.png?600 }} |
* **Export benchmarks (4)**: This will export the main statistics (scenario name, number of messages_sent, | * **Export benchmarks (4)**: This will export the main statistics (scenario name, number of messages_sent, | ||
* **Export collected data to CSV (5)**: export the data collected (any submitted data or file uploads from malware simulations) in the campaign to a CSV | * **Export collected data to CSV (5)**: export the data collected (any submitted data or file uploads from malware simulations) in the campaign to a CSV | ||
+ | |||
+ | ===== Export Collumns ===== | ||
+ | |||
+ | ^ Collumn name ^ Description ^ Value ^ | ||
+ | | name | Name of the recipient | Text | | ||
+ | | email | Email of the recipient | Text | | ||
+ | | phone | Phone number of the recipient | Numeral | | ||
+ | | gender | Gender of the recipient | Male / Female | | ||
+ | | link | Unique link of the recipient | Text | | ||
+ | | lure_submitted_at | Time of lure email submission | Timestamp | | ||
+ | | mail_submitted_at| Time of email submission | Timestamp | | ||
+ | | clicked | Recipient clicked the link in the email | Yes / No | | ||
+ | | clicked_at | Time recipient clicked the link in the email | Timestamp | | ||
+ | | succeeded | Success action triggered for the recipient | Yes / No | | ||
+ | | succeeded_at | Time when success action was triggered | Timestamp | | ||
+ | | trained | Recipient has completed the training | Yes / No | | ||
+ | | trained_at | Time when recipient has completed the training | Timestamp | | ||
+ | | reported | Recipient has reported the message via LUCY Report Plugin | Yes / No | | ||
+ | | reported_at | Time when recipient has reported the message | Timestamp | | ||
+ | | domain | Domain used in the campaign' | ||
+ | | scenario | Name of the scenario on the campaign | Text | | ||
+ | | staff_type | Info about recipient' | ||
+ | | location | Info about recipient' | ||
+ | | division | Info about recipient' | ||
+ | | comment | Additional optional comment about the recipient | Text | | ||
+ | | os | Operational System of the workstation that submitted first click | Text | | ||
+ | | ip | IP of the workstation that submitted first click | Numeral | | ||
+ | | proxy_ip | IP of the proxy | Numeral | | ||
+ | | browser | Browser of the workstation that submitted first click | Text | | ||
+ | | plugins | Plugins detected on the workstation that submitted first click | Text | | ||
+ | | country | Country based on IP | County Code | | ||
+ | | success_rate | How many times a recipient was successfully attacked, depending on the Success Action | Numeral | | ||
+ | | click_rate | How many times a recipient clicked the attack link | Numeral | | ||
+ | | scenario_time | Amount of time the victim has spent on the phishing link page | Numeral | | ||
+ | | awareness_time | Amount of time the victim has spent on the awareness link page | Numeral | | ||
+ | | email_subject | Subject of the sent email | Text | | ||
+ | | first_click_after_delivery | Time value in seconds between mail_submitted_at and succeeded_at | Numeral | | ||
+ | | first_report_after_delivery | Time value in seconds between mail_submitted_at and reported_at | Numeral | | ||
+ | | reminder_click_submitted_at | Time when recipient clicked the reminder link | Timestamp | | ||
+ | | reminder_training_start_submitted_at | Time when the recipient started the training provided by reminder | Timestamp | | ||
+ | | reminder_training_finish_submitted_at | Time when the recipient finished the training provided by reminder | Timestamp | | ||
+ | | downloaded_files | File-based attack downloaded files by the recipient | Text | | ||
+ | | collected_data | The data that has been submitted by the recipient on the landing page | Text | | ||
+ | | out_of_office_at | Time of Out of Office autorespond | Timestamp | | ||
+ | | bounced_at | Time of the Bounced response | Timestamp | | ||
+ | | responded_at | Time of the incoming response to the email | Timestamp | | ||
+ | | certificate_received | Recipient has received a certificate | Yes / No | | ||
+ | | training_with_quiz_passed | Recipient has passed a training with Quiz mode enabled | Yes / No | | ||
+ | | training_with_quiz_passed_at| Time when recipient has passed a training with Quiz mode enabled | Timestamp | | ||
+ | | training_noquiz_finished | Recipient has finished a training without Quiz | Yes / No | | ||
+ | | training_noquiz_finished_at | Time when recipient has finished a training without Quiz| Timestamp | | ||
+ | | security-level | Level of awareness security | Numeral | | ||
Line 32: | Line 84: | ||
{{ export_time_range.png? | {{ export_time_range.png? | ||
- | |||
- | ===== Export SCORM ===== | ||
- | |||
- | *** Export SCORM (6)**: export the e-learning template used in the campaign | ||
Line 50: | Line 98: | ||
{{ export_pwd.png? | {{ export_pwd.png? | ||
+ | ===== Automated Export ===== | ||
+ | |||
+ | The export process can be also automated by using the feature " | ||
+ | |||
+ | {{ au_export_01.png? | ||
+ | |||
+ | The automated export can be configured by the following options:\\ | ||
+ | * **Export Target**: multiple data type exports can be selected, each representing a separate data export\\ | ||
+ | * **Export Frequency**: | ||
+ | * **Export Time**: at what time the export should be generated\\ | ||
+ | * **Export Days**: days of week or month: 1-7 for weekly, 1-31 for monthly. Days of year: 1-12 (month numbers); 1-31 (days of month) for yearly. Example for weekly: 1,3,5,7. Example for monthly: 1, 15, 25. Example for yearly: 1,3,5,7; 1,15.\\ | ||
+ | * **Export Type**: file format XML or CSV. | ||
+ | |||
+ | The following example on the screenshot shows the configuration of the full data weekly report done each Friday at 15:00 in CSV format. | ||
+ | |||
+ | {{ au_export_02.png? | ||
+ | |||
+ | The generated automated exports can be found in this menu section:\\ | ||
+ | Support > Exports |
export_campaign_data.txt · Last modified: 2022/03/05 17:49 by lucysecurity