This section describes the implementation requirements that are necessary to comply with the VPN Security Requirements Guide (SRG).
The following behaviors must be implemented to comply with the VPN SRG rules:
- When any of the following violations are found during IKE, a warning notification must be displayed in the status bar and the VPN connection must be suspended:
- Subject name mismatch violation
- Key usage violation
- Revocation verification failed
- When the user opens the VPN notification on the status bar, an alert dialog is displayed that shows the reason for the failure and offers the user the choice of whether to allow or deny the VPN connection:
- If a certificate has more than one violation, itemize each of the reasons for the violation in a single message box.
- If the user chooses to allow the connection, then the VPN service skips validating this set of violations (for this time only).
- If the user chooses to deny the connection, then the VPN connection fails and traffic is blocked from any packages that belong to the VPN profile.
- The user’s decision to whether to allow or deny a VPN connection only applies to VPN connections in which a violation is identified. If a violation is identified in a different VPN connection, the user receives a separate notification. In other words, a user grants permission for an individual VPN connection to proceed in the case where violations are found in multiple VPN connections.
- The alert dialog message can contain only the reason for the violation.
- To handle certificate validation failure prompts, the MDM API
setServerCertValidationUserAcceptanceCriteria(), whose interface is defined in
IKnoxVpnService.aidl, can be used to enable/disable certificate validation based on the condition set
You must complete the following questions and return your answers to Samsung Knox Product Management at email@example.com once your implementation is complete.
- List the APIs that your app supports from IKnoxVpnService.aidl.
- List the JSON parameters supported in the vendor section.
- How many instances does the VPN client support:
- 1 per user
- 1 per device
- Multiple per-user
- What type of VPN service do you support?
- Generic VPN service (For backwards compatibility and to support Knox 2.0 devices)
- Android VPN service with generic VPN context (Best option for Knox 2.2 (and above) devices)
- When will you release the client software and which version of the client software supports Knox?
- Is the VPN Client going to act as a Knox MDM as well?
- Is the VPN Client an Admin application?
- If a bug is present, whom do we contact in Tech support?
- If a bug is present, how will you collect the relevant logs?
- Is the EULA Model supported??
- What is the package name of your Application?
- Is UID/PID feature supported?
- How many tunnels do you support per instances?
- Define your Test Server setup.
- Do you support Auto-retry behavior?
Is this page helpful?
Thank you for your feedback!