This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
Case of Citigroup, fined for missing suspicious behavior of employee who bilked customers of $750,000, shows IT must be backed by supervisory control.
Even as financial institutions hone their security technology portfolios with advanced database activity monitoring (DAM) implementations, improved fraud detection software, and other tools to sniff out bad behavior from within, malicious insiders will still manage to swindle their employers when all of that technology isn't supported with the right business processes. And when that happens, no amount of check-box compliance implementations will keep regulators from putting the hammer down hard in the form of fines and public embarrassment.
Case in point is the recent name-and-shame campaign by the Financial Industry Regulatory Authority (FINRA) against Citigroup. FINRA recently announced that it was fining Citigroup $500,000 for failing to keep track of an employee who managed to steal almost $750,000 from 22 customers during the course of eight years.
A sales assistant at a branch office, Tamara Moon, stole money from the elderly, people with Parkinson's disease, and even her own dad. And she managed to keep up her thieving ways despite exception reports that popped up for her superiors detailing conflicts in new account application information. Similarly, her supervisors did not spot red flags from suspicious transfers between unrelated accounts.
"Citigroup had reason to know what she was doing and could have stopped her," says Brad Bennett, executive VP and chief of enforcement for FINRA.
The case at Citigroup is indicative of the need for more thorough continuous monitoring practices within the industry, says John Rostern, managing director of the New York office of security and compliance consultancy Coalfire Systems.
"The type of monitoring that's typically employed these days is inconsistent at best and, in many cases, manually driven," Rostern says. "The introduction of continuous controls monitoring where you're not doing statistical sampling, but you really are looking at the wider population and gaining visibility into exceptions as they occur, is important given the amount of data that's flowing through systems and the number of people who are in those outlier areas, like branch offices."
The vendors, contractors, and other outside parties with which you do business can create a serious security risk. Here's how to keep this threat in check. Also in the new, all-digital issue of Dark Reading: Why focusing solely on your own company's security ignores the bigger picture. Download it now. (Free registration required.)
2020: The Year in SecurityDownload this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Assessing Cybersecurity Risk in Today's EnterprisesCOVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Enterprise Vulnerabilities From DHS/US-CERT's National Vulnerability DatabaseCVE-2020-27852 PUBLISHED: 2021-01-20
A stored Cross-Site Scripting (XSS) vulnerability in the survey feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via a textarea field. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
A stored Cross-Site Scripting (XSS) vulnerability in forms import feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via the import of a GF form. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
Multiple stored HTML injection vulnerabilities in the "poll" and "quiz" features in an additional paid add-on of Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary HTML code via poll or quiz answers. This code is interpreted by users in a privile...
Tufin SecureChange prior to R19.3 HF3 and R20-1 HF1 are vulnerable to stored XSS. The successful exploitation requires admin privileges (for storing the XSS payload itself), and can exploit (be triggered by) admin users. All TOS versions with SecureChange deployments prior to R19.3 HF3 and R20-1 HF1...
To save this item to your list of favorite Dark Reading content so you can find it later in your Profile page, click the "Save It" button next to the item.
If you found this interesting or useful, please use the links to the services below to share it with other readers. You will need a free account with each service to share an item via that service.