ishangsf/rspec
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update of developer.android.com links (#3335)

Browse Source
This commit is contained in:
Renaud T 2023-10-19 14:15:34 +02:00 committed by GitHub
parent 531e4225da
commit a1eb0d95e2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
rules/S5324/see.adoc
View File

@ -1,7 +1,7 @@
== See == See
* https://owasp.org/Top10/A04_2021-Insecure_Design/[OWASP Top 10 2021 Category A4] - Insecure Design * https://owasp.org/Top10/A04_2021-Insecure_Design/[OWASP Top 10 2021 Category A4] - Insecure Design
* https://developer.android.com/training/articles/security-tips#ExternalStorage[Android Security tips on external file storage] * https://developer.android.com/privacy-and-security/security-tips#ExternalStorage[Android Security tips on external file storage]
* https://mobile-security.gitbook.io/masvs/security-requirements/0x07-v2-data_storage_and_privacy_requirements[Mobile AppSec Verification Standard] - Data Storage and Privacy Requirements * https://mobile-security.gitbook.io/masvs/security-requirements/0x07-v2-data_storage_and_privacy_requirements[Mobile AppSec Verification Standard] - Data Storage and Privacy Requirements
* https://owasp.org/www-project-mobile-top-10/2016-risks/m2-insecure-data-storage[OWASP Mobile Top 10 2016 Category M2] - Insecure Data Storage * https://owasp.org/www-project-mobile-top-10/2016-risks/m2-insecure-data-storage[OWASP Mobile Top 10 2016 Category M2] - Insecure Data Storage
* https://cwe.mitre.org/data/definitions/312[MITRE, CWE-312] - Cleartext Storage of Sensitive Information * https://cwe.mitre.org/data/definitions/312[MITRE, CWE-312] - Cleartext Storage of Sensitive Information

4
rules/S6288/see.adoc
View File

@ -1,8 +1,8 @@
== See == See
* https://owasp.org/Top10/A04_2021-Insecure_Design/[OWASP Top 10 2021 Category A4] - Insecure Design * https://owasp.org/Top10/A04_2021-Insecure_Design/[OWASP Top 10 2021 Category A4] - Insecure Design
* https://developer.android.com/training/articles/keystore[developer.android.com] - Android keystore system * https://developer.android.com/privacy-and-security/keystore[developer.android.com] - Android keystore system
* https://developer.android.com/training/articles/keystore#UserAuthentication[developer.android.com] - Require user authentication for key use * https://developer.android.com/privacy-and-security/keystore#UserAuthentication[developer.android.com] - Require user authentication for key use
* https://mobile-security.gitbook.io/masvs/security-requirements/0x07-v2-data_storage_and_privacy_requirements[Mobile AppSec Verification Standard] - Authentication and Session Management Requirements * https://mobile-security.gitbook.io/masvs/security-requirements/0x07-v2-data_storage_and_privacy_requirements[Mobile AppSec Verification Standard] - Authentication and Session Management Requirements
* https://owasp.org/www-project-mobile-top-10/2016-risks/m4-insecure-authentication[OWASP Mobile Top 10 2016 Category M4] - Insecure Authentication * https://owasp.org/www-project-mobile-top-10/2016-risks/m4-insecure-authentication[OWASP Mobile Top 10 2016 Category M4] - Insecure Authentication
* https://cwe.mitre.org/data/definitions/522[MITRE, CWE-522] - Insufficiently Protected Credentials * https://cwe.mitre.org/data/definitions/522[MITRE, CWE-522] - Insufficiently Protected Credentials

2
rules/S6301/common/fix/android-apis.adoc
View File

@ -1,3 +1,3 @@
==== Using Android's builtin key storage options ==== Using Android's builtin key storage options
The https://developer.android.com/training/articles/keystore[Android Keystore] system allows apps to store encryption keys in a container that is protected on a system level. Additionally, it can restrict when and how the keys are used. For example, it allows the app to require user authentication (for example using a fingerprint) before the key is made available. This is the recommended way to store cryptographic keys on Android. The https://developer.android.com/privacy-and-security/keystore[Android Keystore] system allows apps to store encryption keys in a container that is protected on a system level. Additionally, it can restrict when and how the keys are used. For example, it allows the app to require user authentication (for example using a fingerprint) before the key is made available. This is the recommended way to store cryptographic keys on Android.

4
rules/S6301/common/resources/docs.adoc
View File

@ -1,5 +1,5 @@
=== Documentation === Documentation
* Android Documentation - https://developer.android.com/training/articles/keystore[Android Keystore system] * Android Documentation - https://developer.android.com/privacy-and-security/keystore[Android Keystore system]
* Android Documentation - https://developer.android.com/training/articles/security-tips#UserData[Security tips - User data] * Android Documentation - https://developer.android.com/privacy-and-security/security-tips#UserData[Security tips - User data]
* OWASP Mobile Application Security Testing Guide - https://mobile-security.gitbook.io/mobile-security-testing-guide/android-testing-guide/0x05d-testing-data-storage[Data Storage on Android] * OWASP Mobile Application Security Testing Guide - https://mobile-security.gitbook.io/mobile-security-testing-guide/android-testing-guide/0x05d-testing-data-storage[Data Storage on Android]