Register for our upcoming webinar with the Maltego CEO and CTO! How Maltego Empowers Law Enforcement Across Everchanging OSINT Landscape with Strategic Acquisitions of PublicSonar and Social Network Harvester on Tuesday, April 30, 2024 at 15:00 CET. Register now! close
23 Mar 2021

Tackling Tool Fatigue: SOC Teams Need Interoperable Tools

Maltego Team

Global spend on information security and risk management tools has shown a steady upward trend in the past years. The spend on enterprise software alone is estimated to grow to 557.4 billion dollars through 2022 as remote work environments become more pervasive—thanks to the COVID-19 pandemic. As organizations continue to equip themselves with the right technologies and skills to combat cyber threats, breaches still continue to occur risking heavy financial and reputational loss to businesses. In 2020, IBM estimated the average cost of a data breach at 3.86 million dollars.

According to a talk at RSA 2019 by security operations consultants from Palo Alto Networks, small organizations use 15 to 20 security tools, medium organizations use 50-60 tools and large organizations use as many as 130 tools! Using so many tools inevitably results in higher costs of ownership, increased complexity, and more technology for security teams to manage and master. Tech Target reported that many CISOs can’t keep up with the endless technology updates to their own security portfolios—as much as 50% of existing functionality actually goes unused—let alone the constant barrage of new controls.

Why Are There So Many Tools in Use? 🔗︎

Organizational teams tasked with protecting the security systems of the organization are called a Security Operations Center (SOC). SOC teams tasks range from set up and configuration, monitoring of systems, and the detection, investigation, and remediation of unintended incidents.

SOC teams undergo multiple stages of evolution as they grow, and over time new tools are acquired to solve new and specific challenges. In addition, enterprise IT infrastructures are becoming increasingly complex as companies steadily move to cloud solutions, workforces become remote, and the use of mobile and inter-connected devices becomes more widespread, resulting in new security solutions.

Finally, we find that larger organizations will tend to have a decentralized SOC and multiple supporting teams, each with their own toolset. This leads to a sprawling number of tools, particularly in large organizations, which are often not integrated with each other.

Standard tools used by a security operations center

Too Many Tools, Too Little Integration 🔗︎

It is apparent that there is a burgeoning number of technologies and vendors on the market, each adding new and more powerful capabilities to help SOCs and adjacent teams. A study by the SANS Institute found that “too many tools that are not integrated” was one of the key challenges faced by SOCs, next to a lack of skilled staff and the need for automation and orchestration.

Another enterprise study on “The State of the SOC” commissioned by Fidelis reported that integrated investigation across endpoints, servers, and networks remains a major challenge for SOCs. While the importance of integrated collaborative investigation remained unquestioned, practical implementation was found to be ineffective due to the tedious work required to tie information from all systems together into a single investigation.

A SOC should be built keeping the interoperability of applications in mind. Tools in a traditional cybersecurity stack tend to be disparate solutions that are difficult to integrate, manage, and use.

How SOC Teams Can Tackle Tool Fatigue 🔗︎

In this whitepaper, we take a look at the standard toolset of a SOC team and present the solution to tackle tool fatigue: Introducing interoperable tools to your SOC team.

Download this whitepaper and learn how to leverage your tool stack to its full potential while ensuring efficiency in the workflow.

Don’t forget to follow us on Twitter and LinkedIn or subscribe to our email newsletter for more whitepapers, case studies, and SOC tips like this!

Download the resource

