4 ms·
This is just as likely to be a rogue employee/sysadmin as it is a actual hack. I wouldn't start placing blame until it's determined what the actual cause is.
by JimmyAustin 9y ago
This is just as likely to be a rogue employee/sysadmin as it is a actual hack. I wouldn't start placing blame until it's determined what the actual cause is.
- duncan_bayne 9y agoSome blame can be placed up-front, at least potentially. Regardless of the _nature_ of the breach, if the data ought not to have been stored, the fault lies with those who decided to store it.
- stubish 9y agoIf it is an employee or sysadmin, they are an idiot. Its $30 a pop for small volume and large risk. If you have a job with access to this data you should be charging a hell of a lot more. But its enough to get someone in a poorer country with little at risk to create a fake gmail account and use it to bootstrap access to an online self service portal or whatever approach they are using.
- iamben 9y agoIndeed. Assuming they have some kind of logs for legitimate use in place (X was logged in and requested X), how hard would it be to add a bogus record, request it and see who looks it up. If it's accessed and the logs are avoided, there's probably something leaky. Assumption is a dangerous thing, however...
- jacques_chester 9y ago> If it is an employee or sysadmin, they are an idiot. Its $30 a pop for small volume and large risk In this scenario, I expect a bad egg would've sold the records in bulk to a middleman for a high price.