Skip to content

Commit b3f7659

Browse files
committed
Refine documentation for SDK method observations and data handling tests
1 parent b088cdd commit b3f7659

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

demos/android/MASVS-PRIVACY/MASTG-DEMO-00de3/MASTG-DEMO-00de3.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This sample collects the following [user data](https://support.google.com/google
3030

3131
## Observation
3232

33-
The output shows all instances of `logEvent` calls to Firebase Analytics SDK that were found at runtime, along with the parameters being sent. A backtrace is also provided to help identify the location in the code.
33+
The output shows all instances of `logEvent` calls to the Firebase Analytics SDK found at runtime, along with the parameters sent. A backtrace is also provided to help identify the location in the code.
3434

3535
{{ output.json }}
3636

tests-beta/android/MASVS-PRIVACY/MASTG-TEST-02te1.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,18 @@ profiles: [P]
1111

1212
This test verifies whether an app references SDK (third-party library) APIs known to handle sensitive data.
1313

14-
> Note: This tests detects only **potential** sensitive data handling. For **confirming** that actual user data are being shared, please refer to @MASTG-TEST-02te3.
14+
As a prerequisite, we need to identify the SDK APIs (methods) it uses as entry points for data collection by reviewing the library's documentation or codebase. For example, [FirebaseAnalytics](https://firebase.google.com/docs/analytics)'s class `com.google.firebase.analytics.FirebaseAnalytics` has the method `logEvent` used to log data. The method to look for would be `logEvent` in class `com.google.firebase.analytics.FirebaseAnalytics`.
15+
16+
> Note: This test detects only **potential** sensitive data handling. For **confirming** that actual user data are being shared, please refer to @MASTG-TEST-02te3.
1517
1618
## Steps
1719

18-
1. Identify common SDK APIs (methods) the SDK uses as entry points to collect data by researching the library's documentation online or its codebase. For example, if the library is `com.example.analytics` and it has a method `trackEvent(String eventName, Map<String, String> properties)` used to accept data, then the method to search for would be `com.example.analytics.trackEvent`.
19-
2. Run @MASTG-TECH-0014 to look for uses of these methods where sensitive data may be passed to the SDK.
20+
1. Use @MASTG-TECH-0013 to reverse engineer the app.
21+
2. Use @MASTG-TECH-0014 to look for uses of these methods where sensitive data may be passed to the SDK.
2022

2123
## Observation
2224

23-
The output should contain a list of locations where SDK methods are called.
25+
The output should list the locations where SDK methods are called.
2426

2527
## Evaluation
2628

tests-beta/android/MASVS-PRIVACY/MASTG-TEST-02te3.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This test verifies whether an app is sending sensitive data to an embedded SDK (
2121

2222
## Observation
2323

24-
The output should contain a list of the locations where SDK methods are called.
24+
The output should list the locations where SDK methods are called, their stacktrace (call hierarchy leading to the call), and the arguments (values) passed to the SDK method at runtime.
2525

2626
## Evaluation
2727

0 commit comments

Comments
 (0)