What you need to know
- Apple is trying to crack down on leaks from its factories and suppliers.
- A new report from The Information details new measures.
- It also says Apple is trying to improve privacy for its own employees but not factory workers.
A new report details how Apple is trying to crack down on leaks of devices like the iPhone 13 with more stringent security measures for suppliers.
From The Information (opens in new tab):
Apple also plans to upgrade computer systems in factories, currently used to determine where products should be on an assembly line to stop manufacturers from cutting corners or component theft. Apple will also reportedly monitor how long it takes components to be moved from one part of a factory to another, with an alarm being triggered if it takes too long.
Apple is also pushing the privacy of its own employees, but with seemingly no nod to the employees of its manufacturing partners:
Whilst Apple leaks do often come from within the walls of Cupertino or Apple's own operation, it is also understood that many leaks, such as CAD renders of products, often come from Apple's supply chain.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple.
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.