doi stringclasses 3
values | chunk-id stringlengths 1 4 | chunk stringlengths 256 1.3k | id stringclasses 3
values | title stringclasses 3
values | source stringclasses 3
values | authors sequence | categories sequence | references sequence |
|---|---|---|---|---|---|---|---|---|
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 0 | UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY// REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT 1
National Security Agency
Cybersecurity Directorate
2
3
Cross Domain Solution (CDS) Design... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 1 | SWE, QAT
Page 2 of 397 Disclaimer 26
References herein to a ny commercial products, process, or service by trade name, trademark, 27
manufacturer, or otherwise, do not constitute an official endorsement, either expressed or implied, by the 28
National Security Agency. 29
References herein to any commercial pro... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 2 | rds or guidelines do not 40
imply a claim that products are in conformance or nonconf ormance with such standard or guideline. 41
Classification markings used in the requirements sections are for example purposes only. This document 42
is UNCLASSIFIED //FOR OFFICIAL USE ONLY //REL TO USA, ARE, BHR, FVEY, ISR, JPN, ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 3 | L USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 3 of 397 Table of Contents 61
LIST OF FIGURES ................................ ................................ ............ | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 4 | ........................... ................................ ................................ .... 23 68
1.4 CLARIFICATION ON TERMINOLOGY USAGE ................................ ................................ ................................ ............. 23 69
1.5 REQUIREMENTS TERMINOLOGY .......................... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 5 | ....... ................................ ................................ ............ 27 76
2.3 CDS OPERATIONS , MAINTENANCE , & LIFECYCLE ................................ ................................ ................................ .... 28 77
3 CDS DEFINITIO NS ................................ ................ | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 6 | ........... ................................ ................................ ........... 40 84
6.2 OPERATIONAL ENVIRONMENT RISK ASSUMPTIONS ................................ ................................ ................................ .. 41 85
6.3 CYBER ENVIRONMENT RISK ASSUMPTIONS .............................. | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 7 | (RAIN) EXPLAINED .................... 53 92
7.4 PLATFORM SECURITY ................................ ................................ ................................ ................................ ....... 56 93
7.5 FILTERING ................................ ................................ ....................... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 8 | , BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 4 of 397 9 GENERAL REQUIREMENTS ................................ ................................ ................................ ........................ 129 100
9.1 SAFETY REQUIREMENTS (SR) ................................ .................................. | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 9 | ......... ................................ ........ 131 107
9.8 NETWORKING RELATED REQUIREMENTS (NRR) ................................ ................................ ................................ .... 132 108
10 GENERAL SECURITY REQUIREMENTS ................................ ................................ ..... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 10 | WARE CONFIGURATION REQUIREMENTS (SIHCR) ................................ .................... 188 116
10.8 PROCESS ISOLATION REQUIREMENTS (PIR) ................................ ................................ ................................ ........ 195 117
10.9 ROLE-BASED ACCESS CONTROL (RBAC) REQUIREMENTS ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 11 | ......... .... 234 124
10.16 DOMAIN ROUTE R REQUIREMENTS (DRR) ................................ ................................ ................................ ....... 235 125
10.17 FILTER REPORT VALIDATOR REQUIREMENTS (FRVR) ................................ ................................ ...................... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 12 | REQUIREMENTS (GDFR) ................................ ................................ ..................... 245 133
11.2 GENERAL XML AND FIXED FORMAT PROCESSING REQUIREMENTS (GXFFPR) ................................ ............................ 258 134
11.3 MILITARY MESSAGING FIXED FORMAT DATA FILTERING AND PR... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 13 | ......................... .................. 283 142UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 5 of 397 15.2 DCCDS -FF/CCOTS ARCHITECTURE... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 14 | 149
16.2 LAB-BASED SECURITY ASSESSMENT (LBSA) REQUIREMENTS (LBSAR) ................................ ................................ ..... 292 150
16.3 SITE-BASED SECURITY ASSESSMENT (SBSA) REQUIREMENTS (SBSAR) ................................ ................................ .... 293 151
17 MULTI -LEVEL DATA... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 15 | OMMISSIONING AND REUSE REQUIREMENTS (CDRR) ................................ ................................ . 327 159
25 HARDWARE -BASED CDS AND HARDWARE -BASED COMPONENTS REQUIREMENTS (HWCR) ..................... 327 160
25.1 HARDW ARE-BASED CDS/C OMPONENTS GENERAL HARDWARE REQUIREMENTS (HWC -GHR) ............... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 16 | STANDARDS ................................ .............................. 352 168
31 APPENDIX C – RTB REQUIREMENTS MAPPING FOR ACCESS CDS ................................ ............................... 355 169
32 APPENDIX D – RTB REQUIREMENTS MAPPING FOR HCFD, PFD, AND HARDWARE CDS ................................ | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 17 | of Figures 178
FIGURE 1 – PITCHER /DIODE/CATCHER (PDC) ARCHITECTURE ................................ ................................ .............................. 34 179
FIGURE 2 – UDP -1: THE SINGLE PROCESS GUARD ................................ ................................ .................................. | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 18 | ................. 80 186
FIGURE 9 – ADP -1 THE “DOUBLE STAR” GUARD ................................ ................................ ................................ ............. 80 187
FIGURE 10 – ADP -2: MULTIPLE DOMAIN LINEAR ASSURED PIPELINE ................................ ................................ .... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 19 | 8: REMOTE VDI ACCESS CDS ................................ ................................ ................................ ............. 92 195
FIGURE 18 – ADP -9: TACTICAL ACCESS CDS WITH EMBEDDED TRANSFER CDS ................................ ................................ ....... 93 196
FIGURE 19 – ADP -10: ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 20 | ..................... ............................ 109 203
FIGURE 26 – OWTDP -1: TRADITIONAL DIODE PATTERN ................................ ................................ ................................ .. 112 204
FIGURE 27 – OWTDP -2: TRADITIONAL DIODE PATTERN FOR BIDIRECTIONAL DATA FLOWS ......................... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 21 | ........... ...... 120 212
FIGURE 34 – OWTDP -4C: MULTI-DOMAIN CDS + CDS INTEGRATED WITH DIODE W /HIGH THREAT CONNECTIONS PATTERN (BI-DIR) – 213
OPTION 4 ................................ ................................ ................................ ................................ .................... 121 214 ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 22 | PATTERN ................................ .......................... 284 221
FIGURE 42 – COMPOSED COTS UNIDIRECTION AL CDS DESIGN PATTERN ................................ ................................ ............. 285 222
FIGURE 43 – COMPOSED COTS BI-DIRECTIONAL CDS DESIGN PATTERN .......................... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 23 | .............................. . 318 228
FIGURE 49 – DFSR -ADP -1 SINGLE PHYSICALLY ISOLATED DFS ENVIRONMENT ................................ ................................ ...... 321 229
FIGURE 50 – DFSR -ADP -3 PER DOMAIN DFS ENVIRONMENT ................................ ................................ ......... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 24 | .................. 352 237
TABLE 6 - APPROVED ALGORITHMS FOR SRTP ................................ ................................ ................................ ............... 353 238
TABLE 7 - APPROVED ALGORITHMS FOR DATA-AT-REST ................................ ................................ ............... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 25 | 3.0 Released – Changelog details removed for brevity in V 4.0. See version
v3.0 and below for detailed changes.
18DEC2021 4.0 Released – Changelog details removed for brevity in V 5.0. See version
v4.0 and below for detailed changes.
11JUL2022 4.1 Released – Changelog details removed for brevity in V 5.0. See... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 26 | ated SIR -14 to include logging
Added SIR -16 to detect process death
Added clarification to send of OWTDP -2 about Impl B and Impl C
being physically separate servers
Added JALSR -42
Added SASR -16 and 16.1
Updated Clarification for RMANR -10
Added CMSR -11
Added POLF to JALSR -1
Fixed minor typo in SIR... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 27 | 1 to clarify independent.
OWT -17 now a SHALL
Added FSR and DFSR sections
Updated to required NIST -800 Rev 5 and related updated to CNSS -
1253 and CDS Overlay
Added RHRR -4 requirements to support overriding filteringUNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, S... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 28 | S drawing
Added ACDSR -8
Added OWT -31
Added Clarification to MPCR -4
Changed DRR -8 from “the DR” to “a DR”
Added OSSR -27.2.1
Rewrote part of MPCR -4 requirements to impro ve clarity and
expanded the clarification
MPCR -7 make interface/protocols both plural
Added clarification to MPCR -10
Added clari... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 29 | MLSWNR -2.1 add IGMP and MLD
Added rationale to MPCR -32
MPCR -6 Changed ‘within a system ’ to ‘within a specific CDS ’
Added T&W for MPCR, PAR, and DRR
Added Clarification to DPMR -12.15
MPCR -28 changed to should
Added rational to OSSR -27.1
Added Section 8.3.4 on hardware content filtering devices (HCFD) ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 30 | Access CDS
Added VIRT -8.3
HWR has largely been written to address changes for HCFDs, the new
tactical CDS patterns from RTB 4.1, and the changes required for the
CDS Anti -tamper requirements. It is stron gly recommend ed that entire
section be reviewed carefully.
Added HWR -16, -17, and -18
HWR -5.1 deleted... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 31 | PN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 13 of 397 12DEC2022 5.0 rev39
24DEC2022 5.0 rev40 -42 Added GCHQ CDS papers to references
Added SIR -17, 17.1, 17.2
28DEC2022 5.0 rev43 Added SIR-11.5
Moved ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 32 | of sections 6.4 headers to phrase as threats
Split OWT -28 and added OWT -28.1
Updated Figure 22/HCFD to reflect DCO OOB connection for the
HCFD
Added HWR -19/20 for sending logs from a HCFDUNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 33 | out deprecating low side filtering in PDC in
future release.
Added Clarification to GAR -1.1
16JAN2023 V5.0 rev 52 Added Clarification to OWT -12.3
Added Clarification NRR -8.1
Minor wording tweaks to GAR -1.1
GAR -7.2 reword to improve clarity
Added Clarification to GAR -9.2
Updated section 9 intro on cla... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 34 | Update rationale.
DPMR -8 2nd sentence moved to Clarification
EDSR -1 2nd sentence moved to Clarification and fixed wording issue.
Multiple updates to EDSR -15 and its sub -requirements and
clarifications to improve clarity
Added T&W to FRVR section
Update d Figure 35 – OWTDP -5 Architecture to show DCO OO... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 35 | OR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 16 of 397 clarification about send original failed fail to DCO OOB
Moved 2nd sentence in GDFR -27 to GDFR -27.1
Remove clarification from HWR -10.1 and moved to Section 1.7
8FEB202... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 36 |
21FEB2023 V5.0 rev65 Added Clarification to NRR -7
Added “PFD” to OWT -29
Added “per destination” to OWR -31
28FEB2023 V5.0 rev 66 -69 Added TPR-13.7
Added TPR-13.8
29FEB2023 V5.0 rev 70 Major updates to CMSR to handle both CMS servers and CMSUNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY,... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 37 | apply to clock
and voltage glitches
SFPGA -6, SFPGA -2 Deleted.
WNVFPGA -4 Deleted.
Updated ADPs 10 -13 to remove support for the management CPU
27APR2023 V5.0 rev79 MLS -3 visit subject/object issue.
Updated MLSWNR -5 and MLDBR -5.1 to support the new S OSA v2
standard for Layer 2 labeling of packets. ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 38 | n for CNSA v2.0 support
CMSR -0.0.1 changed to SHALL
Added Appendix I – Alignment of RTB requirements to NIST
Controls
244
1 245
1.1 246
1.2 247
1.2.1 248
1.2.2 249
1 250
251UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 39 | nt of Defense ( DoD ) Information Security Risk Management 262
Committee (ISRMC) in December 2017 . In the DoD Chief Information Officer (CIO) 263
memorandum “Implementing Cross Domain Bug Bounty Remediation ” dated 5 April 2018 all 264
CDS used by the DoD shall be compliant with RTB by FY2020. Under NSD -42 a... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 40 | ent without 277
further explanation . 278
• Security Assessment of Cross Domain Solutions (CDS): Process and Requirements 279
(NCDSMO Doc ID: NCDSMO -R-0000 3-004_00) describes key concepts and 280
terminology related to the assessment ( e.g., security testing) of CDS . 281
• Cyber One-Way Taps Technical Requir... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 41 | nd general guidance on the scope of testing 287
required for different changes to a CDS . 288
• Cross Domain Solution (CDS) Development and Testing Environment Security 289
Requirements (NCDSMO Doc ID: NCDSMO -R-00011 -001_ 01) describe s the security 290
requirements for CDS development and testing environment ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 42 | 303
• Using Linux Secure Computing (SECCOMP) Mode in Cross Domain Solutions 304
(NCDSMO Doc ID: NCDSMO -G-00050 -001_ 01) 305
• Manage and Secure Processes on Linux -based Cross Domain Solutions Using 20ystem 306
(NCDSMO Doc ID: NCDSMO -G-00051 -001_00 ) 307
• Using Linux Namespaces and Control Groups (CGROUP) t... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 43 | 01_00 ) 322
Implementing RTB requirements substantially reduces the risk of an unsu ccessful L ab-Based 323UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 44 | that is accepted into the LBSA 335
process prior to 1 January 2028, shall comply with the requirements contained within this 336
version or a newer version of this document. A new CDS, or modifications to an existing CDS, 337
accepted into LBSA after 1 January 2028 shall comply with an approved version of this... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 45 | f CDS product ) chang es will be assessed using the version of RTB used to 350
test the Major/Tenths version of the CDS. This applies only the RTB v5.0 and higher . 351
2) The NCDMSO may, at its sole discretion but in consultation with the developer and lab, 352
allow CDS with tenths -level changes to be assessed u... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 46 | l new threats, resolve ambiguities, resolve issues found 361
during LBSA that could impact multiple CDS , and provide securit y requirements for new 362
capabilities that cannot wait until a new yearly release of the document3. The latest version of a 363
yearly release is considered the valid and active version ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 47 | omatically adjust by shifting the Dev & Test and Deployment 374
timelines to the right each year until a new document is released. 375
1.2 Tailoring of Requirements 376
The NCDSMO recognizes that not all RTB requirements apply to a specific CDS and even to all 377
classes of CDS and that all RTB requirements ca... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 48 | The terms CDS Developer and CDS Vendor are interchangeable in this document. If a CDS is developed by a
Government PMO, then the PMO would be consi dered part of the CDS development team.UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFI... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 49 | occasionally uses the term s Low and High to refer to security domains. In most 397
requirements or examples, i t does not discuss domain s beyond Low and High. However, u nless 398
otherwise stated or implied ( e.g., in the diode section), the requirements in this document apply 399
to CDS that support multiple (... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 50 | rity. 412
May 413
The word may, or the adjective optional , mean s that the requirement is truly optional. 414
Systems are permitted to implement but are not required to implement . 415
Should 416
5 RFC 2119 – "Key words for use in RFCs to Indicate Requirement Levels ”, https://www.ietf.org/rfc/rfc2119.t... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 51 | elopment. 426
The NCDSMO understands that some deviations in the design and requirements may be 427
necessary f or different mission applications, operational or unique threat environments, and 428
technology choices. The NCDSMO also understands that security technology continually 429
evolves. If a developer or ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 52 | etworks. Start migration to hardware -based filtering for high 443
threat network connections to Classified NSS . Expected in 2025 release. 444
2. Support for cryptographic modules certified against FIPS 140 -2 will be removed in a 445
future revision. Expected in 202 6 release. See https://csrc.nist.gov/projec... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 53 | emoved in favor of 455
the more secure HTTP Boot in 202 4. 456
5. Use of Virtual TPMs for VM s will be required in the next release (VIRT -28). 457
1.8 CDS and Cryptographic Devices 458
(U//FOUO) The requirements in th is document apply to all cryptographic dev ices that embed 459
CDS functionality. Some NSA Cer... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 54 | loy existing Enterprise Cross Domain 471
Service Provider’s ( ECDSP ) enterprise CD service or enterprise -hosted CDS when their use 472
satisfies the CD mission requirements of DoD Components. Leveraging another operational 473
CDS, deployment of a CDS from the NCDSMO USG CDS Baseline List, or development of a ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 55 | ( US) Battlefield Information 486
Collection and Exploitation System (BICES ) Program Office for coalition and bi -lateral 487
networks including Combined Enterprise Regional Information Exchange System 488
(CENTRIXS ) 489UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 56 | n understand efficiently . The questionnaire can 501
be obtained by email ing ncdsmo @nsa.gov or by contacting your CDSE. 502
2.1 Buy, Buy and Modify, or Build New? 503
If use of an ECDSP will not support your validated mission requirements , then there are three 504
options (provided here in order of prefer... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 57 | t Warfighting Cloud Capability (JWCC) , https://community.hacc.mil/s/jwcc
7 For more information on the criteria for ECDSP and which ECDSPs exist contact the NCDSMO at
ncdsmo@nsa.gov (NIPRNet), ncdsmo@nsa.smil.mil (SIPRNet), or ncdsmo @nsa.ic.gov (JWICS).UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR,... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 58 | LBSA) is required for new 531
CDS . 532
o This approach is the most expensive, has the highest technical and authorization 533
risk, and has the longest timeline to deployment . 534
o If this is the option that must be selected, consider leveraging a proven CDS 535
developer. 536
▪ The divisions of most compan... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 59 | cost, and schedule risks. 550
2.2 CDS Testing (also called Assessment) 551
Beyond the normal internal functional and security testing performed by the developer , there are 552
typically three types of CDS testing activities conduct ed by external entities : security, integration 553
and interoperability , and ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 60 | o confirm the interoperability 563
between the CDS and the system(s) with which it is being integrated . For CDS integrated 564
with weapon or C4ISR systems this is usually performed by the Joint Inter operability 565
Test Command (JITC).8 566
• Flight/Vehicle Safety Testing: Testing of the CDS system to confirm i... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 61 | tained and enhanced to address new cyber threats , 583
component obsolescence , and RTB compliance until the CDS or the system it is 584
embedded in is decommissioned . 585
• Operating systems and CDS components will eventually reach end of life and 586
8 https://jitc.fhu.disa.milUNCLASSIFIED//FOR OFFICI AL USE... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 62 | isms. 596
Audit Data – Specific enumerated structured events from the operating system kernel, operating 597
system application, or CDS processes. 598
Central Audit and Loggin g Daemon (CALD) – The p rocess responsible for receiving CDS 599
audit and log events from CDS components, syntactically and semantical... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 63 | followi ng devices are not considered a CI: 611
keyboards, mice, and video cards (for the purposes of display). 612
Complex Document Data – This is a type of data that cannot be precisely defined and validated 613
via a ruleset or schema and can contain one or more embed ded data types . Examples include 614
M... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 64 | E, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 30 of 397 built specifically for the CDS. CDS processes can be multithreaded. CDS processes do not 624
include software programs that are provided by the operating system developer and are required 625
for the operating s ystem to function ( e.g., cron , ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 65 | ine the route (within the CDS) the data must take to reach the appropriate destination 637
security domain(s) based on the filtering rules applied. The dataflow filtering policy also 638
implements the CDS portion of foreign partn er information exchange agreements when a transfer 639
CDS is used to transfer data t... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 66 | ally includes controlling the read, write, delete, and execute 651
access to files, directories, networking ports, Inter -Process Communications (IPC) mechanisms, 652
9 Data Hiding and Data Disclosure are sometimes lumped together and called Data Loss Prevention (DLP).
10 Universally Unique Identifier (UUID) - ht... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 67 | devices based on owner, group, and others12. DAC 653
can be used to implement limited process isolation and flow control. File system Access Control 654
Lists (ACL) are considered part of the operation system DAC implementation . 655
Domain Router (DR) – The CDS filter process responsible for the transfer of... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 68 | ent Format (PDFs ) files). Filters can operate on a Pass/Fail model or Pass with 667
Change model. The Pass with Change model is the preferred model for imp lementing filters. 668
Filters may generate digitally signed filter reports in some CDS implementation models. Some 669
filters consist of a filter controller t... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 69 | r grouping of CDS) . Filter policy IDs are 680
assigned by the CDS when the filter policy is created , are unique , and are never reused in order 681
to maintain integrity of the audit record . 682
Filter Report Validator (FRV) – This process independently validates filter reports from the 683
filters and Result... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 70 | and validated via a 690
ruleset or schema . Examples include: XML, JavaScript Object Notation (JSON) , Key-Length - 691
Value (KLV), United States Message Text Format (USMTF ), Tactical Digital Information Link 692
(TADIL ) J, and Variable Message Format (VMF). Fixed format data can be textual or binary. 693
... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 71 | nation -state or transnational organized crime level) cyber actor is operating. 705
The cyber actor may be operating on the network without the knowledge of the pri mary user of 706
the network. HTNs are also networks for which the cyber hygiene is known to be insufficient, 707
the entities on the network are known ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 72 | undant and independent 718
filters . It is the last check in verifying that the destination domain is only receiving content and 719
metadata that are appropriate for that domain. The term “inbound” is relative to the domain n ot 720
the CDS , so the inbound pipeline is sending data to the destination domain. ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 73 | ermissions are used. The use of one -way IPCs is preferred to limit 729
the ability of an adversary to exfiltrate filter software and configuration off the CDS if a process 730
(e.g., filter) is compromised. 731
Job Schedule r/Results Processor – Two processes used in combination to implement the core 732
of a Re... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 74 | D. 744
Journaled Data – This is data that has been sent to the CDS. Journaled data includes data that 745
has not yet been filtered (e.g., queued waiting for filtering) , data that has successfully completed 746
filtering, data that is in the filtering pipeline and thus still being filtered, or data that failed... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 75 | ng its privileges
to other subjects; (iii) changing one or more security attributes on subjects, objects, the information system, or
system components; (iv) choo sing the security attributes to be associated with newly created or modified objects; or
(v) changing the rules governing access control. Organization -def... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 76 | ample is a fiber optic isolator. A diode is NOT a CDS itself, but it is a 760
component of a CDS . 761
Outbound Pipeline – This is the first half of an assured pipeline and is located between the 762
originating domain’s PA and the Domain Router . It is the primary filtering pipeline and is 763
responsible f... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 77 | a 773
PDC the content is not filtered. 774
775
Figur e 1 – Pitcher/Diode/Catcher (PDC) Architecture 776
Protocol Adapter (PA) – These CDS process es communicate with entities external to the CDS. 777
Protocol Adapters are the only CDS processes that are part of the dataflow that can interact with 778
the ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 78 | ity domains. Security Domain examples include Joint Worldwide 787
Intelligence Communication System ( JWICS ), Non-Secure Internet Protocol Router Network 788
(NIPRNet ), Secure Internet Protocol Router Network ( SIPRNet ), Combined Enterprise Regional 789
Information Exchange System (CENTRIXS ) – International Se... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 79 | as part of a 800
persistent session without a pre-defined end. The messages may have IDs but do not have file 801
names. Examples of streaming data including Full Motion Video (FMV) , Voice -over-IP (VOIP) , 802
Video Tele-Conference (VTC) , XML or JSON Web Services, and Modeling and Simulation 803
Data ( e.g., ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 80 | n two or more security domains (usually 817
networks) operating at different security levels and/or releasability and handling caveats. 818
Transfer CDS do not give users access into a different security domain; they simply 819
18 CNSSI 4009 definition: A type of CDS that facilitates the movement of data betw... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 81 | Database (see Section 17). 828
o If an MLS CDS does not allow regrading/relabelin g, read -up, read -down, write - 829
up, or write -down then it is a called a Multi -Level File Repository . A Multi -Level 830
Switch (see Section 18) functions similar to a ML File Repository except that it 831
marshals access t... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 82 | core purpose of the device is to provide 844
access to information in another domain not to transfer data . The typical 845
data being transf erred is restricted to keyboard, mouse, video, audio, and 846
smartcard redirection. Remote VDI Access CDS are generally used in 847
Enterprise environments. VM Access CD... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 83 | user so that TS data could be added to the document).
21 The CNSSI 4009 definition for Access CDS is : A type of CDS that provides access to a computing platform,
application, or data residing on different security domains from a single device.UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR,... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 84 | pplies to all classes and all variant s of CDS . In addition, it applies to both 861
Data center and Tactical environment implementations, as described in the following sections . 862
Both Datacenter -class and Tactical -class CDS are used in point -to-point installations . 863
4.1 Datacenter -class Transfer CD... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 85 | users (e.g., dataflows) . 874
The DCCDS category suppor ts three broad types of transfer CDS : 875
• Fixed Format Dataf lows (DCCDS -FF): CDS that typically support dataflow s required 876
for the secure, safe, and proper operation of sensors and weapon systems (e.g., processing 877
a radar track and launc hi... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 86 | IED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 38 of 397 (UAV) video, satellite/UAV ima ges, Video Teleconference (VTC) , and Voice Over 888
Internet Protocol (VOIP) . These dataflows have low tolerance for latency (e.g., 100ms or 889
less) and moderate -to-h... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 87 | designed for use in environmentally constrained condition s (e.g., 902
sand, heat, humidity, shock , and vib ration ) and in most cases are used mainly for fixed format 903
data flows or streaming video/images ( e.g., from an unmanned aerial vehicle (UAV) ). These 904
CDS typically have a low tolerance for latenc... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 88 | a CDS: 917
1) Traditional Software Based (TSB) – CDS implemented in s oftware , operating on 918
trusted operating system (OS) (e.g., Solaris® 11 with Trusted Extensions , Red Hat® 919
Enterprise Linux® with SELinux enabled , General Dynamics PitBull® Trusted 920
Operating Sy stem, BAE Systems STO P™ Operati... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 89 | Manag ement (SCRM) directives . Compos ed COTS CDS use 931
one or more one-way control mechanisms enforced by hardware (e.g., an optical diode) 932
to provide the domain separation and software (along with supporting hardware) to 933
implement filters . A Composed COTS CDS is not typically implemented using a 93... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 90 | ctivities focused on aligning RTB with known threats and 940
weaknesses found in publicly available knowledge bases. It also defines the risk assumptions and 941
threats that are, in part, the basis for the requirements described in this document. The 942
assumptions, as defined below, either reduce or increase the ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 91 | 955
use-cases . RTB, on the other hand, is targeted to the specific problem domain of CDS and is not 956
limited to what has been seen in the wild. Since it applies to a more constrained problem domain, 957
RTB can be more specific or strict than AC&C. For instance, the OSSR -4.5 requirement fits very 958
well wit... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 92 | 4 https://attack.mitre.org
25 https://cwe.mitre.org
26 https://capec.mitre.orgUNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JPN, KOR, NATO, NOR, SAU, SWE, QAT
Page 41 of 397 struc... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 93 | future. 982
6.2 Operational Environment Risk Assumptions 983
This section provides some o f the operational environment risk assumption s for DCCDS and 984
TCDS classes of CDS. The assumptions in this section either reduce or increase the risk to the 985
CDS based on the operational environment. 986
6.2.1 D... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 94 | ositive control of the CDS is substantial. 1002
27 Examples include tanks or similar land vehicles , unmanned vehicles (air, water, land), river boats or similar small
watercraft, planes, man -portable, and forward operating bases/locations.UNCLASSIFIED//FOR OFFICI AL USE ONLY//REL TO USA, ARE, BHR, FVEY, ISR, JP... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 95 | ssentially unbounded threats) networks like the Internet (if not 1013
directly then cascaded from another interconnected system like NIP Rnet ). 1014
• (U//FOUO) The developers of the CDS are not always privy to the true operational 1015
environment(s) in which the CDS will operate. 1016
• (U//FOUO) One or ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 96 | system degradation , or cause a denial 1029
of service (DoS). 1030
6.4.2 Malicious Insider (User) 1031
• (High -side user) Attempts to exfiltrate classified or sensitive data to the Low-side by 1032
manipulati ng data sent to the CDS. 1033
• (Low -side user) Attempts to cause a DoS or undermine the integ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 97 | in) 1044
• Admins can uni ntentionally misconfigure a CDS. 1045
• Users can unintentionally misuse a CDS . 1046
6.4.5 Attacks from Low-side Network(s) 1047
• Use of the Low-side network to attack the CDS and supporting systems to disrupt the 1048
operations of the CDS. 1049
• Use of the Low-side networ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 98 | ccessfully attack and manipulate the CDS component 1062
supply chain. 1063
6.4.8 Insufficient Human Review 1064
• Insufficiently or incorrectly marked content could result in the accidental release of 1065
sensitive information. 1066
• Insufficiently trained RHR Reviewer does not know how to inspect do... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | 99 | of mechanisms within content or a protocol that may pose a 1076
data transfer risk, those mechanisms can be grouped into three broad categories: data attack risks, 1077
data hiding risks, and data disclosure risks. 1078
The NSA publishes a series of documents called Inspection and Sanitization Guidance (ISG) ... | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | Draft_2023_RTB_CDS_Design_Implementation_Requirements_v5_0_rev_85 | [] | [] | [] |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 11