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.

Attacks/Breaches

9/22/2016
10:00 AM
Mark Clancy
Mark Clancy
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

Even A False Positive Can Be Valuable

Sharing information about cyberthreats is important for the financial services industry, even when threats turn out to be not-so-threatening.

The financial services industry has come a long way in bolstering cyber resiliency and threat defenses, even as criminals have become more sophisticated at weakening infrastructures. Undoubtedly, the industry's success has been achieved through technological advancements, but more recently sharing information across organizations and borders has bolstered defenses. Still, more needs to be done to ensure the financial services industry can combat cyberthreats in a timely, cost-effective way.

The ability to utilize accurate cyberthreat intelligence (CTI) information across organizations is key to fighting cybercriminals. If we can't do this, it will take too long between when threats are discovered and when they're mitigated. Furthermore, while threat information may describe intrusions that were recently identified within a firm, similar incidents could have been taking place across the financial services industry for a longer time. We must work together to improve our collective ability to discover breaches and shorten the time it takes us to respond.

Understanding CTI Data
When a company initially receives CTI data, that firm is just a consumer of the information. In some cases, it might find that it has limited technical or operational capabilities to utilize some or all of the information effectively. For example, the firm may receive information about the use of malware hashes but not be able to scan for such files. The company then will realize that it needs to better understand what the data really means in order to use it effectively.

Understanding how to use CTI information, especially when the intrusion took place weeks or months earlier, is also important. If the firm looks for activity from the moment the CTI data is received, it could miss how the intrusion happened hundreds of days earlier. As a company becomes more experienced with cybersecurity, it also moves from primarily using the telemetry in the CTI data to leverage insights and contextual information and instead begins to anticipate hazards down the road, such as adversaries' motivations, tactics, techniques, and methodologies.

As a company learns to use shared CTI data, it starts to realize that some CTI data lacks sufficient context and may indicate a false positive — that is, what appears to be a problem is completely innocuous. False positives are a problem not only because they waste manpower and time, but also because they distract companies from dealing with legitimate security issues.

As a result, it's critical that security specialists and information security officers understand that not everything detected is malicious and that there are ways to categorize incidents in order to identify false positives. These can include examining logs, looking at the URL or IP address of past attacks, and further investigating other user activities involved in the incident. But even if something is identified as a false positive, this information is still important to other firms operating within any cyberthreat intelligence-sharing network. If a company knows that something is a false positive, it doesn't need to spend valuable time and resources investigating the threat.  

A feedback loop is vital in information-sharing communities. If a company finds a false positive, it's important that it can communicate with the original producer of the CTI data so that it can provide an update and send that to other members of the community.

Standardized Formats
One important factor to consider when sharing CTI data inside a community is the format in which it is shared. Improving security through collaboration isn't a new concept, but it has typically been achieved through manual interactions. Today, data sharing is facilitated through the use of standard languages, including Structured Threat Information Expression (STIX), the structure of the message describing the threat, and Trusted Automated Exchange of Indicator Information (TAXII), the transport to send the STIX message. STIX and TAXII allow CTI data to be accessed in a standardized format. These open standards are essential for the interoperability and machine processing that are key to acting on information quickly.

CTI data-sharing systems leverage these open standards and provide information through information-sharing communities to those companies that haven't begun using STIX/TAXII. These common standards also allow those defending networks to use CTI data from community sources such as Information Sharing and Analysis Centers and governmental organizations and leverage that information in various commercial and open source security tools. Open standards also address the problems companies face when using multiple vendors, where the bundling of CTI data may only work with one vendor's tools. CTI-sharing systems allow for information from multiple sources to be used in multiple tools that detect or defend the network.

The security threat and intelligence landscape is evolving quickly because adversaries are growing more sophisticated and motivated. To stay ahead of attacks and mitigate the security threats they pose, the financial services industry needs to ensure that the CTI data it shares, whether a false positive or not, is done so in a timely and automated way. Only then can we be best equipped to achieve our collective goals of accelerating our response and improving our defenses. 

Related Content:

 

Stephen Scharf is chief security officer at The Depository Trust & Clearing Corporation (DTCC). In this role he is responsible for centralizing and aligning the firm's global information security, physical security, employee safety, and crisis/incident management functions, ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...