# Vault 7: Projects

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

### Cherry Blossom

# TestProcedures

- 1
- 2
…
- 66
- 67
- 68
- 69
- 70
- 71

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Internal Test Procedures
Setup: Create a flytrap and have it beacon multiple times.
Run: From the <CB>/CherryTree/Release directory, execute ‘runPruneFlytrap.sh -f
{WLAN MAC}’.
Pass/Fail: The test passes if all but the latest status and security information for the
given flytrap has been removed.
5.48 Validate Authentication Logging
Description: Tests that invalid authentications are stored in the cherrytree.log file
with stack trace information stored in the Authentication.log file.
Setup: Setup a CherryWeb instance.
Run: Attempt to connect to CherryTree on port 80.
Pass/Fail: The test passes if a single line is noted in
/var/log/cherrytree/cherrytree.log referencing the authentication attempt and a
complete stack trace is available in /var/log/cherrytree/Authentication.log.
5.49 Power Cycle Test
Description: Tests that the zakura server can be rebooted and that upon power-on,
all CherryTree and CherryWeb applications are running correctly.
Setup: From a terminal window on either zakura or zakura.bak, gracefully reboot
the system.
Run: Once the server is back online, there are a number of ways to verify that the
processes are running correctly. These tests are assumed to be executed directly
on the server being tested.
Via the web browser, connect to https://127.0.0.1/CherryWeb/app and login with the
cbuser credentials. Verify that you can log in and view missions.
This test verifies that CherryWeb started successfully and that it can connect to the
database.
View the various log files to ensure no errors were reported during startup. The log
files can be found at:
/var/log/cherrytree/CherryTree.log
/var/log/cherrytree/CherryTree_error.log
/var/log/cherryweb/CherryWeb.log
UNCLASSIFIED
68

- 1
- 2
…
- 66
- 67
- 68
- 69
- 70
- 71