Project

General

Profile

Android BYOD Security based on Trusted Network Connect » History » Version 19

« Previous - Version 19/32 (diff) - Next » - Current version
Andreas Steffen, 08.04.2013 15:05


Android BYOD Security based on Trusted Network Connect

An experimental BYOD version of the popular strongSwan Android VPN Client allows the collection of integrity measurements on Android 4.x devices. A special Android BYOD IMC written in Java communicates via the TNC IF-M 1.0 Measurement protocol with an Operating System IMV and a Port Scanner IMV. The strongSwan Android VPN Client transports the IF-M messages (RFC 5792 PA-TNC) in IF-TNCCS 2.0 Client/Server protocol batches (RFC 5793 PB-TNC) via the IF-T for Tunneled EAP Methods 1.1 Transport protocol protected by IKEv2 EAP-TTLS.

VPN Client Configuration

Android VPN client configuration

The Android VPN client profile BYOD has the following properties:

  • The hostname of the VPN gateway is byod.strongswan.org.
  • The user authentication is based on IKEv2 EAP-MD5.
  • Possible user names are john or jane and the user password is byod-test.
  • The byod.strongswan.org server certificate is issued by the strongSwan 2009 certification authority.

Therefore the strongSwan 2009 CA certificate must be imported into the Android certificate trust store before the first connection can be attempted.

Unrestricted Access (TNC recommendation is allow)

Successful connection

If the BYOD IMC (Integrity Measurement Collector) does not detect and report any security issues to the OS, Scanner and Attestation IMVs (Integrity Measurement Verifiers) via the IF-M message protocol then the TNC Server located in the combinded strongSwan PDP/PEP decides to give the VPN client full access to the corporate network.

Restricted Access (TNC recommendation is isolate)

Blocked Access (TNC recommendation is block)

Failed Connection Remediation Instructions for Failed Connection Remediation Instruction Details for Failed Connection