S1NET Message Summary - 1/31/2025

1. CHANGE IN APPROVAL AUTHORITY FOR ACCEPTANCE AND WEAR OF SOME FOREIGN BADGES AND DECORATIONS. From HRC Awards and Decorations Branch: Chapter 9, AR 600-8-22 provides guidance on foreign and international decorations and awards to U.S. Army employees. The current guidance in para 9-26 and 9-27 requires that Commanders or DCGs serving in the rank of BG/O – 7 or above and COL-level commanders who exercise general court-martial convening authority are delegated authority to approve the acceptance, retention, and permanent wear of foreign badges and decorations that are listed in Charts 1 and 2 posted to the HRC Awards and Decorations website. An update to AR 600-8-22 will be published in the next few months that changes the approval authority to an O-5 Commander.  Per the guidance posted on the HRC Awards and Decorations web page, units may start using this guidance now.   https://www.milsuite.mil/book/docs/DOC-1357198

 

 

2. REGULAR ARMY NONCOMMISSIONED OFFICER SLC/MLC SCHEDULING (OML DATA) AS OF JANUARY 2025. To provide transparency and manage expectations, Military Schools Branch releases monthly statistics of Soldiers scheduled for SLC/MLC by MOS and the Evaluation Board Order of Merit List (OML). These numbers reflect the last OML number that has been used to schedule a Soldier in April 2025 by MOS. https://www.milsuite.mil/book/docs/DOC-1357085

 

 

3. US ARMY TRANSITION ASSISTANCE PROGRAM (TAP) TOWNHALL BRIEFING RECORDING. The inaugural Transition Assistance Program (TAP) Townhall took place on January 30, 2025. During the first townhall presentation, we discussed the "TAP 101" briefing. This briefing covered several important topics, including the Soldier TAP timeline, Command Team responsibilities, the TAP system of record, Career Readiness Standards (CRS) and their timeliness, the Career Skills Program (CSP), and the DoD SkillBridge (SB) Program. Briefing slides, and links to the video, are available at the following link on S1NET.  https://www.milsuite.mil/book/message/1085189

 

 

4. IPPS-A QUESTIONS.

 

 

     a. WHAT ARE THE IMPACTS OF DIVERTING AN ASSIGNMENT? SPECIFICALLY IN RELATION TO PAY/ENTITLEMENTS. WHAT ADDITIONAL CHANGES NEED TO BE MADE/UPDATED AFTER A DIVERSION TO AVOID ERRORS/ISSUES IN IPPS-A? I am at the BDE level in an OCONUS unit. We have multiple instances of Soldiers and Officers, usually from AIT and BOLC have PCS orders bringing them to one of our BNs, however, when they arrive that vacancy has either already been filled or another vacancy has taken priority. Our current guidance is to arrive the SMs to their approved assignment and then create a PCA to the UIC and position they will actually be serving in to avoid issues. The issue is it creates a 1-day assignment on their STP that is not necessary and ultimately results in SMs wanting S1s to try and remove it or combined with another assignment for a board later down the road. What is the guidance/SOPs/best practices to divert SMs to correct assignments prior to their arrival while maintaining their entitlements and without causing additional issues in the system? https://www.milsuite.mil/book/message/1084237

 

 

     b. AUTHORIZING SM ON TOD FOR TOUR WHILE SM IS IN THE PROCESS OF PENDING IRR TRANSFER REQUEST APPROVAL ON IPPS-A. Due to TPU distribution, SM is needing to transfer to IRR in order to continue doing ADOS support SOCPAC/INDOPACOM unit? If SM had already submitted IRR Packet via IPPS-A pending on approval and is needing her to report asap. Are there ways to assist the SM getting her order first while waiting for the IRR packet to get approved so she can head to CRC and report to duty? https://www.milsuite.mil/book/thread/295053

 

 

5. Recently published Army Directives and All Army Activity (ALARACT) messages. None. New ALARACTs and ADs are also posted on APD at the following link. armypubs.army.mil/default.aspx

 

 

     a. ALARACT 008/2025, ANNOUNCEMENT OF IRIDIUM DEACTIVATION, DTG: R 301646Z JAN 25. Effective 13 January 2025, Headquarters, Department of the Army, Deputy Chief of Staff, G–6, and Army Network Enterprise Technology Command (NETCOM) will commence deactivating all Army Enhanced Mobile Satellite Services (EMSS) iridium devices, including iridium satellite phones (Subscriber Identity Module (SIM)), Short Burst Data (SBD) devices, and Distributed Tactical Communication Systems (DTCS) that have been inactive for 3 months or more as of the publication date of this ALARACT. https://www.milsuite.mil/book/docs/DOC-1357636

 

 

6. Recently published Military Personnel (MILPER) messages and Military Pay Messages.

 

 

     a. MILPER MESSAGE 25-037, 2025 LTC KAREN WAGNER LEADERSHIP AWARD (KWLA), ISSUED: [30 JAN 25]. This message supersedes MILPER Message 25-003 (2025 LTC Karen Wagner Leadership Award (KWLA)), 6 January 2025. The purpose of the KWLA is to recognize One Regular Army, One Army Reserve, One Army National Guard Officer, and two DA Civilians (1 Military HR & 1 Civilian HR) who have demonstrated principles for which LTC Wagner stood for; leadership, technical competence, professionalism, and customer service. All Regular Army, Army Reserve, and Army National Guard Organizations are encouraged to submit their scanned nomination packets NLT 7 March 2025. https://www.milsuite.mil/book/docs/DOC-1357413

 

 

     b. MILPER MESSAGE 25-038, FY25 U.S. ARMY RESERVE ACTIVE GUARD RESERVE FUNCTIONAL AREA VOLUNTARY TRANSFER INCENTIVE PROGRAM (VTIP) PANEL, ISSUED: [30 JAN 25]. This message provides eligibility criteria and guidance for subject FY25 USAR AGR FA VTIP Panel. USAR AGR officers who meet eligibility requirements can submit an IPPS-A Personnel Action Request (PAR) to request transfer into a FA. This VTIP Panel aligns with the USAR AGR Army Talent Alignment Process (ATAP) for the 26-01 and 26-02 movement cycles. https://www.milsuite.mil/book/docs/DOC-1357434

 

 

     c. MILPER MESSAGE 25-039, FY 2025 ARMY SOCIAL WORK INTERNSHIP PROGRAM (SWIP) APPLICATION PROCEDURES, ISSUED: [31 JAN 25]. This MILPER revokes and replaces MILPER 24-352. This message solicits applications for the FY 2025 Army Social Work Internship Program (SWIP). HQ, US Army Recruiting Command (USAREC) will convene a competitive accession board on 9 June 2025 to consider qualified applicants for selection and accession as Army Social Workers. https://www.milsuite.mil/book/docs/DOC-1357564

 

 

     d. MILPER MESSAGE 25-040, UNITED STATES ARMY WARRANT OFFICER SELECTION BOARD RESULTS JANUARY 2025, ISSUED: [31 JAN 25]. https://www.milsuite.mil/book/docs/DOC-1357619

 

 

     e. MILPER MESSAGE 25-041, UNITED STATES ARMY RESERVE (USAR) WARRANT OFFICER SELECTION BOARD RESULTS, JANUARY 2025, ISSUED: [31 JAN 25]. https://www.milsuite.mil/book/docs/DOC-1357620

 

 

     f. MILPER MESSAGE 25-042, FISCAL YEAR 2025 (FY25) RESERVE COMPONENT (RC), LIEUTENANT COLONEL (LTC), JUDGE ADVOCATE GENERAL’S CORPS (JAGC) ARMY RESERVE ACTIVE GUARD RESERVE (AR AGR) AND ARMY RESERVE NON-ACTIVE GUARD RESERVE (AR NON-AGR), COMPETITIVE CATEGORIES, PROMOTION SELECTION BOARD (PSB) ZONES OF CONSIDERATION, ISSUED: [31 JAN 25]. Promotion selection boards will convene on

or about 24 Jun 25 to consider eligible Judge Advocate Generals Corps (JAGC) Majors

(MAJ) on the Reserve Active Status List (RASL) for promotion to Lieutenant Colonel

(LTC). The boards will recess on or about 2 Jul 25. https://www.milsuite.mil/book/docs/DOC-1357641

 

 

     g. MILPER Message 25-043, Personnel Policy Guidance in Support of Army Wide Preparedness and Response to Permanent Change of Station Summer Surge and Transportation Constraints, Issued: [31 Jan 25]. Due to transportation industry capacity constraints during fiscal year 2025 (FY25) Summer Permanent Change of Station (PCS) season, local commanders in the rank/grade of (COL/O6) or above may approve requests for Soldiers to have report dates to their new duty station adjusted up to 30 days early and up to 30 days later than the published report date on orders. Upon approval, orders must be amended. Requests for more than 30 days, refer to paragraph 4, this message. Requests for deferment or early arrival, for approval at the local command level, will be submitted as soon as the determination is made that transportation capacity will impact movement. In addition, local command must inform the Military Personnel Division for any adjustment to the assignment report dates. https://www.milsuite.mil/book/docs/DOC-1357642

 

 

7. S1NET MEMBER REQUESTS.

 

 

     a. UNUSED LEAVE AFTER MOB.  I was advised I had unused leave after demobilizing. I remobilized but the leave did not transfer. How do you recover the leave? https://www.milsuite.mil/book/message/1084381#1084381

 

 

     b. DOES A BA FLAG STAY IN PLACE AFTER THE SEPARATION AUTHORITY SUSPENDS THE EXECUTION OF APPROVED SEPARATION? https://www.milsuite.mil/book/message/1084679

 

 

8. USARPAC INDIVIDUAL AUGMENTATION (IA) REQUIREMENTS, OPENINGS IN DJIBOUTI, GUAM, SOMALIA, AND QATAR.  https://www.milsuite.mil/book/docs/DOC-1320402

 

 

