it seems like maybe a more reasonable conclusion to draw is that the search feature is still being tested and tweaked quietly, and as such facebook's press office isn't hitting the gas as hard on getting it media attention as it is on the professional services page. There isn't necessarily a 1:1 correlation between what they send out to journalists and what's reported, but there certainly is one.
the common theme for half of the top 10 seems to be physical proximity to the pentagon, fort meade, or both. UMD, GW, George Mason, Georgetown and Hopkins are all in driving distance.
I agree, it also does a lot of little things right that other platforms mess up. For example, it's the only platform that doesn't penalize a team's defense for scores that occur when they're not on the field (e.g. an interception returned for a touchdown). It is, unfortunately though, an unholy browser memory hog as well.
right, that's the aspect they address, it's the same for sellers agents. The issue is that if the agent (recruiter) has the option to increase the salary by say, 2000$, they see a small percentage of that, maybe 100$ worth? If it takes them 4 hours to negotiate that, it's not worth it for them to spend that time for a small gain, so might forego the opportunity. They might focus instead on getting the next placement, effectively increasing the $/hr they earn.
With regards to your last point, it's true that the recruiter and candidate's objectives are loosely aligned, but it plays out a lot like the relationship between a real estate agent and client in practice, in which the best deals aren't always achieved due to effort overhead. Freakonomics did a pretty interesting piece on it. Youtube summary of it: https://www.youtube.com/watch?v=17jO_w6f8Ck
reading between the lines, it seems like they may have cause to believe fitbit induced the employees to grab that information before leaving. If that's the case then the case against fitbit makes more sense
Conley made the most colorful remarks of the day, including saying that he didn’t believe technical experts who said building backdoors is impossible.
“Did John Kennedy say we couldn’t go to the moon?” Conley asked. “He said no, we’re going to go because it’s the hard thing to do.”
“I’m a proud and patriotic American, too,” Farenthold responded. “But maybe the proper analogy would be if Kennedy said ‘We’re going to go the moon and no one else is ever going to go. Ever.’”
We're looking for people with application security skills to join our team. If you've been doing security for a while, or you're a developer with good security fundamentals looking to make the switch, this might be the job for you. We specialize in application security: websites, thick clients, and mobile. We've been around since 2002, and our founders are some of the guys behind the OWASP top 10. We work on a lot of cool technology for major clients in the financial, healthcare, government sectors, as well as others.
We're especially interested in people out of DC, NY, San Francisco, and Chicago, but fully remote is an option as well (a lot of our current engineers are fully remote) but must be able to permanently work in the US
FYI, to reply directly to a comment, hit the "reply" link right below it, rather than typing into the "add comment" box at the top. It makes the thread more readable that way
An aspect of this no one is touching on is the mechanism for it. If it's done digitally, securing the process sufficiently would be nigh impossible. I had an instructor in an application security course who said "the moment we have online voting is the moment you can start referring to me as Mr President" and he's not wrong. Think of all the breaches you hear of involving credit cards, then think of how motivated people can get if the reward isn't money, but control of national policy.
Title is slightly misleading in that that's only the REPORTED losses. I'd venture to guess that the actual numbers are significantly higher. A lot of these go unreported due to embarassment, etc.
Except TPB doesn't actually host the leak, all they do is index the .torrent files, so if it's going to leak, it'll leak, and another tracker will have a link to it. The takedown and the DDoS came pretty close to each other, but it's important to remember that TPB gets taken down every year or two, it's just the cost of doing business with them. I don't see compelling evidence for correlation
If they're going to insist on binding ID to account, it seems like the simplest way to do it would be just to submit the ID as an additional parameter in the login POST request and associate it as a single transaction, but again, using the ID at all is problematic.
Right? I'm also curious about the fix. The vulnerability he describes is most obviously that they fail to associate the token you get after login with an actual account, so you can re-use that token to bind an arbitrary account, but binding to a device ID is also problematic, because that information isn't inherently private. Another app could harvest it and be compromised which then leaks the info, or it could be exposed in some other way because it's not unique to their application.
It makes it more secure, but not fully. If the password hashes ever got dumped via other means, the effort required to brute force those hashes (even salted) would still be far less than you want it to be.
you can check a hash without uploading the file in question. VT only stores a set of results if it has seen the actual file, not if a hash is checked against it. This is why, when doing incident response, a lot of people suggest not uploading suspicious files to VT, because it lets the attackers change up and start using new malware