Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Smartphone Security Shootout
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/30/2015 | 11:14:42 PM
Re: No BlackBerry in this so-called "security shootout"
Incidentally, I'm interested to see if Silent Circle's purportedly ultra-secure smartphone can make any major penetration in the market.

Alas, functionality and features seem to trump security in the consumer market -- which in turn informs and impacts the enterprise market.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/30/2015 | 11:10:07 PM
Re: No Commercial Solutions Are Secure
@digitallachance: Good for you for making me defend the claim.  (Truly.  Not sarcastic.)  I double-checked and it appears that I was apparently relying on reports that in turn relied upon misleading/untrue assertions.

In 2010, here were reports that RIM (as it was then known) had compromised and provided backdoor access to the Indian government.  e.g., articles.economictimes.indiatimes.com/2012-08-02/news/33001399_1_blackberry-enterprise-encryption-keys-corporate-emails

It turns out, however, that these reports were apparently a bit overstated.  www.theregister.co.uk/2012/08/02/rim_keys_india/

It appears that RIM arranged for a "lawful access" compromise -- but that there were no actual keys to give.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/30/2015 | 11:02:56 PM
Re: platform selection
@macker: It's really lamentable how many people/organizations continue to rely on SSNs as a security metric/identifier.  SSNs were originally intended to have more of a "username" function -- and now they are used as "passwords" (which is just silly for anything requiring more security than, say, a 1990s Geocities chat room).
User Rank: Apprentice
4/30/2015 | 12:57:34 PM
No BlackBerry in this so-called "security shootout"
Seriously, I know how the consumers consider BlackBerry to be out of business and irrelevant, but anyone who cares about security will agree you can't talk mobile phone security without mentioning BlackBerry.  The president of the United States is not carrying an iPhone or an Android or a Windows phone.  Only BlackBerry has the high level of certification required for the US DOD to use those devices.



User Rank: Apprentice
4/30/2015 | 12:50:58 PM
Re: No Commercial Solutions Are Secure

Do you have any evidence that BlackBerry provided governments backdoors or is this just a conspiracy theory?
User Rank: Ninja
4/30/2015 | 7:33:41 AM
Re: platform selection

to a point I think you are right: better user training will help.  but you are tackling a blizzard with a push-broom: the rapacious raiding of user computers for "big data" by the commercial sector -- and by government -- is simply stunning.

run NOSCRIPT on your browser for a while and note: when you access a site -- like this one -- how many connections do you actually acquire?    the crux of this is that reading the internet is like running down a dark alley: wear your boots; don't go barefoot.

extending this to "platform" -- or your hardware/software setup -- security needs to be addressed starting from the standpoint of the operating software.   your operating software must not allow itself to be affected by the actions of an application program -- whether by intent or by error.

but o/s security is only a start

in our online environment all of our usual identifiers -- name, address, date of birth, social security number, eMail address, mother's maiden name, ... are all compromised -- either in public bazarrs or out in the DarkNet

Which leads us to the need for Secure Computing in a Compromised Environment

the basic need is an identification that can be used in public but which at the same time can be controlled by the owner

Symmetric keys -- such as eMial address, Soc.Sec.Nr &c are not sufficient: once compromised -- they can be used by anyone.   we must move to Public Key Encryption to provide the AUTHENTICATION of documents that is critical to business requirements.

to do this we must begin by dispelling the MYTH that PGP or GmuPG -- is too difficult for "everyone" to use.  Properly packaged -- such as the ENIGMAIL plugin for Thunderbird -- anyone who can use Excel -- can easily use PGP/GnuPG

it's just another drop-down dialog box.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/29/2015 | 11:26:23 PM
Re: Both are vulnerable !
Funny how older tech is often more secure.

Maybe we should go back to typewriters and smoke signals.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/29/2015 | 11:24:04 PM
Re: No Commercial Solutions Are Secure
@Ian: After the Snowden revelations, would YOU trust a tech company on data privacy and data security if one of their biggest customers is the federal government?  ;)

(For that matter, should we continue to trust IBM?)  ;)
Blog Voyage
Blog Voyage,
User Rank: Strategist
4/28/2015 | 12:08:36 PM
Both are vulnerable !
In fact, iOS is just as vulnerable as Android. Both are more vulnerable than BlackBerry ever was, but that's not relevant today.
User Rank: Ninja
4/27/2015 | 9:01:52 AM
Samsung Knox
I was curious during its inception how the Samsung KNOX security suite would perform. Is it still enabled by default on Samsung based phones or was that removed due to user gripes? If its not set as default I guarantee that the majority of users will not turn it on even if prompted.
Page 1 / 2   >   >>

I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.