This practical entry briefly outlines how to force or defer OS Update for Apple iOS devices (iPhones, iPads). There are two completely opposite use cases for this:
This week I’ve attended an event and one of the other attendees has voiced an interesting thought, which deserves a brief footnote here, for future reference.
Since March 2018 the US Government had passed the so called Cloud Act, which basically “allows federal law enforcement to compel U.S.-based technology companies via warrant or subpoena to provide requested data stored on servers regardless of whether the data are stored in the U.S. or on foreign soil.”
According to my vis-a-vis, this means that no EU company can now trust their data to cloud services offered by US companies – even if the datacenters themselves are located in EU, the US government basically now can demand access to any data of EU residents.
The devil, is, as usual, in details, Let’s read a little deeper:
“[CLOUD Act] asserts that U.S. data and communication companies must provide stored data for U.S. citizens on any server they own and operate when requested by warrant,
but provides mechanisms for the companies or the courts to reject or challenge these if they believe the request violates the privacy rights of the foreign country the data is stored in.
It also provides an alternative and expedited route to MLATs through “executive agreements”; the executive branch is given the ability to enter into bi-lateral agreements with foreign countries to provide requested data related to its citizens in a streamlined manner, as long as the Attorney General, with concurrence of the Secretary of State, agree that the foreign country has sufficient protections in place to restrict access to data related to United States citizens.”
So, EU citizens stay at exactly the same level of protection as before, the new fears are unfounded. What do you think? Do you trust your data to the cloud?
There’s been recently a wave of news along the “OMG Apple DEP is insecure we are all doomed” line. While there is indeed a few flaws in Apple Device Enrollment Program, I want to show how to fight it with Workspace ONE UEM (AirWatch) in a simple 3-step process
Step 1: Go to your DEP profile in Settings -> Devices -> Apple -> Device Enrollment Program
Step 2: Ensure Authentication is ON
Step 3: You are done. Really, this “vulnerability” is only serious in two cases:
So, now you are armed with knowledge!
I had a week of customer meetings, each (literally!) asking the same question: “How can I prevent WhatsApp from grabbing the corporate contacts on my device?”
In this series of posts we will explore the options of deploying corporate email/contacts/calendars with the goal of maximal work/personal contact separation, while trying to minimally impair the user experience (such as the Caller ID).
Table of contents:
I had a week of customer meetings, each (literally!) asking the same question: “How can I prevent WhatsApp from grabbing the corporate contacts on my device?”
In this series of posts we will explore the options of deploying corporate email/contacts/calendars with the goal of maximal work/personal contact separation, while trying to minimally impair the user experience (such as the Caller ID).
Table of contents:
I had a week of customer meetings, each (literally!) asking the same question: “How can I prevent WhatsApp from grabbing the corporate contacts on my device?” This happens more often than you think – the infamous GetContact collected over 3.5B contacts in just a few months, all of which were officially available for sale! With GDRP in effect, how much could this cost?
Of course, both iOS and Android offer means to securely lock down enterprise data on BYOD devices. But this comes at a price of usability, the most cited problem being the caller it. We know that in the modern day an unhappy and discomforted user is essentially a backdoor waiting to happen. How can we keep this balance between security and productivity?
In this series of posts we will explore the options of deploying corporate email/contacts/calendars with the goal of maximal work/personal contact separation, while trying to minimally impair the user experience (such as the Caller ID).
We will explore several approaches, their limitations and shortcomings for iOS and Android. This post lays the foundations and provides a TL:DR style summary/comparison of my current findings.
Table of contents:
Legacy AirWatch reports are being deprecated, and replaced by the next-generation Workspace ONE Intelligence Reporting. The point of this quick post is to provide a bullet-style quick overview and resources for further reading.
TL:DR
