295 karma · joined September 28, 2014
meet.hn/city/ca-Smiths-Falls
They are basically putting the threat out that if you use Cellebrite on Signal in the future, you might not get the data you expect, and at worst, it may corrupt the report/evidence.
This also brings into question the chain of custody, as an untrusted device being imaged can alter reports of unrelated devices.
This obviously does have its own downsides (you have to maintain a login infrastructure, as well as your phishing infrastructure), but this was even seen before 2FA became common to detect if an incorrect password was entered into the phishing site.
It is definitely an improvement, but TOTP doesn't provide much protection from phishing, and as it becomes more popular more phishers will need to accomodate for them in their campaigns, further reducing their effectiveness here.
This is a post about an attack that killed at least 5 people.
According to a quick search, they have 900,000 drivers and 27,000 employees. At most 3-ish% of the people that they pay to work for them are tech employees (and we can probably safely assume most of those 27,000 are not tech).
My team as well is specifically looking for Security Engineers/Analysts/Developers, however we don't have the posting up yet, so feel free to send me a message (my email is in my profile).
Shopify follows the the zero trust networking/Beyondcorp model, and we never had the physical office spaces as part of our threat model. Not much can be done for shoulder-surfing (aside from privacy screens, and our security training), however we have built out robust systems that build trust modeling out of identity and device security.
They did already gave out $1000 for WFH setups: https://www.cnbc.com/2020/03/12/coronavirus-shopify-gives-em...
[0] http://www.pers.ms.gov/Content/Supplemental/persfacts_figure...
On the other hand, those first 8 bytes of the packet may be some authentication/verification scheme which would have to be reverse engineered. Also, it may only play UDP packets coming from 234.0.0.2:2046, which would likely mean you would have to convince the DHCP server to assign you that address instead of its intended host.