MASWE-0036: Authentication Material Stored Unencrypted on the Device
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.).
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-0036
Initial Description or Hints¶
General authentication material management best practices. Note that API keys are covered separately.
Relevant Topics¶
- session IDs
- tokens
- passwords
- use of sign-in with Apple/Google
References¶
- https://developers.google.com/identity/blockstore/android?hl=en
- https://cloud.google.com/docs/authentication/best-practices-applications#semi-trusted_or_restricted_environments
- https://cloud.google.com/docs/authentication/best-practices-applications#security_considerations
- https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_rest_api/authenticating_users_with_sign_in_with_apple/
MASTG v1 Coverage¶
No MASTG v1 tests are related to this weakness.