An update on our security incident

Re:An update on our security incident by londons_explore on Friday July 31, 2020 @02:53AM (#24006326)

I believe the Twitter attack involved tricking a user into installing proxy software on their machine (to be in twitter's internal network).

If that is the case, that same proxy software could proxy the security key requests too.

[ Parent | on HN ]

Re:An update on our security incident by tdhoot on Friday July 31, 2020 @02:59AM (#24006368)

That can be prevented by restricting the software that can be installed on employee machines.

[ Parent | on HN ]

Re:An update on our security incident by c00ls0sa on Friday July 31, 2020 @05:17AM (#24007006)

WFH has caused many companies to ease up on restrictions involving location, ip, and sometimes a broader need for software. Granted, nobody should be this easy to bamboozle, but I get why now more than ever this may have been an issue.

[ Parent | on HN ]

Re:An update on our security incident by Thorrez on Friday July 31, 2020 @03:54AM (#24006640)

If there's malware involved I don't consider that phishing. Although some would debate that.

[ Parent | on HN ]