April 27, 2015 By Doron Shiloach 2 min read

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 X-Force

SoaPy: Stealthy enumeration of Active Directory environments through ADWS

10 min read - Introduction Over time, both targeted and large-scale enumeration of Active Directory (AD) environments have become increasingly detected due to modern defensive solutions. During our internship at X-Force Red this past summer, we noticed FalconForce’s SOAPHound was becoming popular for enumerating Active Directory environments. This tool brought a new perspective to Active Directory enumeration by performing collection via Active Directory Web Services (ADWS) instead of directly through Lightweight Directory Access Protocol (LDAP) as other AD enumeration tools had in the past.…

Smoltalk: RCE in open source agents

26 min read - Big shoutout to Hugging Face and the smolagents team for their cooperation and quick turnaround for a fix! Introduction Recently, I have been working on a side project to automate some pentest reconnaissance with AI agents. Just after I started this project, Hugging Face announced the release of smolagents, a lightweight framework for building AI agents that implements the methodology described in the ReAct paper, emphasizing reasoning through iterative decision-making. Interestingly, smolagents enables agents to reason and act by generating…

Being a good CLR host – Modernizing offensive .NET tradecraft

14 min read - The modern red team is defined by its ability to compromise endpoints and take actions to complete objectives. To achieve the former, many teams implement their own custom command-and-control (C2) or use an open-source option. For the latter, there is a constant stream of post-exploitation tooling being released that takes advantage of various features in Windows, Active Directory and third-party applications. The execution mechanism for this tooling has, for the last several years, relied heavily on executing .NET assemblies in…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today