MASWE-0008: Device Access Security Policy Not Enforced

Content in BETA

This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).

Send Feedback

Draft Weakness

This weakness hasn't been created yet and it's in draft. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.

Check our GitHub Issues for MASWE-0008

Initial Description or Hints

The app may not enforce device access security policy (e.g. device passcode) and may allow for unauthorized access to sensitive data.

Relevant Topics

• user set a device passcode via isDeviceSecure() on Android better than only ensuring that the lock screen is set via KeyguardManager.isKeyguardSecure()
• before attempting to authenticate, test to make sure that you actually have the ability to do so by calling the LAContext.canEvaluatePolicy(_:error:) method on iOS
• to make sure that biometrics can be used, verify that the kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly or the kSecAttrAccessibleWhenPasscodeSet protection class is set when the SecAccessControlCreateWithFlags method is called

References

• https://developer.apple.com/documentation/localauthentication/logging_a_user_into_your_app_with_face_id_or_touch_id
• https://grep.app/search?q=isdevicesecure%28&filter[repo][0]=threema-ch/threema-android

MASTG v1 Coverage

• MASTG-TEST-0064 - Testing Local Authentication (ios)
• MASTG-TEST-0017 - Testing Confirm Credentials (android)
• MASTG-TEST-0012 - Testing the Device-Access-Security Policy (android)