Parting thoughts 4: the big picture

Posted by    on   Dec 20, 2019

At the end of this month, I will step down as Editor of Virus Bulletin. Before I do so, I will share some 'parting thoughts' in five blog posts, based on my experience working in the IT security industry.

Last week, Microsoft published a report on what it calls 'GALLIUM', an attack targeting telecom providers around the world. It was an interesting, well-researched report on a long-running operation, with some useful details and a list of indicators of compromise. The same attack had previously been described by Cybereason, who referred to it as 'Operation Soft Cell'; it was also presented at VB2019 by the Cybereason researchers. Microsoft didn't mention this in its report.

This is not to pick on Microsoft. Lack of proper referencing of other researchers' work is frustratingly common in threat intelligence, despite a general spirit of cooperativeness among researchers.

This isn't about different companies giving different names to malware, groups and operations either. There are often valid reasons for them doing so, from trying to maintain consistent naming conventions to parallel discovery of threats and differing views on what can be grouped together under a single name. Often threat reports do include other names given to the same groups. In many other cases they do not.

I also understand the desire among marketing departments to claim research as their company's own. I am not a marketing person and it is not for me to criticise marketing blog posts that do so. It is fine to publish a separate blog post that focuses on the marketing aspect.

I also understand that some companies have made the decision to monetise their research and share some reports only with paying customers. It does mean that a lot of research is hidden from public view, but good research costs a lot of money and it seems only fair that companies are looking to be compensated for that.

But the moment a company publishes a report for the research and defender communities, complete with IoCs, there is no excuse not to link to related research and explain how the research fits into the broader context. In fact, this will make the report many times more valuable.

Of course, this also encourages other researchers to refer to the work. And perhaps more importantly, by showing the bigger context into which the research fits, the possibility is opened of interesting collaborations that could not only add value to the research but also one's product or service.

big-picture.jpg

 Tags

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2021 localhost call for last-minute papers

The call for last-minute papers for VB2021 localhost is now open. Submit before 20 August to have your paper considered for one of the slots reserved for 'hot' research!

New article: Run your malicious VBA macros anywhere!

Kurt Natvig explains how he recompiled malicious VBA macro code to valid harmless Python 3.x code.

New article: Dissecting the design and vulnerabilities in AZORult C&C panels

In a new article, Aditya K Sood looks at the command-and-control (C&C) design of the AZORult malware, discussing his team's findings related to the C&C design and some security issues they identified.

VB2021 localhost call for papers: a great opportunity

VB2021 localhost presents an exciting opportunity to share your research with an even wider cross section of the IT security community around the world than usual, without having to take time out of your work schedule (or budget) to travel.

New article: Excel Formula/Macro in .xlsb?

In a follow-up to an article published last week, Kurt Natvig takes us through the analysis of a new malicious sample using the .xlsb file format.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.