MASWE-0017: Cryptographic Keys Not Properly Protected on Export
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-0017
Initial Description or Hints¶
Before exporting, keys should be "wrapped" or encrypted with another key. This process ensures that the cryptographic key is protected during and after export. This is true even if the key is sent over a secure channel.
Relevant Topics¶
- key wrapping (NIST.SP.800-175Br1 5.3.5)
References¶
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf
- https://developer.android.com/reference/kotlin/android/security/keystore/KeyProtection
- https://developer.apple.com/documentation/cryptokit/aes/keywrap
- https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys/storing_keys_as_data#2933723
MASTG v1 Coverage¶
No MASTG v1 tests are related to this weakness.