# Vault 7: Projects

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

### Cherry Blossom

# CherryBlossom -- Installation Guide

19 July, 2012

- 1
- 2
…
- 9
- 10
- 11
- 12
- 13
…
- 20
- 21

SECRET//20350112
6.3.1 (U) Configuring Catapult
(U) This configuration step is generally only necessary in the case of a new installation
(i.e., not an upgrade). The forwarding of Alert information to Catapult can be configured
through the Cherry Web interface. A test email can be sent to Catapult through Cherry
Web as well. See Section “Configuring Forwarding of Alerts to Sponsor Alert System
(Catapult)” (or similar) in the “Cherry Blossom User’s Manual”.
6.3.2 (S) Configuring the Windex Connection
(S) This configuration step is generally only necessary in the case of a new installation
(i.e., not an upgrade). The connection to the Windex system is configured using Cherry
Web, and requires the following:
• A certificate generated/provided by the Windex team
• A URL to the Windex server provided by the Windex team
(S) From an Icon (formerly Genesis) terminal, copy the certificate (use WinSCP or
similar) onto the (Master) CB-CC Server. On CherryWeb, navigate to the Admininster ->
Windex Connection page. Enter the Windex Connection URL. Import the certificate. Test
the connection using the Test button – success will be indicated by a “Success” message
displaying the Windex server time.
6.3.3 (U) Configuring the Default Mission
(U) This configuration step is generally only necessary in the case of a new installation
(i.e., not an upgrade). After a successful installation, it may be desirable to create a new
Mission and set it as the default Mission. See section “Setting the Default Mission” in the
“Cherry Blossom User’s Manual”. Consult appropriate sponsor personnel (see section 3
for COTR information) before creating a new default Mission.
6.3.4 (U) Point of Presence (PoP/Snowball) Configuration
(S) This configuration step is generally only necessary in the case of a new installation
(i.e., not an upgrade) or if a new PoP is to be used by the system. CB communications
from the outside world (i.e., from Flytraps) are forwarded to the CB Servers through
Points of Presence (PoPs/Snowballs). PoPs are configured and maintained by the
sponsor’s network group (see section 3 for network group contact). A CB Server must be
configured properly for the PoPs that it will be using. On a CB Server, PoP
configurations are stored in:
/etc/cb-PoP-X.conf
where X is an integer number.
(U) To configure a PoP, first disable the server:
~/cbuser/bin/disable-server.sh
Next, edit the self-documenting “/etc/cb-PoP-X.conf” file appropriately. Finally,
enable the server:
~/cbuser/bin/enable-server.sh
SECRET//20350112
11

- 1
- 2
…
- 9
- 10
- 11
- 12
- 13
…
- 20
- 21