# 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
…
- 37
- 38
- 39
- 40
- 41
…
- 174
- 175

SECRET//20350112
8.1.4 (U) User Management
(U) To perform User Management, login to CW (see 9.2) as a User with “cwadmin”
privileges. On the CW left menu pane, click the Administer -> Users link.
(U) To create a User, under the “Create User” heading, enter a unique name and click the
“Create” button. Note that names that differ only in case are not considered unique (e.g.,
“Red”, “red”, and “RED” are not considered unique, whereas “Red” and “red1” are
considered unique). Enter/Re-enter a secure (many digits, not commonly found in a
dictionary, mixture of numbers, letters, and punctuation marks) password. Select the User
Role of either “cwuser” or “cwadmin” (see 8.1.2), and click submit. Note that when a
new User with a “cwuser” Role is created, they are given “Read-only” permission to the
DEFAULT Operation, and “No Access” to all other Operations (see 8.1.6 and 8.1.8). A
User with “cwadmin” Role has “Read-Write” access to all Operations.
(U) To edit a User, under the “Edit User” heading, select the User of interest. Enter/Re-
enter a secure (many digits, not commonly found in a dictionary, mixture of numbers,
letters, and punctuation marks) password, select the User role (see 8.1.2), and click
submit.
(U) To delete a User, under the “Delete User” heading, select the User of interest, and
click the “Delete” button. Note that a deleted User cannot be recovered, but can be re-
created.
8.1.5 (U) Operations
(U) A Operation is an entity around which CB system data is organized and to which this
data is eventually reported via One-way Transfer. Operations are explicitly associated
with Missions and Target Decks, and implicitly associated with any data resulting from
these Missions and Target Decks (e.g., Alerts, Harvest Data, Copy Data, etc). One-way
Transfer scripts run on a per-Operation basis, and package all Operation-associated data
(Missions, Target Decks, and resulting data). Operations are loosely akin to the UNIX
“group” concept.
8.1.5.1 (U) Operation-Owned Entities
(U) As stated before, a Operation is an entity around which CB system data is organized.
This is accomplished by specifying Operation ownership when planning Missions and
Target Decks. The Operation then “inherits” any data (e.g., Alerts, Copy Data, Harvest
Data, etc) resulting from an owned Mission and/or Target Deck. Figure 3 illustrates
Operation-owned and inherited data. The left box shows Mission “DELTA” with Target
Decks all with ownership by Operation “RED”. The right box shows resulting data that
Operation “RED” inherits from the Mission and Target Decks.
39
SECRET//20350112

- 1
- 2
…
- 37
- 38
- 39
- 40
- 41
…
- 174
- 175