9. ARNG/USAR POSITIONS/JOBS AVAILABLE. S1NET members have posted the following RC position/job vacancy information. For a listing of all USAR primary vacancies (updated weekly) visit milsuite.mil/book/docs/DOC-375787. Units/commands who wish to post vacancies on S1NET may do so by following the instructions posted on the front page of the Job Announcements topic at the following link. Those posts which are in the correct location and which are posted in accordance with the instructions provided will be included in a future S1NET Message Summary. milsuite.mil/book/community/spaces/apf/s1net/jobannouncementsmobvacancies

 

 

     a. TPU OFFICER POSITION VACANCY ANNOUNCEMENT, CHIEF OF STAFF, 95TH TRAINING DIVISION (INITIAL ENTRY TRAINING), FORT SILL, OK. https://www.milsuite.mil/book/docs/DOC-1357050

 

 

     b. 446TH TC BN, TPU, MULTIPLE VACANCIES, KAISERSLAUTERN, GERMANY. https://www.milsuite.mil/book/docs/DOC-1357091

 

 

     c. 3-313TH LOGISTIC SUPPORT BATTALION VACANCIES, JBMDL, NJ. https://www.milsuite.mil/book/docs/DOC-1335451

 

 

     d. DEPUTY ASSISTANT SECRETARY OF DEFENSE FOR MATERIEL READINESS, PENTAGON, DC-  4 ADOS-RC POSITIONS,O1A TPU LTC/O5 AND MAJ/O4. https://www.milsuite.mil/book/docs/DOC-1357388

 

 

     e. 1395TH DEPLOYMENT & DISTRIBUTION SUPPORT BATTALION, TPU O-3, 42B/CW2, 420A/CW3, 882A VACANCIES, JBLM, WA. https://www.milsuite.mil/book/docs/DOC-1357439

 

 

     f. T32 AGR ANNOUNCEMENT 25-016 SENIOR MASTER TRAINER, MSG/79T, RECRUITING AND RETENTION BATTALION, AUGUSTA, ME. https://www.milsuite.mil/book/docs/DOC-1357503

 

 

     g. USACE DEPLOYMENT OPPORTUNITY (ALL COMPONENTS) - SENIOR ENLISTED ADVISOR, 12A/X/Z E9, CAMP ARIFJAN, KUWAIT.  https://www.milsuite.mil/book/docs/DOC-1357630

Read More

PPM CIO-040 ARMY INFORMATION SYSTEMS SOFTWARE ASSURANCE POLICY

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN42924-PPM_CIO-040-000-WEB-1.pdf

DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
CS-SEC-IA-040
SAIS-CS (25-1rrrr) 31 January 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Army Information Systems Software Assurance Policy
1. References. See enclosure.
2. Purpose. To provide amplifying guidance regarding Army information systems (IS)
software assurance (SwA) policy in support of Army and DoD development, security,
and operations (DevSecOps) initiatives and the DoD Risk Management Framework
(RMF) process.
3. Applicability.
a. Per Army Regulation (AR) 25-2, the Army Chief Information Officer (CIO), on
behalf of the Secretary of the Army, establishes policy, resourcing, and oversight of the
Army Cybersecurity Program. This policy memorandum meets provisions outlined in
AR 25-2, para 1-8, where the Army CIO, if applicable, will issue policy memoranda to
amplify guidance for the policies in AR 25-2.
b. This policy applies to all Headquarters Department of the Army (HQDA)
elements, Army Commands (ACOM), Army Service Component Commands (ASCC),
Direct Reporting Units (DRU), and the Reserve Component (Army National Guard/Army
National Guard of the United States, and the U.S. Army Reserve) regardless of the service
status.
c. This guidance applies to all development teams, contractors, integrators, and
third-party vendors involved in software development activities at all stages of the
SDLC.
4. Software assurance.
a. SwA is the level of confidence that software is free from unmitigated
vulnerabilities, either intentionally designed into the software or accidentally inserted at
any time during its lifecycle, and that software functions in the intended manner. All
Army systems are required to have SwA requirements validated against the latest
National Institute of Standards and Technology Special Publication (NIST SP) 800-53
security control requirements and reported through the RMF process when obtaining
authorizations under the Assess & Authorize (A&A) or assess only process.
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
b. Organizations must perform SwA to the greatest extent practicable on all
software and source code.
c. Software and the code sourced to build it are divided into the following
categories:
(1) Commercial off-the-shelf (COTS). Software that is available for sale, lease, or
license to the general public without custom development or modification. COTS is
further subdivided into the following two categories: open-source software and closed-
source software. These software components, particularly open-source, are often found
in government off-the-shelf (GOTS) and other than commercial software.
(2) GOTS. Software that is developed by the technical staff of a U.S.
Government organization for use by the Government. GOTS may be developed by an
external entity with specification from a government organization to meet a specific
Government purpose and can normally be shared among Federal agencies without
additional cost. GOTS products are not commercially available to the general public.
(3) Other than commercial. Software that is created for government purpose, not
available to the general public, and with restricted rights to the government.
Note: Each of these categories can be modified based on the amount of code sourced
from each software product category and are not all encompassing.
5. Policy. All information system owners will perform SwA, using a certified
DevSecOps platform, in accordance with policy outlined in this memo and applicable
Army policy. This memo updates, amplifies, and as applicable, supersedes guidance in
AR 25-2, Department of the Army Pamphlet (DA Pam) 25-2-5, and Deputy Chief of Staff
(DCS), G-6 SwA tactics, techniques, and procedures (TTP).
6. Roles and responsibilities.
a. The Army Chief Information Officer will publish and maintain SwA policies for
Army IS.
b. The Army Chief Information Security Officer (CISO) will collaborate with the DCS,
G-6 to develop procedures, guidelines, and baseline requirements acceptable for SwA.
c. The DCS, G-6 will:
(1) Advise the Army CIO in developing SwA policy.
2
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
(2) In conjunction with the Army CISO, develop procedures, guidelines, and
baseline requirements for SwA.
(3) Update and maintain applicable SwA procedures, specifically, DA Pam 25-2-5
and the DCS, G-6 SwA TTP.
(4) Develop, organize, and implement an Army approved product list (APL).
(5) Integrate industry standard cyber supply chain risk management practices
outlined in NIST SP 800-161 Rev. 1 and Executive Order (EO) 14028 into Army SwA
procedures.
d. Authorizing officials will:
(1) Consider SwA risks into the overall authorization determination.
(2) Approve baseline requirements for tailoring security controls during SwA.
(3) After the initial assessment, determine if information system owners (ISOs)
are sufficiently trained and have the appropriate resources to conduct continuous SwA
assessments internally. AO approval is documented in a memorandum for record and
uploaded into Enterprise Mission Assurance Support Service (eMASS).
e. Information system security managers will:
(1) Develop and maintain the baseline requirements for tailoring security controls
during SwA. These requirements will vary from program to program based on the
specific requirements to satisfy each program’s SwA requirements, however, all controls
referenced by the Application Security and Development security technical
implementation guide must be included as required security controls.
(2) Work with the ISO and manage the SwA process, providing input to the AO to
inform the overall authorization determination.
f. Information system owners will:
(1) Create/update the security plan as part of the system’s RMF package.
(2) Use existing third-party assessment results to the greatest extent possible to
prevent unnecessary reassessment of software. Existing third-party assessments
should include test plan information in adequate detail, allowing the ISO to confirm
whether the assessment addresses the applicable portions of the security plan and
meets the program’s baseline requirements for tailoring security controls.
3
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
(3) Manage SwA risk throughout the life cycle of the software.
(4) Ensure evidence is included in the applicable eMASS record showing SwA
has been performed in accordance with the security plan.
(5) Create a continuous assessment strategy to address timely remediation of
known and emerging SwA requirements. This must be included in the security plan.
(6) Submit justification via an eMASS POA&M if SwA assessment cannot be
performed for the RMF authorization. Exception requests must include justification
(including cost and mission impacts) and will be adjudicated based upon cybersecurity
risk to the IS and the Army enterprise.
g. The control assessor will conduct a comprehensive independent assessment of
SwA management activities employed within or inherited by an IT system. This includes
a review of weaknesses or deficiencies discovered in the IS and recommended
corrective actions to address identified vulnerabilities.
7. Guidance.
a. This memo aligns with the adoption of modern software development and
acquisition practices, enabling the transition from the traditional authority to operate
(ATO) process to continuous authority to operate (cATO). For software development
see reference 1.j and associated Army policy on the use of certified DevSecOps
platforms and pipelines as well as DevSecOps configuration management.
b. Security plan.
(1) The security plan will include the results of the SwA assessment, to include
the vulnerabilities and weaknesses found, the controls implemented to mitigate the
associated risk, and the continuous assessment strategy.
(2) Additional guidance for the security plan, incorporating SwA results into the
security plan, and the security plan approval process can be found in NIST SP 800-18,
on the DoD RMFKS portal (https://rmfks.osd.mil/rmf/Pages/default.aspx), and at the
following links on the Army RMF portal:
(a) https://armyeitaas.sharepoint-mil.us/sites/NETCOM-CSD-
RMF/SitePages/SSPInformation.aspx
(b) https://armyeitaas.sharepoint-mil.us/sites/NETCOM-CSD-
RMF/SitePages/SPApproval.aspx
4
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
c. Software assurance assessments.
(1) An initial SwA assessment is required for software not already present in the
RMF authorization package. A third party must conduct this assessment, and
organizations are encouraged to leverage existing assessments to reduce the time and
cost associated with conducting a new SwA assessment.
(2) Existing assessments provided by the following external agencies’ approved
product lists are granted reciprocity:
(a) Defense Information Systems Agency
(b) National Geospatial-Intelligence Agency
(c) National Reconnaissance Office
(d) National Security Agency
(e) Additional organizations as approved by the Army CIO
(3) Army organizations may also use existing third-party assessments from
organizations other than the ones referenced above, provided they have a reciprocity
agreement with the organization.
(4) The Army will use eMASS to share security authorization packages and risk
assessment data with AOs from other organizations.
(5) Third-party service providers can be found on the Joint Federated Assurance
Center portal (https://jfac.dso.mil).
(6) Continuous SwA assessments must be conducted by an internal team and in
accordance with DA Pam 25-2-5 and the DCS, G-6 SwA TTP.
(7) Assessments will be conducted to support a threat-focused baseline control
set, with the findings and mitigation strategy for each vulnerability/weakness
documented in the security plan.
d. Software assurance controls.
(1) All systems should have the following activities included in their security
control baseline, as applicable based on the type of software being used, data rights,
and threat environment-
5
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
(a) Static code analysis, RMF control enhancement: SA-11(1)
(b) Dynamic code analysis, RMF control enhancement: SA-11(8)
(c) Flaw remediation, RMF control enhancement: SI-2
(2) ISOs will tailor the security controls for the SwA assessment and document in
the security plan.
(3) ISOs will plan, develop, and implement additional controls in accordance with
the organization’s security control tailoring requirements.
e. Supply chain risk assessment. The ISO is responsible for the supply chain risk
assessment of the product, in accordance with NIST SP 800-161 Rev. 1 and EO 14028.
The assessment must also be included in the security plan. The assessment may be
conducted by a third-party or an internal team and must include the following items tied
to their corresponding control enhancements outlined in NIST SP 800-53-
(1) A review of the software bill of materials (control enhancement SR-12(10)).
(2) A review of the supply chain characteristics and cybersecurity risk factors
associated with the vendor in accordance with NIST SP 800-161 Rev. 1, Table 3-2.
(3) A review of the vendor’s usage of software security labels or data sheets
(control enhancement SR-12(9)).
(4) An analysis of the vendor’s usage of open-source data (control enhancement
SR-6).
(5) An analysis of the ties between the vendor and any foreign government
(control enhancement SA-12(8), SA-12(9)).
(6) A review of commercially available third-party assessments and security
ratings of the vendor (control enhancement SA-12(5), SA-12(8)).
f. Continuous monitoring.
(1) Automated SwA tools must reside on a certified DSOP and will be leveraged
to ensure software meets a minimum threshold of quality and does not introduce
weaknesses or vulnerabilities into the system.
6
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
(2) The development of a continuous assessment strategy and use of automated
SwA tools must be combined with active cyber defense for the implementation of
continuous monitoring (ConMon). ConMon requirements are detailed in reference 1j.
8. Exception requests. Requests for exceptions to the requirements in this policy
should be documented and submitted to the CIO. Exception requests must include
justification (including cost and mission impacts). Each request will be adjudicated
based upon all factors including cybersecurity risk.
9. This policy will be reviewed annually, or as required, and updated as appropriate.
10. Points of contact.
a. CIO Policy Inbox: usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil.
b. SAIS-CS Director: BG Urbi N. Lewis, urbi.n.lewis.mil@army.mil.
c. SAIS-CSP policy team: usarmy.pentagon.hqda-cio.mbx.sais-csp@army.mil.
Encl 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
(CONT)
7
SAIS-CS (25-1rrrr)
SUBJECT: Army Information Systems Software Assurance Policy
DISTRIBUTION: (CONT)
U.S. Army Intelligence and Security Command
U.S. Army Corps of Engineers
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 of Enterprise Management
Director, Office of Analytics Integration
Commander, Eighth Army
8
REFERENCES
a. AR 25-2 (Army Cybersecurity).
b. DA Pam 25-2-5 (Software Assurance).
c. DoD CIO memorandum (Software Development and Open Source Software),
24 January 2022.
d. HQDA DCS, G-6 (Software Assurance (SwA) Tactics, Techniques, and Procedures
(TTP)), Version 1.0, 22 March 2022.
e. Executive Order 14028 (Improving the Nation’s Cybersecurity), 12 May 2021.
f. Defense Information Systems Agency (DISA) Application Security and Development
(ASD) Security Technical Implementation Guide (STIG), 24 July 2024.
g. NIST SP 800-18 (Guide for Developing Security Plans for Information Technology
Systems), 24 February 2006.
h. NIST SP 800-53 Rev. 4 (Security and Privacy Controls for Information Systems and
Organizations), 22 January 2015.
i. NIST SP 800-161 Rev. 1 (Cybersecurity Supply Chain Risk Management Practices
for Systems and Organizations), 05 May 2022.
j. Army CIO memorandum (Army Transition to Continuous Authority to Operate).
k. AD 2024-02 (Enabling Modern Software Development and Acquisition Practices).
l. Army CIO memorandum (Information Technology Reciprocity Acceptance
Guidance), 3 November 2023.
m. Army CIO memorandum (Army Software Modernization Directive—Initiative 8—
Implementation Plan).
Enclosure 

Read More

PPM CIO-063 ARMY CROSS DOMAIN SOLUTION AS A SERVICE POLICY

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN42947-PPM_CIO-063-000-WEB-1.pdf

DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
CS-GOV-SV-063
SAIS-CS (25-1rrrr) 31 January 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Army Cross Domain Solution as a Service Policy
1. Purpose. Provide policy for Armywide Cross Domain Solution as a Service
(CDSaaS) utilization.
2. Definitions.
a. Cross Domain Solution (CDS): An integrated information assurance system
composed of specialized software or hardware that provides a controlled interface to
manually or automatically enable and/or restrict the access or transfer of information
between two or more security domains based on a predetermined security policy.
b. CDSaaS: A cloud computing-based solution that commercial cloud service
providers offer as a service to government tenant organizations enabling the transfer of
information across two or more different classification domains. This transfer can be
offered from High-to-Low, Low-to-High, or in any combination required to meet mission
needs.
3. Applicability.
a. This policy governs all non-intelligence security domains and applies to
Headquarters Department of the Army (HQDA) elements, Army Commands, Army
Service Component Commands, Direct Reporting Units, and Army National Guard and
Reserve components.
b. This policy applies to all Army usage, processes, and management needs for
CDSaaS services.
c. This policy is not applicable to the Joint Worldwide Intelligence Communications
System for TOP SECRET–sensitive compartmented information or special access
program systems.
d. This is not applicable to operations of on-premises, tactical or non-cARMY cloud
based CDS, to include any account outside of the Enterprise Cloud Management
Agency (ECMA) or the Cloud Governance Committee (CGC) approval.
SAIS-CS (25-1rrrr)
SUBJECT: Army Cross Domain Solution as a Service Policy
4. Background.
a. The Army has an operational requirement to enable warfighting, mission and
enterprise capabilities, and rapid capability development for data to move across
network and platform security domains. The current infrastructure continues to be
bifurcated and not standardized. This increases risk to Department of Defense
Information Network—Army (DoDIN-A) operations and mission success. Existing
processes have also weakened the Army’s ability to quickly approve, deliver and
operationalize enterprise level CDS. The lack of capable CDS services to support these
critical mission areas has a strategic effect on the ability for the Army to conduct
missions at the scope and scale necessary to meet Army Senior Leader objectives.
b. Commercial multi-mode CDSaaS within the Govcloud Impact Level (IL) 2, IL4,
IL5 and IL6 are currently available. These offerings provide the Army with the
opportunity to quickly streamline safe and secure Raise the Bar (RTB) compliant and
mission specific CDS services at-scale across the Army mission portfolio. To take
advantage of these offerings, the Army CIO requires the service to strictly follow this
policy.
5. Roles and Responsibilities.
a. The Army Chief Information Officer (CIO) serves as the approval authority for all
CDSaaS used within the US Army. With this responsibility, the CIO will manage the
oversight and resourcing of all CDSaaS and the reciprocity of cloud CDS RTB
compliance.
b. The Cloud Governance Committee (CGC) serves as the governance and
approval committee for Enterprise Cloud Management Agency (ECMA) CDSaaS tenant
requests to ensure alignment to Army portfolio management.
c. ECMA serves as the lead organization for all cloud DoDIN-A operations. Since
CDSaaS is a part of the Cloud DoDIN-A, ECMA has the sole responsibility in the Army
to develop all governance, management, maintenance, and approval for unit utilization
of CDSaaS. This includes all development, security and operations (DevSecOps)
environments. Additionally, ECMA is responsible for providing support and guidance to
the CGC. ECMA is the sole US Army organization that can utilize reciprocity for
CDSaaS operations.
d. Army Cyber Command (ARCYBER) provides cybersecurity service provider
integration and monitoring and the management of CDSaaS operations.
e. All Army organizations, units, tenants, individuals requiring CDSaaS services
must submit a request for services to ECMA. No other CDSaaS services will be
2
SAIS-CS (25-1rrrr)
SUBJECT: Army Cross Domain Solution as a Service Policy
allowed unless a waiver from the Army CIO has been granted. A waiver will only be
obtainable after all requirements have been considered with ECMA as not available.
6. Policy.
a. All Army cloud CDS requirements will be approved and managed through the
ECMA CGC. ECMA tenants will adhere and meet RTB requirements. CGC will review
requests for specific critical missions and/or operational workloads for consideration for
approval.
b. Only ECMA will provide CDSaaS services for use by US Army organizations. All
US Army organizations must use ECMA for CDSaaS services. No other enterprise CDS
solutions will be used or paid for without explicit approval from the Army CIO.
c. Depending on the CDSaaS service, requesting organizations will submit a
request for CDS services utilizing the specific templates provided by ECMA. This will
ensure a proper solution is provided to satisfy the request.
d. All alternate CDSaaS solutions are strictly prohibited and are subject to
immediate enclave and network denial of authorization to operate. All organizations
must report non-cArmy cloud based CDS to the ECMA Cybersecurity Division.
7. Points of Contact.
a. CIO Policy Inbox: usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil
b. ECMA Cloud Cybersecurity Division: Rosalynn Pittman,
rosalynn.s.pittman.civ@army.mil.
c. HQDA CIO Cybersecurity Directorate, Oversight and Compliance Division:
William Bessemer, william.g.bessemer.civ@army.mil.
LEONEL T. GARCIGA
Chief Information Officer
DISTRIBUTION:
Principal Officials of Headquarters, Department of the Army
Commander
US Army Forces Command
US Army Training and Doctrine Command
(CONT)
3
SAIS-CS (25-1rrrr)
SUBJECT: Army Cross Domain Solution as a Service Policy
DISTRIBUTION: (CONT)
US Army Materiel Command
US Army Futures Command
US Army Pacific
US Army Europe and Africa
US Army Central
US Army North
US Army South
US Army Special Operations Command
Military Surface Deployment and Distribution Command
US Army Space and Missile Defense Command/Army Strategic Command
US Army Cyber Command
US Army Medical Command
US Army Intelligence and Security Command
US Army Corps of Engineers
US Army Military District of Washington
US Army Test and Evaluation Command
US Army Human Resources Command
US Army Corrections Command
US Army Recruiting Command
Superintendent, US Military Academy
Commandant, US Army War College
Director, US Army Civilian Human Resources Agency
Executive Director, Military Postal Service Agency
Director, US Army Criminal Investigation Division
Director, Civilian Protection Center of Excellence
Director, US Army Joint Counter-Small Unmanned Aircraft Systems Office
Superintendent, Arlington National Cemetery
Director, US Army Acquisition Support Center
CF:
Principal Cyber Advisor
Director of Enterprise Management
Director, Office of Analytics Integration
Commander, Eighth Army
4 

Read More

MILPER 25-039 FY 2025 Army Social Work Internship Program (SWIP) Application Procedures

BLUF: This message solicits applications for the FY 2025 Army Social Work Internship Program (SWIP), which is referred to as “the program” throughout this message. Request command support and dissemination of this information to all commissioned officers, enlisted Soldiers, and civilians seeking to become an Active Duty Army Social Worker.

MILPER 25-039 FY25 Army Social Work Internship Program (SWIP) Application Procedures.pdf

Read More

ALARACT 008/2025, ANNOUNCEMENT OF IRIDIUM DEACTIVATION, DTG: R 301646Z JAN 25

Effective 13 January 2025, Headquarters, Department of the Army, Deputy Chief of Staff, G–6, and Army Network Enterprise Technology Command (NETCOM) will commence deactivating all Army Enhanced Mobile Satellite Services (EMSS) iridium devices, including iridium satellite phones (Subscriber Identity Module (SIM)), Short Burst Data (SBD) devices, and Distributed Tactical Communication Systems (DTCS) that have been inactive for 3 months or more as of the publication date of this ALARACT.

ALARACT 008_2025 ANNOUNCEMENT OF IRIDIUM DEACTIVATION.pdf

Read More

MILPER 25-042 Fiscal Year 2025 (FY25) Reserve Component (RC), Lieutenant Colonel (LTC), Judge Advocate General’s Corps (JAGC) Army Reserve Active Guard Reserve (AR AGR) and Army Reserve Non-Active Guard Reserve (AR Non-AGR), Competitive Categories, Promotion Selection Board (PSB) Zones of Consideration

BLUF: Mandatory Department of the Army (DA) promotion selection boards will convene on or about 24 Jun 25 to consider eligible Judge Advocate Generals Corps (JAGC) Majors (MAJ) on the Reserve Active Status List (RASL) for promotion to Lieutenant Colonel (LTC). The boards will recess on or about 2 Jul 25.

MILPER 25-042 ANCMNT FY25 RC LTC JAGC PSB.pdf

Read More

MILPER 25-041 United States Army Reserve (USAR) Warrant Officer Selection Board Results January 2025

BLUF: The below named individuals have been selected to attend Warrant Officer Candidate School (WOCS). An email notification from the United States Army Reserve Careers Group (USARCG) Warrant Officer Initial Military Training (WOIMT) office will be sent to each "Selectee" via the Enterprise Email System within 10 business days.

MILPER 25-041 United States Army Reserve (USAR) Warrant Officer Selection Board Results January 2025.pdf

Read More

MILPER 25-040 United States Army Warrant Officer Selection Board Results January 2025

BLUF: The below named individuals were selected to attend the Warrant Officer Candidate School (WOCS). Applicants should expect to receive a notification via email with their WOCS class date from the Human Resources Command (HRC) within 90 days after selection.

MILPER 25-040 United States Army Warrant Officer Selection Board Results.pdf

Read More

***REVOKED***MILPER 24-352 FY 2025 Army Social Work Internship Program (SWIP) Application Procedures

This MILPER has been revoked and is superseded by MILPER 25-039.

BLUF: Purpose: This message solicits applications for the FY 2025 Army Social Work Internship Program (SWIP), which is referred to as “the program” throughout this message. Request command support and dissemination of this information to all commissioned officers, enlisted Soldiers, and civilians seeking to become an Active Duty Army Social Worker.

Read More

***REVOKED***MILPER 25-003 2025 LTC Karen Wagner Leadership Award (KWLA)

This MILPER has been revoked and MILPER 25-037 will supersede it.

BLUF: The United States Army Medical Command will award the 2025 LTC Karen Wagner Leadership Award (KWLA) to three Army Medical Department (AMEDD) Human Resource Managers-70F and two DA Civilians

Read More

S1NET Message Summary - 1/29/2025

1. HRC G1/S1 TOUCHPOINT, THE ARMY SELECTION BOARD SYSTEM 2 (ASBS2), 6 FEB 25. Join us for the relaunch of the HRC G1/S1 Touchpoint on 6 February 2025, at 1200 ET. This interactive session is your chance to stay updated on the latest in personnel management and processes. Hear from The Adjutant General, BG Adam D. Smith, as he kicks off this exciting event with opening remarks. The topic of this session is the Army Selection Board System 2 (ASBS2). https://www.milsuite.mil/book/thread/295075

 

 

2. WARRANT OFFICER PROMOTION SELECTION BOARD PROCESS TOWNHALL/LPD *VIDEO LINK AND SLIDE INSIDE.* On 28 Jan 25 the DA Secretariat held a Townhall/LPD on the Warrant Officer Selection Board process. Slides from the brief and a link to the video are available at the following link on S1NET.  https://www.milsuite.mil/book/message/1084360 

 

 

3. TAP TALK - EPISODE 14 (12 FEB 25). The US Army Transition Assistance Program (TAP) will broadcast episode 14 of the TAP Talk podcast on 12 February from 1000 to 1100 (EST). This episode will focus on the Career Skills Program (CSP). The CSP helps Soldiers obtain industry-recognized credentials by facilitating apprenticeships, on-the-job training, internships, and job shadowing. This program enables Soldiers to learn job responsibilities, acquire new skills, and understand industry-specific practices. https://www.milsuite.mil/book/docs/DOC-1356713

 

 

4. iPERMS TOWN HALL AND LPD: PERSONNEL RECORDS REVIEW SESSION II. Join us for training and a live demo!  Who: S1/HR Professionals; When: February 20, 2025; Time: 1300-1400 (ET). https://www.milsuite.mil/book/message/1084820

 

 

5. RESERVE PAY DIGEST, JANUARY 2025 (ISSUE 2). USARC G-8, Pay Management Division (PMD) FY25 Quarter 1 Reserve Pay Digest. https://www.milsuite.mil/book/docs/DOC-1356721

 

 

6. IPPS-A ITEMS.

 

 

     a. IPPS-A KNOWN ISSUES: 15 JAN 2025. Attached at the following link are updated details on Known Issues, as of 15 Jan 2025. https://www.milsuite.mil/book/docs/DOC-1356738

 

 

7. Recently published Military Personnel (MILPER) messages and Military Pay Messages.

 

 

     a. MILPER MESSAGE 25-036, FISCAL YEAR 2025 (FY25), ACTIVE COMPONENT (AC), CAPTAIN (CPT), ARMY NURSE CORPS (AN), MEDICAL SERVICE CORPS (MS), AND ARMY MEDICAL SPECIALIST CORPS (SP), FULLY QUALIFIED CERTIFICATION (FQC), ZONES OF CONSIDERATION, ISSUED: [28 JAN 25]. When the needs of the Army require, the SECARMY may recommend the promotion of all 1LTs in the promotion zone who are fully qualified for promotion to CPT using an all-qualified officer list in lieu of convening a Promotion Selection Board (PSB). Promotion Fully Qualified Certification (FQC) screening authorities will convene and begin review of the Army Military Human Resource Record (AMHRR) of eligible First Lieutenants (1LT) on the Active Duty List (ADL) for promotion to CPT, 31 Mar 25. The screening authority will recess on or about 10 Apr 25. https://www.milsuite.mil/book/docs/DOC-1356659

 

 

     b. ARMY RESERVE PAY MESSAGE 25-05, JAN 2025 UNIT PAY REPORTS. The Jan 2025 Unit Commander’s Pay Management Report (UCPMR) and the Jan 2025 Master Military Pay Account (MMPA) 2405 reports are available in RLAS for downloading. https://www.milsuite.mil/book/docs/DOC-1356658

 

 

8. USARPAC INDIVIDUAL AUGMENTATION (IA) REQUIREMENTS, OPENINGS IN DJIBOUTI, GUAM, SOMALIA, AND QATAR.  https://www.milsuite.mil/book/docs/DOC-1320402

 

 

9. ARNG/USAR POSITIONS/JOBS AVAILABLE. S1NET members have posted the following RC position/job vacancy information. For a listing of all USAR primary vacancies (updated weekly) visit milsuite.mil/book/docs/DOC-375787. Units/commands who wish to post vacancies on S1NET may do so by following the instructions posted on the front page of the Job Announcements topic at the following link. Those posts which are in the correct location and which are posted in accordance with the instructions provided will be included in a future S1NET Message Summary. milsuite.mil/book/community/spaces/apf/s1net/jobannouncementsmobvacancies

 

 

     a. 7TH ILE (CGSOC) DETACHMENT TPU, 01A, LTC-MAJ (P), INSTRUCTOR VACANCY, GRAFENWOEHR, GERMANY. https://www.milsuite.mil/book/docs/DOC-1356610

 

 

     b. MULTIPLE VACANCIES: TPU - COL/O6 AND LTC(P)/O5 - 85TH ARSC CHIEF OF STAFF (COS) AND G3/7, ARLINGTON HEIGHTS, IL. https://www.milsuite.mil/book/docs/DOC-1356633

 

 

     c. 3D BRIGADE, 95TH TRAINING DIVISION (IET), TPU, MULTIPLE CDR (O3/O1A), XO (O2/O1A), AND  1SG POSITIONS IN MULTIPLE LOCATIONS. https://www.milsuite.mil/book/docs/DOC-1356640

 

 

     d. USMTM-LFD, ADOS, INFANTRY O4 / 11A00 VACANCY, RIYADH, SAUDI ARABIA. https://www.milsuite.mil/book/docs/DOC-1349154

 

 

     e. SECURITY ASSISTANCE GROUP-UKRAINE (SAG-U) CIVIL AFFAIRS (ENERGY) MOBILIZATION OPPORTUNITY – O3-O5, 38A/G, WIESBADEN, GERMANY. https://www.milsuite.mil/book/docs/DOC-1356906

 

 

     f. 120TH REGIONAL SUPPORT GROUP, 882A - MOBILITY OFFICER (M-DAY), WO1-CW3, AUGUSTA, MAINE. https://www.milsuite.mil/book/docs/DOC-1356932

 

 

     g. T10 ADOS OPPORTUNITIES FOR THE ARNG WARRIOR TRAINING CENTER BRIGADE FOR IMMEDIATE HIRE, FT MOORE, GA, FT CHAFFEE, AR, AND FT JOHNSTON, LA. https://www.milsuite.mil/book/message/1084870

 

 

     h. TROOP XO (TPU), SR DRILL SERGEANTS (TPU), AND DRILL SERGEANTS (TPU) VACANCIES - 2/415TH CAV OSUT, MULTIPLE LOCATIONS IN CALIFORNIA. https://www.milsuite.mil/book/docs/DOC-1356974

Read More

PPM CIO-059 DATA AGGREGATION FRAMEWORK

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN42903-PPM_CIO-059-000-WEB-1.pdf

DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
ADD-GOV-DS-059
SAIS-ADD (25-1rrrr) 28 January 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Data Aggregation Framework
1. References. See Enclosure 1.
2. Purpose. Provide amplifying guidance to reference 1a on data management—
specifically, data aggregation.0F
1
a. This memorandum provides a framework for assessing and mitigating risks as
part of the data management and product development lifecycles.
b. The framework ensures the sensitivity of data (including data, metadata, and data
products1F
2) is established and any associated risks are identified and mitigated to ensure
proper data management and protection are implemented. This includes any time that
data is aggregated whether a data product is deployed, two or more data products are
joined, a new system is developed, or any other actions where the aggregation of data
may be a concern.
3. Background.
a. Reference 1b identifies “Data Protect” as a key strategic effort to the Army Data
Plan, to “develop Enterprise-wide policy and guidance for the Army to specify, when
data is aggregated and integrated into operations…The term ‘aggregation’ is used here
in the sense of associating data describing one set of information to data for a different
set of information.” Additionally, data protection directly supports VAULTIS (Visible,
Accessible, Understandable, Linked, Trustworthy, Interoperable, and Secure) goals,
specifically the “S – Secure” aspect.
b. Data protection is critical to achieve information advantage and deliver cutting-
edge and uncompromised capabilities. Data (including metadata) is an Army asset,
ownership and protection of that data is an Army mission and priority. To be effective,
the Army must improve its efforts to safeguard mission and business data (including any
1 As defined in reference 1f. This may implicate or involve “compilation” as defined in reference 1g, if
determined by an Original Classification Authority.
2 As defined in reference 1h.
SAIS-ADD (25-1rrrr)
SUBJECT: Data Aggregation Framework
metadata) through its entire lifecycle. Security and protection require the
implementation and enforcement of proper management and operational procedures by
the entire organization. This includes Commanders and senior leaders who provide the
strategic vision and goals for the organization, to strategic planners as well as program,
project, and program managers (PMs), down to everyone who helps the Army deploy,
fight, and win our nation’s wars. Furthermore, everyone, at all echelons and all levels,
is responsible for procedural compliance with the proper practices and procedures for
safeguarding data, information, and information technology.
4. Applicability.
a. This memorandum applies to the entire Army Data Enterprise as defined in
reference 1c. This includes, but not be limited to, Commanders and senior leaders of
agencies and activities at all levels and those they appoint, to include—
(1) Chief Information Officers (CIOs)
(2) Chief Innovation Officers
(3) Program Managers (PMs)
(4) System Owners
(5) Application Owners
(6) IT Service Owners
(7) Information Owners
(8) Portfolio Managers
(9) Resource Managers
(10) Security Managers
(11) Records Officers
(12) Operations Security Practitioners
(13) Acquisition Senior and Functional Services Managers
2
SAIS-ADD (25-1rrrr)
SUBJECT: Data Aggregation Framework
b. These roles are accountable for the implementation and enforcement of the Data
Aggregation Framework (Enclosure 2) and will ensure individual and organizational
accountability for activities under their purview.
5. Way Ahead. Implementation of the new Data Aggregation Framework will require a
phased approach. This memorandum is intended to be iterative over the first year
of implementation. The Chief Data and Analytics Officer (CDAO) will request feedback
from the data governance community and capture lessons learned to incorporate into
future iterations of the memorandum which will be rewritten on an annual basis. The
Department of Defense (DoD) will also publish future implementation guidance and
develop data protection policies through the DoD CDAO. The future update of
references 1c–e or a new regulation will incorporate this data protection policy.
6. Compliance. All organizations must comply with and are responsible for compliance
with all applicable laws, regulations, and policies to manage and protect data.
7. Points of contact.
a. CIO Policy Inbox at usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil
b. OCIO, Data Integration Division, at usarmy.data.management@army.mil
c. Mr. Alfred Hull, Data Integration Division, alfred.d.hull2.civ@army.mil
Encls 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
(CONT)
3
SAIS-ADD (25-1rrrr)
SUBJECT: Data Aggregation Framework
DISTRIBUTION: (CONT)
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
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
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
Superintendent, Arlington National Cemetery
Director, U.S. Army Acquisition Support Center
CF:
Principal Cyber Advisor
Director of Enterprise Management
Director, Office of Analytics Integration
Commander, Eighth Army
4
REFERENCES
a. AR 25-1 (Army Information Technology).
b. HQDA EXORD 009-20 (Army Data Plan Implementation in Support of Cloud
Migration), November 2019.
c. HQDA CIO memorandum (Army Data Stewardship Roles and Responsibilities
(Fiscal Year 2024)), 2 April 2024. Available at
https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN40630-PPM_CIO-021-000-WEB-1.pdf.
d. DoDI 8320.07 (Implementing the Sharing of Data, Information, and Information
Technology (IT) Services in the Department of Defense).
e. DoDI 8510.01 (Risk Management Framework for DoD Systems).
f. CNSSI 4009 (Committee on National Security Systems (CNSS) Glossary).
g. AR 380-5 (Army Information Security Program).
h. HQDA CIO memorandum (Army Enterprise Data Product Definition),
18 July 2024. Available at https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN41492-
PPM_CIO-036-000-WEB-1.pdf.
i. NIST slide presentation (NIST Risk Management Framework Quick Start Guide,
RMF Roles and Responsibilities Crosswalk), September 2024. Available at:
https://csrc.nist.gov/CSRC/media/Projects/risk-
management/documents/Additional%20Resources/NIST%20RMF%20Roles%20and%2
0Responsibilities%20Crosswalk.pdf.
j. DoD Architecture Framework (DoDAF) Version 2.02, August 2010. Available at
https://dodcio.defense.gov/Library/DoD-Architecture-Framework/
k. EO 13526 (Classified National Security Information), 29 December 2009.
l. National Security Presidential Memorandum 28 (The National Operations
Security Program), 13 January 2021. Available via ncsc_etd_partnership@odni.gov
m. DoDI 8320.02 (Sharing Data, Information, and Information Technology (IT)
Services in the Department of Defense).
n. DoDM 5200.01, Volume 1 (DoD Information Security Program: Overview,
Classification, and Declassification), 24 February 2012.
o. DoDM 5200.45 (Original Classification Authority and Writing a Security
Classification Guide).
ENCLOSURE 1
p. DoDM 5205.02 (DoD Operations Security (OPSEC) Program Manual).
q. AR 25-2 (Army Cybersecurity).
r. AR 25-22 (The Army Privacy and Civil Liberties Program).
s. AR 25-400-2 (Army Records Management Program).
t. AR 381-20 (The Army Counterintelligence Program).
u. AR 530-1 (Operations Security).
v. Army Techniques Publication 3-13.3 (Army OPSEC at Division and Below).
w. HQDA ASA (ALT) and CIO (Army Unified Data Reference Architecture, v.1.0), 22
March 2024. Available at
https://api.army.mil/e2/c/downloads/2024/03/25/c3d9b3aa/udra-version-1-0-final.pdf.
2
DATA AGGREGATION FRAMEWORK PROCESS
1. Data must be protected from unauthorized access, unauthorized use by authorized
personnel, and as otherwise required by law, regulation, or policy. The Data
Aggregation Framework outlines a process to identify, assess, and mitigate risks as part
of the data management and product development lifecycles in collaboration with
stakeholders to meet these requirements.
2. Information systems are already required to have controls (e.g., cybersecurity plans,
privacy plans, access control policies, etc.) in place to meet the requirements identified
in paragraph 1. System Owners may comply with the Data Aggregation Framework by
certifying annually from this point forward that:
a. The system has a current Authority to Operate (ATO).
b. The objectives for each Data Aggregation Framework step were evaluated as
part of the system’s risk management process to obtain an ATO.
c. Controls are in place to protect the data contained within the system.
d. The certification is stored in the Army Data Catalog.
3. Data Aggregation Framework Six-Step Process Overview. The Data Aggregation
Framework, illustrated in Figure 1, is a six-step process for data governance roles to
follow to ensure the protection of data products as they move across the enterprise and
are linked or aggregated with other data products.
Figure 1. Data Aggregation Framework
ENCLOSURE 2
4. The Data Aggregation Framework is risk-based and is composed of three
elements—
a. Identification of the security risk based on data exposure.
b. Specifying the data protection techniques to be used to protect the information
and limit the risk of exposure.
c. Performing a risk assessment and creating measurement/monitoring mechanisms
against exposure through vulnerabilities of data: data inference and data aggregation.
5. Escalation Process. For any conflicts during this process that cannot be resolved,
the matter should be escalated to the next higher level of data stewardship (see
Figure 2).
Figure 2. Escalation Structure
6. Data Aggregation Framework Six Steps.
a. Step 1: Risk Identification
(1) Objectives. To complete the essential activities to identify risks anytime data
assets are being aggregated.
2
(2) Stakeholders. The Office of Primary Responsible (OPR) designee0F
1 leads the
effort and engages with other stakeholders to leverage existing processes to identify
risks1F
2. These individuals or organizations may include—
(a) System Owners
(b) Other Data Stewardship Personnel (i.e., Functional Data Managers (FDM),
Data Stewards, and Mission Area Data Officers (MADO))
(c) Original Classification Authorities (OCA)
(d) Operations Security (OPSEC) Practitioners
(e) Cybersecurity Practitioners (i.e., Information System Security Managers
(ISSM), Information System Security Officers (ISSO), etc.)
(f) Army Records Management Office
(g) Army Privacy and Civil Liberties Office
(h) Any other required personnel or organizations that may be identified.
(3) Actions. The OPR designee must, at a minimum—
(a) Follow the OPSEC Planning Cycle to preserve friendly essential secrecy by
identifying, controlling, and protecting Critical Information Indicators (CII) and Critical
Program Information (CPI).
(b) Identify and follow other processes that may be required based upon the
nature of the data assets.
(c) Review the data models (i.e., conceptual2F
3 and logical3F
4 data models), business
processes, and workflows available through the planned data products.
(d) Notify the appropriate OCA that a new or updated Security Classification
Guide (SCG) may be needed.
1 The OPR is the office or organization that is aggregating the data.
2 For non-binding guidance, see Encl 1, reference i.
3 A Conceptual Data Model “is used to document the business information requirements and structural
business process rules of the architecture. It describes the information that is associated with the
information of the architecture. Included are information items, their attributes or characteristics, and their
inter-relationships.” See Encl 1, reference j, https://dodcio.defense.gov/Library/DoD-Architecture-
Framework/dodaf20_div1/
4 A Logical Data Model “allows analysis of an architecture's data definition aspect, without consideration
of implementation specific or product specific issues. Another purpose is to provide a common dictionary
of data definitions to consistently express models wherever logical-level data elements are included in the
descriptions.” See Encl 1, reference j, https://dodcio.defense.gov/Library/DoD-Architecture-
Framework/dodaf20_div2/
3
(e) Notify the appropriate office of any risks or gaps that may require the need to
develop a new or updated Commander’s Critical Information List (CIL).
(4) Outcomes. The outcomes from this step should include, at a minimum—
(a) A list of the data assets involved with the effort with classifications according
to sensitivity, regulatory requirements, and impact.
(b) An understanding of the intended data actions (e.g., collection, retention,
logging, generation, transformation, use, disclosure, sharing, transmission, disposal,
etc.).
(c) A documented list of identified risks and the associated categories (e.g.,
privacy, integrity, confidentiality, availability, security, compliance, operational risks,
etc.).
(d) A list of personnel and organizations with equities in the data that need to be
involved in the process.
(e) A list of other processes that may be required based upon the nature of the
data assets.
b. Step 2: Risk Assessment
(1) Objectives. To understand, quantify, prioritize the risks identified; evaluate
the potential impact of each risk; and review and document the protections that are or
will be implemented on the data assets (e.g., access control policies4F
5, etc.).
(2) Actions. The OPR designee must, at a minimum, continue the relevant
actions identified in Step 1, collaborate with Data Consumers to identify the
requirements driving data requests and any limitations on uses of the data, and any
analyses necessary to accomplish the outcomes in this step.
(3) Outcomes. The outcomes from this step should include, at a minimum, a
prioritized list of the identified risks, a list of protections that are or will be implemented,
and an evaluation as to whether the intended use of the data by the Data Consumers is
in line with the authorized use of the data.
c. Step 3: Sensitivity Determination
(1) Objectives. To determine the sensitivity of the aggregated data assets;
review and evaluate the protections; and determine whether additional protections need
to be implemented.
5 While Application Programming Interfaces (APIs) and other data sharing/transfer methods may handle a
larger amount of data, access should be restricted to only the parts of the business process and workflow
that a user is authorized to view.
4
(2) Actions. The OPR designee must, at a minimum, continue the relevant
actions identified in prior steps and complete the necessary analyses to achieve the
outcomes in this step. Cases may arise where there are conflicting sensitivity
determinations from different perspectives involved in the data aggregation framework.
In this case, conflicting views should be elevated to the Army Data Board (ADB) and/or
Army Wide Capabilities Protection (AWCP) for socialization and reconciliation.
(3) Outcomes. The outcomes from this step should include, at a minimum, the
sensitivity of the data asset and an established baseline of protections that comply with
the requirements laid out by the appropriate office identified above.
d. Step 4: Re-examine and Re-assess
(1) Objectives. To review the intended data actions to ensure compliance with
the established protections baseline; review the artifacts (i.e., data models, business
processes, and workflows) available through the planned data products to ensure
compliance with the established protections baseline; and establish a data protection
agreement.
(2) Actions. The OPR designee must, at a minimum, continue the relevant
actions identified in prior steps, complete the required analyses to achieve the outcomes
in this step, and ensure a data protection agreement is established. The agreement
should be coordinated between all relevant Functional Data Managers. The data
protection agreement should address aggregation concerns, impact level, and potential
releasability to external entities, at a minimum. The agreement should be in a central
location where Data Consumers can access the document.
(3) Outcomes. The outcomes from this step should include, at a minimum, data
actions that comply with the established protections baseline; artifacts that comply with
the established protections baseline; and a completed data protection agreement.
e. Step 5: Implementation
(1) Objectives. To apply and operationalize the identified data asset protections
throughout the data asset lifecycle.
(2) Actions. The OPR designee must engage with the identified stakeholders to
ensure that the baseline protections are implemented and consistent throughout the
entire data asset lifecycle as well as complete the required analyses to achieve the
outcomes in this step.
(3) Outcomes. Baseline data asset protections are implemented throughout the
data asset lifecycle and implementation of the data protection is documented.
5
f. Step 6: Monitoring/Annual Reassessment
(1) Objectives. To evaluate the ongoing effectiveness of the data asset
protections, support compliance efforts, and complete the annual attestation.
(2) Actions. The OPR designee must implement continuous monitoring and
engage with the identified stakeholders to ensure that protections are evaluated
throughout the entire data asset lifecycle as well as complete the required analyses to
achieve the outcomes in this step. If at any time the protections are determined not to
be effective, the OPR must start at Step 1 and reevaluate the circumstances to make
sure the proper protections are in place. Any deficiencies in the protections must be
documented. If there are no deficiencies, annual certification is required to confirm data
asset protections are in place and are effective.
(3) Outcomes. Assessment documentation is maintained, and annual
attestations are completed.
6 

Read More

PPM CIO-060 UPDATED GUIDANCE FOR APPLICABILITY OF DEPARTMENT OF DEFENSE MANUAL 8140.03 REQUIREMENTS UNDER PERFORMANCE WORK STATEMENTS

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN42902-PPM_CIO-060-000-WEB-1.pdf

DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
CS-RES-PW-060
SAIS-CS (25-1rrrr) 28 January 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Updated Guidance for Applicability of Department of Defense Manual
8140.03 Requirements Under Performance Work Statements
1. References.
a. CIO memorandum (Applicability of Department of Defense Manual 8140.03
Requirements Under Performance Work Statements), 12 December 2024 (hereby
superseded).
b. DoDM 8140.03 (Cyber Workforce Qualifications).
2. Purpose. Update the reference 1a guidance (hereby superseded) on the application
of Department of Defense Manual (DoDM) 8140.03 to Army contracts awarded
pursuant to a Performance Work Statement (PWS).
3. Background.
a. The DoD Chief Information Officer released DoDM 8140.03, Cyber Workforce
Qualification, in February 2023 (reference 1b). It applies to contractor cyber-coded
positions. On 12 December 2024, the Army Chief Information Officer (CIO) issued the
reference 1a guidance. New developments require this update to reference 1a.
b. Army organizations should maximize the use of Performance Work Statements,
which articulate task deliverables and the standards for acceptance. When using a
PWS, the Army does not dictate specifics regarding personnel, just the work to be
accomplished. The former is solely the contractor’s responsibility.
4. Guidance on the application of DoDM 8140.03 to contractor personnel.
a. In most situations, it would be inappropriate and unnecessary to assign a cyber
work role code to all contractor personnel performing work resulting from a PWS.
b. The requirements set forth in DoDM 8140.03 should not be applied to contractor
personnel performing work pursuant to a PWS. The DoDM 8140.03 requirements
should only be applied to contractors working in coded positions.
SAIS-CS (25-1rrrr)
SUBJECT: Updated Guidance for Applicability of Department of Defense Manual
8140.03 Requirements Under Performance Work Statements
c. Per DoDM 8140.03, the requirements set forth for DoD 8570.01-M are no longer
in effect and should not be included in Army contracts awarded pursuant to a PWS.
5. Implementation. Authorizing Officials (AOs), Program Executive Offices, and all
Army commands are responsible for ensuring compliance with this guidance.
Furthermore, the use of Performance Work Statements should be maximized, unless is
it impractical under existing circumstances.
6. Expiration and review. This guidance is effective immediately and remains in effect
until rescinded. The Army Chief Information Security Officer (CISO) will review this
guidance for update annually or as needed.
7. Points of Contact.
a. CIO Policy Inbox: usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil
b. SAIS-CS Deputy Director: Nathan Colodney, nathan.colodney2.civ@army.mil
c. SAIS-CSP Policy Team: usarmy.pentagon.hqda-cio.mbx.sais-csp@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
(CONT)
2
SAIS-CS (25-1rrrr)
SUBJECT: Updated Guidance for Applicability of Department of Defense Manual
8140.03 Requirements Under Performance Work Statements
DISTRIBUTION: (CONT)
U.S. Army Intelligence and Security Command
U.S. Army Corps of Engineers
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
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
Superintendent, Arlington National Cemetery
Director, U.S. Army Acquisition Support Center
CF:
Principal Cyber Advisor
Director of Enterprise Management
Director, Office of Analytics Integration
Commander, Eighth Army
3 

Read More

PPM CIO-061 CONTINGENCY PLANNING FOR CARMY CLOUD TENANTS

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN42912-PPM_CIO-061-000-WEB-1.pdf

DEPARTMENT OF THE ARMY
CHIEF INFORMATION OFFICER
107 ARMY PENTAGON
WASHINGTON DC 20310-0107
ZAX-TECH-CS-061
SAIS-ZAX (25-1rrrr) 28 January 2025
MEMORANDUM FOR SEE DISTRIBUTION
SUBJECT: Contingency Planning for cArmy Cloud Tenants
1. References.
a. DODI 8510.01 (Risk Management Framework for DOD Systems)
b. NIST SP 800-53 Rev. 5 (Security and Privacy Controls for Information Systems
and Organizations)
c. FIPS 199 (Standards for Security Categorization of Federal Information and
Information Systems)
d. NIST SP 800-34 Rev. 1 (Contingency Planning Guide for Federal Information
Systems)
2. Purpose. To establish organizational policy for Alternate Site Storage, Alternate
Processing Site, and retention of backups/snapshots within the Program Executive
Office (PEO) Enterprise cloud environments.
3. Applicability. This policy applies to all tenant organizations that manage cloud
resources within the Army Cloud (cArmy) environment.
4. Background. The Enterprise Cloud Management Agency (ECMA) currently
maintains the baseline infrastructure in support of Army Multi-Cloud and supporting
strategy. Enterprise Cloud Service Providers (CSPs), to include Amazon Web
Services (AWS), Microsoft Azure, Oracle Cloud Infrastructure (OCI), and Google
Cloud Platform (GCP) provide highly redundant and highly available services. The
CSPs have developed a tiered approach to providing these services:
a. Availability Zones: Discrete data centers, each of which has redundant power,
networking, and connectivity, and is housed in separate facilities. Each Availability
Zone (AZ) has multiple Internet connections and power connections to multiple grids.
SAIS-ZAX (25-1rrrr)
SUBJECT: Contingency Planning for cArmy Cloud Tenants
b. Regions: Geographically located centers of computing that consist of multiple
Availability Zones (multi-AZs) to enable fault tolerance, data sovereignty, network
connectivity, etc.
c. Cloud AZs within a single region provide a sufficient degree of separation
between primary and alternate processing sites to meet the requirements for
moderate and most high availability requirements. Implementation of cloud-based
multi-AZ infrastructure, platforms, and applications in accordance with this policy will
reduce costs, increase efficiency, improve cyber security posture, and standardize
deployments within the Army.
5. Policy. All cArmy tenants with a system security categorization level of moderate
or high for availability shall implement contingency plans based on deploying across
specific Cloud AZ architecture. Programs currently operating in the cArmy baselines
across NIPRNET and SIPRNET shall update organizational critical controls to update
in accordance with this policy.
a. All cloud hosted systems will utilize multi-AZ configuration for their Alternate
Processing Site requirements. Systems should be configured to utilize a minimum of
two AZ’s.
b. All cloud hosted systems will utilize multi-AZ configuration to meet Alternate
Storage Site requirements.
c. Programs that require additional data protection, replication, and/or availability
requirements not met through cloud multi-AZ shall work with the ECMA to identify
additional storage replication requirements.
d. All Enterprise cloud hosted information systems will implement fourteen (14)
day automated lifecycle policies for retention of data backups and snapshot images.
For data requiring additional retention requirements per non-cyber controls, (e.g.
Army Records retention policy) shall follow policies outlined.
e. Lifecycle policies shall be configured to prevent modification to backups/
snapshots and protect against deletion.
f. All programs are responsible for ensuring compliance with this policy.
g. Any requests for extending services beyond data retention/replication in multi-
Region must be submitted for approval for waiver to the point of contact (POC) in
paragraph 6b below for review by the Cloud Governance Committee (CGC).
2
SAIS-ZAX (25-1rrrr)
SUBJECT: Contingency Planning for cArmy Cloud Tenants
6. POCs.
a. CIO Policy Inbox: usarmy.pentagon.hqda-cio.mbx.policy-inbox@army.mil.
b. Mr. Gabriele Chiulli, ECMA CTO, gabriele.j.chiulli.civ@army.mil,
(520) 725-1758.
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
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
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
(CONT)
3
SAIS-ZAX (25-1rrrr)
SUBJECT: Contingency Planning for cArmy Cloud Tenants
DISTRIBUTION: (CONT)
Director, Civilian Protection Center of Excellence
Superintendent, Arlington National Cemetery
Director, U.S. Army Acquisition Support Center
CF:
Principal Cyber Advisor
Director of Enterprise Management
Director, Office of Analytics Integration
Commander, Eighth Arm
4 

Read More

MILPER 25-036 Fiscal Year 2025 (FY25), Active Component (AC), Captain (CPT), Army Nurse Corps (AN), Medical Service Corps (MS), and Army Medical Specialist Corps (SP), Fully Qualified Certification (FQC), Zones of Consideration.

BLUF: When the needs of the Army require, the SECARMY may recommend the promotion of all 1LTs in the promotion zone who are fully qualified for promotion to CPT using an all-qualified officer list in lieu of convening a Promotion Selection Board (PSB). Promotion Fully Qualified Certification (FQC) screening authorities will convene and begin review of the Army Military Human Resource Record (AMHRR) of eligible First Lieutenants (1LT) on the Active Duty List (ADL) for promotion to CPT, 31 Mar 25. 

MILPER 25-036 ANCMT FY25 AC CPT AMEDD FQC.pdf

Read More

S1NET Message Summary - 1/27/2025

1. (REMINDER) DA SECRETARIAT HOSTS WARRANT OFFICER PROMOTION SELECTION BOARD TOWNHALL. The DA Secretariat will host a Warrant Officer Promotion Selection Board Townhall Tuesday, 28 January, 1000-1200 EST. The intent of the Promotion Selection (PSB) Townhall is to inform and educate G1/S1s and ALL Warrant Officers in ALL Warrant Officer Military Occupational Specialty (WMOS) who are in the above the Zone (AZ), in the Zone (IZ), and below the zone (BZ) during the upcoming Active Component FY25 Chief Warrant Officer Three (CW3), Chief Warrant Officer Four (CW4), and Chief Warrant Officer Five (CW5) PSB. Visit the following link for Teams connection information. https://www.milsuite.mil/book/message/1084360

 

 

2. DESIGNATION OF THE RED SEA AND ADJACENT WATERWAYS FOR IMMINENT DANGER PAY, 18 DEC 24.  Memo from the Asst SECDEF Manpower and Reserve Affairs:  This memorandum designates the Red Sea, the Bab al-Mandeb Strait, the Gulf of Aden and the air spaces above them, effective October 19, 2023, as an imminent danger pay (IDP) area. Service members entitled to basic pay under Section 204, or compensation under Section 206 of Title 37, United States Code, who are on duty in the designated area during any month or portion of a month in which this designation is in effect, and are qualified in all other respects, may be paid IDP at a rate of $225 for the entire month, prorated at $7.50 per day, retroactive to the effective date. https://www.milsuite.mil/book/docs/DOC-1356579

 

 

3. (UPDATE) TRANSITION ASSISTANCE PROGRAM (TAP) TOWNHALL, 30 JAN 25. The US Army Human Resources Command’s Transition Division will conduct their inaugural Transition Assistance Program (TAP) Townhall on 30 January 2025 from 1100-1200 (Eastern) on Teams (change, was previously 1300-1400). The purpose of TAP Townhalls is to educate the field on pertinent transition topics and how command teams and units can best support transitioning Soldiers. https://www.milsuite.mil/book/docs/DOC-1355840

 

 

4. IPPS-A ITEMS.

 

 

     a. DRIVE THE CHANGE MASTER SERIES 2025. Join us and learn about the newly released IPPS-A functionality and training resources on Drive the Change. Team IPPS-A recently started briefing these updates, Training information and Job Aids for New Releases, to provide users with a better understanding of changes and where to find resources. Visit the following link for dates and times of upcoming briefs. https://www.milsuite.mil/book/docs/DOC-1356238

 

 

     b. DRIVE THE CHANGE 24 JAN 25. Visit the following link for a summary of changes and updates, briefing slides, and a video link. https://www.milsuite.mil/book/docs/DOC-1356252

 

 

5. BRANCH/COMMAND ITEMS.

 

 

     a. ARMY ACQUISITION CORPS NONCOMMISSIONED OFFICER (MOS 51C) ACTIVE COMPONENT RECLASS PANEL (MAY 2025). CMF 51 is accepting reclassification packets from 28JAN to 11APR 2025 for consideration into the career field for all Active Duty Sergeants and Staff Sergeants (all NCOs must have less than 12 years of service at the time the board convenes; E5s must have 2 years TIG). The next board is scheduled from 7-12 MAY 2025 and results will be announced within 60 days of the close. This panel will be utilized to fill training seats in FY26. Sergeants(E5) selected for this panel will be promoted to Staff Sergeant(E6) upon graduation from the Army Acquisition Transition Course in Huntsville, Alabama. https://www.milsuite.mil/book/message/1084419

 

 

6. Recently published Army Directives and All Army Activity (ALARACT) messages. None. New ALARACTs and ADs are also posted on APD at the following link. armypubs.army.mil/default.aspx

 

 

     a. ARMY DIRECTIVE 2025-01, RESCISSION OF DIVERSITY, EQUITY, INCLUSION AND ACCESSIBILITY POLICIES AND PROGRAMS, 24 JAN 25. Effective immediately, all references to Diversity, Equity, Inclusion, and Accessibility (DEI/DEIA) policies and programs that are prescribed in an Anny Regulation, Anny Directive, and any other Anny publication or memorandum of instruction are rescinded. DEI/DEIA does not include Equal Employment Opportunity (EEO), Military Equal Opportunity (MEO), and Sexual Harassment and Sexual Assault Prevention (SHARP) policies and programs. DEI programs and policies are considered policies and programs that were implemented directly in response to Executive Order 14035. Commanders and Directors shall review their internal policies and training material, in coordination with their servicing legal advisor, to comply with this directive. Within 5 days, all proponents of an Army publication will review the policy for which they are the proponent and report to the DAS whether a policy has DEI/DEIA material. If there is DEI/DEIA material, the proponent will initiate an expedited revision and remove the material within 15 days. https://www.milsuite.mil/book/docs/DOC-1356496

 

 

     b. ALARACT 007/2025, NOMINATIONS FOR SELECTION TO ATTEND THE

2025 ARMY MEDICAL DEPARTMENT IRON MAJORS WEEK, DTG: R 242310Z JAN 25. This ALARACT message replaces ALARACT 078/2024 (which is now inactive). The Army Medical Department (AMEDD) Iron Majors Week (IMW) begins with a nomination and selection process to identify outstanding AMEDD active and reserve component majors and captains promotable, as well as outstanding civilian corps leaders in the grades of GS 12–13 or equivalent, who have performed exceptionally. The 2025 AMEDD IMW will be conducted at Fort Belvoir, VA from 17 March through 21 March 2025.  https://www.milsuite.mil/book/docs/DOC-1356495

 

 

7. Recently published Military Personnel (MILPER) messages and Military Pay Messages.

 

 

     a. MILPER MESSAGE 25-033, FY 25 CONTINUING HEALTH EDUCATION (CHE) PROGRAM, ISSUED: [24 JAN 25]. This memorandum provides policies, eligibility criteria, and application procedures for USAR AMEDD IMA, and IRR Officers requesting funded CHE opportunities. https://www.milsuite.mil/book/docs/DOC-1356225

 

 

     b. MILPER MESSAGE 25-034, ACADEMIC YEAR 2026 (AY26) USAR ACTIVE GUARD RESERVE (AGR) ARMY MEDICAL DEPARTMENT (AMEDD) MEDICAL SERVICE (MS) AND ARMY NURSE (AN) CORPS LONG TERM HEALTH EDUCATION AND TRAINING (LTHET) PROGRAM SELECTION PANEL ANNOUNCEMENT, ISSUED: [24 JAN 25]. This message announces the eligibility requirements and application procedures for USAR AGR MS Corps and AN Corps officer to apply for selection to attend LTHET in AY26. The Army-Baylor LTHET for Master of Health Administration (MHA) or the dual MHA and Master of Business Administration (MHA/MBA) LTHET programs deliver quality education, training, and officer leader development opportunities to optimize officer career progression. https://www.milsuite.mil/book/docs/DOC-1356274

 

 

     c. MILPER MESSAGE 25-035, FISCAL YEAR 2025 (FY25), ACTIVE COMPONENT (AC), MAJOR (MAJ), CHAPLAIN CORPS (CH), PROMOTION SELECTION BOARDS (PSB) ZONES OF CONSIDERATION, ISSUED: [27 JAN 25]. Selection boards will convene on 7 Apr 25 to consider eligible CPT CH on the Active Duty List (ADL) for promotion to MAJ. The boards will recess on or about 11 Apr 25. https://www.milsuite.mil/book/docs/DOC-1356595

 

 

     d. ARMY MILITARY PAY E-MESSAGE 25-006, SUBJECT: REISSUED AND CORRECTED IRS FORMS W-2 FOR 2024. The purpose of this message is to provide information on the procedures for obtaining reissued 2024 IRS Forms W-2, Wage and Tax Statements, and corrected 2024 IRS Forms W-2c, Statement of Corrected Income and Tax Amounts. https://www.milsuite.mil/book/docs/DOC-1356561

 

 

8. USARPAC INDIVIDUAL AUGMENTATION (IA) REQUIREMENTS, OPENINGS IN DJIBOUTI, GUAM, SOMALIA, AND QATAR.  https://www.milsuite.mil/book/docs/DOC-1320402

 

 

9. ARNG/USAR POSITIONS/JOBS AVAILABLE. S1NET members have posted the following RC position/job vacancy information. For a listing of all USAR primary vacancies (updated weekly) visit milsuite.mil/book/docs/DOC-375787. Units/commands who wish to post vacancies on S1NET may do so by following the instructions posted on the front page of the Job Announcements topic at the following link. Those posts which are in the correct location and which are posted in accordance with the instructions provided will be included in a future S1NET Message Summary. milsuite.mil/book/community/spaces/apf/s1net/jobannouncementsmobvacancies

 

 

     a. COLORADO MDAY ANNOUNCEMENT, (18Z) FIRST SERGEANT, 5/19TH SFG(A), WATKINS, CO. https://www.milsuite.mil/book/docs/DOC-1355995

 

 

     b. SPECIAL OPERATIONS DETACHMENT – EUROPE (SOD-E), CSM VACANCY (M-DAY), 18Z, KINGWOOD, WV (ARNG). https://www.milsuite.mil/book/docs/DOC-1356206

 

 

     c. 505TH MILITARY INTELLIGENCE BRIGADE (THEATER), WARRANT OFFICER VACANCIES (WO1-CW4 351L AND 915A/E), CAMP BULLIS, TX (SAN ANTONIO). https://www.milsuite.mil/book/docs/DOC-1356211

 

 

     d. 350TH CA CMD, TPU, COL/38A, G3 CHIEF OFFICER VACANCY, PENSACOLA, FL. https://www.milsuite.mil/book/docs/DOC-1356248

 

 

     e. 256TH IBCT DMD VACANCIES 35 SERIES (E3 TO O5)  ARNG G2 NGB T10 ADOS VACANCIES, MULTIPLE LOCATIONS. https://www.milsuite.mil/book/docs/DOC-1356273

 

 

     f. 5TH BDE (SC), 102D TD (MS), TPU, MULTIPLE VACANCIES, FORT EISENHOWER, GA. https://www.milsuite.mil/book/docs/DOC-1356340

 

 

     g. 5TH SPACE COMPANY (ARMY SPACE SUPPORT TEAMS), FORT CARSON CO, TPU VACANCIES, 25B, 25S, 12Y, 35F, PFC - SSG POSITIONS. https://www.milsuite.mil/book/docs/DOC-1356374

 

 

     h. 5-98TH (CIVIL AFFAIRS/PSYCHOLOGICAL OPERATIONS) BN S-3 VACANCY, EDDISON, NJ. https://www.milsuite.mil/book/docs/DOC-1343498

 

 

     i. 389TH CSSB, TPU, MULTIPLE 1LT(P)-CPT COMPANY COMMAND OFFICER VACANCIES, VARIOUS LOCATIONS IN NYC AREA. https://www.milsuite.mil/book/docs/DOC-1356363

 

 

     j. MULTIPLE VACANCIES, ACO 301ST MI BN, TPU, CO COMMANDER(O2(P)-O3) & 1SG(E7(P)-E8), 35A&35Z, PHOENIX, AZ. https://www.milsuite.mil/book/docs/DOC-1356535

 

 

     k. MULTIPLE TPU VACANCIES ENL/OFF FOR STAFF AUGMENTATION TEAM- MEDICAL (SAT-M), SOUTHEAST MEDICAL AREA SUPPORT GROUP (SEMARG), NASHVILLE, TN. https://www.milsuite.mil/book/docs/DOC-1356573

 

 

     l. UNITED STATES ARMY FLIGHT TRAINING DETACHMENT – PEACE VANGUARD (USAFTD-PV), ADOS-AC MULTIPLE ENL E4-E6, WO & OFF VACANCIES, RED ROCK, AZ (SILVER BELL ARMY HELIPORT). https://www.milsuite.mil/book/docs/DOC-1353484

Read More