01.12.2014 Views

monitoring

monitoring

monitoring

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UNCLASSIFIED<br />

DEFENSE SCIENCE BOARD | DEPARTMENT OF DEFENSE<br />

The third integral part of the testing capability would be a standing analytical “White Team”<br />

that would use the scenario‐generator and scenario‐to‐asset planning approach (see Chapter 4)<br />

to guide exercises/experiments, assess implications of testing and training results, and identify<br />

needed changes/improvements for the next cycle. It would provide a simulation capability and<br />

translate test results to deployed <strong>monitoring</strong> operations. The information management aspects<br />

of the White Team activities would eventually become part of the real world ops center for the<br />

comprehensive nuclear <strong>monitoring</strong> system of systems.<br />

The fourth essential element of the testing capability would be a standing Red Teaming activity.<br />

Red teaming would include active R&D on means by which adversaries could (or do) evade<br />

threat‐assessment <strong>monitoring</strong> and by which treaty partners might evade treaties and treaty<strong>monitoring</strong>,<br />

including by deception and denial. A key step would be to rebuild a national<br />

nuclear threat assessment capability, principally but not exclusively with the National Labs, that<br />

anticipates “nth group” weapon designs, development, and production approaches (as<br />

discussed in Chapter 3). The services and certain combatant commands (COCOMs) could<br />

explore ways in which nth‐countries might deploy, operate, and employ nuclear and dualcapable<br />

weapon systems and forces. The White Team would referee red‐teaming, for example<br />

by specifying the levels of technology, or degree of knowledge of U.S. systems, that might be<br />

attributed to various actual or simulated adversaries.<br />

6.2.3. What Would Be Done Using the Testing Capability?<br />

The testing capability would eventually cover the full range of experiment, test, demonstrate,<br />

exercise, and train, through multiple cycles of learn‐iterate‐adapt. The testing capability could<br />

be used to explore very specific detailed topics, like improved CONOPS for a particular type of<br />

advanced sensor, and very general questions, like the interplay between transparency and<br />

stability. Each experiment would use a few or many of the types of facilities and capabilities<br />

that are part of the testing capability. The exercises, tests, etc., would explore the full scope of<br />

current and possible future <strong>monitoring</strong> applications: nonproliferation, counter‐proliferation,<br />

countering nuclear terrorism, IAEA <strong>monitoring</strong> applications, Comprehensive Nuclear‐Test‐Ban<br />

Treaty (CTBT) <strong>monitoring</strong>, cooperative threat reduction, routine and challenge on‐site<br />

inspections, negotiated over‐flights (Open Skies done right – see Chapter 2), and confidencebuilding<br />

measures.<br />

The exercises and experiments would be sponsored by all relevant USG agencies, occasionally<br />

singly but more often jointly. In certain important cases there would be international<br />

participation, partly for confidence‐building purposes or ideally, as an integral part of the<br />

phased strategy for cooperative regimes discussed in Chapter 2. There would be red‐ and blueteaming,<br />

in multiple forms.<br />

DSB TASK FORCE REPORT Chapter 6: Experiment to Iterate and Adapt: National Testing Capability | 68<br />

Nuclear Treaty Monitoring Verification Technologies<br />

UNCLASSIFIED

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!