An overview of the samsung knox platform v1 14

February 2016
Samsung Research America
Samsung Electronics Co.,Ltd.
White Paper:An Overview of the Samsung KNOXTM
Platform
Javier Hernán González Carrillo mailto:j.hergonca@gmail.com – http://www.linkedin.com/in/JavierHernanGonzalezCarrillo - +34 673 403 421

Contents
Samsung KNOX Platform 2
Technology Overview 3
Platform Security 3
Hardware Root of Trust 3
Secure Boot and Trusted Boot 4
Security Enhancements for Android 4
TrustZone-based Integrity MeasurementArchitecture 5
TrustZone-based Security Services 7
Application Security 8
KNOX Workspace 8
Android for Work on a Samsung device 12
Virtual Private Network Support 12
SmartCard Framework 15
Single Sign-On 16
Mobile Device Management 16
Comprehensive Management Policies 17
Active Directory Integration 17
KNOX Mobile Enrollment 18
Enterprise Billing 18
Certifications 20
Summary 22
About Samsung Electronics Co., Ltd. 23

Acronyms AES Advanced Encryption Standard
AOSP Android Open SourceProject
BYOD Bring Your OwnDevice
CAC U.S. Common AccessCard
CESG Communications and Electronic SecurityGroup
COPE Corporate-Owned PersonallyEnabled
DAR Data-at-Rest
DISA U.S. Defense Information SystemsAgency
DIT Data-in-Transit
DoD U.S. Department ofDefense
FIPS Federal Information Processing Standard
IPC Inter ProcessCommunication
MAC MandatoryAccess Control
MDM MobileDevice Management
NIST National Institute of Standards andTechnology
ODE On-Device Encryption
OS OperatingSystem
PKCS Public Key CryptographyStandards
RAM Random-AccessMemory
ROM Read-OnlyMemory
SBU Sensitive But Unclassified
SEfor Android Security Enhancements forAndroid
SELinux Security-EnhancedLinux
SRG Security Requirements Guide
SSO Single Sign-On
STIGs Security Technical ImplementationGuides
TIMA TrustZone-based Integrity Measurement Architecture
VPN Virtual PrivateNetwork
WhitePaper
An Overview of the Samsung KNOX Platform
1

WhitePaper
An Overview of theSamsung KNOX Platform
KNOX is Samsung's defense-grade mobile security platform built into our newest devices. Just
turn on the device, and you're protected.
KNOX provides strong guarantees for the protection of enterprise data by building a hardware-
rooted trusted environment. A trusted environment ensures that enterprise-critical operations,
such as decryption of enterprise data, can only occur when core system components are proven
to not be compromised. For many pieces of device software, such as the kernel and TrustZone
apps, this is done by checking the cryptographic signature of each piece of software. A trusted
environment is hardware-rooted if both the cryptographic keys and code used to compute these
signatures are tied back to unmodifiable values stored in hardware.
Key features of KNOX include Secure Boot, Trusted Boot, ARM®
TrustZone®
-based Integrity
Measurement Architecture (TIMA), Security Enhancements for Android (SE for Android), and
TrustZone-based Security Services.
The KNOX Workspace container is designed to separate, isolate, encrypt, and protect work data
from attackers. This enterprise-ready solution provides management tools and utilities to meet
security needs of enterprises large and small.
Samsung KNOXTM
Platform
Figure 1 – Samsung KNOX Platform, Workspace, Management Tools and Utilities
2

WhitePaper
Technology Overview
3
This section describes the technical aspects of three key pillars of Samsung KNOX platform:
1. PlatformSecurity
2. ApplicationSecurity
3. MobileDevice Management
Platform Security
Samsung KNOX addresses security using a comprehensive, hardware-rooted trusted
environment:
• Hardware Root ofTrust
• SecureBoot and Trusted Boot
• Security Enhancements for Android (SE for Android)
• TrustZone-based Integrity Measurement Architecture (TIMA)
• TrustZone-based Security Services
Hardware Root of Trust
Three hardware components are the foundation of Samsung KNOX’s trusted environment.
The Device Root Key (DRK) is a device-unique asymmetric key that is signed by Samsung
through an X.509 certificate. This certificate attests that the DRK was produced by Samsung.
The DRK is injected in the device at manufacture time in the Samsung factory, and is only
accessible by specially privileged software modules within the TrustZone Secure World.
Because the DRK is device-unique, it can be used to identify a device. For example, a
certificate included with TIMA attestation data is signed by DRK (more precisely, through a key
attested by the DRK), which proves that the attestation data originated from the TrustZone
Secure World on a Samsung device. KNOX also uses device-unique hardware keys and keys
derived from the hardware keys, which are only accessible in the TrustZone Secure World.
Such keys can be used to tie data to a device. For example, KNOX Workspace data is encrypted
by such a key, and it cannot be decrypted on any other devices.
The Samsung Secure Boot key is used to sign Samsung-approved executables of boot
components. The public part of the Samsung Secure Boot key is stored in hardware at
manufacture time in the Samsung factory. The Secure Boot process uses this public key to
verify whether each boot component it loads is approved.
Rollback prevention fuses are hardware fuses that encode the minimum acceptable version
of Samsung-approved executables. These fuses are set at manufacture time in the Samsung
factory. Because old images may contain known vulnerabilities that can be exploited, this
feature prevents approved-but-old versions of boot executables from being loaded.

