From Samsung Android OS 7 with Knox 2.x Security Technical Implementation Guide
Part of PP-MDF-991000
Associated with: CCI-000366
Users must not be able to override the system policy on the maximum number of consecutive failed authentication attempts because this could allow them to raise the maximum, thus giving adversaries more chances to guess/brute force passwords, which increases the risk of the mobile device being compromised. Therefore, only administrators should have the authority to set consecutive failed authentication attempt policies.
Not Applicable for the COBO use case. Review Samsung Android 7 with Knox configuration settings to determine if the mobile device is enforcing 10 or less failed Container authentication attempts. This validation procedure is performed on both the MDM Administration Console only. On the MDM console, do the following: 1. Ask the MDM administrator to display the "Maximum Failed Attempts for wipe" field in the "Android Knox Container >> Container Password Restrictions" rule. 2. Verify the value of the setting is "10" or less. If the MDM console "Maximum Failed Attempts for wipe" is not set to "10" or less or on the Samsung Android 7 with Knox device, the user is able to fail more than "10" authentication attempts, this is a finding.
Configure the Samsung Android 7 with Knox to enforce "10" or less failed Container authentication attempts. On the MDM console, set the "Maximum Failed Attempts for wipe" to the organization-defined value in the "Android Knox Container >> Container Password Restrictions" rule.
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer