{{#invoke:other uses|otheruses}} Template:Short description

File:RedBlack.png
Red/black box

The red/black concept, sometimes called the red–black architecture<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> or red/black engineering,<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref><ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> refers to the careful segregation in cryptographic systems of signals that contain sensitive or classified plaintext information (red signals) from those that carry encrypted information, or ciphertext (black signals). Therefore, the red side is usually considered the internal side, and the black side the more public side, with often some sort of guard, firewall or data-diode between the two.

In NSA jargon, encryption devices are often called blackers, because they convert red signals to black. TEMPEST standards spelled out in Tempest/2-95 specify shielding or a minimum physical distance between wires or equipment carrying or processing red and black signals.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

Different organizations have differing requirements for the separation of red and black fiber-optic cables.

Red/black terminology is also applied to cryptographic keys. Black keys have themselves been encrypted with a "key encryption key" (KEK) and are therefore benign. Red keys are not encrypted and must be treated as highly sensitive material.<ref>Template:Cite book</ref>

Red/Gray/BlackEdit

File:NSA Red-Gray-Black diagram.png
NSA Red-Gray-Black diagram

The NSA's Commercial Solutions for Classified (CSfC) program, which uses two layers of independent, commercial off-the-shelf cryptographic products to protect classified information, includes a red/gray/black concept. In this extension of the red/black concept, the separated gray compartment handles data that has been encrypted only once, which happens at the red/gray boundary. The gray/black interface adds or removes a second layer of encryption.<ref>NSA Mobile Access Capability Package, Version 2.1, 26 June 2018, accessed 21 February 2021</ref>

See alsoEdit

ReferencesEdit

Template:Reflist


Template:Asbox