Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Businesses Security

Telling Your Superiors Their Financial Data Is At Risk? 100

alterimage asks: "I'm a Computer Science major at night, working by day in Accounting for a major telecom provider, with clients consisting of most the entities on Fortune's Top 20 Most Admired Companies of 2006 list. Daily, I see customer payments in excess of $50,000 come and go. Strangely enough, rather than have these payments conducted by an IVR system or over the Internet, the majority of these payments are conducted over the phone with individuals such as myself, who are instructed to write down, document all the specific banking information, and to keep them on hard-copy in an unlocked file cabinet that is accessible to anyone. Having experience with social engineering and fraud, I've already advised my boss that it's probably not a good idea for those bank routing and account numbers to be laying around unsecured, and was told that I'm over-reacting. So I ask Slashdot: At what point should the human aspect of security be considered in the business environment? Should I just smile, nod, and play along in this situation?"
This discussion has been archived. No new comments can be posted.

Telling Your Superiors Their Financial Data Is At Risk?

Comments Filter:
  • by User 956 ( 568564 ) on Wednesday March 07, 2007 @02:48AM (#18259374) Homepage
    I've already advised my boss that it's probably not a good idea for those bank routing and account numbers to be laying around unsecured, and was told that I'm over-reacting. So I ask Slashdot

    translation: I'm looking for a creative way to get myself fired.

    and if it bugs you, just keep your head down and look for a better job. If you make a stink, the first time something goes wrong, you'll be the first guy they blame.
  • In a word: yes (Score:4, Insightful)

    by Icarus1919 ( 802533 ) on Wednesday March 07, 2007 @02:50AM (#18259378)
    Continue to make good faith efforts to change the policy. However, if you keep getting stonewalled, then let it slide; you may start making enemies if you continue past that point. It won't be your ass on the line if something goes wrong, especially if you can document that you tried to solve the problem.
  • by arlo5724 ( 172574 ) <jacobw56@gmail. c o m> on Wednesday March 07, 2007 @03:02AM (#18259428)
    If you have communicated your concerns to your superiors then your obligation is filled and you don't have to worry about it.

    That said, if you are still worried for some reason then you should either find a way to express the problem to your superiors' superiors (if they have any) or possibly anonymously report it to the clients themselves (if you won't be endangering yourself in the process).

    Good luck.
  • Ethical issues at a brokerage firm? I'm shocked :P

    All kidding aside, I feel kind of sorry for the people who post this kind of ask slashdot. As bad as it sounds, the best course of action most of the time is just to keep your mouth shut and continue with life as usual. Most entrenched management and executives do not want anyone to rock the boat and will make your life a living hell not only in your current job, but also possibly in the industry as a whole if you do rock the boat (and I don't care how big you think your industry is, most of the people at the upper levels know, or at least know of, each other).

    Unless your job is specifically to do security audits, just let it go. Chances are they don't want to hear it and won't be happy if they *do* hear it.

    I used to be bright-eyed, idealistic, and naieve with respect to this sort of thing. It lasted all of five minutes. Now I'm more of a hopeful cynic (expect the worst and hope it doesn't happen) lol

    Offtopic: I think this makes you It again...
  • Yes and no... (Score:3, Insightful)

    by Cervantes ( 612861 ) on Wednesday March 07, 2007 @03:41AM (#18259564) Journal
    You have a moral responsibility to encourage data to be safe.

    If you push it, you're quite likely to get stonewalled, destroy your future at the company, and possibly hasten the demise of your job.

    If you plan a long future at this company and can live with the moral ambiguity, shut up and leave it until you're higher up in the chain.

    If you can live with possibly losing career opportunities, make your complaints, but target the right person. Usually most companies will have someone who's actually supposed to make sure data is secure and privacy is assured. Find them and explain things to them.

    If you really don't care about the job, make a good list of all the problems, written out and carefully phrased, and push it as far up the chain as you can. You'll get shit for it, maybe tossed, but with those concerns sitting on the CEOs desk, it's quite unlikely they'll get forgotten.

    At the end of the day, it just depends on your personal moral standing.
  • by Warbringer87 ( 969664 ) on Wednesday March 07, 2007 @03:44AM (#18259572)
    If you warn people and they don't listen you've done your part.
  • Re:In a word: yes (Score:4, Insightful)

    by Splab ( 574204 ) on Wednesday March 07, 2007 @05:40AM (#18259970)
    Pay particular care to the last part, documenting! Some time back I worked as a PHP programmer part time, and during transition from one server to another for one of our major sites I noticed that forms was open for injection attacks, now this being a legacy system it wasn't just fixing it a few places, but all over the site which means a lot of hours. The reason for this being a non issue on the old server was it was running with magic quotes. The reason for the new one not being able to run it was newer sites was programmed around the assumption that magic quotes was off and would thus escape all input.

    I told my boss on several occations that it also meant you could easily gain admin priviledge, but fixing it meant spending money so it wasn't. I made sure to document my warnings, because sooner or later someone would stumble across the sites admin interface and deface the site - which they did and when the boss wen't haywire I had documentation that he was warned.

  • by qwijibo ( 101731 ) on Wednesday March 07, 2007 @08:55AM (#18260816)
    What the law says and how it works are very different. Anyone who takes a hard stand based on being legally in the right is in for a firm reality check.

    Depending on the size of the company, there is a very real possibility that the people in management got there by knowing the law well enough that they can violate it with plausable deniability. I work in a large bank where I see that happen all the time. I have pointed out numerous security problems and blatant violations of company policy, but management is willing to take those risks. We have people telling us what we need to do because sarbox has teeth, but there's absolutely no consequences for when we blatantly ignore them. The reality is that the worst that can happen is the offender gets transferred to another department, or in extreme cases, they could get fired.

    Everyone has a potential security breech waiting to happen. The laws exist to point fingers after the fact. The law isn't going to help someone who is just pointing out a potential flaw. What's worse is that if someone exploits the hole this person identified, the law has good reason to consider him a suspect since he's obviously thought about it.
  • by markov_chain ( 202465 ) on Wednesday March 07, 2007 @11:01AM (#18261888)
    The sad thing is, his unlocked filing cabinet is probably more secure than having the information sit on some server where hackers from Bulgaria can steal it and blackmail the company.
  • Comment removed (Score:3, Insightful)

    by account_deleted ( 4530225 ) on Wednesday March 07, 2007 @11:04AM (#18261928)
    Comment removed based on user account deletion
  • by Gary W. Longsine ( 124661 ) on Wednesday March 07, 2007 @11:50AM (#18262458) Homepage Journal
    If you're giving the routing number and account number of your checking account to 3rd parites to make payments over the web then you're not treating the data as though it were confidential. Now, in addition to any employee at your bank, any random person at the company of the 3rd party has access to this information. They could rack these things up for a year and then sell them on the internet. Or maybe their web server gets hit by a worm which steals all these numbers along with credit card numbers.

    I like your analysis that this is a cryptosystem with the "routing + account" number standing in for both the public and private key. A proper crypto system would allow you to pay someone with some information and a public key, perhaps with a one-time use bit of some sort. This would prevent funds-extraction by 3rd parties (who bought your information on the internet after you paid the first 3rd party for something) because the information couldn't be used to extract money from your account without a new one-time thingy. Meanwhile, never provide your "routing + account" number to anyone (except your employer for auto-deposit... life is all about risk-reward trade-off). Instead, use credit cards to pay third parties so you have better consumer protection against fraud.

    However, it's not completely clear that the problem in the original post would be solved by such a system without disrupting the "business process" that the customers probably think they need. An obvious approach would be something like a PKI system with a little card that generated a one-time tidbit on the fly, which the customer would provide to 3rd parties to authorize a payment, and presumably to a banker to authorize a fund transfer or wire or whatever over the phone. The bank's customers may view this as inconvenient and may switch to another bank (the key generator is yet another thing they need to carry around and keep physically secure). After all, the customers clearly want to be able to make a phone call and talk to a person to perform a transaction. In any case, the bank managers will fear this customer response.

    Under the existing system, the bank employees are trusted and the customer will need to detect the missing funds and report them to the bank. Many other bank employees (any teller, any banker, any computer operator) already have access to the same sensitive information as is written to paper and placed in the drawer, which is why the bank managers are not really concerned about the drawer. They know, but perhaps haven't completely thought through that the funds will have been transferred to another account somewhere, and that will be traceable. The funds may not be recoverable but the money trail could be followed from account to account to the perpetraitor... right up to the point where the bank manager and the FBI agents are watching a grainy video of somebody in a wig and fake nose-mustache-glasses pull up to a drive through window in a car that was purchased with cash and uh, donated to a rural fire department for, uh, practice extinguishing gasoline fires shortly thereafter, close their account, and drive off with the cash.
  • Re:Take some money (Score:3, Insightful)

    by DreadSi ( 1070682 ) on Wednesday March 07, 2007 @12:39PM (#18263150)
    Better yet - move a large sum of money into your apathetic boss's account. You would be doing your employer a favor and killing two birds with one stone.

The moon is made of green cheese. -- John Heywood

Working...