snowchive-meta/data/spiegel_-_media-35536/spiegel_-_media-35536.md
2026-11-19 04:39:11 +02:00

93 lines
No EOL
3.1 KiB
Markdown

SCARLETFEVER - WikiInfo
The accredited security level of this system is: TOP SECRET//SI-GAMMA/TALENT
KEYHOLE//ORCON/PROPIN/RELIDO/REL TO USA, FVEY *
TOP SECRET//SI//REL TO USA, FVEY
(U) SCARLETFEVER
From WikiInfo
This Project page has moved to the: CES 2P
PIQ Wiki
This page is registered as
go scarletfever [REDACTED]
(URN info: alias ([REDACTED]), yeeha [REDACTED])
([REDACTED])
JAVA
This application makes use of the
Java programming language.
C++
This application makes use of the
C++ programming language.
Contents
* 1 (U) Overview
* 2 (U) Development Process and Standards
* 2.1 (U) Related Wiki Pages
* 3 (U) History
* 4 (U) Design
* 5 (U) Contact Info
(U) Overview
(TS//SI//REL) SCARLETFEVER is the second LONGHAUL capability. It is a message driven cryptologic exploitation service for DNSC traffic. Currently, the list of SCARLETFEVER clients includes TURMOIL, WEALTHYCLUSTER and the TEe. Each client can connect to SCARLETFEVER using ISLANDTRANSPORT. Once connected, clients send and receive XML messages encrypted using ISLANDHIDEAWAY.
An in depth look at SCARLETFEVER can be found here. ([REDACTED]
[REDACTED])
(U) Development Process and Standards
(U//FOUO) SCARLETFEVER follows the LONGHAUL Development Process
1 of 3
SCARLETFEVER - WikiInfo
KEYHOLE//ORCON/PROPIN/RELIDO/REL TO USA, FVEY *
(U) Related Wiki Pages
* (U//FOUO) LONGHAUL - the Parent Project
* (U//FOUO) POISONNUT - a Sibling LONGHAUL Project
(U) History
* (TS//SI//REL) The SCARLETFEVER development started in July 2009.
* (TS//SI//REL) The basic high level functional design was completed in early September 2009.
(U) Design
(TS//SI//REL) The SCARLETFEVER team then met several times over the July-September time frame to refine the design of the system. The output of those meetings was a series of BPMN diagrams and technology areas for further investigation. The BPMN diagrams exposed:
* The flow of information through the system (messages).
* The high level components and critical elements.
(TS//SI//REL) The messages, component and critical elements, and technology areas were used to generate an initial list of Engineering Change Requests (ECRs) for further refinement and development.
(TS//SI//REL) SCARLETFEVER also has a geographically distributed architecture concept which is currently being fleshed out. Why is this being pursued?
* Resume session pairing generates the bulk of the load. If this processing can be shifted to the edge, then:
* Less total aggregated network traffic due to collaboration with the core
* Less aggregate memory requirements at any one location
* Redundant capabilities for better total mission survivability
(U) Contact Info
* (U//FOUO) SCARLETFEVER Development Team email alias: TBD
* (U//FOUO) Jabber Chat Room: TBD
* (U//FOUO) LONGHAUL JSignout group [REDACTED]
[REDACTED]
Retrieved from "[REDACTED]"
Categories: URN | Applications using Java | Applications using C++ | TLS | SCARLETFEVER | LONGHAUL
2 of 3
SCARLETFEVER - WikiInfo
Derived From: SI Classification Guide, 02-01, Dated: 20060711
and NSA/CSSM 1-52, Dated: 20070108
Declassify On: 20320108
TOP SECRET//SI//REL TO USA, FVEY
3 of 3