back to article Korean credit card bosses offer to RESIGN over huge data breach

An IT contractor has been arrested over the theft of credit card and personal details of 20 million South Koreans. Investigators allege an IT worker at the Korea Credit Bureau copied names, social security numbers and credit card details of millions onto a USB stick before flogging them to a marketing firm. He has been charged …

COMMENTS

This topic is closed for new posts.
  1. Yet Another Anonymous coward Silver badge

    Right response - wrong target ?

    The banks presumably have to give the credit agency access to their data

    So whether the banks had it encrypted or not seems irrelevant - it was the credit agency that didn't protect it.

    Unless of course the response now is for the banks to give the credit agency access to their customer's data but not the encryption key !

    1. Anonymous Coward
      Anonymous Coward

      In Korea they resign or fall on their sword.

      In the UK they hang on by their fingernails until they agree to leave with share options, golden handshake and health care.

      Then walk into another job for the boys.

      1. Anonymous Coward
        Anonymous Coward

        Sounds like a job description for a politician!

  2. dssf

    How can it NOT be a risk?

    That is an incredible leap in logic, that just because the CVC and password do not appear to have been obtained, there is no likely fraud to take place.

    It is no secret that unlike the USA and other countries, where voluntary tax reporting is considered "compliant", and in SK, "non-compliant", some number of SK's (IIUC, those older than 35 or so) have two to five alter egos/alternate IDs, just for evading taxes, among other things.

    Anyone with this info now can target those victims and use enough existing facts to create alternate IDs and possibly obtain credit or loans in those people's names if collateral is not required. With so many people having the same surname, it only will take a crafty con a few days with an analytics program to match up stolen IDs to prospective buyers to minimize the risk of fraud alert detection going off.

    This is just one more incident that will likely lead to biometrics at point of sale becoming the norm.

    But, if these kind of snafus will probably make more people resort to carrying around wads of extra cash for a few months. It can be pretty scary for those who use love motels for purposes outside of their relationships if the data buyers/users can figure out how to access transaction histories. Blackmail could really put people into a tailspin, too.

    It is just totally improper to state that the lack of the CVC and password diminishes the risk of harm to the victims. Downplaying these events is likely to lead to complacency.

  3. Mark 85

    The difference between their culture and others...

    The most senior management take responsibility. Here in the States, they would want a large bonus.

    1. Gene Cash Silver badge

      Re: The difference between their culture and others...

      Yup, just like Target, where their reaction has been "Yup, it happened. Your bank'll take care of it if someone steals your money. Have a nice day."

  4. dssf

    A little bit about culture

    http://english.chosun.com/site/data/html_dir/2014/01/22/2014012200837.html

    http://www.inc.com/magazine/201112/the-returnees.html

    Over there, if you are from a wealthy family (at least as of 2011), and you run a start-up, you're regarded with suspicion. Read about Daniel Shin, from the USA, who started Ticket Monster in Korea in a room in his grandmother's home, and is (in 2011) doing better than most Koreans born and raised in Korea, who struggle their butts off to stay at the top of the boiling kettle.

    People with lots of money probably wonder what'll happen to them if these banks keep suffering data breaches. SK's been hit multiple times in the past few years.

  5. Anonymous Coward
    Anonymous Coward

    best industry practise?

    I'm perhaps seeing a confusion in the security industry with many areas requiring partners/contributors to follow "Best Industry Practise", fine, that'll get you hopefully above-average levels of safety/security, if all your partners/contributors are doing what they say they are doing.

    Unfortunately, due the buggy nature of human written software, the engineered & accidental backdoors, and just human frailty in comprehending the 'real' level of security paranoia that a situation requires - I think that best practise does not actually work in security. Not when there's a high value target, or easy money from a few hours script-kidding or subverting a "Trust Anchor" in implausible (to the industry) but easily practical ways (to the attacker)

    For example, allegedly maybe 60% of Banking Apps send cleartext - perhaps after some sort of vague trust element/certificate handshake, perhaps.

    For another example: Some standards bodies' that work on Trust in Internet Commerce & certificate authorities - think that "pin" means '4 digit bank-card personal number' - whereas I'd like them to consider it to mean 'the service has just presented me with a security object from the *expected* supplier' - not from some random man in the middle state or enterprise.

    poor passwords - databreaches - shouldn't happen, but in a world where according to the BBC a distributed military system is guessing offline 4 billion password hashes a second, then passwords themselves have had their day and we need a new working trust element, with pinning, not just "Best Practise" established by a probably subverted standardisation system.

    1. Tom 13

      Re: best industry practise?

      The only practical answer to PIN cracking is a two independent connection model using the equivalent of a cypher pad. You contact the vendor, the vendor contacts the payment company. The payment company contacts you (via a pre-established secure method) with the key from the cypher pad, which you then provide to the vendor to complete the order.

      You of course see the immediate problem: too complex for a typical user to implement the solution.

This topic is closed for new posts.

Other stories you might like