Harish Shenoy, Author at XTHE - Page 43 of 136

Home

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
About US

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
Tech Reviews

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
- AI
- Troubleshooting
- Smartwatches
- Smartphones
- Camera
- Gadgets
- Games
- Laptops
- Seasonal Sales
Phone Features

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
Buying Guides

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
Comparison

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
News

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom
Contact

Armonk, New York

Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they exposed tens of millions of social security numbers, credit card numbers, and billing histories. On average, it takes companies 60 days to fix a discovered flaw. Criminal networks use that two-month gap to their advantage.

IBM and Red Hat want to close that gap for good.

The Project Lightwell Vault: What IBM Is Actually Building

Project Lightwell Vault defends corporate files by taking a new approach: it puts a large team of engineers directly into the software supply chain. The IBM Security Initiative, announced at the company’s headquarters in Armonk, New York, comes with a $5 billion investment and involves 20,000 engineers. That’s about as many people as work in a mid-sized American city. These engineers focus solely on identifying, verifying, and fixing weaknesses in open-source code before they reach a company’s systems.

This isn’t just a firewall upgrade or a new antivirus subscription. IBM is building what it calls a centralized security clearinghouse for enterprise open-source software. This idea directly affects every CFO, CTO, and chief risk officer at companies that use cloud infrastructure.

Why Open Source Became the Soft Underbelly of Enterprise IT

About 90 percent of today’s commercial software uses open-source parts. The Linux kernel, Apache web server, and OpenSSL encryption library are examples. These tools are the hidden foundation of the internet, but many are maintained by volunteers who often don’t have formal security review processes.

When a researcher finds a serious flaw in one of these components, a Common Vulnerabilities and Exposures (CVE) alert is made public. Unfortunately, this alert also reveals the weakness to hackers. Companies then rush to fix the problem, but often release patches weeks or months after criminals have already begun exploiting it.

Red Hat Engineering identified this structural problem years ago. The company’s enterprise Linux distribution, RHEL, has long maintained backported patches security fixes extracted from the latest upstream code and surgically reapplied to older, stable versions running in production environments. The technique allows a bank running a three-year-old server configuration to receive a critical security update without rebuilding its entire software stack. Open Source Backporting, as it is formally known, is the operational backbone of the IBM Red Hat Project Lightwell enterprise open-source security architecture.

The 20,000-Engineer Machine and How It Runs

Red Hat Engineering brings unmatched open-source expertise to the corporate world. With Project Lightwell, their engineers do more than just scan for known problems. They carefully review source code, identify production vulnerabilities before they become public, create tested patches, and apply these fixes directly to live business systems.

The automation part is what sets the IBM Security Initiative apart from what most companies can do on their own. IBM has built a continuous integration pipeline, similar to an assembly line for security patches. This system tests each fix on many different business setups before it goes live. If a patch works on a standard Red Hat system but causes problems for a custom database at an insurance company, it won’t be sent to that company. Instead, the system signals the issue and sends it to a person for review.

This degree of detail is very important. Many companies put off applying known fixes because they worry about interrupting their operations. A 2024 Ponemon Institute study found that 57 percent of IT managers had delayed patching a critical fault because they feared downtime. Project Lightwell Vault does this by providing pre-tested, environment-specific fixes that require little additional checking before use.

What Production Vulnerabilities Actually Cost American Businesses

Take a mid-sized regional retailer that uses an e-commerce platform built with open-source components. This is common for thousands of American companies. If a new vulnerability emerges in a popular authentication tool, the retailer’s IT team might have only a few engineers to assess, test, and install the patch. While this process takes weeks, the company stays at risk.

Multiply that scenario across the Fortune 500 and the small- to midsize enterprises that supply them. The IBM Red Hat Project Lightwell enterprise open-source security architecture is designed to collapse that exposure window from weeks to hours by performing evaluation and backporting work centrally and at scale, and by delivering a verified fix directly to the customer’s environment.

The customer’s network keeps running. Their engineers can focus on other tasks. And a backdoor that hackers could have used on Tuesday is closed by Wednesday morning.

The Wider Signal IBM Is Sending to the Market

A $5 billion investment is much more than a research grant. It’s a major bet on the market. IBM is showing that enterprise security, especially the tough work of maintaining open-source software at scale, is important enough to deserve the same kind of investment as a big hospital or a highway project.

For executives looking at their own security, Project Lightwell Vault raises an important question. If IBM is spending five billion dollars to fix a problem your team handles with just a few engineers and quarterly patches, what does that say about your current approach?

The answer is becoming clear: protecting corporate files from today’s fast-moving threats needs the kind of Red Hat Engineering expertise and automation that most companies can’t build on their own. IBM is betting that businesses will pay for centralized access to this service, and with breach costs rising, the numbers seem to support their bet.

The true test of Project Lightwell won’t be in press releases, but in breach statistics over the next few years. If the clearinghouse model works, the 60-day window for hackers will get smaller. That means American shoppers’ Social Security numbers will be a bit safer on the servers that store them.

Source: IBM Newsroom

Harish Shenoy

Total Post: 1358

Harish Shenoy | Technology Journalist Harish Shenoy is a veteran technology journalist at Xthe with over 21 years of experience spanning tech, health, finance, and future technology. Specializing in semiconductor roadmaps, enterprise AI infrastructure, and consumer hardware, his reporting is driven by primary-source verification and official corporate disclosures. With more than a decade of focused writing across the US, UK, Australia, Canada, and India, Harish maintains a strict commitment to factual, non-sensationalized reporting on the economic and logistical shifts within the global tech sector. His current work centers on the technical evolution of "agentic AI" and next-generation silicon.

Why This New Project Lightwell Vault Defends Corporate Files

Armonk, New York Last year, hackers exploited known software vulnerabilities to steal about $4.5 billion from American businesses. In the process, they...

How Google Just Fixed Over One Hundred Secret Android Software Bugs

Mountain View, California Even a single unnoticed vulnerability on a smartphone can put far more than the device at risk....

How Massive Upgrades Spark Incredible New Power on Windows 11

Redmond, Washington Your laptop fan kicks on, a browser tab freezes mid-presentation, and the spinning cursor becomes the most hated...

What Apple Handed To Twelve Genius Phone App Creators This Week

Cupertino, California Most apps are forgotten within three days of being downloaded. While the average American has 80 apps on their...

Why Congress Wants Nvidia Chief Jensen Huang To Testify Now

Washington, District of Columbia The top executive in the semiconductor industry has been called to Capitol Hill, and he can expect some...

How This New Microsoft Work IQ Tool Does Your Hardest Tasks

Redmond, Washington Your inbox contains 340 unread messages. Three calendar appointments overlap with a board presentation you still need to start. A...

Why Are Cisco AI Agents Becoming Your New Office Teammates?

Las Vegas, Nevada When your video call froze during a presentation, or your company’s cloud apps slowed down, someone in...

How Rugged New AMD Electronic Brains Drive Farm Robots Safely

Santa Clara, California At 3 a.m. in a Nebraska soybean field, a driverless tractor moves through the crops. Dust fills...

Which Qualcomm Smartphone Chip Keeps Your Screen Alive All Day Long?

San Diego, California Your phone is dead. It’s 2:47 p.m., you’re between meetings, and the nearest outlet is three floors away. This situation happens...

How New Palo Alto Firewalls Stop Bad Guys From Stealing Files

Santa Clara, California Last year, a mid-sized e-commerce retailer found that about 200,000 customer records had quietly left its network...