Skip to content

MASTG-TEST-0212: Clarify test case for hardcoded cryptographic keys - #3945

Open
cpholguera wants to merge 3 commits into
masterfrom
cpholguera-patch-2
Open

cpholguera wants to merge 3 commits into
masterfrom
cpholguera-patch-2

Conversation

@cpholguera

Copy link
Copy Markdown
Collaborator

Updated the test case to clarify the focus on hardcoded cryptographic keys and the importance of tracing key material sources. Enhanced steps and observations for better guidance on identifying hardcoded keys.

Updated the test case to clarify the focus on hardcoded cryptographic keys and the importance of tracing key material sources. Enhanced steps and observations for better guidance on identifying hardcoded keys.
Comment thread tests-beta/android/MASVS-CRYPTO/MASTG-TEST-0212.md Outdated
Comment thread tests-beta/android/MASVS-CRYPTO/MASTG-TEST-0212.md Outdated
@bernhste

bernhste commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Should we also mention non OS crypto?

If the app provides its own crypto library (for example in Android native), the test should also make sure to detect hardcoded material there.

If we add that, we should align the iOS test MASTG-TEST-0213.

@cpholguera You can add me to review it and if I would make the PR for the iOS test, if you agree to add non OS-APIs.

@cpholguera
cpholguera requested a review from bernhste September 4, 2026 18:42
@cpholguera

Copy link
Copy Markdown
Collaborator Author

Thanks @bernhste! The review is assigned to you. Please consider whether we should add that to this test or it'd be better to have as a separate / independent test.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants