You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new risk for "Unsafe Handling of Imported Cryptographic Keys (MASVS-CRYPTO-2)" using the following information:
Importing keys without validating their origin or integrity, or using insecure custom key exchange protocols, can inadvertently introduce malicious or compromised keys into the app environment.
Create "risks/MASVS-CRYPTO/2-***-****/unsafe-imported-key-handling/risk.md" including the following content:
When creating the corresponding tests, use the following areas to guide you:
key import from untrusted sources
key import from untrusted storage
MASTG v1 Refactoring:
If the risk has a MASVS v1 ID, you can use it to search for related tests in the MASTG and use them as input to define your risks and associated tests.
Acceptance Criteria
The risk has been created in the correct directory (risks/MASVS-CRYPTO/2-***-****/unsafe-imported-key-handling/risk.md)
Description
Create a new risk for "Unsafe Handling of Imported Cryptographic Keys (MASVS-CRYPTO-2)" using the following information:
Importing keys without validating their origin or integrity, or using insecure custom key exchange protocols, can inadvertently introduce malicious or compromised keys into the app environment.
Create "
risks/MASVS-CRYPTO/2-***-****/unsafe-imported-key-handling/risk.md
" including the following content:To complete the sections follow the guidelines from Writing MASTG Risks & Tests
Use at least the following references:
When creating the corresponding tests, use the following areas to guide you:
MASTG v1 Refactoring:
If the risk has a MASVS v1 ID, you can use it to search for related tests in the MASTG and use them as input to define your risks and associated tests.
Acceptance Criteria
risks/MASVS-CRYPTO/2-***-****/unsafe-imported-key-handling/risk.md
)The text was updated successfully, but these errors were encountered: