# 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
…
- 129
- 130
- 131
- 132
- 133
…
- 174
- 175

SECRET//20350112
internet connectivity test will failover to a different technique from attempt to
attempt, and will follow fast/slow retry logic at each failure to avoid being overly
“noisy”.
• Initial/Periodic Beacon Traffic Requirement Timeout – the maximum amount of
time a Flytrap will adhere to the Initial/Periodic Beacon Traffic Requirement before
reverting to a Traffic Requirement of NONE.
• Power-Cycle Wait – the Mission-configurable amount of time the Flytrap waits after
a power-cycle event before sending a Power-Cycle Beacon. Note that when a Flytrap
is power-cycled, its Mission data is lost due to the requirement to store target
information in volatile memory. Thus, it may be desired to have the Flytrap send a
Beacon to retrieve a mission more immediately after a power-cycle event than would
have been normally scheduled with the Periodic Beacon.
• Initial/Periodic Beacon Fast/Slow Retry Pause – if a Beacon attempt has failed,
wait the “fast” amount of time before attempting another Beacon -- unless “fast”
attempts to every PoP have failed. In this case, wait the “slow” amount of time before
attempting another Beacon.
(S) It should be noted that time values are stored in seconds as 32-bit signed integers, so
that maximum times are on the order of 2^31-1 seconds, which is approximately 68
years.
(S) Initial Beacon Interval, Traffic Requirement, Traffic Requirement Timeout, Fast
Retry Pause, Slow Retry Pause, and Number of Fast Retries are all hard coded into the
Flytrap’s firmware image at Image Formation time (see 15.3 and 15.5). The Periodic
Beacon Interval, Traffic Requirement, Traffic Requirement Timeout, Fast Retry Pause,
and Slow Retry Pause, as well as the Power-Cycle Wait are all sent as part of the
Mission, and stored in non-volatile memory. Also, when the Initial Beacon is sent
successfully, a flag is written to non-volatile memory.
(S) Figure 60 shows the Mission Manager Beacon Logic (note this figure uses the term
“Tumbleweed”, which is the now-deprecated term for PoP). The upper-left decision box
is the starting point from a Flytrap power-cycle event. This power-cycle could be related
to the first power-cycle after the device has been implanted, or a normal power-cycle
event.
131
SECRET//20350112

- 1
- 2
…
- 129
- 130
- 131
- 132
- 133
…
- 174
- 175