WhitePaper
Secure Boot and Trusted Boot
The startup process for Android begins with the primary bootloader, which is loaded from
Read-only Memory (ROM). This code performs basic system initialization and then loads
another bootloader, called a secondary bootloader, from the file system into Random-Access
Memory (RAM) and executes it. Multiple secondary bootloaders may be present, each for
a specific task. The boot process is sequential in nature with each secondary bootloader
completing its task and executing the next secondary bootloader in the sequence, finally
loading the Android bootloader known as aboot, which loads the Android operating system.
Secure Boot is a security mechanism that prevents unauthorized bootloaders and operating
systems from loading during the startup process. Secure Boot is implemented by each
bootloader cryptographically verifying the signature of the next bootloader in the sequence
using a certificate chain that has its root-of-trust resident in hardware. The boot process is
terminated if verification fails at any step.
Secure Boot is effective in preventing unauthorized bootloaders (and sometimes the kernel
when it is also applied to the kernel binary). However, Secure Boot is unable to distinguish
between different versions of authorized binaries, for example, a bootloader with a known
vulnerability versus a later patched version, since both versions have valid signatures. In
addition, when some carriers decide to allow custom kernels to run on their devices, Secure
Boot is not effective in preventing non-Samsung kernels from running on these devices. This
exposes an attack surface that poses a potential threat to enterprise applications and data.
Samsung KNOX implements Trusted Boot (in addition to Secure Boot) to address
this limitation. With Trusted Boot, measurements of the bootloaders are recorded in
secure memory during the boot process. At runtime, TrustZone applications use these
measurements to make security-critical decisions, such as verifying the release of
cryptographic keys from the TIMA KeyStore, container activation, and so on.
Additionally, if the aboot bootloader is unable to verify the Android kernel, a one-time
programmable memory area (colloquially called a fuse) is written to indicate suspected
tampering. Even if the boot code is restored to its original factory state, this evidence of
tampering remains. However, the boot process is not halted, and the aboot bootloader
continues to boot the Android operating system. This process ensures that normal operation
of the device is not affected.
Security Enhancements forAndroid
Samsung KNOX introduced Security Enhancements for Android (SE for Android) in 2012 to
enforce Mandatory Access Control (MAC) policies. These enhancements protect applications
and data by strictly defining what each process is allowed to do, and which data it can
access. Samsung’s innovative collaborations with the authors of SELinux resulted in the
gold standard for Android security. In version 4.4 of Android Open Source Project (AOSP),
Google introduced a subset of the SE for Android enhancements Samsung pioneered
(i.e., the SELinux portion). Samsung continues to lead Google, and all others, in continuing
to implement new extensions of SE for Android. Our improvements allow us to protect
areas of the Android framework to which access was previously unrestricted. Our policy
protects software created by Samsung, AOSP, and other third-party partners. The increased
4

WhitePaper
enforcement granularity from our AOSP enhancements, and Samsung’s industry-leading
granular access policies that define over 200 unique security domains, are designed
together to enforce the tightest restrictions with the lowest rates of over- or under-
privileging.
Samsung also built an innovative global policy validation system that can detect when
prohibited actions are attempted. This gives us unique visibility into how our devices are
used and can alert us to new threats. This system can be used to refine our policy and very
accurately grant only the minimum permissions needed.
The KNOX platform now includes the SE for Android Management Service (SEAMS) that
provides Application Programming Interface (API)-level control of the security policy engine.
SEAMS is primarily used internally by the KNOX Workspace container, but is also available to
third-party vendors to secure their own container solutions. The SEAMS APIs allow software
permissions to be tailored for each organization. Leveraging our controls to define and
protect security containers allows customers to dynamically isolate applications and data.
Our containers use new SE for Android Multi-Level Security (MLS) protections designed to
offer far more protection than any other existing Android isolationmechanism.
Our enhancements to Android, along with our robust policy, security tools, data collection,
and policy management show that Samsung KNOX devices are designed to provide the best
protections of any mobile device manufacturer. These protections form a foundation for
protecting users from malicious or accidental security breaches.
TrustZone-based Integrity MeasurementArchitecture
The system protection offered by SE for Android relies on the assumption of Operating
System (OS) kernel integrity. If the kernel itself is compromised (by a perhaps as yet
unknown future vulnerability), SE for Android security mechanisms could potentially be
disabled and rendered ineffective. Samsung’s TrustZone-based Integrity Measurement
Architecture (TIMA) was developed to close this vulnerability. TIMA leverages hardware
features, specifically TrustZone, to ensure that it cannot be preempted or disabled by
malicious software.
TIMA PeriodicKernelMeasurement(PKM)
TIMA PKM performs continuous periodic monitoring of the kernel to detect if legitimate
kernel code and data have been modified by malicious software. In addition, TIMA also
monitors key SE for Android data structures in OS kernel memory to detect malicious
attacks that corrupt them and potentially disableSE for Android.
Real-time KernelProtection(RKP)
RKP performs ongoing, strategically-placed real-time monitoring of the operating system
to prevent tampering of the kernel. RKP intercepts critical kernel events, which are then
inspected in TrustZone. If an event is determined to have impact on the integrity of the
OS kernel, RKP either stops the event, or logs an alert that tampering is suspected. This
alert information is included in remote attestation results sent to the MDM for IT Admins to
determine any further actions required by the enterprises security policies. This protects
against malicious modifications and injections to kernel code, including those that
coerce the kernel into corrupting its own data. RKP checks are performed in an isolated
environment that is inaccessible to the kernel, so potential kernel exploitations cannot be
extended to compromise RKP. Depending on the device model, this isolated environment
can be in the TrustZone Secure World or the hypervisor extensions.
5

