The Security for Business Innovation Council (SBIC) recently released a report detailing how to battle advanced...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
persistent threats (APTs), including the necessity of sharing security intelligence, including attack indicators, with one another. How should enterprises go about building security relationships with other enterprises and creating security networks? What limits should be placed on the information to be shared?
It is widely believed that attackers share information faster than defenders share information, and if defenders could only share information faster, more security incidents could be prevented.
A number of different organizations have worked to improve the sharing of security intelligence data like attack or compromise indicators, including Computer Emergency Response Teams (CERTs), Information Sharing and Analysis Centers (ISACs), which are focused on industry verticals, Infragard and the like. There are information-sharing frameworks like the Verizon VERIS, Mandiant OpenIOC and others. With the increased scrutiny on effectiveness in information security, using hard data for making decisions is critical. These information security sharing organizations could gather incident data and then produce reports like the Verizon Data Breach Investigations Report.
Enterprises can build security intelligence sharing networks with other enterprises through traditional methods such as joining information security organizations (local, regional and national) and an ISAC. Just joining an organization is not sufficient, though. To create a strong security network and most effectively build security relationships, an enterprise must engage other enterprises and become a trusted member of the community.
There are, of course, limits to the information that should be shared, and these limits must be strictly followed to support the trusted relationships. Sharing appropriate information should be done liberally within trusted communities, but sharing others' information should be done conservatively and only with the intent with which the information was shared. Maintaining trust in the community is critical. Many organizations are apprehensive about sharing sensitive incident information because of concerns about negative repercussions, but there is scant public information available about an organization being harmed due to sharing incident information within a trusted community (or even publicly). Enterprises should evaluate how an attacker could use information before it is shared or aggregated, though.
Ask the expert!
Have questions about enterprise information security threats for expert Nick Lewis? Send them via email today! (All questions are anonymous).
Dig Deeper on Business Management: Security Support and Executive Communications
Related Q&A from Nick Lewis
An HTTPS session with a reused nonce is vulnerable to the Forbidden attack. Expert Nick Lewis explains how the attack works, and how to properly ...continue reading
The Irongate malware has been discovered to have similar functionality to Stuxnet. Expert Nick Lewis explains how enterprises can protect their ICS ...continue reading
APT groups have been continuously exploiting a flaw in Microsoft Office, despite it having been patched. Expert Nick Lewis explains how these attacks...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.