Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.
5.11.4 (U) Step 4: Define Mission Files (for Application Execution)
(S) To have an application execute as part of the Mission, first add the application to the
system as a “Mission File”. Click the “Plan Application Execution Mission File”
menu link (see Figure 20). Upload the application using the “Browse” button. Select a
“File Compatibility” for the file.
Figure 20: Cherry Web Plan Flytrap Applications Mission File Page
(S) NOTE: applications must be built using the proper toolchain for the Flytrap of
interest, so the “File Compatibility” selector will limit Mission Assignment to this device
type. Furthermore, a Mission File can in general be any type of file (for example a data
file or a shell script), so “Universal” can be selected to allow a Mission File to be
pushed to any device type.
(S) Next, select the “Upload Action” as “Retain” or “Replace” – “Retain” will give an
error if the user tries to upload a Mission File that has the same name and Device
Compatibility as a Mission File already in the system, whereas “Replace” will overwrite
the Mission File already in the system.
(S) Click the “Import” button to import the Mission File into the system. The new file
should show in the table. A user can click the “Download” link in the table to pull a copy
of the Mission File from the system.
31
Plan
Flytrap Applications
Mission File