WhitePaper
Figure 2 – Samsung KNOX Platform Security Overview
Remote Attestation
Remote Attestation (sometimes simply called attestation) is based on Trusted Boot and used
to verify the integrity of the platform. Remote attestation can be requested on-demand by the
enterprise's Mobile Device Management (MDM) system, typically before creating the KNOX
Workspace.
When requested, attestation reads the Trusted Boot collected measurement data and returns
them to the attestation requestor. To simplify the handling in MDM servers, the attestation
agent on the device produces a verdict indicating the overall status of attestation. It compares
these measurements to the factory values inside the TrustZone Secure World. Trusted Boot
measurement data includes a hardware fuse value that indicates if the device booted into an
unauthorized kernel in the past. Trusted Boot measurement data, along with the SE for Android
enforcement setting, forms the basis of the produced attestation verdict. This verdict, essentially
a coarse indication that tampering is suspected, is returned to the requesting MDM. In addition to
the verdict, the attestation data includes all the trusted boot measurements, RKP and PKM logs
that can indicate the presence of malicious software in the device, and other device information
that can be used to bind the attestation result to the device.
6

WhitePaper
The remote server requesting attestation provides a random nonce to prevent replay attacks.
The nonce, the attestation verdict, and the rest of the attestation data are returned to the
server, signed with the attestation certificate. The attestation certificate is signed by the
Device Root Key (DRK), a device-unique asymmetric key that is signed by a Samsung root key
through an X.509 certificate. This chain of certificates ensures that the attestation verdict
cannot be altered intransit.
Depending on the attestation verdict and the data, any further action is determined by
the enterprise's MDM security policy. The security policy might choose to detach from the
device, erase the contents of the secure application container, ask for the location of the
device, or any of many other possible security recovery procedures.
TrustZone-based Security Services
TrustZone-based Client Certificate Management (CCM)
TIMA CCM is a TrustZone-based security service also built on the basis of Trusted Boot. A key
feature of TIMA CCM is that if the Trusted Boot measurements do not match the authorized
values, or if the KNOX warranty bit is voided, the entire TIMA CCM functions shut down,
ensuring the protection of enterprise data in case of device compromise. TIMA CCM enables
storage and retrieval of digital certificates, as well as other operations using those certificates
such as encryption, decryption, signing, verification, and so on, in a manner similar to the
functions of a SmartCard. The CCM TrustZone code provides a PKCS #11 interface to the
Android OS, effectively emulating a smart card interface on a mobile device. The certificates
and associated keys are encrypted with a device-unique hardware key that can only be
decrypted from coderunning within TrustZone.
TIMA CCM provides the ability to generate a Certificate Signing Request (CSR) and the
associated public/private key pairs in order to obtain a digital certificate. A default certificate
is provided for applications that do not require their own certificate. TIMA CCM supports the
standard Android Key Chain API, and apps can use CCM by calling APIs that configure Android
to use an alternate Key Chain Provider.
All cryptographic components used by CCM are FIPS-140 2 compliant to meet US
government requirements for Mobile Device Fundamentals Protection Profile (MDFPP).
TrustZone-based KeyStore
Similar to TIMA CCM, TIMA KeyStore is a TrustZone-based security service also built on
the basis of Trusted Boot. The KeyStore provides applications with services for generating
and maintaining cryptographic keys. The keys are further encrypted with a device-unique
hardware key that can only be decrypted by the hardware from within TrustZone. All
cryptographic operations are performed only within TrustZone and are disabled if the system
is compromised as determined by Trusted Boot.
TIMA KeyStore supports the Android Key Store API. Application developers can continue to
use the familiar Android KeyStore APIs and specify that the TIMA KeyStore is used to provide
theservice.
7

WhitePaper
TrustZone-based On-DeviceEncryption
The KNOX platform further strengthens the full-device encryption capability offered by the
Android platform. In addition to successful password authentication, the system integrity
as determined by Trusted Boot is also verified before the data is decrypted. This feature is
available only if the enterprise IT Admin activates encryption via the MDM. This ensures that
all device data is protected in the unlikely event that the operating system is compromised.
Application Security
In addition to securing the platform, Samsung KNOX provides solutions to address the
security needs of individualapplications:
• KNOX Workspace
• Virtual Private NetworkSupport
• SmartCard Framework
• Single Sign-On
KNOX Workspace
Samsung KNOX Workspace is a defense-grade dual persona container product designed
to separate, isolate, encrypt, and protect enterprise data from attackers. This work/play
environment ensures work data and personal data are separated and that only the work
container is managed by the enterprise. Personal information such as photos and messages
are not managed or controlled by the IT department. Once activated, the KNOX Workspace
product is tightly integrated into the KNOX platform.
Workspace provides this separate environment within the mobile device, complete with its
own home screen, launcher, applications, and widgets.
Applications and data inside Workspace are isolated from applications outside Workspace,
that is, applications outside Workspace cannot use Android inter-process communication or
data-sharing methods with applications inside Workspace. For example, photos taken with
the camera inside Workspace are not viewable in the Gallery outside Workspace. The same
restriction applies to copying and pasting. When allowed by IT policy, some application data
such as contacts and calendar data can be shared across the Workspace boundary. The end
user can choose whether to share contacts and calendar notes between Workspace and
personal space; however, IT policy ultimately controls this option.
8

