Language Selection

English French German Italian Portuguese Spanish

FDIC advises banks on how to protect against spyware

Filed under
Security

The Federal Deposit Insurance Corp. (FDIC) today issued a list of best practices for financial services firms that details how to protect against spyware, which the agency said can be used by criminals to collect customer data or hack into banking systems.

"It is critical that banks stay vigilant about the risks involved with this malicious software and take appropriate action so that they and their customers do not fall victim to it," said Michael Zamorski, director of the FDIC's Division of Supervision and Consumer Protection.

The guidance spells out the risks associated with spyware and recommends actions that financial institutions can take to mitigate those risks on internal computers as well as on those used by customers to connect to transactional banking Web sites.

The FDIC recommends rolling out multifactor authentication to limit the ability of identity thieves to access customer accounts. Firms should also consider spyware as part of their risk-assessment analysis and bolster security against it by setting Internet-use policies for employees. The FDIC also recommends that banks advise customers on the risks of using public computers such as those in hotels, libraries or Internet cafes to connect to online banking Web sites because of the uncertainty of what spyware may have been installed on the public equipment.

According to the FDIC, the risks associated with spyware include allowing attackers to eavesdrop and intercept sensitive communications, such as customer IDs and passwords; allowing unauthorized access to user accounts; permitting unauthorized access to bank systems; and increasing vulnerability to other Internet-based attacks, such as phishing.

By Lucas Mearian
ComputerWorld.

More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more