Mobile

5/10/2017
03:25 PM
50%
50%

'Systemic' Cyberattack Most Likely to Hit Financial, Energy Sectors

The financial services industry is among the top five industries that likely face a systemic cyberattack, according to a survey released today.

A systemic cyberattack attack that simultaneously affects multiple companies is likely to occur this year, with the financial services industry ranked at the top of the list of targeted sectors, according to a survey released today by American International Group (AIG).

AIG queried 70 cybersecurity, technology, and insurance professionals, in the study, and found that the industries most likely to face a systemic attack this year are:

  • financial services, with financial networks and transaction systems at greatest risk (19%)
  • power and energy, with the Internet infrastructure a likely target (15%)
  • telecommunications and utilities, with the power grid at risk (14%)
  • healthcare, with the healthcare system a likely target (13%) 
  • information technology, with software and hardware organizations getting hit, thus disabling the backbone of the digital economy (12%)

More than half of the survey respondents believe a simultaneous attack will occur involving five- to 10 companies, while one-third of those surveyed believe there is more than an even chance that as many as 50 companies will be attacked simultaneously. As for the remaining 20% of survey respondents, they think the number of companies that could be attacked at once could reach into as many as 100 businesses.

Read more about the survey here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RahulB593
50%
50%
RahulB593,
User Rank: Apprentice
5/11/2017 | 2:58:30 AM
cyber attack
This articles are truly great. very informative post.
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14084
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
CVE-2018-14085
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function swe...
CVE-2018-14086
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. The contract has an integer overflow. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell(...
CVE-2018-14087
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback functio...
CVE-2018-14088
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounde...