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
When It Comes To Security Tools, More Isn't More
Lamont Orange, Chief Information Security Officer at Netskope,  1/11/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-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.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16961
PUBLISHED: 2021-01-15
SolarWinds Web Help Desk 12.7.0 allows XSS via a Schedule Name.
CVE-2020-35733
PUBLISHED: 2021-01-15
An issue was discovered in Erlang/OTP before 23.2.2. The ssl application 10.2 accepts and trusts an invalid X.509 certificate chain to a trusted root Certification Authority.
CVE-2021-23836
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A stored XSS vulnerability was identified in the prefs_smtp_psw HTTP request body parameter for the acp interface. An admin user can inject malicious client-side script into the affected parameter without any form of input sanitization. The...
CVE-2021-23837
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A time-based blind SQL injection was identified in the selected_folder HTTP request body parameter for the acp interface. The affected parameter (which retrieves the file contents of the specified folder) was found to be accepting malicious...
CVE-2021-23838
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A reflected XSS vulnerability was identified in the media_filter HTTP request body parameter for the acp interface. The affected parameter accepts malicious client-side script without proper input sanitization. For example, a malicious user...