What you need to know
- Apple CEO will meet with U.S. President Joe Biden on Wednesday to discuss cybersecurity.
- Microsoft's Satya Nadella and Amazon's Andy Jassy will also be in attendance.
Tim Cook is heading to Washington D.C. to talk cybersecurity with President Joe Biden.
As reported by Bloomberg, the Apple CEO will attend an event at the White House on Wednesday to discuss the ways that private companies can work to improve cybersecurity. Microsoft's Satya Nadella and Amazon's Andy Jassy also plan to be in attendance.
According to the report, the executives will likely discuss "how software can drive better security in the supply chain."
Cook is flying to Washington D.C. as the company continues to face concerns over its new technology that will scan iCloud Photos, Siri, and iMessage for Child Sexual Abuse Material (CSAM).
The company has admitted it could have done a better job of explaining how the new technology does not infringe on privacy the way that many have brought thought, deploying both its head of privacy and software to talk about the new technology.
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
I thought his name was Tim Apple?
Too bad sleepy Joe won't have any clue what they are saying. Probably won't be awake for most of the meeting.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.