Department of Defense documentation describing cyberspace-related concepts uses a variety of terminology defined in joint doctrine—but also other sometimes ambiguous terms in documents, presentations, and references—often implying a similar meaning to official terminology, yet without clear definitions. Clear definitions avoid confusion and misunderstanding based on metaphor, simile, or implied meaning that may be interpreted differently by readers with different perspectives on cyber operations (CO) or mission planners working at different tactical, operational, and strategic levels who need to include the intended and unintended effects of CO in their mission analysis and planning. It is important for commanders and the technical experts on their staff to have a shared understanding of key terms in order to integrate CO into multidimensional mission analysis and mission planning. This paper discusses the relationships between several terms used to describe characteristics of CO and how they relate to other terms important to military operations and mission planning. Focusing on defensive cyber operations, we discuss key terrain-cyber and mission-relevant terrain-cyber and review current definitions for each term and their synonyms. We also describe how these terms relate to the joint doctrine multi-domain concept of key terrain.
Publisher Statement
This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute.
This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100.
NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.
[DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.Copyright Statement
Copyright 2025 Carnegie Mellon University.