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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Apple Reportedly Further Locking Down The iPhone
Threaded  |  Newest First  |  Oldest First
RyanSepe
100%
0%
RyanSepe,
 User Rank: Ninja
2/25/2016 | 2:24:53 PM
Raising the bar
Even though this is a shot at the FBI for their current quarrel, further locking down the iPhone increases its security. So even if the underlying cause is this incident, it has had a positive outcome for security.
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
2/26/2016 | 12:26:30 PM
Re: Raising the bar
Agree. FBI can always get the information they are looking for with different means, such as talking to involved parties :--))
Whoopty
50%
50%
Whoopty,
 User Rank: Ninja
2/26/2016 | 7:47:13 AM
Buck stops?
I love how Apple is playing this. Doubling down shows it is really serious about the defence it's mounting which is great to see.

What I'm curious about now though is where the buck stops? If Apple flat out refuses to comply with the court's demands, does Tim Cook get in trouble legally? Are Apple employees forced at gunpoint to make the software changes?

How does it work if a company just says no?
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
2/26/2016 | 12:28:34 PM
Re: Buck stops?
If the government wants to pursue further they can, based on how court rules Apple has to comply regardless. The is the Republican of Apple. :--)).
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
2/26/2016 | 12:30:35 PM
Re: Buck stops?
Also, I do not thing Tim Cook is personally liable on this, it is Apple, I f it was financial dispute it may end up with Tim Cook being responsible but this is not that.
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
2/26/2016 | 12:24:37 PM
Right strategy
This would be right strategy in my view so we do not have this non-sense conversation between a government and the private sector. 
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
2/26/2016 | 12:30:57 PM
Others
One more thing, other should follow what apple is doing. They need to give responsibility of securing devices to users themselves. If I want to secure it I would if not I would not, neither apple nor government should be deciding that.
cyberpink
50%
50%
cyberpink,
 User Rank: Strategist
3/3/2016 | 10:50:34 AM
Apple, FBI and our privacy
Apple is doing exactly what you would expect.  This is not their first standoff with a government over cellphone security.  They have an ongoing standoff with China, who demands to have backdoors into their systems, which would give China a view at Apple's intellectual property.  There is no evidence that Apple has treated the situation with the US any differently than it has with China.  The main difference I see in the arguement is the US government protects our civil liberties, while the other foreign nation-states do not.  Apple is not giving in to anyone at this point.

Our FBI is tasked with protecting our civil liberties by catching and stopping the perpetrators before a lethal attack occurs.  In my eyes, the FBI is fighting to protect our civil liberties by taking a stand to protect the US homeland.  Being able to gain access to cell phone data is critical to their mission.

As a US born citizen, I feel privacy is important.  I agree with Apple's standoff.  I also agree with the FBI's demands.  My question is their a happy medium for all parties involved?  Both groups are being true to their mission - which has put them at odds.  I would really like so see a good resolution that benefits both security and privacy in our country.  Apple has always found their partnership with the FBI and the US government as beneficial.  I feel they can come to a reasonable resolution.


Edge-DRsplash-10-edge-articles
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
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
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
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-22703
PUBLISHED: 2022-01-17
In Stormshield SSO Agent 2.x before 2.1.1 and 3.x before 3.0.2, the cleartext user password and PSK are contained in the log file of the .exe installer.
CVE-2021-42357
PUBLISHED: 2022-01-17
When using Apache Knox SSO prior to 1.6.1, a request could be crafted to redirect a user to a malicious page due to improper URL parsing. A request that included a specially crafted request parameter could be used to redirect the user to a page controlled by an attacker. This URL would need to be pr...
CVE-2022-0242
PUBLISHED: 2022-01-17
Unrestricted Upload of File with Dangerous Type in GitHub repository crater-invoice/crater prior to 6.0.
CVE-2021-38965
PUBLISHED: 2022-01-17
IBM FileNet Content Manager 5.5.4, 5.5.6, and 5.5.7 could allow a remote authenticated attacker to execute arbitrary commands on the system by sending a specially crafted request. IBM X-Force ID: 212346.
CVE-2021-33040
PUBLISHED: 2022-01-17
managers/views/iframe.js in FuturePress EPub.js before 0.3.89 allows XSS.