Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.
5.11.9 (U) Step 9: Edit Mission Support Parameters (Mission Workflow 2)
(S) On the “Mission Support Parameters” page of the Mission workflow, edit the Mission
Support parameters appropriately (see Figure 26 – note this page is quite large with a lot
of fields and does not completely show in the figure).
Figure 26: Cherry Web Mission Support Parameters Mission Workflow Page
• Name – the name of the Mission
• Periodic Beacon Parameters (see CBUM for more detailed descriptions):
o Interval (sec) – the amount of time in seconds to wait before attempting to
send the next Periodic Beacon
o Traffic Requirement – the traffic requirement that must be achieved for
the Flytrap to send a Beacon. High/Medium/Low/None requires that at
least 100/50/10/0 packets per second be passing through the Flytrap for a
beacon to be sent
o Traffic Requirement Timeout (sec) – the maximum amount of time in
seconds to wait before sending a Beacon if the Beacon Traffic requirement
is never met.
o Power Cycle Wait (sec) – The amount of time in seconds to wait after a
Flytrap has been power-cycled before sending the next Beacon.
Remember that Mission data (e.g., Targets and Actions) is stored in
volatile RAM, and so is lost when the device is power-cycled; hence, if
the device is power-cycled, it will need to successfully Beacon before it
can continue performing its Mission tasking.
37