# Vault 7: Projects

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

### Cherry Blossom

# CherryBomb -- CherryBlossom Internal Test Procedures (CDRL-14c)

21 June, 2012

- 1
- 2
…
- 47
- 48
- 49
- 50
- 51
…
- 70
- 71

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Internal Test Procedures
Pass/Fail: The test passes if the expected alert can be generated for the email
target added to the deck after it was added to the deck but not before it was added,
and the new target appears when the target deck is edited.
4.4.9 Transparency of Auto-generated Missions
Description: Tests that when a mission is auto-generated to reflect target deck
edits, any internal prefixes or suffixes identifying the auto-generated mission are not
visible to the end user.
Setup: log into Cherry Web
Run: After the previous test has been performed, access the various screens that
list mission names (ViewFlytraps, mission workflow, and so on) and verify that no
rev number or other prefixes or suffixes indicated an auto generated mission are
visible.
Pass/Fail: This test passes if all mission names appear normal with no extraneous
suffixes or prefixes.
5 Cherry Tree Tests
This section describes CherryBlossom tests related to the Cherry Tree product (i.e., the
backend server running CherryTree (CT), CherryWeb (CW), and other
services/functions running on the backend server).
Hardware/Software Required:
• Zakura Server running latest release of Cherry Blossom backend software
• Control Computer with internet connection, IE 6.0 or greater (this computer will
connect to CherryWeb on zakura)
• Flytrap
• Client Computer
• Ethernet cable(s)
UNCLASSIFIED
49

- 1
- 2
…
- 47
- 48
- 49
- 50
- 51
…
- 70
- 71