WhitePaper
Figure 3 – Samsung KNOX Personal Environment and KNOX Workspace Enviornment
The enterprise can manage Workspace like any other IT asset using an MDM solution. This
container management process is called Mobile Container Management (MCM). Samsung
KNOX supports many of the leading MDM solutions on the market. MCM is affected by setting
policies in the same fashion as traditional MDM policies. Samsung KNOX Workspace includes
a rich set of policies for authentication, data security, VPN, e-mail, application blacklisting,
whitelisting, and soon.
The KNOX 2.X platform features the elimination of application wrapping, which was used by
KNOX 1.0 and many other competing solutions. This is achieved by leveraging technology
introduced by Google in Android 4.2 to support multiple users on devices. It reduces
the barrier to entry for independent software developers wishing to develop and deploy
applications for KNOXWorkspace.
At the time of container creation, IT Admins can choose the UI style of the container (folder
or launcher style), and can also prevent end users from changing the style.
9

WhitePaper
KNOX Workspace can also be configured for container-only mode. In this mode, the entire
device experience is restricted to the Workspace. This mode is suitable for industries such as
health care, finance, and others who provide devices for employees that seek to restrict
access to businessapplications.
Workspace also has a two-factor authentication process. The user can configure the
Workspace to accept a fingerprint as the primary authentication factor for the container with
a PIN, password or pattern as a second factor.
The KNOX platform also supports two containers, thus meeting the needs of professionals
that use their own devices for corporate use Bring Your Own Device (BYOD) and have multiple
employers, such as doctors orconsultants.
New features include the ability to enable Bluetooth®
and Near Field Communication (NFC)
inside Workspace. NFC enables a device to act as a SmartCard-based credential for use cases
such as physical access and access to IT accounts. Bluetooth can be used to communicate
with connected devices, and supports Bluetooth profiles that enable use cases beyond music
and calls inside the KNOX Workspace. Examples include printing, file sharing, and external card
readers. External SD cards can also be enabled with security restrictions.
Apps inside Workspace can also connect with USB accessories such as a USB printer. For
security purposes, IT Admins must explicitly allow USB between container apps and external
storage. The MDM default for mass storage is set to OFF, and is controlled by enterprise IT
Adminpolicy.
For Samsung Note users, S-Pen Air Command is also supported inside Workspace for writing
memos, adding app shortcuts (personal apps only), screen capture, and writing notes on a
screen capture (depending on IT policy).
KNOX caller ID for incoming calls when in Personal mode can also be configured by IT
Admins to display caller ID information derived from personal contacts and KNOX Workspace
contacts.
Figure 4 – Samsung KNOX Workspace
10

WhitePaper
Google Play forWork
IT Admins can install Google Play for WOrk inside KNOX Workspace for app management to
silently install and uninstall apps and blacklist or whitelist apps. Enterprise employees can
download apps in KNOX Workspace that are approved by IT Admins.
Google Voice for apps inside the KNOX container allows users to use voice recognition for
input in addition to the touchscreen keyboard.
Sensitive Data Protection and KNOX Chamber
KNOX defines two classes of data – protected and sensitive. All data written by apps in the
secure Workspace is protected. Protected data is encrypted on disk when the device is
powered off. In addition, the decryption key for protected data is tied to the device hardware.
This makes protected data recoverable only on the same device. Furthermore, access controls
are used to prevent applications outside the KNOX Workspace from attempting to access
protected data.
Even stronger protection is applied to sensitive data. Sensitive data remains encrypted as
long as the Workspace is locked, even if the device is powered on. When a user unlocks KNOX
Workspace using their password, Sensitive Data Protection (SDP) allows sensitive data to be
decrypted. When the user re-locks the Workspace, SDP keys are cleared. The SDP data
decryption key is tied to both device hardware and to the user input. Therefore, the data is
recoverable only on the same device and with user input.
SDP can be used in one of two ways. First, all emails received are considered sensitive, and are
immediately protected by SDP encryption. Emails received when the Workspace is locked,
are immediately encrypted, and can only be decrypted the next time Workspace is unlocked.
The second way to use SDP is through the KNOX Chamber. The Chamber is a designated
directory on the file system and a user-accessible folder inside Workspace. Any data placed
into the Chamber is automatically marked as sensitive and protected by SDP.
Third-party app data can also be encrypted when a device is locked and decrypted when a
device is unlocked to prevent data leakage if a device is lost, stolen, or re-used. Keys required
for data decryption when unlocking a device are based on the user password.
KNOX Quick Access
On Samsung Galaxy S6 devices, based on proximity of a registered and connected Gear device,
KNOX Quick Access extends the unlock period of the KNOX Workspace, thereby reducing the
frequency with which the end user must enter password credentials.
Shareddevices
Manyenterprises such as hospitals, banks, and airlines use shared devices for employees.
KNOX supports the use of shared devices so IT Admins can manage device and security
policies, and install apps with an MDM.Each employee can login separately with an Active
Directory ID and password, which is also integrated with SSO. For security and privacy, all
user data is deleted when each employee logs out of the shared device.
KNOX Active Protection (KAP)
End users can activate or deactivate KNOX Active Protection (KAP) via the Smart Manager app
on devices not managed by an MDM.KAP uses both Real-time Kernel Protection (RKP) and DM
Verity, a feature that provides integrity checking for system code and data. On MDM-managed
devices, KAP is alwaysenabled.
11

