Microsoft and Crowdsstrike today announced that they have really participated to add nicknames used for specific danger groups without using single naming standard.
As the two companies explained on Monday, it would be done by mapping (or linking), which track various names used by their safety analysts for each group.
Microsoft has updated it Threat actor reference guide With a list of normal hacking groups tracked by Crowdastric and Redmund, all mapped using naming systems of each company.
“This reference guide acts as an early point, is a way to translate into naming systems so that defenders can work rapidly and more efficiently, especially in an environment where many sellers are in playing insight by many sellers,” Said Vasu Jakkal, Corporate Vice President for Microsoft Security.
“This effort is not about creating a single nomenclature standard. Rather, it is to help our customers and the comprehensive security community has more easily aligned intelligence information, responded rapidly, and is to be ahead of the danger actors.”
This naming taxonomy mapping effort tracking overlapping threes is an early step towards making actor activity easier and avoiding unnecessary confusion and complexity.
As Microsoft still revealed, Google/Mandiant and Palo Alto Nettors’ Unit 42 are also contributing their information to rapid and clear the atribution with other cyber security companies with the possibility of joining this initiative in future.
After the more security firm joining this alliance and sharing its telemetry data, this initiative will bring clarity and simplify it to translate naming systems for network guards and create more accurate views about malicious campaigns.
“Crowdastric and Microsoft are proud to take the first step, but we know that it must be a community -led initiative to succeed,” couple Adam Mayors, Senior Vice President for Intelligence in Crowdastrik.
“Together, companies have already disintegrated actors with more than 80 threats through direct, analyst -led cooperation. They represent some of the most active and sophisticated opponents in the world.
Manual patching is old. It is slow, error-prone and hard for scale.
On June 4, join Kandji + Tines, to see why the older methods are short. See the real -world examples of how modern teams use automation to patch rapid patching, risk cuts, obedient stay and leaving complex scripts.
