June 20, 2016 By Larry Loeb 2 min read

At its Worldwide Developers Conference (WWDC) last week, Apple announced that it will require the use of HTTPS for apps in its App Store ecosystem as of January 2017.

Laying Down the Law

Ivan Krstić, head of security engineering and architecture at Apple, told the audience, “This is going to provide a great deal of real security for our users and the communications that your apps have over the network,” SecurityWeek reported.

Krstić went on to say that apps will be required to use Application Transport Security (ATS), a TLS v1.2 channel, when they communicate. But there is an exception to this requirement: If the data that is being transferred has already been encrypted, as in the case of streaming media, then it will not require further encryption.

Users and developers alike can point any device to How’s My SSL to determine which version of TLS their device is running, along with some other good information about its security.

Backlash to HTTPS for Apps

Many developers expressed displeasure with the change on official Apple forums when they realized that ATS — which had been present in Apple’s operating systems since OS X 10.11 and iOS 9 but was turned off by default — would make their lives more challenging.

One developer said, “In my particular use case, I call a REST API on an embedded board, and it would literally be impossible to use SSL on [it] without forcing all of our customers to upgrade.” Others reported similar limitations.

There are going to be specific exemptions needed for this policy. At this early stage it seems that Apple understands this: SecurityWeek noted that the standard can be waived if developers provide “reasonable justification” for it.

One Piece of the Puzzle

The move by Apple is part of an overall project to bring its disparate operating system files into one functional and protected entity. While there may be privacy enhancements coming, Apple is still going to be collecting anonymized big data sets from these new data structures, Wired noted.

Some, like Bruce Schneier, are skeptical that Apple can pull this “differential privacy” off without vulnerabilities being present in the software. But if vulnerabilities and loopholes can be eliminated through the use of HTTPS for apps, it may be an admirable and attainable effort.

More from

Passwords, passkeys and familiarity bias

5 min read - As passkey (passwordless authentication) adoption proceeds, misconceptions abound. There appears to be a widespread impression that passkeys may be more convenient and less secure than passwords. The reality is that they are both more secure and more convenient — possibly a first in cybersecurity.Most of us could be forgiven for not realizing passwordless authentication is more secure than passwords. Thinking back to the first couple of use cases I was exposed to — a phone operating system (OS) and a…

DOD establishes Office of the Assistant Secretary of Defense for Cyber Policy

2 min read - The federal government recently took a new step toward prioritizing cybersecurity and demonstrating its commitment to reducing risk. On March 20, 2024, the Pentagon formally established the new Office of the Assistant Secretary of Defense for Cyber Policy to supervise cyber policy for the Department of Defense. The next day, President Joe Biden announced Michael Sulmeyer as his nominee for the role.“In standing up this office, the Department is giving cyber the focus and attention that Congress intended,” said Acting…

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today