DE +49
Albania +355
Algeria +213
Andorra +376
Angola +244
Anguilla +1264
Antigua And Barbuda +1268
Argentina +54
Armenia +374
Aruba +297
Australia +61
Austria +43
Azerbaijan +994
Bahamas +1242
Bahrain +973
Bangladesh +880
Barbados +1246
Belarus +375
Belgium +32
Belize +501
Benin +229
Bermuda +1441
Bhutan +975
Bolivia +591
Bosnia and Herzegovina +387
Botswana +267
Brazil +55
Brunei Darussalam +673
Bulgaria +359
Burkina Faso +226
Burundi +257
Cambodia +855
Cameroon +237
Canada +1
Cape Verde +238
Cayman Islands +1345
Central African Republic +236
Chile +56
China +86
Cote d'Ivoire +225
Colombia +57
Comoros +269
Congo +242
Cook Islands +682
Costa Rica +506
Croatia +385
Cuba +53
Cyprus +90392
Czech Republic +42
Denmark +45
Djibouti +253
Dominica +1809
Dominican Republic +1809
Ecuador +593
Egypt +20
El Salvador +503
Equatorial Guinea +240
Eritrea +291
Estonia +372
Ethiopia +251
Falkland Islands (Malvinas) +500
Faroe Islands +298
Fiji +679
Finland +358
France +33
French Guiana +594
French Polynesia +689
Gabon +241
Gambia +220
Georgia +7880
Germany +49
Ghana +233
Gibraltar +350
Greece +30
Greenland +299
Grenada +1473
Guadeloupe +590
Guam +671
Guatemala +502
Guinea +224
Guinea-Bissau +245
Guyana +592
Haiti +509
Honduras +504
Hong Kong +852
Hungary +36
Iceland +354
India +91
Indonesia +62
Iran, Islamic Republic of +98
Iraq +964
Ireland +353
Israel +972
Italy +39
Jamaica +1876
Japan +81
Jordan +962
Kazakhstan +7
Kenya +254
Kiribati +686
Korea, Democratic People's Republic of +850
Korea, Republic of +82
Kuwait +965
Kyrgyzstan +996
Lao People's Democratic Republic +856
Latvia +371
Lebanon +961
Lesotho +266
Liberia +231
Libyan Arab Jamahiriya +218
Liechtenstein +417
Lithuania +370
Luxembourg +352
Macao +853
Macedonia, the former Yugoslav Republic of +389
Madagascar +261
Malawi +265
Malaysia +60
Maldives +960
Mali +223
Malta +356
Marshall Islands +692
Martinique +596
Mauritania +222
Mauritius +230
Mayotte +269
Mexico +52
Micronesia, Federated States of +691
Moldova, Republic of +373
Monaco +377
Mongolia +976
Montserrat +1664
Morocco +212
Mozambique +258
Myanmar +95
Namibia +264
Nauru +674
Nepal +977
Netherlands +31
New Caledonia +687
New Zealand +64
Nicaragua +505
Niger +227
Nigeria +234
Niue +683
Norfolk Island +672
Northern Mariana Islands +670
Norway +47
Oman +968
Pakistan +92
Palau +680
Panama +507
Papua New Guinea +675
Paraguay +595
Peru +51
Philippines +63
Poland +48
Portugal +351
Puerto Rico +1787
Qatar +974
Reunion +262
Romania +40
Russian Federation +7
Rwanda +250
San Marino +378
Sao Tome and Principe +239
Saudi Arabia +966
Senegal +221
Serbia +381
Seychelles +248
Sierra Leone +232
Singapore +65
Slovakia +421
Slovenia +386
Solomon Islands +677
Somalia +252
South Africa +27
Spain +34
Sri Lanka +94
Saint Helena +290
Saint Kitts and Nevis +1869
Saint Lucia +1758
Sudan +249
Suriname +597
Swaziland +268
Sweden +46
Switzerland +41
Syrian Arab Republic +963
Taiwan +886
Tajikistan +7
Thailand +66
Togo +228
Tonga +676
Trinidad and Tobago +1868
Tunisia +216
Turkey +90
Turkmenistan +993
Turks and Caicos Islands +1649
Tuvalu +688
Uganda +256
United Kingdom +44
Ukraine +380
United Arab Emirates +971
Uruguay +598
United States +1
Uzbekistan +7
Vanuatu +678
Holy See (Vatican City State) +379
Venezuela +58
Viet Nam +84
Virgin Islands, British +84
Virgin Islands, U.S. +84
Wallis and Futuna +681
Yemen +967
Zambia +260
Zimbabwe +263

By clicking on "Access", you agree to the processing of the data you entered and you allow us to contact you for the purpose selected in the form. For further information, see our Data Privacy Policy.

By clicking on "Subscribe", you agree to the processing of the data you entered and you allow us to contact you for the purpose selected in the form. For further information, see our Data Privacy Policy.