BlackBerry AtHoc

General Information

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

Website:	Go to site
Description:	BlackBerry AtHoc allows institutions to communicate in emergency situations with the general population, targeted groups, or special needs individuals across widespread locations via multiple, redundant devices and communication methods. Alerting capabilities also extend to Federal Emergency Management Agency`s (FEMA`s) Integrated Public Alert Warning System (IPAWS). AtHoc refers to the overarching solution and platform. This technology can be run with a desktop/client deployment as well as a server side deployment. AtHocGov is the desktop client portion of the product. AtHocGov can also be known as AtHocVA. Users can run the stand-alone BlackBerry AtHoc Suite on the server side with the AtHocGov client deployed. The platform is usually updated ahead of that of the client side and will often exceed that of the desktop/client implementation. AtHocGov provides the underlying platform for VA`s emergency alert systems. This technology can be run on-premises or in the cloud. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO. This entry covers the Desktop Edition of this technology and not any mobile versions. See Category tab/Comparable for the corresponding Mobile entry. Note: The implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/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 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 technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	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 be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.3
Decision Date:	03/08/2023 at 02:40:28 UTC
Aliases:	AtHocGov; AtHoc Suite; AtHoc Installation Warning System (IWS); AtHocVA; AtHocVAEAAS
Introduced By:	SCCM
Vendor Name:	BlackBerry

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.x (AtHocGov - Mac)	03/01/2020
6.1.x (Platform)
6.2.x (AtHocGov)	12/31/2016
7.4.x (Platform)	01/30/2018
7.6.x (Platform)	09/01/2018
7.7.x (Platform)	09/01/2019
7.12.x (Platform)	07/01/2020
7.4.x (AtHocGov)	12/01/2022
7.15.x (Platform)	06/01/2022

Current Decision Matrix (03/07/2023)

Users must ensure their use of this technology/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 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 technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent 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 available as 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 will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by 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 technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found 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 time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate 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 decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.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 not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.x (AtHocGov - Mac)

Unapproved

6.1.x (Platform)

Unapproved

Divest
[5, 9, 12, 14, 15]

6.2.x (AtHocGov)

Approved w/Constraints
[5, 6, 7, 8]

Approved w/Constraints
[5, 7, 8, 9]

Divest
[5, 9, 10, 11, 12]

Divest
[5, 9, 11, 13]

Approved w/Constraints
[5, 9, 12, 14, 15]

7.4.x (Platform)

Unapproved

Approved w/Constraints
[5, 9, 10, 11, 12]

Divest
[5, 9, 11, 13]

Divest
[5, 9, 12, 14, 15]

7.6.x (Platform)

Unapproved

Approved w/Constraints
[5, 9, 11, 13]

Approved w/Constraints
[5, 9, 12, 14, 15]

7.7.x (Platform)

Unapproved

7.12.x (Platform)

Unapproved

7.4.x (AtHocGov)

Unapproved

7.15.x (Platform)

Unapproved

Decision Constraints


[1]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. This technology should not be used to communicate any VA Sensitive information without a full evaluation of the technology for such use. Precautionary steps and procedures should be put in place to prevent accidental transmission of sensitive data. Finally, new installations or major expansions of this technology must complete a Systems Engineering Design Review (SEDR) prior to implementation.

[2]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law 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 technology to the production environment, or have project design and implementation plans approved, may continue 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 expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[3]	This technology should not be used to communicate any VA Sensitive information without a full evaluation of the technology for such use. Precautionary steps and procedures should be put in place to prevent accidental transmission of sensitive data. Finally, new installations or major expansions of this technology must complete a Systems Engineering Design Review (SEDR) prior to implementation.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

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

[6]	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 by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[7]	This technology should not be used to communicate any VA Sensitive information without a full evaluation of the technology for such use. Precautionary steps and procedures should be put in place to prevent accidental transmission of sensitive data. Finally, new installations or major expansions of this technology must complete a Systems Engineering Design Review (SEDR) prior to implementation.

[8]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[9]	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 by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	This technology should not be used to communicate any VA Sensitive information without a full evaluation of the technology for such use. Precautionary steps and procedures should be put in place to prevent accidental transmission of sensitive data. Finally, new installations or major expansions of this technology must complete a ITOPS Solution Delivery (SD) (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation.

[11]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[12]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[13]	This technology should not be used to communicate any VA Sensitive information without a full evaluation of the technology for such use. Precautionary steps and procedures should be put in place to prevent accidental transmission of sensitive data. Finally, new installations or major expansions of this technology must complete a ITOPS Solution Delivery (SD) (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation.

[14]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[15]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

Note:

At the time of writing, version 7.15 (Platform) is the most current version, released 09/01/2022. Version 7.4 (AtHocGov) is the most current version, released 12/01/2022. Version 2.5 (AtHocGov-Mac) is the most current version, released 10/01/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Document Portal	This site links to manuals for the varying installs of this software.
Vendor Provided*	Blackberry Data Sheet	This document indicates that the Blackberry AtHoc service is FIPS 140-2 compliant.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Application Server	The Application Server acts as a Web-based application server that provides all user-related interactions. The application server also runs scheduling events, providing notification delivery, and running background batch processes used for integration with external applications and content sources. The servers provide integration points with enterprise application suites such as Lightweight Directory Access Protocol, Active Directory, Human Resources, and corporate portals.
AtHoc User Sync Client	AtHoc User Sync Client is included in later versions of this software and it supports synchronization of distribution lists, synchronization of users and creation of organization hierarchies.
Blackberry AtHoc Desktop App	The AtHoc Desktop App is a desktop application that continuously runs on your computer. When a new alert targeted at user desktops is published in the BlackBerry AtHoc system, a notification screen pops up on your desktop, accompanied by an audio notification.
BlackBerry AtHoc Desktop App for Mac	Release notes for MacOS.
Database Server	The Database Server is based on Microsoft Structured Query Language (SQL) Server and can be installed in a clustered database configuration, providing hot failover between the database machines.
Lightweight Directory Access Protocol (LDAP) Data Integration Module	The Lightweight Directory Access Protocol (LDAP) Data Integration Module is designed to synchronize organizational structure and user information with BlackBerry AtHoc. This module is affiliated with older versions of this software.
Personnel Directory Integration Module (PDIM)	Personnel Directory Integration Module (PDIM) allows for the communication and integration of contact data with Active Directory. This is a legacy module and has been replaced by the AtHoc User Sync Client in later versions.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Operations Management	Emergency Management

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a well-documented technology.
This technology supports VA`s emergency services.
This technology is Federal Information Processing (FIPS) 140-2 compliant.

Adoption Risks

This technology can integrate with and alter database technologies.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
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.
There are other TRM-approved technologies that provide similar functionality.
This technology may utilize external data connections.

Architectural Benefits

This technology is packaged with its own database that allows for the syncing of data across sources and it allows for data to be saved for future use.
This technology is portable as it runs on multiple TRM-approved operating systems.
This technology can use a VA-preferred database.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/07/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/07/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES