News and blog
NXLog main page
  • Products
    NXLog Platform
    Log collection
    Log management and analytics
    Log storage
    NXLog Community Edition
    Integrations
    Professional Services
  • Solutions
    Use cases
    Specific OS support
    SCADA/ICS
    Windows event log
    DNS logging
    MacOS logging
    Solutions by industry
    Financial Services
    Government & Education
    Entertainment & Gambling
    Telecommunications
    Medical & Healthcare
    Military & Defense
    Law Firms & Legal Counsel
    Industrial & Manufacturing
  • Plans
  • Partners
    Find a Reseller
    Partner Program
  • Resources
    Documentation
    Blog
    White papers
    Videos
    Webinars
    Case Studies
    Community Program
    Community Forum
  • About
    Company
    Careers
  • Support
    Support portals
    Contact us

NXLog Platform
Log collection
Log management and analytics
Log storage
NXLog Community Edition
Integrations
Professional Services

Use Cases
Specific OS support
SCADA/ICS
Windows event log
DNS logging
MacOS logging
Solutions by industry
Financial Services
Government & Education
Entertainment & Gambling
Telecommunications
Medical & Healthcare
Military & Defense
Law Firms & Legal Counsel
Industrial & Manufacturing


Find a Reseller
Partner Program

Documentation
Blog
White papers
Videos
Webinars
Case Studies
Community Program
Community Forum

Company
Careers

Support portals
Contact us
Let's Talk Start free
NXLog search
  • Loading...
Let's Talk Start free
February 13, 2023 strategysiem

Avoid vendor lock-in and declare SIEM independence

By Andrew Brown

Share
ALL SIEM STRATEGY SECURITY ANNOUNCEMENT DEPLOYMENT COMPLIANCE COMPARISON RSS

The global Security Information and Event Management (SIEM) market is big business. In 2022, it was valued at $5.2 billion, with analysts projecting that it will reach $8.5 billion dollars within five years.

It’s a highly consolidated market dominated by a few major players in the information security field. They want your business, and they don’t want to lose it.

As companies ship more and more data to their respective solutions and make use of more and more features, they become specialized and dependent on a vendor. If this sounds familiar, then you may have fallen prey to vendor lock-in.

What is vendor lock-in?

vendor lock in

Vendor lock-in is a situation where a customer becomes dependent on a particular product from a particular vendor, regardless of how well the product fits. You are essentially locked into using a product because of the high (or even unknown) cost associated with switching to a new vendor.

Imagine an office with printing services brought in by a third-party vendor, bringing in printers with their servicing, and so on. However, these machines require software sold by this particular third-party company only. Now imagine a steep decline in the quality of the printing that this vendor delivers (printed pages are of poor quality).

Switching to a new printing vendor would mean the old machines you purchased become useless, as the switch likely requires the purchase of new printing equipment, including a new software solution. Given the hassle and added expense of replacing every piece of the existing system, you are effectively locked into the old printing solution agreement with the old vendor and forced to get on with the low-quality printing.

Why is vendor lock-in a concern?

Oftentimes, companies don’t know that they’re locked into a particular product or solution until disaster strikes. Let’s think ahead and list some of the most prominent concerns.

  • Perhaps your vendor goes out of business or stops trading.

  • Your vendor might stop maintaining the product that you are dependent on.

  • A vendor may change its offerings which will be unsuitable for your business needs.

  • License costs could increase beyond your budget - knowing that clients are locked-in.

  • An expert employee leaves your company without a proper handover.

There are a number of ways for companies to get locked into a certain solution. Ultimately, when you’ve decided that your current solution isn’t working and subsequently realize there isn’t an easy or cheap way to change, you’ve fallen victim to vendor lock-in.

Mitigating vendor lock-in

Once you have an understanding of how vendor lock-in can cause headaches for, and even damage to, your company, you’re ready to start mitigating the risk.

First things first, determine whether and how much you are at risk. How heavily do you rely on a particular vendor’s solution? Is the vendor a reliable partner? For example, do you receive timely notifications of service contract updates? Are bug fixes provided promptly? These are the types of questions that should be asked and answered to quantify the vendor lock-in risk.

Ask yourself, are you happy to live with the risk? Companies make risk-based decisions constantly; many of these are decisions to bear the potential cost of the risk if it ever develops.

If retaining this risk is not possible or undesirable, start taking back control of your data.

Microsoft’s early fight against vendor lock-in

In the early 1990s, Lotus123 was the premier spreadsheet program. It held a near-monopolistic grasp on the spreadsheet market. An upstart competitor, eager to break into the domain, developed a program of their own. The company was Microsoft, and the software was Excel. What followed was something of a David vs Goliath tale, with Microsoft incredibly playing the role of David.

We all know who won the 'spreadsheet wars', but it was never a foregone conclusion. Microsoft’s fundamental challenge against its entrenched competitor was that potential customers had already made substantial investments in Lotus123 spreadsheets, and couldn’t easily switch. In other words, these companies were locked into Lotus123.

So how did Microsoft solve this problem? They programmed Excel to read and write Lotus123 spreadsheet files. This allowed them to sell into Lotus123-powered companies without resistance. It also allowed the companies to focus on their data and analysis, without worrying about the file format they were using.

Locked into a SIEM? NXLog can help

SIEMs are especially complex software products, processing near-incomprehensible amounts of data across an entire organization. Most often, their capricious pricing models are based on throughput, rather than a consistent monthly or annual cost. The deeply-entwined relationship between an organization’s log data and a monolithic, all-knowing SIEM proves inordinately difficult to untangle once implemented.

