https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN44562-PPM_CIO-085-000-WEB-1.pdf
DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
CSO-SEC-SC-085
SAIS-CS (25-1rrrr) 31 July 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Authorizing Officials for Operational and Tactical Enclaves
1. References.
a. DoDI 8510.01 (Risk Management Framework for DoD Systems).
b. AR 25-2 (Army Cybersecurity).
c. DA Pam 25-2-14 (Risk Management Framework for Army Information
Technology).
d. NIST SP 800-37 (Risk Management Framework for Information Systems and
Organizations).
e. ATP 6-02.71 (Techniques for Department of Defense Information Network
Operations).
f. JP1, Volume 1 (Joint Warfighting).
2. Purpose. To further delegate System Authorizing Official (SAO) appointments to
Corps Commanders to support the mission, afford operations to continue through the
cyber terrain environment, and increase combat readiness. This will bridge the gap
between cybersecurity authorities and commanders, ensuring decision to connect
enables the warfighter.
3. Definitions.
a. Operational Enclaves. Networks or systems used to support large-scale
missions or campaigns, often at higher echelons like Theater Army or Corps levels.
b. Tactical Enclaves. Networks or systems used to support deployed forces in
specific, localized missions.
SAIS-CS (25-1rrrr)
SUBJECT: Authorizing Officials for the Operational and Tactical Enclaves
4. Roles and Responsibilities.
a. SAO.
(1) Responsible for ensuring all units, both organic and assigned, remain in
compliance with all cybersecurity policies, practices, and processes.
(2) Is not authorized to accept risk outside their respective enclave-controlled
interface (firewall) and will not delegate authorization decisions.
(3) Is required to maintain the mandatory training certificates and attend CIO-led
information sessions.
b. Authorizing Official Designated Representative (AODR).
(1) Must be appointed in writing by the AO.
(2) M ,
both organic and assigned.
(3) Must complete training consistent with AO training and certification
requirements.
(4) Coordinate and conduct day-to-day activities associated with the
cybersecurity process and oversight of system compliance on behalf of the AO.
(5) Serves as the principal advisor to the AO pertaining to risk to mission and
risk to the network.
(6) Has no authority to make risk-based decisions (e.g., Authorization to Operate
(ATO)).
c. Network Authorizing Officials (NAOs) play a critical role in providing guidance
to Corps Commanders as they operate across diverse geographical locations as
outlined in paragraph six (6). Their responsibilities are particularly focused on network
cybersecurity, ensuring the swift issuance of Authority to Connect (ATC) approvals to
enhance operational efficiency and effectively support the warfighter.
d. All subordinate Divisions to the Corps will create a core enterprise Mission
Assurance Support Service (eMASS) record based on hardware and software, to
include fielded Program Executive Officer (PEO) systems.
2
SAIS-CS (25-1rrrr)
SUBJECT: Authorizing Officials for the Operational and Tactical Enclaves
5. Policy. Corps AOs are responsible to ensure the proper processes and required
cybersecurity practices are in place within their respective enclave s-controlled interface
(firewall). This includes ensuring all controls and documents are processed, approved,
and submitted in compliance with relevant Army regulations and directives.
a. During CONUS exercises, the Corp Commander will remain the AO for their
enclave, maintaining alignment with the Army CIO, ARCYBER, and CYBERCOM.
b. During OCONUS exercises and Army operations, the AO will remain the Corps
Commander with alignment to the Army Service Component Command (ASCC) within
that geographical location (e.g., Pacific is the United States Army Pacific Command
(USARPAC) Commander).
c. During joint operations, the AO will remain at the Corp level with alignment to the
ASCC or Geographic Combatant Command (GCC) as appropriate.
6. Use Case Scenarios.
a. CONUS Exercise. Tactical SIPR (TACSIPR) encompasses all IT assets
deployed within each organization's on-premises classified environment for mission-
critical activities. XVIII Airborne Corps (ABC) G-6 serves as the AO for the XVIII ABC
IL5 and IL6 Cloud Environment and the XVIII ABC on premises TACSIPR. This will
include the Corps, Divisions, and Corps separates networks. Corps maintain their own
domain and network that exceeds issued Tactical Server Infrastructure (TSI) server
stacks extended to meet reach back to Home Station Mission Command (HSMC)
services.
b. OCONUS Exercise (Army Service Component Command (ASCC)). USARPAC
establishes a single Interconnection Service Agreement (ISA) (additional ISAs for
special equipment or experiments such as a previous Identity, Credential, and Access
Management (ICAM) experiment); units can arrive into Pacific Theater, and anywhere
we put a Global Agile Integrated Transport Point of Presence (GAIT PoP), with minor
configurations, can connect.
c. Operation (United States Army Europe Africa (USAREUR-AF)). Units must
complete firewall exemptions and collaborate on core services integration. This level of
effort is required regardless of a unit having an organic AO or boundary. Tactical units
route through the Regional Hub Node (RHN) via commercial, GAIT, Multiprotocol Label
Switching (MPLS), or NIPR transport. *Note: The Mission Partner Network (MPN) is
actively consolidating tactical domains into a single structure with unified Fully Qualified
Domain Name (FQDN) under a Mission Command-Led C2 construct. This enhances
interoperability and enables more streamlined cross-unit access to shared services.
3
SAIS-CS (25-1rrrr)
SUBJECT: Authorizing Officials for the Operational and Tactical Enclaves
d. Joint Task Force (JTF). in Pacific Theater do not have AOs in their
formations. INDOPACOM provides the Mission Partner Environment (MPE) and RMF
support to JTF Commanders. Units attached to JTFs do one of two things, either (1) fall
in on the existing network (in real-world ops, Army personnel are using Windows Data
at Rest (WINDARS) in one place and Modular Communication Network (MCNET) in
another), (2) connect their equipment directly (which falls into the pre-environment,
requiring an ATC for every piece of equipment).
7. Effective Date. This memorandum is effective immediately until rescinded.
8. Points of contact.
a. CIO Policy Inbox: usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil.
b. Ms. Suzanne Rodriguez at suzanne.p.rodriguez.civ@army.mil.
c. CISO Team: usarmy.pentagon.hqda-cio-g-6.mbx.rmf-team@army.mil.
LEONEL T. GARCIGA
Chief Information Officer
DISTRIBUTION:
Principal Officials of Headquarters, Department of the Army
Commander
U.S. Army Forces Command
U.S. Army Training and Doctrine Command
U.S. Army Materiel Command
U.S. Army Futures Command
U.S. Army Pacific
U.S. Army Europe and Africa
U.S. Army Central
U.S. Army North
U.S. Army South
U.S. Army Special Operations Command
Military Surface Deployment and Distribution Command
U.S. Army Space and Missile Defense Command/Army Strategic Command
U.S. Army Cyber Command
U.S. Army Medical Command
U.S. Army Intelligence and Security Command
U.S. Army Corps of Engineers
(CONT)
4
SAIS-CS (25-1rrrr)
SUBJECT: Authorizing Officials for the Operational and Tactical Enclaves
DISTRIBUTION: (CONT)
U.S. Army Military District of Washington
U.S. Army Test and Evaluation Command
U.S. Army Human Resources Command
U.S. Army Corrections Command
U.S. Army Recruiting Command
Superintendent, U.S. Military Academy
Commandant, U.S. Army War College
Director, U.S. Army Civilian Human Resources Agency
Executive Director, Military Postal Service Agency
Director, U.S. Army Criminal Investigation Division
Director, Civilian Protection Center of Excellence
Director, U.S. Army Joint Counter-Small Unmanned Aircraft Systems Office
Superintendent, Arlington National Cemetery
Director, U.S. Army Acquisition Support Center
CF:
Principal Cyber Advisor
Director, Office of Analytics Integration
Commander, Eighth Army
5