Skip to content

Commit af50568

Browse files
serek8cpholguera
andauthored
Update risks/MASVS-STORAGE/1-store-sensitive-data-securely/data-unencrypted-external/android-data-unencrypted-external-frida/test.md
Co-authored-by: Carlos Holguera <perezholguera@gmail.com>
1 parent 0bc19a7 commit af50568

File tree

1 file changed

+1
-1
lines changed
  • risks/MASVS-STORAGE/1-store-sensitive-data-securely/data-unencrypted-external/android-data-unencrypted-external-frida

1 file changed

+1
-1
lines changed

risks/MASVS-STORAGE/1-store-sensitive-data-securely/data-unencrypted-external/android-data-unencrypted-external-frida/test.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ type: [dynamic]
77

88
## Overview
99

10-
Android apps utilize a variety of APIs to obtain a file path and save a file. Collecting a comprehensive list of these APIs can be challenging, especially when an app employs a third-party framework, loads code at runtime, or incorporates native code. Therefore, dynamic testing might be the most effective approach to find writing to the external storage.
10+
Android apps use a variety of APIs to obtain a file path and store a file. Collecting a comprehensive list of these APIs can be challenging, especially if an app uses a third-party framework, loads code at runtime, or includes native code. The most effective approach to testing applications that write to device memory is usually dynamic analysis, and specifically method tracing.
1111

1212
## Steps
1313

0 commit comments

Comments
 (0)