Cybersecurity news

Cybersecurity news

Cybersecurity news

  • A threat actor is promoting a new version of their free-to-use ‘Redeemer’ ransomware builder on hacker forums, offering unskilled threat actors an easy entry to the world of encryption-backed extortion attacks. The author states that the new 2.0 release was written entirely in C++. It works on Windows Vista, 7,8,10, and 11, featuring multi-threaded performance and a medium AV detection rate.
  • A cryptomining gang known as 8220 Gang has been exploiting Linux and cloud app vulnerabilities to grow their botnet to more than 30,000 infected hosts. The group is a low-skilled, financially-motivated actor that infects AWS, Azure, GCP, Alitun, and QCloud hosts after targeting publicly available systems running vulnerable versions of Docker, Redis, Confluence, and Apache.
  • Atlassian has patched a critical hardcoded credentials vulnerability in Confluence Server and Data Center that could let remote, unauthenticated attackers log into vulnerable, unpatched servers.

Cybersecurity news

Cybersecurity news

Approaches to threat data exchange are currently in an active phase of formation and standardization. Today there are a couple of significant standards, namely, MISP and STIX,  and entire assemblage of less significant ones that are less commonly used or considered deprecated,  such as MAEC, IODEF, OpenIOC (Cybox), CAPEC, VERIS and many others. At that, a decent number of community feeds are still distributed in the txt or csv formats, as well as in the form of human-readable analytical summaries, bulletins, and reports.

This article deals with analysis of the generally accepted practices of data exchange about cyber threats, namely, specialized formats and general-purpose standards designed not only for threat intelligence (TI). At that, purely proprietary, rare and “reinvent-the-wheel” formats, as well as thematic blogs, news portals, messenger communities, and other TI sources in human-readable formats are left out of the scope of the present article. Today the focus is on machine-readable formats.

Cybersecurity news

Consultants from Defensys’s Center of expertise along with our partners are ready to map the current correlation rules of SIEMs and other security tools of our customers with MITRE tags so that the incident registered in SOAR will already contain all the needed data.

It’s been almost a year and a half since we started this practise with one of our Telecom customers. At the moment we’ve got all SOAR implementation projects where this mapping exists. This way you can ease the process of incidents classification, adopt proper playbooks, draw metrics with statistics. And of course you can speak the same language with the community when it comes to discuss some interesting or critical cases.” – says Andrey Chechetkin, Deputy CEO of Defensys.

We’d like to remind you that after the implementation of the Defensys SOAR in the incident card a customer is able to see:

The Defensys company issued the fifth version of its SOAR platform which is core solution for building Security Operations Centers (SOC) of different scales. SOAR v 5.0 got a lot of new features. In particular there appeared a native part in the incident card for working with IoCs which come from security alerts and Threat Intelligence platforms. User experience in operating with playbooks updated significantly as well. Besides the overall interface of the system got serious enhancements.

Important changes are ready to be used in the core functional block of incident management. The version 5.0 of Defensys SOAR gives you the opportunity to work with groups of incidents and it helps users conveniently handle cases when several incidents are related between each other. You can simply customize policies for auto filling field values inside this group of incidents. For example the parent incident status could be just inherited in included incidents or the total amount of damage will be automatically placed into the dedicated field in the parent incident. One more important feature is the part of incident card specially tailored to work with IoCs in the most convenient way and of course all the results of operating with IoCs are distributed into the variety of dashboards.

Challenge

With 5 independent regional SOCs connected to the main SOC in HQ the Company’s cybersecurity staff had to register incidents in service desk, that wasn’t connected to an IT SD but all the other data needed for the investigation was manually collected from multiple sources: security tools, data lakes, billing systems. Also, it was quite difficult to quickly find properties of the technical equipment involved in the cyber incident. Threat Intelligence data was processed semi-automatically without any connections to other systems.

Defensys products

After a comprehensive procedure of comparing different technologies for building the next version of SOC the Company have chosen Defensys as a leader in automating cybersecurity processes. The decision was to use SOAR and TIP to enhance capabilities of an existing SOC with a lot of systems not connected with each other.

Results

All the incidents from different security tools along with customers’ enquiries are processed in one system that helps to use the same investigation frameworks for different teams that is important when it comes to collect performance metrics. These incidents are automatically registered based on the MITRE ATT&CK framework so the whole team operates with the same terms when working during the response process.