OpenControls Logo

STIG Viewer

STIGViewer Support

All mobile Honeywell cryptography must be configured to be in FIPS 140-3 validated mode.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-274411HONW-13-009600SV-274411r1100864_ruleCCI-002450high
Description
Unapproved cryptographic algorithms cannot be relied on to provide confidentiality or integrity, and DOD data could be compromised as a result. The most common vulnerabilities with cryptographic modules are those associated with poor implementation. FIPS 140-3 validation provides assurance that the relevant cryptography has been implemented correctly. FIPS 140-3 validation is also a strict requirement for use of cryptography in the federal government for protecting unclassified data. SFR ID: FCS
STIGDate
Honeywell Android 13 COPE Security Technical Implementation Guide2025-05-07

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (9) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
CRY-01.2Export-Controlled Cryptography
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (29) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
AU-9(3)Cryptographic Protection
1.00
CM-5(6)Limit Library Privileges
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-3(1)Cryptographic Bidirectional Authentication
1.00
IA-5(1)Password-based Authentication
1.00

+19 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.11
1.00
CCI1 mapping
CCI-002450
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00

Who does this work

8 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-274411r1100864_chk)

Review the configuration to determine if the Honeywell Android devices are in FIPS mode. On the MDM console (for SDM660 only): 1. In the MDM console, load the active DeviceConfig.xml for the managed device 2. Verify that item DeviceConfig >> HoneywellSetting >> EnforceOSFipsMode has a value of "1" for "Enable OS FIPS Mode". On the Honeywell Android 13 device (SDM660 only): 1. Open Settings >> Honeywell Settings >> FIPS Enforce Mode. 2. Verify that "FIPS Enforce Mode" is enabled. If "FIPS Enforce Mode" is not enabled, this is a finding.

Fix Text (F-78407r1100802_fix)

On the MDM console (for SDM660 only): 1. Ask the MDM administrator to edit the following item in DeviceConfig.xml: Modify item: DeviceConfig >> HoneywellSetting >> EnforceOSFipsMode Value sample: 1: Enable OS FIPS mode; 0: Disable OS FIPS mode. 2. In the MDM console, the MDM administrator will package this DeviceConfig.xml and push this package to the CN80G device. On the Honeywell Android 13 device (SDM660 only): 1. Open Settings >> Honeywell Settings >> FIPS Enforce Mode. 2. Enable "FIPS Enforce Mode".