Sdm Software Gpo Reporting Pak Download

VA Technical Reference Model v 22.two

Group Policy Object (GPO) Exporter

General
Determination
Reference
Component
Category
Analysis

Technologies must be operated and maintained in accordance with Federal and Section security and privacy policies and guidelines. More information on the proper apply of the TRM can be constitute on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Grouping Policy Object (GPO) Exporter provides the user's ability to filter and report on settings across all GPOs in the Windows surround. This technology allows users to consign settings to a comma-separated values (CSV) file or the clipboard for review and/or processing by other applications. This software is a part of the GPO Reporting Pak. Annotation: Group Policy is a characteristic of the Microsoft Windows NT family of operating systems that controls the working surround of user accounts and computer accounts. Group Policy provides the centralized management and configuration of operating systems, applications, and users` settings in an Agile Directory environment. GPO Exporter and GPO Compare accept been replaced by the consolidated GP Reporting Pak, which includes the functionality of both. Website no longer is agile for the product every bit the production is no longer available
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, simply not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this applied science, users should check with their supervisor, Information Security Officer (ISO), Facility Master Information Officer (CIO), or local Function of Information and Engineering science (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Data:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may exist reviewed by the Section 508 Office and appropriate remedial activity required if necessary. For boosted information or assistance regarding Department 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Procedure:	One-VA TRM v20.x
Decision Appointment:	10/15/2020
Aliases:	SDM Software, GPO Reporting & Assay; GPO Exporter
Introduced Past:	TRM Asking
Vendor Name:	SDM Software

The Vendor Release tabular array provides the known releases for the TRM Engineering, obtained from the vendor (or from the release source).

Version	Release Date	Vendor Finish of Life Date	Vendor Desupport Date
two.0
ii.1.x	09/thirty/2016
three.0	08/06/2019

Users must ensure their use of this engineering/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Found of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive information is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Role of Information and Applied science (OI&T) representative to ensure that all actions are consequent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information bachelor every bit of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology volition exist supported. Whatever major.pocket-size version that is not listed in the VA Conclusion Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for utilise.
Yellowish	Approved westward/Constraints: The technology/standard can be used within the specified constraints located beneath the decision matrix in the footnote[ane] and on the General tab.
Grayness	Unapproved: This technology or standard can be used simply if a POA&M review is conducted and signed past the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the engineering.
Orangish	Divest: VA has decided to divest itself on the apply of the applied science/standard. As a event, all projects currently utilizing the engineering/standard must plan to eliminate their use of the engineering/standard. Additional information on when the entry is projected to become unapproved may be plant on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of fourth dimension this technology is currently being evaluated, reviewed, and tested in controlled environments. Employ of this technology is strictly controlled and not bachelor for use within the general population. If a client would similar to use this technology, please piece of work with your local or Regional OI&T role and contact the advisable evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a '.x' wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a conclusion for 7.ten would encompass whatsoever version of seven.(Anything) - 7.(Annihilation). Yet, a 7.four.x decision would encompass whatever version of vii.4.(Anything), but would non comprehend whatever version of 7.5.x or seven.6.x on the TRM.

VA decisions for specific versions may include '+' symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is non to exceed or touch previous decimal places.

For example, a technology canonical with a decision for 12.half dozen.four+ would cover whatsoever version that is greater than 12.half-dozen.4, but would non exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.seven.0 or xiii.0 is not.

<Past

CY2021

CY2022

CY2023

Future>

Release

ii.0

Unapproved

two.one.x

Unapproved

iii.0

Unapproved

Decision Constraints


[1]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an cess by the VA Section 508 role. Department 508 of the Rehabilitation Deed Amendments of 1998 is a federal police force that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the applied science to the production environment, or have project design and implementation plans approved, may go on to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to aggrandize operations to other sites or to an increased user base, it may do so as long equally the projection stays on the existing version of the engineering that was canonical or implemented as of Apr 22, 2015. Utilize of this engineering science in all other cases is prohibited.

[ii]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed past the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[3]	Utilise of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing assay with this technology need to work closely with system owners and concur on security scanning rules, such equally the assets scanned, along the schedule and frequency of those scans.

[four]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this engineering science should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	If complimentary trialware is utilized, the software must be purchased or removed at the end of the trial menstruation.

[half dozen]	Users should bank check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and employ this software. Downloaded software must always be scanned for viruses prior to installation to forbid adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community date. Users should annotation, whatsoever attempt by the installation procedure to install any additional, unrelated software is non approved and the user should accept the proper steps to turn down those installations.

[7]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, actress vigilance should be practical to ensure the versions remain properly patched to mitigate known and time to come vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

Note:

At the time of writing this, version iii.0 is the latest.

The following reference(due south) are associated with this entry:
Type	Name	Source	Description
There are no references identified for this entry.

Note: This list may not be consummate. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage determination for a component is establish in the Decision and Decision Constraints.
Name	Clarification
No components accept been identified for this entry.

Domain Surface area	Category	Client Guidance	Category Locked Past ELT Appointment
Platforms and Storage Operating Systems	Os Tools

Windows Client - Approved westward/Constraints
Windows Server - Approved due west/Constraints

Runtime Dependencies:

No runtime dependencies have been identified.

Adoption Benefits

At the time of writing, there are a limited number of TRM options providing this functionality. The addition of this technology will provide cease users with multiple viable options.
This engineering may improve productivity for specific staff whose responsibilities include windows setting queries.
The use of this technology may help improve the security posture of the organization.

Adoption Risks

The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
The potential of vendor lock exists when utilizing proprietary vendor engineering science.
This applied science has a free trial period, which carries the potential for the disruption of service commitment and inaccurate fiscal planning.
There are known Common Vulnerabilities and Exposures (CVEs) and VA Network & Security Operations Eye (NSOC) vulnerabilities.
Arrangement scans signal that this technology is no longer in use within the VA network.

Architectural Risks

This technology is no longer offered as a standalone solution.
This engineering science is not portable as it runs only on Windows platforms.

- The information independent on this page is accurate as of the Decision Appointment (10/15/2020).

Sdm Software Gpo Reporting Pak Download

DOWNLOAD HERE

Source: https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=7707

Posted by: peltonprept1997.blogspot.com

Pelton Prept1997

Sdm Software Gpo Reporting Pak Download Updated FREE

Sdm Software Gpo Reporting Pak Download

VA Technical Reference Model v 22.two

Decision Constraints

Runtime Dependencies:

Adoption Benefits

Adoption Risks

Architectural Risks

Sdm Software Gpo Reporting Pak Download

DOWNLOAD HERE

Menu Halaman Statis