-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
platform: ios | ||
title: References to Device-Access-Security Policy APIs | ||
id: MASTG-TEST-0243 | ||
apis: [LAContext.canEvaluatePolicy, kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly] | ||
type: [static] | ||
weakness: MASWE-0008 | ||
best-practices: [] | ||
--- | ||
|
||
## Overview | ||
|
||
This test verifies that an application is running on a device with a set passcode. A set passcode ensures that data on the device is encrypted and access to the device is restricted. | ||
|
||
## Steps | ||
|
||
1. Run a static analysis tool such as @MASTG-TOOL-0073 on the app binary, or use a dynamic analysis tool like @MASTG-TOOL-0039, and look for uses of `LAContext.canEvaluatePolicy` API. | ||
|
||
## Observation | ||
|
||
The output should contain a list of locations where relevant APIs are used. | ||
|
||
## Evaluation | ||
|
||
The test fails if an app doesn't use API that verifies Device-Access-Security Policy. |