While threat intelligence has become a standard part of the suite of tools a company uses to defend itself, the sharing of that threat intelligence is still in its infancy. You might even say we’re taking baby steps, and years from now, we’ll look back fondly on the home videos. To continue the analogy, threat intelligence sharing is in somewhat of an awkward stage right now, where the tools and standards are further along than the actual practices themselves. Our feet want to move, but our brain is still figuring out how to get from point A to point B.

With that, I would like to share some of the basic principles to help sharing stand on its own and further its adoption since its potential benefits are truly enormous. Let’s begin with a few ideas of what to do to help establish a good sharing program.

Do:

  • Create a stable of reliable sources to research threat intelligence.
  • Take advantage of industry consortia to validate processes and findings and the right online tools to enable those interactions.
  • Pay attention to industry standards such as Structured Threat Information Expression, Trusted Automated Exchange of Indicator Information and Cyber Observable Expression to ensure interoperability between your security products regardless of who your vendor is.
  • Encourage your security practitioners to stay on top of best practices through continuing education and industry consortia such as the International Information Systems Security Certification Consortium, SANS Institute, the National Cybersecurity and Communications Integration Center, the Cybersecurity Intelligence and Integration Center and the Information Sharing and Analysis Centers.

However, we should also be realistic and set clear expectations.

Don’t:

  • Think you have to share intimate details of your security ecosystem to contribute to a threat intelligence sharing community. Sharing something as simple as a suspicious IP address or spam sample can help the next company prevent an attack.
  • Expect a platform to solve all your organization’s security issues. A rigorous set of policies and procedures to complement security products is still necessary to ensure your data and your clients’ data is protected.
  • Drink from the fire hose. Identify the right sources of threat intelligence that will help best protect your organization while allowing for actionable results.

The sharing of threat intelligence is at an exciting stage of development in which there is recognition of the power of this concept. The next stage is establishing a foundation of what it means to share effectively and confidently. I can’t wait to see what it looks like when this baby is off and running!

Be Among the first to experience the brand new IBM X-Force Exchange

Image Source: iStock

More from Threat Research

Operational Technology: The evolving threats that might shift regulatory policy

Listen to this podcast on Apple Podcasts, Spotify or wherever you find your favorite audio content. Attacks on Operational Technology (OT) and Industrial Control Systems (ICS) grabbed the headlines more often in 2022 — a direct result of Russia’s invasion of Ukraine sparking a growing willingness on behalf of criminals to target the ICS of critical infrastructure. Conversations about what could happen if these kinds of systems were compromised were once relegated to “what ifs” and disaster movie scripts. But those days are…

Patch Tuesday -> Exploit Wednesday: Pwning Windows Ancillary Function Driver for WinSock (afd.sys) in 24 Hours

‘Patch Tuesday, Exploit Wednesday’ is an old hacker adage that refers to the weaponization of vulnerabilities the day after monthly security patches become publicly available. As security improves and exploit mitigations become more sophisticated, the amount of research and development required to craft a weaponized exploit has increased. This is especially relevant for memory corruption vulnerabilities.Figure 1 — Exploitation timelineHowever, with the addition of new features (and memory-unsafe C code) in the Windows 11 kernel, ripe new attack surfaces can…

When the Absence of Noise Becomes Signal: Defensive Considerations for Lazarus FudModule

In February 2023, X-Force posted a blog entitled “Direct Kernel Object Manipulation (DKOM) Attacks on ETW Providers” that details the capabilities of a sample attributed to the Lazarus group leveraged to impair visibility of the malware’s operations. This blog will not rehash analysis of the Lazarus malware sample or Event Tracing for Windows (ETW) as that has been previously covered in the X-Force blog post. This blog will focus on highlighting the opportunities for detection of the FudModule within the…

Defining the Cobalt Strike Reflective Loader

The Challenge with Using Cobalt Strike for Advanced Red Team Exercises While next-generation AI and machine-learning components of security solutions continue to enhance behavioral-based detection capabilities, at their core many still rely on signature-based detections. Cobalt Strike being a popular red team Command and Control (C2) framework used by both threat actors and red teams since its debut, continues to be heavily signatured by security solutions. To continue Cobalt Strikes operational usage in the past, we on the IBM X-Force…