<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cheng Luo on Medium]]></title>
        <description><![CDATA[Stories by Cheng Luo on Medium]]></description>
        <link>https://medium.com/@chengluo?source=rss-1273d858bc5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RUc8Lc9azSyT8JNFhM_goQ.jpeg</url>
            <title>Stories by Cheng Luo on Medium</title>
            <link>https://medium.com/@chengluo?source=rss-1273d858bc5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:28:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chengluo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Knox E-FOTA on MDM Integration Explained]]></title>
            <link>https://medium.com/@chengluo/knox-e-fota-on-mdm-integration-explained-b937005b4d7d?source=rss-1273d858bc5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b937005b4d7d</guid>
            <category><![CDATA[e-fota]]></category>
            <category><![CDATA[android-enterprise]]></category>
            <category><![CDATA[samsung-knox]]></category>
            <category><![CDATA[firmware-update]]></category>
            <dc:creator><![CDATA[Cheng Luo]]></dc:creator>
            <pubDate>Fri, 21 Feb 2020 12:20:00 GMT</pubDate>
            <atom:updated>2020-02-21T20:30:49.039Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2017, Samsung announced the Enterprise Firmware Over The Air (E-FOTA) service to help enterprise IT admins to remotely control the version of Android OS running on corporate devices. Since then, E-FOTA has been widely adopted by many enterprises and organisations.</p><p>If you are familiar with E-FOTA, there are two flavours of E-FOTA service: E-FOTA on MDM and E-FOTA Advanced. E-FOTA on MDM offers the user a integrated UI within your chosen EMMs, but the UX and available features are highly depended on the integration from the EMM. You manage E-FOTA Advanced through a separated admin console, but you gain more features and granularities in terms of how to manage your firmware update campaigns (aka. firmware management policies). In this article, we will walk through some of the E-FOTA on MDM differences between major EMMs, and hopefully give you a good understanding of how E-FOTA works together with EMMs. And more importantly, help you to make the decision to choose which flavours of E-FOTA when you considering to manage your devices.</p><h3>Firmware management explained</h3><p>Most of enterprise IT admins is facing the challenge of keeping its mobile fleet most up to date while maintaining the stability and productivity of business apps. The conventional way of how they manage this in the PC time is to control when the updates will be installed on user PCs after a thorough test and approval process. So the updates don’t impact the business. In the mobile world, this process is not that trivial because both iOS and stock Android iOS don’t offer the level of control that IT admin needs. The only a few options IT admins have is to delay or turn off the OS updates (including security patches). The disadvantages are obvious. On one hand, you might have less secure software running on your fleets if you delay or turn off the firmware update. On another hand, your business apps might not ready or compatible with the new version of OS if you allow the firmware updates without proper vetting and review process.</p><p>The answer relies in E-FOTA. The firmware is generated by Samsung to make sure the device runs properly and securely. When there is a new version of firmware released by Samsung, the delta is generated and registered on the FOTA server. In the event of the firmware update, for example, a bug fix, a OS upgrade, or a security patching, the delta will be delivered to the devices via the Internet connection. When the device received the delta, it will apply the necessary changes to the firmware.</p><p>The delta is created by comparing the difference between the existing version of firmware and the target version of firmware to reduce the size of FOTA delivered over the network. Typically, devices receive their firmware updates from their service provider, through a Samsung Business-To-Consumer (B2C) FOTA server. With Knox E-FOTA, enterprises get updates from a Samsung Business-To-Business (B2B) FOTA server. For details of how E-FOTA works, please refer to the document [here](https://docs.samsungknox.com/dev/knox-e-fota/about-e-fota.htm).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*FSzuRVgTkhtOqCvnjWA0Fw@2x.jpeg" /></figure><h3>E-FOTA on MDM</h3><p>When it comes to the firmware management, the first place you think of is probably the EMM. That’s why we launched E-FOTA on MDM at the first place. But it can be complicated when EMMs takes their own approaches to integrate the E-FOTA service. The difference can be found in the UX/UI design, version of E-FOTA APIs used, how campaign is managed, and visibility of E-FOTA campaigns. We made a table (credit @Simon Minshall) to compare the above differences across major EMMs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7NXu6BqokWtn5EjncmrhQ@2x.jpeg" /></figure><p>In this table, you can see there are three APIs related to device firmware update functions:</p><ul><li><strong><em>serverInit()</em></strong> in E-FOTA v1: To use this API, EMMs have to provide mandatory information such as the target firmware version, the campaign start date &amp; time, and campaign end date &amp; time.</li><li><strong><em>forceUpdate()</em></strong> in E-FTOA v2: Comparing to the <em>serverInit()</em> API in v1, the campaign start and end dates are not mandatory anymore. Instead, a new parameter called networkType is introduced, which allows the EMM to specify whether the firmware updates is allowed on any network type or WiFi only. Additional to the revised firmware update API <em>forceUpdate()</em> in v2, the <em>forceUpdateSummary()</em> and <em>forceUpdateDetail()</em> APIs are also introduce to provide more insights returned from a particular campaign.</li><li><strong><em>setAllowedFOTAVersions()</em></strong> in the Knox SDK: by calling this API, you switch the device from getting firmware from the Samsung B2C FOTA server to the B2B Knox E-FOTA server. User can not update device to the higher version of allowed version set by this API. The device will still check whether there is a new version of firmware in a weekly basis.</li></ul><p>Once you understand the above three APIs and their differences, it is fairly straight forward to understand which version of APIs the EMM integrated, and more importantly, what information needed while creating E-FOTA campaigns across EMMs and the expected behaviours. For example, a scheduled window is mandatory when you create the E-FOTA campaign using Blackberry UEM, which indicate it uses the v1 API. While creating the E-FOTA campaign using VMWare Workspace One, you can specify the network type. This means Workspace One integrated with v2 API. But once you click the “Install on demand” option, there is no additional information need other than the target version. We can assume that it calls the <em>setAllowedFOTAVersion()</em> API with the target version selected from the Device Updates list. The new firmware will be upgraded when the user manually click the “Software update” from the Settings app, or the device requests firmware upgrade from the E-FOTA server once a week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*_QitItUKOi9YpxGf3N-BTg@2x.jpeg" /></figure><h3>E-FOTA Advanced with MDM</h3><p>It’s relatively simple to understand how E-FOTA Advanced works together with EMMs. The only dependence is how the E-FOTA Advanced firmware management agent is installed on the device via EMMs. The prerequisites of E-FOTA Advanced is that the firmware management agent has to be installed on the device side, and launched by the EMM at least once to register the device to the E-FOTA server. Due to the Google policy, the firmware management agent cannot be published on the Google Play store. That means EMMs have to have the capability to install apps bypassing the Managed Google Play store when enrolling the device using Android Enterprise activations. On the table, we made a separate columns for the E-FOTA Advanced in terms of firmware management agent installation and auto-launch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b937005b4d7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The essential guide on deploying Samsung devices with Microsoft InTune]]></title>
            <link>https://medium.com/@chengluo/the-essential-guide-on-deploying-samsung-devices-with-microsoft-intune-4fbbce47f5da?source=rss-1273d858bc5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fbbce47f5da</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[oemconfig]]></category>
            <category><![CDATA[samsung-knox]]></category>
            <category><![CDATA[android-enter]]></category>
            <dc:creator><![CDATA[Cheng Luo]]></dc:creator>
            <pubDate>Mon, 12 Aug 2019 21:31:24 GMT</pubDate>
            <atom:updated>2019-09-15T17:50:18.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>An essential guide on deploying Samsung devices with Microsoft Intune</h3><h3>Introduction</h3><p>Since Microsoft bundled InTune service with its Microsoft 365 offerings, there are more companies moving or considering moving their EMM to InTune. The benefits are obvious, for example, a single console to manage both InTune and other Microsoft services, the cost of EMM is low or even free depending on which bundle you purchased, Microsoft application management is much simpler because it’s better integrated with Intune.</p><p>But these benefits come with a cost — limited IT policy support on Android Enterprise comparing to other major EMM vendors. This does not surprise me since the EMM business seems not the core of Microsoft. In this blog, I will explain how you can overcome some of limitations utilizing the additional features offered via Knox products on Samsung devices.</p><h3>Device Enrollment Support</h3><p>Intune has improved substantially in the last few months. The most noticeable one being the support around Samsung Knox Mobile Enrollment (KME) service. Intune supports both the legacy Knox enrolment and Android Enterprise enrolment using KME. You can also add the token information on the KME profile, which further streamlines the Intune enrollment experience, for example, users don’t need to manually scan the QR code for the enrolment token, or type in user names.</p><p>Here are the details taken from Microsoft Intune help document of how to setup a KME MDM profile:</p><h4>For Android Enterprise</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWHMpaIwA8TBuszqOL3hiA.png" /></figure><h4>For Android legacy Device Admin</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*znoXciwMiqzc1ClxDhO8DQ.png" /></figure><h3>Android Enterprise Support</h3><p>At the time of writing, Intune supports three types of enrolment from Android Enterprise, 1) Personal device with work profile, 2) corporate-owned dedicated devices, and 3) corporate-owned, fully managed user devices.</p><p>Behind jargons of Android Enterprise terminologies, the enrolment type simply reflects the device ownership and its use cases. <strong><em>Personal devices with work profile</em></strong> is meant to be used for BYOD deployment. IT admins don’t have the right to manage or control personal devices. But instead to create a separated container for work apps and data. <strong><em>Corporate-owned dedicated devices </em></strong>is meant<strong> </strong>for the device to be used as a kiosk or customer-facing device. There is no user profile (aka user account) attached to the device. While <strong><em>corporate-owned, fully managed user device</em></strong> is meant for the Corporate Liable (CL) device used by employees, but everything is managed by IT. Hence it’s popular among the most restricted use cases such as regulated users in banks.</p><p>The second noticeable improvement is from the Knox Service Plugin (KSP) support. KSP is based on the Android Enterprise OEMConfig which allows EMM to support Knox Platform for Enterprise (KPE) features. For more information about KSP can be found <a href="https://www.samsungknox.com/en/blog/samsung-knox-platform-for-enterprise-evolution-to-5g-enterprise-iot-and-ai">here</a></p><p>Intune has done a good job in terms of integrating KSP. It supports both configuring KSP using the native Configuration designer UI or the JSON editor. When you use the native Configuration designer, you can see clearly the 4 levels of nesting of OMEConfig from KSP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--9FoIl58gU-d9aVkCFBfA.png" /></figure><p>As I mentioned above, the limited support from Intune on the Android Enterprise fully managed device enrollment type, such as lacking native VPN client support, certificate management, proxy and firewall settings, and other advanced configuration such as APN and DeX are made available to Samsung devices via KSP.</p><p>IT admins from companies who deploy Samsung devices can use these advanced features while still enjoy the unified Intune console experience.</p><h3>The missing piece of the puzzle — Knox Configure</h3><p>If you are Android Enterprise veterans, you will notice that the fourth Android Enterprise enrolment type — <strong>fully managed device with work profile</strong>, which<strong> </strong>is currently not supported by Intune. If your organization is keen to enable the personal use on a corporate owned device, you can have a workaround by using the personal device with work profile enrollment type from Intune in conjunction with Knox Configure. The benefits of this combination are that you get the conveniences and security by creating the Android Enterprise Work profile, but you still can manage the device level policies from Knox Configure. This workaround fills the gaps of lacking COMP (Corporate Owned Managed Profile) support.</p><p>To summary the overall benefits of Samsung Knox add-ons in Intune, here is the table explains the 4x types of Android Enterprise enrollment and how Knox products can help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqWzSdkuXH-u562a3fhsjg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fbbce47f5da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security doesn’t have to be paid]]></title>
            <link>https://medium.com/@chengluo/security-doesnt-have-to-be-paid-eeb2f5bfabca?source=rss-1273d858bc5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeb2f5bfabca</guid>
            <category><![CDATA[knox]]></category>
            <category><![CDATA[emm]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Cheng Luo]]></dc:creator>
            <pubDate>Thu, 23 Nov 2017 22:50:14 GMT</pubDate>
            <atom:updated>2017-11-23T22:53:19.350Z</atom:updated>
            <content:encoded><![CDATA[<p>Have been working in the mobile enterprise business for the last few years, I often heard IT managers talking about how to get the security bits correct. This is definitely a good way of thinking and starting the enterprise mobility, but security is not just about getting the design, architecture and initial deployment right, it’s about different way of thinking your IT and business, and most importantly how your employees think.</p><p>With most of mobility projects I involved, the first question to answer is always about how to improve the users experience of your employees and your customers, how to make your employee more productive while adopting the mobile working style, and make your customers more satisfied while using your services on mobile.</p><p>Then it’s about how to securely provide your services at each stage. Take the example of rolling out corporate phones in your company. No doubt the first thing to think of from a IT perspective is whether to embrace the buzz word of BYOD, or stay peace mind with fully controlled COBO, or even have a mix of COPE encourage more use of phones instead of ending as expensive desktop. None of this question can be answered without thinking your employees experience, and no one model is absolutely better than others. With the more and more regulatory around finance and data privacy, we assume the COBO and COPE are becoming more controllable and adaptive model when it comes to the IT end users device policy.</p><p>Let’s walk through the journey of a IT manager of deploying his/her digital transformation project. Journey starts with enrolling devices.</p><p><strong>Use dedicate WiFi network or private APN for enrollment when needed</strong></p><p>For these security critical customers, they might prefer to provide a dedicated WiFi or private APN for enrollment purpose only. A dedicate WiFi network for enrollment is good in the sense of employees work at a remote site without a IT team, or companies provide self-service IT service employees for ordering and enrolling their devices to the EMM. It’s a challenge to provision the WiFi or APN information before a device is enrolled.</p><p>Of course, you can setup a certificate based authentication WiFi network which might require a Active Directory Domain Service (AD DS) and Network Police Server (NPS) to make it properly functioning. You can even choose the private APN service from your ISP or operators to achieve even securer enrollment. But it’s cost money.</p><p>There is a simple solution from Samsung called Knox Configure (KC) which doesn’t any additional services. You can simply upload the WiFi SSID and password information to a KC profile. Devices registered with KC will automatically receive the WiFi configuration information prior to the KME enrollment process.</p><p>You can achieve further security by hidding your enrollment WiFi SSID, so that none KC registered device will not able to connect to the dedicate enrollment WiFi network. Bear in mind, KC can configure far more than just WiFi SSIDs. There are tons of other settings you can pre-configure before enroll devices to EMMs. To find more information, go to <a href="http://www.samsungknox.com/">www.samsungknox.com</a></p><p><strong>Enforce only corporate device enrollment</strong></p><p>Automated mobile enrollment service such as Apple Device Enrollment Program (DEP) and Samsung Knox Mobile Enrollment (KME) have became the de facto way to enroll your mobile devices to EMMs. It simplifies the process of downloading and installing MDM agents on the device, push the MDM configurations onto the device, and making sure the device is provisioned before IT allowing the device to be connected to the corporate network. In this sense, the enrollment service is the gatekeeper of your security. So how to get it right then?</p><p>First and foremost thing the IT manager needs to consider is to enforce only corporate devices can be enrolled to your EMM. Different EMM has different way to achieve this. Take an example of AirWatch,</p><p>Step 1: There is a settings under the Devices &amp; Users &gt;Enrollment, you can check the Registered Device Only button to allow only registered device from DEP or KEM device to enroll.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CON1fYDoMiK2Fymxbugz8A.jpeg" /><figcaption>AirWatch Enrollment Settings</figcaption></figure><p>Step 2: You can add devices into the registered or whitelisted devices list under the Devices&gt;Lifecycle&gt;Enrollment Status tab. Devices registered via DEP will automatically appears under the Registered device. For KME, you can using batch import to manually import your KME device into AirWatch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3MXhVwYLN2yOEzNKkR6dw.jpeg" /><figcaption>AirWatch Enrollment Status</figcaption></figure><p>Once you’ve done this, you have a decent gatekeepers of your EMM and corporate networks that no random devices can enroll to your EMM and connect to your corporate networks.</p><p>In Blackberry UEM case, you can achieve this by simply applying “Do not allow unsupervised devices to activate” under the Activation Profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2ZUVHDWcy0DQ1ORVzSpEg.jpeg" /><figcaption>UEM Activation Profile</figcaption></figure><p>At the time of writing, you can’t enforce KME device enrollment with UEM.</p><p>It’s very interesting how MobileIron is implemented to achieve the registered device only enrollment. There is no obvious settings available from MobileIron to enable this. You have to figure out by yourself. The trick is to utilise the different types of Device Registration settings. The way MobileIron distinguish normal enrollment and DEP enrollment is via Device Registration settings and a DEP Enrollment Profile. For example, you can set the In-app registration to use Registration PIN, while in the DEP enrollment profile to use password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*sWvoXpHOm535phHdjT-4Fw.png" /><figcaption>MobileIron Device Registration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*QT2E_hwPLvgfpJfPCk734g.png" /><figcaption>DEP enrollment Profile</figcaption></figure><p>In this way, any non-DEP device is forced to use a Registration PIN which is generated by the IT admin as it is categorised as in-app registration. Depends on PIN issued or not, a IT admin has the full control whether a secondary personal devices is allowed to registered or not.</p><p><strong>Use attestation &amp; compliance rules to safeguard your system</strong></p><p>We talked about how to gain extra security during enrollment and configuration phases. There are tones of other things you can do during the in-life management of a device. I am sure as a IT manager, you are well-knowledged about best practise of EMM policies, such as separate personal data and corporate data using Knox Workspace or Android Enterprise, protect data at rest (DAR) by encryptions, or secure data-in-transit (DIT) using VPN.</p><p>But EMM should not simply assume a device is not compromised. Attestation allows EMM to check the device integrity, and apply compliance rules to protect your corporate network being compromised.</p><p>Instead, a Knox-enabled device provides the EMM with an , a cryptographically verifiable collection of device state measurements.This attestation includes bootloader hashes, kernel, TrustZone, and logs from runtime protection mechanisms, among others. Attestation is signed using a key derived from a hardware protected (DRK). Because Knox Attestation is TrustZone based, and the Attestation agent is sitting inside the Secure World, so there is no way to forge the attestation results even the Normal World is compromised, such as a rooted device. So the attestation results from the device can be trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*yeb-A9fiZLqBxUGArTjVtQ.png" /><figcaption>Knox Attestation Flow</figcaption></figure><p>For EMMs to verify the attestation, The remote Samsung server can verify message integrity using Samsung’s root key. The signature includes a server-generated cryptographic nonce (a random number used only once) to ensure an attacker cannot replay old valid attestation messages on an already compromised device.</p><p>Major EMMs all support Knox attestation when the Knox Workspace is created on the device. For example, in MobileIron, you can enable the attestation from the Samsung General policy. (N.B. You need a valid Knox license to enable this feature)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*95TiUBnkQV_GzprJlRNrPg.png" /><figcaption>Samsung General policy</figcaption></figure><p>With BlackBerry UEM, you can enable the attestation from Settings &gt; General settings &gt; Attestation. To turn on attestation for Samsung Knox devices, select Enable periodic attestation challenges for KNOX Workspace devices.</p><p><strong>Remove devices from the enrollment service after retiring &amp; delete a device</strong></p><p>The mobile enrollment service we talked about earlier such as DEP and KME provides great convenience on a newly purchased device enroll to EMMs, but as a IT manager, when a broken device returned to the device service centre, it’s good to remember to remove the device from your KME console as well. This will make sure the refurbished devices doesn’t trigger the enrollment when it is re-used by other customers.</p><p>In this blog post, we talked about how to sure your enrollment network by using dedicated WiFi network or completely closed network using private APN. Knox Configure could be a great helper to get the network settings correct before devices enrolled. We then moved to the enrollment stage, how you can enforce a corporate device only enrollment police to build the gatekeeper for your EMMs. During the in-life management stage, Knox Attestation can give you the trusted attestation to provide your fleet integrity and further safeguard your corporate network. At the end, we talked about some best practise when retiring and delete a device fore a return or break fix.</p><p>Believe or not, most of above points doesn’t cost you anything if you are already using a EMM.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeb2f5bfabca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hide the phone number when making a call in Android]]></title>
            <link>https://medium.com/@chengluo/hide-the-phone-number-when-making-a-call-in-android-fd53c2a7628a?source=rss-1273d858bc5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd53c2a7628a</guid>
            <category><![CDATA[samsung-enterprise]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[knox]]></category>
            <category><![CDATA[knox-customization]]></category>
            <dc:creator><![CDATA[Cheng Luo]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 21:57:32 GMT</pubDate>
            <atom:updated>2017-09-13T19:38:17.930Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever came cross a situation that you want to hide the phone number from a call made through an app due to the customer privacy issue. For example, a pizza delivery guy using a mobile app to delivery pizza, he needs to make a call to the customer when there is something happened during the delivery, such as delay or couldn’t find the address. As a company, you may not want to reveal your customer information to your contracted delivery guys, or even outsourced teams. The GDPR makes this even a better excuse not to do so.</p><p>So here is the solution you can find by using Samsung Knox Customization SDK. The two simple steps you need is to:</p><ol><li>Make your app a ProKiosk app: This disables the quick panel access and the Recent key. Further more, when pressing the home button, you won’t see the home screen, but your own app.</li><li>After making a call through your app using the ACTION_CALL intent, force to bring your own app into foreground. You can put a second or half second sleep in between the intent and bringing the activity to the foreground. This will make sure the intent is handled before the foreground activity.</li></ol><p>Take a look at the API reference documents of Knox Customization SDK <a href="https://seap.samsung.com/sdk/knox-customization-android/api-references">here</a>, and you can find the proof of concept video <a href="https://youtu.be/4mXaZURLTOg">here</a> as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd53c2a7628a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>