WhitePaper
Android for Work on a Samsung device
Android for WorkManaged Profiles on a Samsung device benefit from key KNOX security
modules that protect the device and sensitive work data at all times. KNOX enables Android
for Workprotection with the following KNOX features:
12
y RKP actively prevents kernel code modification
y PKM periodically checks kernel codeintegrity
y DM-Verity verifiies the integrity of applications and data stored on the critical
system partition
y Trusted Boot measures each software component during boot-time and securely
stores the cryptographic hash of the next component in TrustZone memory before
loadingit.
y Sensitive Data Protection APIs are available for apps in Managed
Profiles. The native email app enables SDP once it's installed inside Managed Profiles.
y TIMA and CCM provides the TrustZone-based KeyStore as the default for storing
certificates such as VPN and email app certificates.
y Access to Managed Profiles depends on the integrity of the devie.
If the integrity check fails at the time of creating Android for Work,it is not allowed. If
an integrity check fails after Andriod for Workis installed, the device is not allowed
toboot.
Android for Workon a Samsung device does not require a KNOX license activation fee.
KNOX security enhancements for existing Android for WorkManaged Profiles areupdated
seamlessly with Over-the-Air (OTA)updates.
Virtual Private Network Support
The KNOX platform offers additional comprehensive support for enterprise Virtual Private
Networks (VPN). This support enables businesses to offer their employees an optimized,
secure path to corporate resources from their BYOD or Corporate-Owned Personally Enabled
(COPE)devices.

WhitePaper
KNOX offers the following VPN features for IPsec and SSL:
y Per-appconnections
y On-demand connections
y Always-onconnections
y Device-wideconnections
y VPN chaining (nestedconnections)
y Blocking routes to prevent data leakage if a mandatory VPN connection drops
y Pushing VPN profiles to multiple managed devices
y Traffic usagetracking
y HTTPProxy
KNOX supports the ability to configure VPN connections to enforce redirection of web
traffic through an HTTP proxy server, allowing enterprises greater visibility into network
traffic and device usage patterns of employees. The KNOX VPN framework supports VPN
configurations using a static proxy server IP and port, and web proxy authentication.
The KNOX platform offers broad feature support for the IPSec protocol suite including:
y Internet Key Exchange (IKE and IKEv2)
yIPsec IETF RFCs – IKEv1
y IKEv1 – Mainand aggressive IKE exchange modes with pre-shared key, certificates,
Hybrid RSA, andEAP-MD5 authentications
y I IKEv2 with PSKand certificate-based authentication
y IKEv2 – Pre-shared key, certificates, EAP-MD5 EAP-MSCHAPv2 authentication
methods, and mobileextensions
y Triple DES (56/168-bit), AES (128/256-bit) encryption with MD5 or SHA
y IKEv1 Suite B Cryptography supported with PSK and ECDS signature-based
authentications
y IKEv2 Suite B Cryptography supported with ECDSA signatures
Because a large number of enterprises have deployed Secure Socket Link (SSL) VPNs , the
KNOX platform provides support for leading SSL VPN vendors. As SSL implementations are
proprietary, KNOX features a generic VPN framework which enables third-party SSL vendors
to provide their clients as plug-ins. Enterprise IT Admins use KNOX MDM policies to install
and configure a specific SSL VPN client.
13

WhitePaper
Figure 6 – Per Application VPN inKNOX
Figure 5 – Multi-Vendor Support in KNOX
The per-application VPN feature in the KNOX Workspace container enables the enterprise to
automatically enforce the use of VPN only on a specific set of applications. For example, an
IT Admin can configure an employee’s device to enforce VPN for only business applications.
Such a configuration ensures that the data from the user’s personal applications do not use
the VPN and overload the company’s intranet. At the same time, user privacy is preserved
because personal data does not enter the enterprise network.
The per-app VPN feature can also be applied to the KNOX Workspace container for all or a
subset of the applications in the container.
14

WhitePaper
SmartCard Framework
The United States Department of Defense (US DoD) has mandated the use of Public Key
Infrastructure (PKI) certificates for employees to digitally sign documents, encrypt and decrypt
e-mail messages, and establish secure online network connections. These certificates are
typically stored on a SmartCard called the Common Access Card (CAC).
The Samsung KNOX platform provides applications access to the hardware certificates on the
CAC via standards-based Public Key Cryptography Standards (PKCS) APIs. This access process
enables the use of the CAC card by the browser, e-mail application, and VPN client, as well as
other custom government applications.
Other enterprises have growing interest to use SmartCards for the same purpose, especially
those that require high levels of security and information protection.
The KNOX platform provides improved SmartCard compatibility via a software framework that
allows third-party SmartCard and reader providers to install their solutions into the framework.
Figure 7 – Samsung KNOX support forSmartcards
15

WhitePaper
Single Sign-On
Single Sign-On (SSO) is a feature that provides common access control to several related, but
independent software systems. The user logs in once and has access to all systems without
being prompted to log in again. For example, SSO allows access to the Workspace container
(and participating apps that require credentials within the container) with one password.
SSO shares centralized authentication servers that all other applications and systems use for
authentication purposes. It combines this with techniques to ensure that users do not have to
actively enter their credentials more than once. SSO reduces the number of user names and
passwords a user must remember, and reduces IT costs with fewer help desk calls about login
credentials.
KNOX Identity and Access Management (IAM) provides a comprehensive and flexible SSO
solution to support enterprise applications on Samsung mobile devices. This framework was
created to reduce the complexity for enterpriseapplications to support SSO on mobile devices.
There are many Identity Providers with different SSO solutions and with various support
protocols such as SAML, OAuth, OpenID, etc. They each distribute their Software Development
Kits (SDKs) to mobile app developers, however, developers must customize multiple versions
of their apps to support different SSOsolutions.
The KNOX generic SSO framework is a bridge between the Identity Providers and software
developers that allows a single version of an app to work with any SSO solution. The KNOX
SSO solution provides a unified API for SSO token retrieval and management, called getToken.
Samsung partners with leading Identity Partners including Microsoft (Azure Active Directory),
CA Technologies, and Centrify. Identity Providers plug their Android Application Package (APK)
authenticators into the KNOX generic SSO framework and each authenticator works as a
proxy to process SSO authentication requests and responses, thereby eliminating the need
for developersto create multipleversions of their apps.
Mobile Device Management
Enrolling mobile devices into the enterprise network and remote management of these
devices are key aspects of an enterprise mobility strategy. Key device management features
of the KNOX platforminclude:
y Comprehensive management with over 1500 MDMAPIs
y Active Directory integration
y KNOX Mobile Enrollment for a faster and intuitive user experience, including bulk
enrollment to assist IT Admins to quickly enroll many employees at once
y Enterprise Billing to separate work and personal data costs
16

WhitePaper
Comprehensive Management Policies
The various policy groups are classified into two major categories: Standard and Premium. The
Standard Policy suite represents continuous enhancements Samsung developed over Google
Android management capability since 2009. The SDK for these policy APIs is available to MDM
vendors and other interested ISVs free of charge. Further, no runtime license fee is associated
with these APIs.
The KNOX Premium Policy suite is the collection of policy groups offering advanced
capabilities such as management and control of the KNOX Workspace, security features such
as the Trusted Boot-based TIMA KeyStore and Client Certificate Manager, Per-application VPN,
and so on. The SDK for these policy APIs is also available at no charge; however, enterprises
using these features are required to purchase a KNOX License that is verified on the device at
runtime.
The KNOX Audit Log meets MDFPP 2.0 audit requirements. IT Admins can select a set of
events to audit and periodically push logs to the server.
Some of the events include:
y Administrative actions such as creating containers, password setting policies for
devices and containers, app installations andremoval
yCertificate failure and key generation
y Adding and removing accounts
y Attempts to exchange files overWi-Fi
Active Directory integration
KNOX provides an option for the IT Admin to choose an Active Directory password as the
unlock method for KNOX containers. This has two important benefits. First, it allows IT
Admins to use a one-password management policy for desktop and mobile devices. Second,
the end user only needs to remember one password to access all services offered by the
employer, thereby reducing employee password fatigue and improving productivity.
At the heart of this feature is the proven industry-standard Kerberos protocol. Active
Directory is the most widely-deployed enterprise grade directory service that has built-in
support for Kerberos. KNOX provides a set of Workspace creation parameters to configure
Workspace to use the Active Directory password as the unlock method. Additionally, IT
Admins can also configure Single Sign-on for services inside Workspace, along with the
unlockmethod.
Active Directory passwords can be changed by the user on the mobile device from the
settings menu inside the KNOX Workspace container. When SSO is configured, the password
change does not require entering the password a second time.
17