If you’ve found yourself locked into a SIEM solution with no easy escape, NXLog can help. NXLog Enterprise Edition sits upstream from your log management solutions—​whether they be SIEMs or data lakes—​and provides a vendor-agnostic solution to collecting and centralizing your logs. This allows flexibility in the log management products used downstream.

NXLog seamlessly integrates with literally any solutions out of the box. Our agent accepts every type of common log format and can transform this data to the required output format.

If you want to switch SIEMs, you can—​easily. By using NXLog Enterprise Edition, you can declare SIEM independence.

NXLog Platform is an on-premises solution for centralized log management with
versatile processing forming the backbone of security monitoring.

With our industry-leading expertise in log collection and agent management, we comprehensively
address your security log-related tasks, including collection, parsing, processing, enrichment, storage, management, and analytics.

Start free Contact us
  • SIEM
  • vendor lock-in
Share

Facebook Twitter LinkedIn Reddit Mail
Related Posts

Three important features you can have with the Enterprise Edition over the Community Edition
3 minutes | October 27, 2021
Using Raijin Database Engine to aggregate and analyze Windows security events
11 minutes | July 29, 2021

Stay connected:

Sign up

Keep up to date with our monthly digest of articles.

By clicking singing up, I agree to the use of my personal data in accordance with NXLog Privacy Policy.

Featured posts

Announcing NXLog Platform 1.6
April 22, 2025
Announcing NXLog Platform 1.5
February 27, 2025
Announcing NXLog Platform 1.4
December 20, 2024
NXLog redefines log management for the digital age
December 19, 2024
2024 and NXLog - a review
December 19, 2024
Announcing NXLog Platform 1.3
October 25, 2024
NXLog redefines the market with the launch of NXLog Platform: a new centralized log management solution
September 24, 2024
Welcome to the future of log management with NXLog Platform
August 28, 2024
Announcing NXLog Enterprise Edition 5.11
June 20, 2024
Raijin announces release of version 2.1
May 31, 2024
Ingesting log data from Debian UFW to Loki and Grafana
May 21, 2024
Announcing NXLog Enterprise Edition 6.3
May 13, 2024
Raijin announces release of version 2.0
March 14, 2024
NXLog Enterprise Edition on Submarines
March 11, 2024
The evolution of event logging: from clay tablets to Taylor Swift
February 6, 2024
Migrate to NXLog Enterprise Edition 6 for our best ever log collection experience
February 2, 2024
Raijin announces release of version 1.5
January 26, 2024
2023 and NXLog - a review
December 22, 2023
Announcing NXLog Enterprise Edition 5.10
December 21, 2023
Raijin announces release of version 1.4
December 12, 2023
Announcing NXLog Enterprise Edition 6.2
December 4, 2023
Announcing NXLog Manager 5.7
November 3, 2023
Announcing NXLog Enterprise Edition 6.1
October 20, 2023
Raijin announces release of version 1.3
October 6, 2023
Upgrading from NXLog Enterprise Edition 5 to NXLog Enterprise Edition 6
September 11, 2023
Announcing NXLog Enterprise Edition 6.0
September 11, 2023
The cybersecurity challenges of modern aviation systems
September 8, 2023
Raijin announces release of version 1.2
August 11, 2023
The Sarbanes-Oxley (SOX) Act and security observability
August 9, 2023
Log Management and PCI DSS 4.0 compliance
August 2, 2023
Detect threats using NXLog and Sigma
July 27, 2023
HIPAA compliance logging requirements
July 19, 2023
Announcing NXLog Enterprise Edition 5.9
June 20, 2023
Industrial cybersecurity - The facts
June 8, 2023
Raijin announces release of version 1.1
May 30, 2023
CISO starter pack - Security Policy
May 2, 2023
Announcing NXLog Enterprise Edition 5.8
April 24, 2023
CISO starter pack - Log collection fundamentals
April 3, 2023
Raijin announces release of version 1.0
March 9, 2023
Avoid vendor lock-in and declare SIEM independence
February 13, 2023
Announcing NXLog Enterprise Edition 5.7
January 20, 2023
NXLog - 2022 in review
December 22, 2022
Need to replace syslog-ng? Changing to NXLog is easier than you think
November 23, 2022
The EU's response to cyberwarfare
November 22, 2022
Looking beyond Cybersecurity Awareness Month
November 8, 2022
GDPR compliance and log data
September 23, 2022
NXLog in an industrial control security context
August 10, 2022
Raijin vs Elasticsearch
August 9, 2022
NXLog provides native support for Google Chronicle
May 11, 2022
Aggregating macOS logs for SIEM systems
February 17, 2022
How a centralized log collection tool can help your SIEM solutions
April 1, 2020

Categories

  • SIEM
  • STRATEGY
  • SECURITY
  • ANNOUNCEMENT
  • DEPLOYMENT
  • COMPLIANCE
  • COMPARISON
logo

Subscribe to our newsletter to get the latest updates, news, and products releases. 

© Copyright 2024 NXLog FZE.

Privacy Policy. General Terms of Use

Follow us

  • Product
  • NXLog Platform 
  • Log collection
  • Log management and analysis
  • Log storage
  • Integration
  • Professional Services
  • Plans
  • Resources
  • Documentation
  • Blog
  • White papers
  • Videos
  • Webinars
  • Case studies
  • Community Program
  • Community forum
  • Support
  • Getting started guide
  • Support portals
  • About NXLog
  • About us
  • Careers
  • Find a reseller
  • Partner program
  • Contact us