# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# SRI-SLO-FF-2012-177-CherryBlossom_UsersManual_CDRL-12_SLO-FF-2012-171

- 1
- 2
…
- 124
- 125
- 126
- 127
- 128
…
- 174
- 175

SECRET//20350112
14 (U) FAQ
(U) This section enumerates Frequently Asked Question about the system.
14.1 (U) Why can’t I edit a Mission after it has been assigned?
(S) Once a Mission has been assigned to a Flytrap, the Flytrap will receive that Mission
at the next Beacon. The Mission must be in a fixed state when this Beacon happens, or
the Flytrap could behave unexpectedly. The most convenient point to “fix” a Mission is
at the point of Mission Assignment. Note that if a mistake is discovered in a Mission after
it has been assigned, the operator can simply plan and assign a new Mission.
14.2 (U) Why can’t I remove/delete a Mission?
(S) Missions cannot be deleted because every Alert is associated with the Mission that
was assigned to the Flytrap when the Alert was generated. Removing the Mission would
remove the Alert’s reference to the Mission, losing additional and potentially useful
information for that Alert.
(U) To avoid displaying a Mission on many pages, use the Mission Archive feature
described in 9.14.
14.3 (U)What’s the difference between the Alerts page and the Target
Activity page?
(S) The Alerts page represents a rolling list of all Alerts that have been received. Each
new Alert will show up as a new row in the table. The Target Activity page shows one
row only for each unique Target Name, Flytrap, and Client MAC – it displays the
information related to only the most recent relevant Alert.
14.4 (S) What’s a derived MAC?
(U) See sections 7 and 7.4.
14.5 (S) Why Are Expected Beacon Times Off Slightly?
(S) This could be due to a few things. First, a Flytrap could be adhering to a Traffic
Requirement (see 5.2.3.3 and 15.2). Second, Flytrap devices have shown to have typical
clock errors on the order of a few tenths of a percent (highly accurate time for Flytrap
devices is not essential). Some devices may adjust the clock reference with an NTP
client, but this is typically only as needed, which could be less frequent than once per
day. Other devices do not have NTP clients. Thus, a Beacon Interval of 1 day (=86400
seconds) could easily have an error of +/- 100 seconds.
126
SECRET//20350112

- 1
- 2
…
- 124
- 125
- 126
- 127
- 128
…
- 174
- 175