Dark Reading is part of the Informa Tech Division of Informa PLC

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.

6 Most Dangerous New Attack Techniques in 2015
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
4/23/2015 | 3:24:13 PM
Data Engineering
Of these, I think it is Technique #1 that interests me the most in terms of how lethal it can actually be.  When you look at Data Engineering (acquire->ingest->transform->store->retrieve) programmatically, there is this incredible opportunity to inject AI into the software that drives illegal data engineering, especially when the source is internal, such as a whistleblower or disgruntled worker, and someone who can help place malicious code onsite.  Then, with endpoints working together, cyber criminals can program data manipulation activities that are innocuous and ride everyday traffic, raise no alarms, and have as their key attribute patience.  Sensitive data leaks have the potential to become almost imperceptible with the addition of dummy endpoints (shadow companies, banks, etc) receiving information from both malicious sources and unsuspecting (depending on how well the insider is able to plant malicious code).  In short, data science holds the key to taking what used to be blatant and forensic-heavy incidents and now burying it into the white noise of everyday electronic traffic. 
User Rank: Ninja
4/23/2015 | 9:34:53 AM
I definitely agree with most of these, especially with the IoT. Devices are being made smart down to the nearest toaster. (Aside from the satire in that statement the big example I have in mind right now is the smart watch) These devices will only become more prevalent and for security to keep up will be a challenge.

What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Post a Comment
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-06-14
The Yes/No Chart WordPress plugin before 1.0.12 did not sanitise its sid shortcode parameter before using it in a SQL statement, allowing medium privilege users (contributor+) to perform Blind SQL Injection attacks
PUBLISHED: 2021-06-14
The Smart Slider 3 Free and pro WordPress plugins before did not sanitise the Project Name before outputting it back in the page, leading to a Stored Cross-Site Scripting issue. By default, only administrator users could access the affected functionality, limiting the exploitability of the v...
PUBLISHED: 2021-06-14
When deleting a date in the Xllentech English Islamic Calendar WordPress plugin before 2.6.8, the year_number and month_number POST parameters are not sanitised, escaped or validated before being used in a SQL statement, leading to SQL injection.
PUBLISHED: 2021-06-14
The page lists-management feature of the Sendit WP Newsletter WordPress plugin through 2.5.1, available to Administrator users does not sanitise, validate or escape the id_lista POST parameter before using it in SQL statement, therefore leading to Blind SQL Injection.
PUBLISHED: 2021-06-14
The Stock in & out WordPress plugin through 1.0.4 has a search functionality, the lowest accessible level to it being contributor. The srch POST parameter is not validated, sanitised or escaped before using it in the echo statement, leading to a reflected XSS issue