WhitePaper
KNOX Mobile Enrollment
Enrolling an Android device into a company’s MDM system typically begins with a user
downloading the agent application from the Google Play store, then configuring it for
authentication. Enterprises are facing increasing help desk calls as more and more users are
activating mobile devices for work. When presented with prompts, privacy policies, and
license agreements, users might experience difficulties during the process, resulting in a poor
overall experience.
The KNOX platform provides a simplified enrollment solution for supported MDMs that is
streamlined and intuitive and eliminates many steps and human error.
The enrollment process happens via either self-discovery using an email domain, or
employees are provided with an enrollment link sent by e-mail, text message, or through the
company's internal or external website. Once the link is clicked, users are prompted to enter
their corporate e-mail address. This action triggers the display of all required privacy policies
and agreements. After accepting the terms, users enter a corporate account password for
authentication from the enterprise. Any agent application required is automatically
downloaded andinstalled.
Samsung KNOX Mobile Enrollment allows IT Admins to enroll hundreds or thousands of
employees at the same time. Samsung provides a web tool and an application to scan package
bar codes (the device IMEI). This enrollment method is targeted for devices purchased for
COPE enterprises and for supported carriers and resellers.
Another option for IT Admins includes using a master device to automatically enroll devices
using NFC. The master device is configured by downloading an app from Playstore. Each
device is enrolled to an MDMprofile selected by the IT Admin.
MDM vendors can take advantage of this feature to simplify the onboarding process for
enterprise users, significantly improve the user experience, and reduce support costs.
KNOX Mobile Enrollment supports multiple MDM configurations per account. With complex
device environments, and multiple MDM profiles or configurations, KNOX Mobile Enrollment
gives IT Admins the ability to prepare hundreds of devices and get them connected to the
right MDM with ease. End users only need to turn on the device and connect to the network.
KNOX Mobile Enrollment takes care of activation without users needing to do a thing.
Enterprise Billing
Enterprise Billing provides enterprises a mechanism to separate enterprise data usage from
personal data usage. This enables enterprises to compensate their employees for costs
generated because of work, particularly in BYOD cases, or to only pay for work-related data
in COPEcases.
The KNOX platform supports Enterprise Billing from KNOX version 2.2 or above, and requires
MDMsupport.
18

WhitePaper
Enterprises configure two Access Point Name (APN) gateways. One APN is for data associated
with enterprise-approved apps, and a different APN is for all other personal data. Enterprises
must first register with a network operator’s enterprise billing service. Once a new APN is
provisioned for business use, KNOX Workspace can be enabled for that dedicated APN. IT
Admins can also select individual apps inside or outside Workspace to use data over the
enterpriseAPN.
Enterprise billing configured with a dedicatedAPN:
y Supports dual-APN Enterprise Billing for carriers using IPv6networks.
y Separates data usage over the mobile internet for 2G/3G/4Gconnections
y Routes all data traffic from KNOX Workspace over the enterpriseAPN
y Provides the capability to select individual apps inside or outside KNOX Workspace
to use data over the enterprise APN
The enterprise APN can also be configured to allow or not allow roaming. When roaming is
enabled, personal data is routed through the default APN, and enterprise data is routed
through a dedicated enterprise APN. By default, roaming over the enterprise APN is disabled.
When a user is roaming in a single Packet Data Protocol (PDP) network, all enterprise apps are
automatically routed to the personal APN for work continuity.
If enterprise apps use a VPN connection to the network, the VPN profile can be configured to
route data through the enterpriseAPN.
Dual SIM devices can also be enabled for KNOX Enterprise Billing. The primary, or first SIM slot,
is automatically selected to configure an APN and activate Enterprise Billing on the device.
To avoid personal use of a SIM card, IT Admins can lock the SIM card with a unique PIN
combination. This ensures that the SIM can only be used for enterprise billing on the
authorized device. In addition, dedicated enterprise APNs are restricted, and APN settings are
not visible or editable on the device.
Users can check personal and enterprise data usage on a KNOX device in the Settings menu.
To view data usage, employees can go to Settings > Data Usage > Mobile Tab (personal) or
Enterprise Tab(work).
19

WhitePaper
Certifications
20
FIPS140-2
Certification
Issued by the National Institute of Standards and Technology (NIST), the
Federal Information Processing Standard (FIPS) is a US security standard that
helps ensure companies that collect, store, transfer, share, and disseminate
sensitive but unclassified (SBU) information and controlled unclassified
information (CUI) can make informed purchasing decisions when choosing
devices to use in their workplace.
Samsung KNOX meets the requirements for FIPS 140-2 Level 1 certification
for both data-at-rest (DAR) and data-in-transit(DIT).
DISA ApprovedSTIG The Defense Information Systems Agency (DISA) is an agency within the US
DoD that publishes Security Technical Implementation Guides (STIGs) which
document security policies, requirements, and implementation details for
compliance with DoDpolicy.
DISA approved the STIG for Samsung KNOX 2.x.
DISAApproved
ProductList
DISA has approved select KNOX-enabled devices to the US DoD Approved
Products List(APL).
NOTE: Select Samsung KNOX-enabled devices and tablets are certified
under the National Information Assurance Partnership (NIAP) Common
Criteria (CC) Mobile Device Fundamental Protection Profile(MDFPP).
CommonCriteria
Certification
The Common Criteria for Information Technology Security Evaluation,
commonly referred to as Common Criteria, is an internationally-recognized
standard for defining security objectives of information technology products
and for evaluating vendor compliance with these objectives. A number of
Governments use Common Criteria as the basis for their own certification
schemes.
Select Galaxy devices with KNOX embedded received Common Criteria (CC)
certification. The current CC certification targets the new Mobile Device
Fundamentals Protection Profile (MDFPP) of the National Information
Assurance Partnership (NIAP), which addresses the security requirements
of mobile devices for use in enterprise.
Samsung KNOX is approved by the United States government as the first
NIAP-validated consumer mobile devices to handle the full range of classified
information.

WhitePaper
Certifications
21
ANSSI Samsung KNOX has obtained first-level security Certification Sécuritaire de
Premier Niveau (CSPN) from the Agence nationale de la sécurité des
systèmes d’information (ANSSI). The CSPN methodology and criteria is
defined by ANSSI with evaluations run by ANSSI accredited testing labs.
ISCCC Samsung KNOX received the security solution certificate by the China
Information Security Certification Center (ISCCC). Samsung worked closely
withISCCCtodevelopthecertificationprocess,includingdevicerequirements
and security standards. By securing the critical ISCCC certification, Samsung
has a stronger foothold to garner mobile device contracts with China’s
regulated industries, including government authorities, ministries, and
finance.
CSfC Fifteen Samsung devices have been listed in the NSA/CSS's Commercial
Solutions for Classified Program (CSfC) for approved security components.
CESGApproved The CommunicationsandElectronicSecurityGroup(CESG)approvedKNOX-
enabled Android devices for United Kingdom government use.
FICORA Samsung devices withKNOX fulfillnationalsecurity requirementsas defined
by the Finnish National Security Auditing Criteria (KATAKRI II).
ASD Australian Signals Directorate: ASD endorsing the Protection Profile for
Mobile Device Fundamentals as well as recognizing evaluations against this
ProtectionProfile.
NOTE: For the most recent updates to Samsung KNOX certifications, see the followinglink:
https://www.samsungknox.com/en/security-certifications

WhitePaper
The Samsung KNOX platform addressed several CIO concerns aboutsecurityandmanagementof
Androiddevices:
- Trusted Boot, TIMA,and SE for Android protect the operating system and platform services
frommalwareattacksandhacking
- KNOX Workspaceprovides enhancedsecurityto enterprise applications bypreventingdata
leakage
- The per-application VPN features enables enterprises to enforce secure VPN connectivity
onlyforcorporate apps.
- The rich set of MDMpoliciesenables enterprise IT Admins to comprehensively manage the
device
The KNOX platform further raises the baron security, manageability, and ease-of-use with several
features andenhancements:
- Real-time kernelprotectionagainst maliciouskernelattacks
- Hardware-backed storage forcryptographykeysandclient certificates
- Remote attestation capability that allowsenterprises to verify the authenticityandintegrity
ofKNOXdevices during andafterenrollment
- KNOX Workspace runs unmodified Android applications and eliminates the need for
applicationwrapping
- Enterprise-controllable datasharing between personal spaceandenterprise container
- Amulti-vendor VPN frameworkthat allowsavarietyofthird-partyclients including SSL VPN
- AnopenSmartCardframeworkthatallowsenterprises tochoosefromanarrayofSmartCard
readers
Summary
22

WhitePaper
Copyright © 2016 Samsung Electronics Co. Ltd. All rights reserved. Samsung is a registered
trademark of Samsung Electronics Co. Ltd. Samsung KNOX is a trademark of Samsung Electronics,
Co., Ltd. in the United States and other countries. Specifications and designs are subject to change
without notice. Non-metric weights and measurements are approximate. All data were deemed
correct at time of creation. Samsung is not liable for errors or omissions. Android and Google Play
are trademarks of Google Inc. ARM and TrustZone are registered trademarks of ARM Limited (or its
subsidiaries) in the EU and/or elsewhere. iOS is a trademark of Apple Inc., registered in the U.S. and
other countries. Microsoft Azure and Microsoft Active Directory are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries. Bluetooth® is a
registered trademark of Bluetooth SIG, Inc. worldwide. NFC Forum and the NFC Forum logo are
trademarks of the Near Field Communication Forum. Wi-Fi is a registered trademark of the Wi-Fi
Alliance. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Cisco AnyConnect
is a registered trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain
other countries. KeyVPN Client is a trademark of Mocana Corporation. F5 Big IP-Edge Client is a
registered trademark of F5 Networks, Inc. in the U.S. and in certain other countries. Junos Pulse is
a trademark of Pulse Secure, LLC. strongSwan is an open source software under General Public
License as published by the Free Software Foundation. OpenVPN is a registered trademark of
OpenVPN Technologies Inc. All brands, products, service names and logos are trademarks and/or
registered trademarks of their respective owners and are hereby recognized and acknowledged.
Samsung Electronics Co.,Ltd.
416, Maetan 3-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-772, Korea
Samsung Electronics Co., Ltd. is a global leader in technology, opening new possibilities for people
everywhere. Through relentless innovation and discovery, we are transforming the worlds of
televisions, smartphones, personal computers, printers, cameras, home appliances, LTE systems,
medical devices, semiconductors and LED solutions. Weemploy 236,000 people across 79 countries
with annual sales exceeding KRW201trillion. To discover more, please visit www.samsung.com
For more information about Samsung KNOX, visitwww.samsung.com/knox
About Samsung Electronics Co., Ltd.
23
Version Date
An Overview of the Samsung KNOX Platform_V1.14 Feb. 22,2016
An Overview of the Samsung KNOX Platform_V1.13 Nov. 12, 2015
An Overview of the Samsung KNOX Platform_V1.12 Sept. 2,2015

An overview of the samsung knox platform v1 14

More Related Content

What's hot

Similar to An overview of the samsung knox platform v1 14

More from Javier Gonzalez

Recently uploaded

An overview of the samsung knox platform v1 14