ANNEX A: C2 PROTECT POLICY
ANNEX B: C2 PROTECT DOCTRINE
ANNEX C: C2 PROTECT FORCE DESIGN AND STRUCTURE
ANNEX D: C2 PROTECT PERSONNEL AND STAFFING IMPLEMENTATION STRATEGIES
ANNEX E: C2 PROTECT TACTICS, TECHNIQUES AND PROCEDURES
ANNEX F: TASK 6 C2 PROTECT TRAINING
ANNEX G: C2 PROTECT INTELLIGENCE
ANNEX H: DEFINE AND PRIORITIZE PROTECT RDA REQUIREMENT
ANNEX I: C2 PROTECT RESOURCING
ANNEX J: C2 PROTECT COMMON TOOL SET
ANNEX K: C2 PROTECT CENTRAL REACT CAPABILITY
ANNEX L: C2 PROTECT RISK MANAGEMENT PROCESS
APPENDICES
The Army Command and Control Protect (C2 Protect) Implementation Plan is the accompanying plan to the Army enterprise strategy implementation plan,
and is the integration and application of all necessary operational, engineering, and security disciplines and intelligence (or counterintelligence) support to
ensure the availability, integrity, and confidentiality of information when and where it is needed throughout the DoD. The goal of this integration and
application of disciplines and support is an information infrastructure that is capable of providing complete and unaltered information while withstanding
naturally occurring and malicious (insider and enemy) disruptions or attacks against the infrastructure.
The Army C2 Protect Implementation Plan outlines the measures that Army leadership will undertake to ensure that the Army's portion of the C2 Protect
Program is implemented into the Defense Information Infrastructure (DII) and is prioritized to set the baseline for adequate C2 protection. It incorporates the
Army Enterprise Strategy of a single unified vision for the Army C4I community.
This Implementation Plan supports other volumes, which will make up the C2 Protect Library.
The Army C2 Protect approach addresses all threat protection schemes from the National Command Authority to the Foxhole: maintaining confidentiality,
integrity, and availability of information necessary for decision making and control of forces and systems.
The implementation of C2 Protect measures are impacted by current downsizing issues on both a personnel resources and funding level. Current actions to
address these issues are being orchestrated within the ARSTAF and by the members of the Army C2 Protect General Officer Steering Committee. Roles and
responsibilities of primary Army Staff have been integrated with developmental responsibilities for execution of the Army Enterprise Strategy and Force
XXI. It is imperative that prioritization of expenditure of resources for C2 Protect ensures that the Army can keep the information highway open now and in
the future.
The Implementation Plan is designed to establish, manage and control the growth of Army C2 Protect initiatives and their execution. It is in agreement with
the Army Enterprise Strategy, and supports the Defense Information Systems Agency Defensive Information Warfare efforts.
The Implementation Plan addresses the vulnerabilities inherent in the Military Information Environment (MIE). Efforts directed toward Power Projection
and Split Base Operations present increased risks to warfighting operations. The Army C2 Protect Program Management Plan outlines current constraints
and identifies threats and risks to warfighter information assets. The Implementation Plan addresses means to reduce the impact of these constraints and
identifies the increasing need to understand, act upon and react to on-going attacks to Army Information Systems (AIS).
The C2 Protect Program Management Plan strategy defines the PROTECT, DETECT and REACT measures, and coordinating effort related to information
assurance and reliability. It also outlines the funding and resourcing constraints and their impact on implementation of the Army's C2 Protect Program.
Implementation of the C2 Protect strategies has been divided into three categories for action. The timeline for each category begins with approval and
signature of the plan:
As part of the implementation process, the C2 Protect missions and responsibilities for ARSTAF, Special Staff, USAMACOMs, FOAs, and subordinate
elements have been identified in the Program Management Plan. These roles and responsibilities address planning, resourcing, executing, and evaluation
tasks.
With the publication of this keystone plan the Army begins the implementation of its Command and Control Protect program which encompasses new
strategy for integration of TTP and technologies. This plan provides guidance to Senior Commanders and Operations planners for addressing threats and
vulnerabilities to Army C4 systems. The goal of the Army C2 Protect Program is a strong foundation for the construction of C2 Protect training,
implementation and execution of TTP for C4I for the Warrior.
The capstone of Information Operations is "winning the Information War." The integration of effective C2 Protect technologies and measures assures dominance of the Cyberspace battle ground.
This is the Army Command and Control Protect Implementation Plan for C2 Protection measures. These measures will ensure reliable and continual use of
the available transport and information systems in the Defense Information Infrastructure, Military Information Environment, the National Information
Infrastructure, and the Global Information Environment through which the Force XXI Warrior will navigate.
The Army Command and Control Protect Implementation Plan has been produced under the direction of HQDA, ODISC4, ODCSINT, ODCSOPS, and the
C2 Protect Council of Colonels. This version was developed by the Army C2 Protect Working group chaired by the ODISC4.
Other organizations and supporting participants in this effort included: USAINSCOM LIWA, USASIGCEN, USACECOM, USAISC, USA Forces Command,
USAICS, NSA, and USATRADOC.
Command and Control Protect (C2 Protect) encompasses those measures taken to maintain effective C2 of our own forces by turning to friendly advantage or negating adversary efforts to deny information to, influence, degrade, or destroy the friendly C2 system. Headquarters Department of the Army has formed a C2 Protect TRIAD consisting of the Office of the Deputy Chief of Staff for Operations and Plans (ODCSOPS), Office of the Deputy Chief of Staff for Intelligence (ODCSINT) and the Director of Information Systems for Command, Control, Communications and Computers (ODISC4). Under this TRIAD the ODISC4 established an Army C2 Protect working group (WG) and tasked them to develop the C2 Protect library. This library consists of six volumes: C2 Protect Program Management Plan (PMP) (Volume I), C2 Protect Master Training Management Plan (Volume II), C2 Protect Implementation Plan (Volume III), Intelligence Support To C2 Protect Action Plan (Volume IV), C2 Protect Future Year Resourcing Proposal (Volume V), and C2 Protect Threats and Vulnerabilities Document (Volume VI).
The Army C2 Protect Implementation Plan (IP) identifies those tasks necessary to ensure Battlefield Information dominance and incorporates corresponding action plans. This IP designates specific tasks and responsible authorities to ensure C2 Protect requirements are properly implemented, integrated and resourced for the total force. This plan synchronizes on-going and planned C2 Protect implementation initiatives across the Army, as well as managing the growth of Army C2 Protect developments.
The Army will continue to optimize the information technology environment increasing the Warrior's reliance upon information. C2 Protect concepts are designed to provide the Warrior with an information infrastructure that is capable of providing complete and unaltered information while withstanding naturally occurring and malicious disruptions to the information infrastructure. C2 Protect implementation, in an integrated manner with all other facets of Information warfare (IW), will ensure sustainment of Information Operations (IO) during all phases of military operations and in all deployed environments.
This plan applies to the Active Army, the Army National Guard (ARNG), the United States Army Reserve (USAR), and their agents. The scope of the C2 Protect IP addresses implementation requirements of the C2 Protect PMP, covering strategic through tactical operations in support of sustaining base and soldiers in the foxholes.
This document is developed under the authority of the Department of the Army C2 Protect TRIAD (ODISC4, ODCSINT, and the ODCSOPS) and under the direction of the C2 Protect and the Information System Security (ISS) Councils of Colonels. This plan augments the Army C2 Protect PMP and the Master Training Management Plan.
This plan, in cooperation with the ODCSOPS, ODCSINT, and ODISC4's Information Systems Security (ISS)' (Electronic warfare, OPSEC, PSYOP, Deception, Physical destruction and Intelligence) Management Office, is developed in response to the C2 Protect PMP in order to support the Army's portion of the Military Information Environment (MIE). In support of the plan's implementation, ODISC4 launched an initiative by forming the Army C2 Protect Working Group.
Army implementation of C2 Protect requires the close integration and coordination of a large number of Subject Matter Experts (SMEs) and the importation of technology knowledge bases from across the RDT&E communities. The intent is to leverage knowledge.
It is important that C2 Protect technology and Tactics, Techniques and Procedures (TTP) efforts not be developed independently or in isolation. Cohesive centralized oversight of the C2 Protect General Officer Steering Committee (GOSC) and other appropriate committees and centers is required.
The acquisition community assumes a greater role in standardization, integration, and interoperability of C2 Protect solutions and TTP in their mission of C2 system design, development and sustainment.
Doctrine development and implementation proponencies are now charged with the responsibility to ensure that C2 Protect doctrine integration across the Total Force is consistent and compatible.
The intermediate steps to the end state that must be accomplished by functional proponents are identified in Section 9. This plan supports the Army Battlefield Command Systems (ABCS) Master Plan, the ABCS Campaign Plan, and the Army Intelligence Master Plan's Intelligence Support to C2 Protect Operations.
A major portion of the C2 Protect Implementation strategy shall be the incorporation of Risk Management. A risk management modeling process will be key to Army C2 Protect decisions and TTP integration into C2. The process, shown in Figure 8-1, shall be used to determine value added. It will form a basis to manage risk and make system decisions which will drive system developments, modifications and employments.
The following tasks are those critical actions deemed necessary for implementation of steps to integrate C2 Protect into Army Command and Control Systems. These tasks are representative of those actions listed in Tables 7-2-1 through 7-2-7 Volume I of the C2 Protect PMP.
The ODCSINT, in coordination with the ODISC4 and the ODCSOPS, will develop C2 Protect policy that recognizes the need to ensure confidentiality, integrity and availability of information during all phases of military operations and in all deployment environments. Policies must be network-oriented and sufficiently flexible to cover the full range of resource systems, including equipment and personnel. These policies will be incorporated into appropriate Army publications. ODISC4's action plan is shown at Annex A.
USATRADOC will ensure C2 Protect is addressed in Army Information Operations, Information Warfare and Command & Control Warfare doctrine. This task will include development of operational doctrine for commander and manager, developer, system administrator, security manager and user functions.
Functions and duties building on emerging programs and initiatives will also be addressed. It will incorporate current information system security standards and programs, as well as other supporting security disciplines to establish a foundation for achieving C2 Protect capability.
The sustaining base is a key piece supporting Force XXI concept of "force projection."
The force's sustaining base in CONUS requires doctrine to be developed to support the Army Digitization Architecture. The success of force projection implementation depends on reliable Pentagon-to-foxhole command communications and information systems. Commander/user requirements will be incorporated into system development activities starting at Milestone Zero of the life-cycle to ensure that interoperability and continuity of operations are considered and maintained. The action plan to address this section is shown at Annex B.
ODCSOPS in coordination with the C2 Protect Triad will manage force structure initiatives (Infrastructures and Architectures) and analyses to ensure C2 Protect issues are addressed.
As the Army Information and Command and Control Systems are designed and fielded for operational integration a mechanism must be implemented to assure information system security requirements are incorporated.
Migrating systems must be evaluated using a risk management process to determine if modernization and upgrade investments are appropriate or whether these systems should be phased out.
The ODCSOPS' action plan is shown at Annex C.
The designated personnel proponent will initiate action to establish a C2 Protect career management program. ODCSPER (OPM/ASA) and ASA (RDA) will provide guidance to the designated personnel proponent for submission of action to establish appropriate skill identifier (Army Occupation Code/Military Occupation Skill/Skill Identified/Additional Skill Identified) (AOC/MOS/SI/ASI).
The personnel process requires designation of personnel proponent per AR 600-3. The personnel proponent is responsible for initiating and coordinating the establishment of training requirements, qualifications and resource requirements for the appropriate skill identifier. They will also initiate the appropriate Military Occupational Classification Structure action per AR 611-1.
The ODCSPER will advise the designated personnel proponent on the development of new skill identifier(s) per AR 611-1 for C2 Protect. The results of this effort will drive the requirements for modifications to USATRADOC courses.
The C2 Protect career management system must encompass tracking schemes for the appropriate officer and/or enlisted skill identifier and/or civilian career programs. The designated personnel proponent will determine personnel proficiency requirements. Technically proficient personnel must be assigned to C2 Protect positions at all appropriate command and staff levels within the Army. A method must be implemented for identifying personnel with C2 Protect skills resulting from their civilian careers.
The designated personnel proponent, in coordination with ODSCOPS, must determine the staffing requirements to support commanders, managers, developers, systems administrators, security managers, users and other discipline specialists (e.g., OPSEC, COMSEC, PSYOPS, etc.).
The designated personnel proponent action plan is shown at Annex D.
USATRADOC, in coordination with ODCSOPS and ODISC4, will develop C2 Protect TTP. Identify, develop, and implement TTP in accordance with policy and doctrine for training of commanders, managers, developers, systems administrators, security managers and users. Develop a DA customer support (clearinghouse) for acquiring network intrusion detection tools. Develop TTP guidelines for their employment and use. Develop and implement TTP in accordance with policy and doctrine to manage, protect, detect, and restore operations for C4I systems.
USATRADOC's action plan is shown at Annex E.
USATRADOC, in conjunction with ODISC4, ASA (RDA) and the Major Commands (MACOMs), will develop and implement the C2 Protect MTMP that articulates the overarching direction for C2 Protect training in the Army.
USATRADOC must develop an education and training program that integrates the five pillars of Command and Control Warfare into an Army-wide military and civilian training program.
Developing effective/innovative responses to IW threats will occur via experimentation during exercises and training.
USATRADOC's action plan is shown at Annex F.
The ODCSINT will identify threat and/or related vulnerability issues for C2 Protect that require further study. As appropriate, the ODCSINT will direct, supervise, manage, coordinate and disseminate the studies.
This task is further delineated in, Volume IV "Intelligence Support to C2 Protect Action Plan," and Volume VI "C2 Protect Threats and Vulnerabilities."
The ODCSINT shall incorporate C2 Protect requirements into AR 380-19 (Information Systems Security) and require all-source threat assessments by local intelligence staff offices (G2/ODCSINT) to be part of the automated information systems accreditation process to ensure systems are capable of operating in their intended environments (to include the IW threat environment).
ODCSINT shall coordinate with ODISC4 a revision of AR 25-3 (Life-Cycle Management of Automated Information Systems) to require the development of System Threat Assessment Reports (STARs) beginning at Milestone Zero of the life-cycle of major (Category 1-3) automated information systems. The STARs supporting automated information systems should be reviewed by the Major Automated Information System Review Council (MAISRC) and be used as the basis for selection of information systems security countermeasures as an integral part of the life-cycle (vice retrofitting systems after fielding). The use of the STAR process will identify Critical Intelligence Parameters (CIPs) of emerging automated information systems which will, in turn, drive the development of formal Production Requirements (PRs) to provide the basis for ongoing intelligence collection focusing on threats impacting upon C2 Protect issues.
ODCSINT will insure that experts from the intelligence production agencies and the major Army commands representing intelligence, security and user communities share information and document threat concerns impacting upon C2 Protect concern with the Army leadership.
ODCSINT's action plan is shown at Annex G.
Define and Prioritize Command, Control, Communications and Intelligence (C4I) C2 Protect RDA Requirements. ASA (RDA) must ensure that C2 Protect measures are integrated into Army acquisition life-cycle management programs in coordination with the C2 Protect Triad. Emerging information technologies must be incorporated into the life-cycle process to meet end user requirements while ensuring that interoperability and continuity of operations are maintained throughout development, testing, production and fielding.
ASA (RDA), in conjunction with the C2 Protect Triad, shall develop an RDA strategy to implement C2 Protect capability in information materiel development and acquisition, including incorporation of Non-Developmental Items/Commercial-off-the-shelf (NDI/COTS) hardware, software, and their integration for use in the MIE.
Commercial hardware and software will comprise the bulk of Army C2 systems, RDT&E for C2 Protect should focus on the modifications required of commercial hardware and software systems for use by the military. In addition, this strategy shall support the continued development of C2 Protect technology, encouraging innovative approaches, and efforts underway in academia and private industry. Because commercial hardware and software will comprise the bulk of Army C2 systems, RDT&E for C2 Protect should focus on the modifications required of commercial hardware and software systems for use by the military, and on the technologies needed to verify the integrity of all initially delivered systems and all subsequent updates and/or modifications to fielded C2 systems, and on capabilities unique to military applications. In order to support this strategy the following items must be accomplished:
The RDA process will address and resolve technical interoperability problems of information and command and control systems throughout the Army
environment. It will embed System Security Engineering in system acquisition, possibly using NSA's System Security Engineering Model as a tool.
ASA (RDA)'s action plan is shown at Annex H.
The resourcing plan for the total force shall have traceability to near, mid, and long term C2 Protect requirements developed by the C2 Protect and ISS Council of Colonels. The plan shall support Section 3 of the Defense Planning Guide, subsection d, Force Structure, paragraph 4, and C4I Information Warfare, as defined in The Army Plan (TAP) and the Army Modernization Plan, which address winning the Information War. This task will support the development of the C2 Protect, Future Years Resource Plan, Volume V.
The end objective of this task is to ensure that adequate funding and resourcing is made available to commanders, managers, developers, security personnel and systems administrators responsible for the effective management and operations of the Army's Command and Control and Information Based Systems.
The risk management process will be a major factor in determining resource requirements and resource commitments.
ODISC4's action plan is shown at Annex I.
USAMC (USACECOM'S INFORMATION OPERATION SPO) as the focal point, in coordination with the C2 Protect Triad, will establish a capability to identify, develop, manage (certification and configuration control), sustain, train and provide automated tools for effective implementation of C2 Protect strategies, programs and policies. The scope of this capability will encompass Pentagon to foxhole support for Command and Control Warfare (C2W).
The C2 Protect Common Tool Set will be employed to provide specific capability at all Army echelons responsible for the management, detection, protection and reaction to C2 systems anomalies, vulnerabilities, threats, reconfiguration and reconstitutions.
USAMC (USACECOM'S INFORMATION OPERATION SPO), in coordination with functional proponents and materiel developers shall integrate C2 Protect common tools into Army legacy, migration, developing and future systems, incorporating emerging information technologies throughout research, development, testing, production, fielding and life-cycle support.
The USAMC (USACECOM'S INFORMATION OPERATION SPO), in coordination with the C2 Protect Triad, shall develop a C2 Protect common tools strategy plan to support C2 Protect. Planning shall support the continued evolution of C2 Protect technology developments, innovative approaches, and leveraging efforts underway in academia and private industry. Investigations of the modifications required to adapt commercial hardware and software for use by the military shall be conducted. Technology assessments and technology demonstrations shall be accomplished to provide insights into what is possible and feasible.
In the future commercial hardware and software will comprise the bulk of Army Command and Control systems. C2 Protect common tools should focus on
the identification of system vulnerabilities, and employment of active and passive countermeasures.
USAMC's action plan is shown at Annex J.
LIWA in cooperation with USAISC and USAINSCOM, in coordination with the C2 Protect Triad, shall develop an operational concept for the Army Central React Capability. This concept will integrate intelligence support to automated systems and the capabilities of network management into a unified C2 Protect effort.
This CERT concept shall leverage existing theater and installation network management capabilities by linking them with the Army Power Projection Centers (APPOC). Additionally, this concept shall investigate the co-location of intelligence and security assets at the APPOC to facilitate rapid protect, detect and react actions.
The action plan is contained in Annex K.
USAMC (USACECOM'S INFORMATION OPERATION SPO) and USATRADOC, in coordination with the C2 Protect Triad, define a risk management strategy and develop a process which can be used by all Army echelons for managing and assessing risks associated with the entire system life-cycle process, applicable to both functional proponents and materiel developers. The developed process shall a provide a model which can be used in support of risk management decisions to identify countermeasures to protect the Army's portion of the Global Information Environment (GIE).
The development of the risk management process shall focus on the criticality of the information and the operating environments of employed systems within the context of the GIE. The Risk Management process must be generic so as to be exportable for application to Information Operation concept as defined in TRADOC Pam 525-5 and TRADOC Pam 525-69, the C2W operations .
The development of the Risk Management process shall encompass the leveraging of ongoing efforts at OSDC3I, and appropriate screening of available
commercial products. This will ensure that terminology is consistent throughout the process, and compatible with joint requirements and doctrine.
USAMC (USACECOM'S INFORMATION OPERATION SPO) and USATRADOC action plan is shown at Annex L.
Table 9-1 is a composite representation of the actions and requirements defined in the Army C2 Protect PMP, and MTMP showing coordination with each functional task and action plan group used in this Implementation Plan.
The layout of Table 9-1 consists of general functional categories and subordinate tasks. Lateral tasks have been assigned a tracking number relative to the
reference document's original table identification. Horizontally the task is referenced by tracking its requirement documentation in Volumes I, II, and III of
the C2 Protect library.
| Trace Metrics ID # | Volume I C2 Protect Program Management Plan | Volume II C2 Protect Master Tng Management Plan | Volume III C2 Protect Implementation Plan |
100 | 2.2, 7-2-2d | 3.1 | 4.0 | |
Assumptions | 101 | 2.4 | 4.0 |
|
C2 Protect Policy | TM ID# | Volume I | Volume II | Volume III |
C2 Policy Actions | 200 | Table 7-2-2 | 6.4.1, 7.2.4 | Annex A |
C2 Protect PMP integration into Security Architecture | 201 | 2.4, 7-2-2g | 1.5 | 9.0 Annex A |
Commercial Transmission and Processing DI | 202 | 2.4, 3.1, 4.1, 7-2-2k |
| Annex A |
Defense Information Infrastructure (DII) | 203 | 2.4, 3.1 |
| Annex A |
Defense Integrated Systems Network (DISN) | 204 | 2.4 |
| Annex A |
Threat Information Dissemination | 204a | 3.7, 4.1, 5.3, 7-2-5c | 6.2 | Annex A |
Interoperability Security Stds | 204b | 3.8, 7-2-6d |
| Annex A |
Information Technology Transfer | 204c | 3.9 |
| Annex A |
C2 Protect Doctrine | TM ID# | Volume I | Volume II | Volume III |
C2 Doctrine Actions | 300 | Table 7-2-2, 7-2-2 | 6.4.1, 7.2.4 | Annex B |
Army Enterprise Strategy | 301 |
|
|
|
Ten Principles | 302 | 2.5, 3.1, 4.1 |
| 8.0, Annex B |
Focus on the Warfighter | 302a | 2.5 |
| Annex B |
Joint Interoperability | 302b | 2.5, 3.9 |
| 9.0, 7.0, Annex B |
Space Based Assets | 302c | 2.5, 7-2-6d |
| Annex B |
Digitize the Battlefield | 302d | 2.5, 7-2-6c |
| 8.0, Annex B |
Power Projection Platforms | 302e | 2.5 |
| Annex B |
Information Technology Environment | 302f | 7-2-4g, 2.5, 3.1, 3.2, 3.9 | 1.4 | 3.0, Annex B |
Multi-Level Security | 302g | 2.5 | 1.4 | Annex B |
Spectrum Supremacy | 302h | 2.5 |
| Annex B |
Integrated Commercial System Technology | 302i | 2.5, 3.1 | 4.5, 6.3.1 | 9.0, Annex B |
Exploit Modeling and Simulation | 302j | 2.5 | 6.3.6 | 8.0, Annex B, C |
C2 Organ. & Arch. Actions | 400 | Table 7-2-4, 7-2-4 | 6.1.2 | Annex A, B |
C2 Protect PMP integration into Security Architecture | 401 | 2.4, 7-2-2g | 1.5 | 9.0, Annex C |
Multi-Level Security | 402 | 2.5 | 1.4 | Annex C |
Commercial Transmission and Processing | 403 | 2.4, 3.1, 4.1, 7-2-2k |
| Annex C |
Defense Information Infrastructure (DII) | 404 | 2.4, 3.1 |
| Annex C |
Defense Integrated Systems Network (DISN) | 405 | 2.4 |
| Annex C |
Integrated Commercial System Technology | 406 | 2.5, 3.1 | 4.5, 6.3.1 | 9.0, Annex C |
Exploit Modeling and Simulation | 407 | 2.5 | 6.3.6 | 8.0, Annex C |
Interoperability Security Standards | 408 | 3.8, 7-2-6d |
| Annex C |
C2 Protect Personnel Actions | 500 | Table 7-2-3, 7-2-3 | 1.4, 5.1.1, 5.3.3, 7.3 | Annex D, F |
ISS C2 Protect Staffing | 501 | 6.3, 7-2-4b | 6.3.3, 7.4.5, 9.4, Annex D |
|
Requirements | 502 | 6.6, 7-2-3 | 3.2, 5.2.1, 5.3.2, 6.3.1, 9.6, Annex A, C, D, F |
|
Systems Administrator | 502a | 6.6, 7-2-3b | 5.3.1, 5.3.2,7.8.12, 5.3.8, 9.2, Annex D, E, F |
|
ISS Manager | 502b | 6.6, 7-2-3b | 6.1.2, 6.4.1, Annex D, E, F |
|
Network Security Mgr | 502c | 6.6, 7-2-3b | 6.1.2, 6.4.1 | Annex D, E, F |
C2 Funding & Resourcing | 503 | 7.2, Table 7-2-1, 7-2-1 | 7.1.1, 5.3.7, 6.3.3, 6.3.5 | Annex I |
C2 Protect Tactics, Techniques, and Procedures (TTP) | TM ID# | Volume I | Volume II | Volume III |
Detection Capability | 600 | 3.5, 5.4, 7-2-7a & c |
| 9.5, 9.8, Annex E |
C2 Protect Goal | 601 | 5.1 | 2.1, 5.1 | 10.1, Annex E |
Red Team Operations | 602 | 5.2, 7-2-6e |
| Annex E |
Protect | 603 | 5.3 |
| Annex E |
Detect | 604 | 5.4 |
| Annex E |
React | 605 | 5.5 |
| Annex E |
C2 Protect Execution Strategy | 606 | 5.6 |
| Annex E |
Reporting Channels | 607 | 3.6, 7-2-7a |
| 9.8, Annex A, E, G |
Detection Capability | 700 | 3.5, 5.4, 7-2-7a & c |
| 9.5, 9.8, Annex E, F, G |
C2 Protect for Protect/Detect/React/Restore | TM ID# | Volume I | Volume II | Volume III |
Detection Capability | 800 | 3.5, 5.4, 7-2-7a & c |
| 9.5, 9.8, Annex E, F, G |
C2 Protect Goal | 801 | 5.1 | 2.1, 5.1 | 10.1, Annex E, F, G, J |
Red Team Operations | 802 | 5.2, 7-2-6e |
| Annex E, F, G, J |
Protect | 803 | 5.3 |
| Annex E, F, G, J |
Detect | 804 | 5.4 |
| Annex E, F, G, J |
React | 805 | 5.5 |
| Annex E, F, G, J |
C2 Protect Execution Strategy | 806 | 5.6 |
| Annex E, F, G, J |
Reporting Channels | 806 | 3.6, 7-2-7a & c |
| 9.8, Annex E, F, G, J |
C2 Protect Training | TM ID# | Volume I | Volume II | Volume III |
C2 Protect Training Actions | 900 | Table 7-2-3, 7-2-3 | 1.4, 5.1.1, 5.3.3, 7.3 | Annex C, D, E, F |
Certification & Accreditation | 901 | 6.5 | 5.3.1 | Annex F |
ISS/C2 Protect Training | 902 |
|
|
|
Requirements | 903 | 6.6, 7-2-3 | 3.2, 5.2.1, 5.3.2, 6.3.1, 9.6, Annex A, C, D, F |
|
COMPUSEC Training | 903a | 6.6 |
| Annex A, C, D, F |
Systems Administrator | 903b | 6.6, 7-2-3b | 5.3.1, 5.3.2,7.8.12, 5.3.8, 9.2 Annex A, C, D, F |
|
ISS Manager | 903c | 6.6, 7-2-3b | 6.1.2, 6.4.1 | Annex A, C, D, F |
Network Security Mgr | 903d | 6.6, 7-2-3b | 6.1.2, 6.4.1 | Annex A, C, D, F |
C2 Protect Intelligence | TM ID# | Volume I | Volume II | Volume III |
C2 Intel. & Studies Actions | 1000 | Table 7-2-5, 7-2-5 |
| Annex G, H |
ISS/C2 Protect Investigation Capability | 1001 | 6.4, 7-2-1d |
| Annex G, H |
Threats to the Army Information Infrastructure | 1002 | 4.0, 7-2-5b |
| Annex A |
Threat to the Enterprise Strategy | 1002a | 4.1, 7-2-5a |
| Annex G, H |
Types of Threat | 1002b | 4.2 |
| Annex E, G, H |
C2 Protect Research, Development, Acquisition, (RDA) | TM ID# | Volume I | Volume II | Volume III |
C2 RDT&E Actions | 1100 | Table 7-2-7, 7-2-7 |
| Annex H, J, L |
C2 Protect Resourcing | TM ID# | Volume I | Volume II | Volume III |
C2 Protect Personnel Actions | 1200 | Table 7-2-3, 7-2-3 | 1.4, 5.1.1, 5.3.3, 7.3 | Annex D, F |
C2 Funding & Resourcing | 1201 | 7.2, Table 7-2-1, 7-2-1 | 7.1.1 | Annex I |
C2 Protect Funding Constraints | 1202 | 6.2, 7-2-1 | 5.3, 6.3.3, 6.3.5, 7.1.1, 7.4.5 Annex I |
|
C2 Protect Common Tool Set | TM ID# | Volume I | Volume II | Volume III |
C2 Common Tool Set | 1300 | 7-2-7a |
| 9.10, Annex F, J |
C2 Protect Central React Capability | TM ID# | Volume I | Volume II | Volume III |
Central React Organ. | 1400 | 3.4 |
| Annex F, J, K |
Red Team Operations | 1401 | 5.2, 7-2-6e |
| Annex F, J, K |
Organic Assistance/ | 1401a |
|
| Annex F, J, K |
Computer Emergency | 1401b |
|
|
|
Response Team (CERT) | 1401c | 3.4 | 6.6 |
|
Reporting Channels | 1402 | 3.6, 7-2-7a, 7-2-5c |
| 9.8, Annex G, H |
C2 Protect Risk Management Process Development | TM ID# | Volume I | Volume II | Volume III |
Vulnerabilities | 1500 |
|
| Annex F, J, L |
Enterprise Vulnerabilities | 1501 | 3.1, 4.1, 4.2, 7-2-5a | 5.1.3, 5.3.5, 4.4 | Annex F, J, L |
Life Cycle Mgt Process | 1502 | 3.2, 7-2-4e |
| 9.7, Annex F, J, L |
Sys. Security Engineering | 1503 | 3.3, 7-2-1f |
| 9.8, 9.9, Annex F, J, L |
Central React Organ. | 1504 | 3.4, 3.5 |
| Annex F, J, L |
Detection Capability | 1505 | 3.5, 5.4, 7-2-7a |
| 9.5, 9.8, Annex F, J, L |
Reporting Channels | 1506 | 3.6, 7-2-7a, 7-2-5c |
| 9.8, Annex F, J, L |
C2 Protect Army Responsibilities | TM ID# | Volume I | Volume II | Volume III |
Assistant Secretary Army for Research, Development and Acquisition (ASA (RDA)) | 1601 | Table 7-2.1, 7-2-2,7-2-3, ë7-2-4, 7-2-7, 8.1 | 7.1 | 9.8, Annex A, F, H, I, J |
Deputy Chief of Staff for Operations and Plans (ODCSOPS) | 1602 | Table 7-2-1 - 7-2-6, 8.2 | 1.5, 7.1.6, 7.2 | 9.1, 9.3, 9.9, Annex A, B, C, D, E, F, G, H, I J, K, L |
Deputy Chief of Staff for Personnel (ODCSPER) | 1603 | 8.3 | 7.3 | 9.4, Annex A, C, D, F, I |
Deputy Chief of Staff for Logistics (ODCSLOG) | 1604 | 8.4 |
| Annex A, B, C, D, E, F, H, L |
Deputy Chief of Staff for Intelligence (ODCSINT) | 1605 | Table 7-2-1 - 7-2-6, 8.5 | 1.5, 7.4 | 9.1.9.7, Annex A, B, C, D, E, F, G, H, I, J, K, L |
Director of Information Systems for Command, Control, Communications, & Computers (ODISC4) | 1606 | Table 7-2-1 - 7-2-6, 8.6 | 1.5, 7.5 | 1.0, 5.0, 9.1, Annex A, B, C, D, E, F, G, H, I, J, K, L |
Army Chief of Public Affairs | 1609 | 8.9 | 7.6 | Annex A |
Commanders of Major Army Commands (MACOMS) | 1610 | 8.12, 7.2.3c | 7.6 | Annex A, C, D, E, F, I, K |
Office of Assistant Secretary of Army for Manpower and Reserve Affairs | 1611 | 8.10 |
| Annex ,l D, F |
PEOs/PMs | 1612 | 8.11, 7-2-1f | 7.9 | Annex F, I |
Field Operating Agencies, and their Subordinated Elements | 1613 | 8.13 | 7.7 | Annex A, C, D, E, F, I, K |
Chief National Guard Bureau (NGB) | 1614 | 8.14 |
| 4.0, Annex B, D |
Commander, US Army Information Systems Command | 1615 | 8.15, 7-2-3b |
| Annex F, K |
Commander US Army Training and Doctrine Command (CG, USATRADOC) | 1616 | 7-2-2b, f, g, 7-2-3b, c, 8.16 | 6.1.2, 7.8 | 9.2, 9.4, 9.5, 9.6, 9.9, Annex B, C, E, F, I, K, L |
Commander, US Army Materiel Command (CG, USAAMC) | 1617 | 8.17 |
| Annex F, H, J, L |
Commander, US Army Intelligence and Security Command (USAINSCOM) | 1618 | 8.18 |
| Annex K, L |
Commander, US Army Operational Test and Evaluation Command(OPTEC) | 1619 | 8.19 |
| Annex D, E, G, F, L |
Office of the Chief of Army Reserve | 1620 | 8.20 |
| Annex D |
Commanders at ALL Levels | 1621 | 8.21 |
| Annex E |
ADO | 1622 | 8.7 |
| Annex A, B, C, E, F, G, H, J, K |
Proponency and a brief explanation for each of the tasks has been identified in Section 9. Supporting action plans (Annexes A through L) identify specific goals, objectives and sub-tasks. The consolidation of individual action plans for each task will result in the C2 Protect Action Plan.
The C2 Protect GOSC will remain in control, guiding the responsible agencies to complete all tasks. Reviews by the C2 Protect GOSC will serve to maintain a standard structure for all C2 Protect activities, ensure that all issues are identified and resolved quickly at the lowest possible level. C2 Protect GOSC oversight is key to guaranteeing that the C2 Protect IP decision process balances development risk against the pace of change.