June 28, 2022 By Michael Thompson 4 min read

It might be cliché to say that security is critical for enterprises, but that doesn’t make it any less true.

Across the IT landscape, security is a multifaceted exercise. Security in depth is the concept where security best practices are applied at every level of IT — including networks, operating systems, databases, applications (purchased or developed) and physical access to machine rooms, server racks and buildings. Advanced techniques like intrusion detection, penetration testing (sometimes called “white hat hacking”) and threat monitoring have become standard at large enterprises and government entities.

Patch currency remains a challenge for parts of the software stack

While these advanced practices are absolutely critical to maintaining a strong security posture for the enterprise, there remain areas where foundational security practices are not always rigorously applied. One foundational practice is keeping the software stack up to date with the latest software levels and security patches. Keeping software up to date, particularly in the middleware and application space, can lag behind — sometimes significantly. 

This is due to a variety of factors — the human time cost of applying updates, the risks and test effort required from breaking changes in the software (typically from version-to-version incompatibilities), the old adage of “if it ain’t broke, don’t fix it” and other organizational priorities superseding the software patching and maintenance process. Being behind on software security patches (or worse, being on old, outdated versions of software that no longer receive such patches) increases an organization’s threat risk.

Essentially, “patch currency” is a critical software security practice, and delays in the security patching process increase an organization’s threat exposure. Efforts to remain current are often hampered by the burdensome effort it puts on the teams who maintain the software. The operations teams are required to test and deploy the updates, and the development teams are required to react to new versions and breaking changes.

For enterprises to be agile and secure — without placing an undue burden on these teams — they need to select technologies that are secure by design, provide rapid updates in response to software vulnerabilities and deliver frequent, easy-to-consume updates to their software.

Solutions from Software as a Service (SaaS) providers have alleviated much of this concern, as the responsibility for maintaining the security of the software that underpins the service is the responsibility of the SaaS provider and is enforced with SLAs. However, for software that remains on-premises and managed by software operations teams, the challenge persists. Operating system vendors like Microsoft, Red Hat and Canonical have been delivering strong software patching and update capabilities over the past few decades. In contrast, seamless security updates for middleware and applications have received less attention.

This is one of the many spaces in which IBM has been investing. With IBM’s long track record on security — from world-class security on the Z mainframe to the long-standing X-Force capabilities — and with the recent announcement of the acquisition of Randori, IBM’s commitment to security is clear.

Within IBM Automation, we’ve unleashed our creativity to apply automation to key pain point areas that we understand from the general market and from our customers.

Automation will ease the burden faced by teams

The top reported pain point is the burden of patch currency for middleware. The burden of the effort means teams are inhibited from spending time on strategic initiatives. At the heart of this pain point is a lack of automation and a lack of visibility across the variety of deployments for which teams are responsible. The lack of visibility often correlates to a weakened security posture, as visibility is necessary in order to understand what attack surface exists for a given software product or application and thereby understand what actions are necessary to maintain a secure posture. In order to reduce the burden of the security patching process, a combination of automation (to reduce cycle times and human burden) and increased visibility (to ensure required actions are taken and updates are applied successfully) is required.

Automation will help teams achieve continuous security by reducing the burden and cost to maintain software. Practices like vulnerability assessment, tracking and remediation can be automated to reduce or remove labor-intensive, repetitive tasks. There are various software solutions that focus on specific aspects of patch currency, but very few bring together a comprehensive view that is actionable by the actual team responsible for the work. 

Typically, security scanning tools and expertise is centralized within an organization and then actions are “pushed down” to owning teams. This can create delays and silos of information that create suboptimal workflows and split responsibility. A more efficient approach is to have tools that deliver actionable insights to the responsible operations and development team(s), with reporting capabilities to key stakeholders like executives and compliance teams.

Innovations from the WebSphere portfolio will ease continuous security compliance

The WebSphere portfolio has evolved to help our customers alleviate the burden of maintaining a strong security posture for the WebSphere deployments, enabling them to achieve continuous security compliance in two key ways: Liberty continuous security updates and IBM WebSphere Automation.

WebSphere Liberty and Open Liberty: It has never been easier to keep your application server up to date with the Liberty runtime. Open Liberty and the commercial version, WebSphere Liberty, deliver updates every four weeks. These production-ready software updates include the latest security fixes, performance enhancements and new capabilities which can be rapidly deployed with minimal effort. Liberty’s zero-migration policy, which is a commitment from IBM to not regress application APIs or server configuration, and Liberty’s features-by-configuration model mean that the latest Liberty update can be deployed confidently without risk of breaking your application deployments.

IBM WebSphere Automation: IBM is offering WebSphere Automation to simplify the way operations teams work with automation to proactively automate the protection, health and optimization of your WebSphere estate so that your teams can focus on the work that matters the most. Automate your existing IBM WebSphere security and operational activities to reduce the cycle time of threat remediation, so your threat exposure is minimized and your business and most critical assets are protected. Stay on top of the latest security threats with automation for vulnerability detect, remediation and compliance tracking.

Was this article helpful?

More from Automation

Announcing the general availability of IBM Concert

< 1 min read - At Think 2024, we announced IBM Concert®. It provides generative AI driven insights for your applications and puts site reliability engineers (SREs) and developers in control, enabling them to simplify and optimize their operations across any environment. IBM Concert is now generally available. You can now start using IBM Concert to get a detailed view of your applications and environments and apply generative AI to get insights on how to optimize your applications so your business works better.  Powered by…

Making HTTPS redirects easy with IBM NS1 Connect

3 min read - HTTPS is now the standard for application and website traffic on the internet. Over 85% of websites now use HTTPS by default—it’s to the point where a standard HTTP request now seems suspicious.  This is great for the security of the internet, but it’s a huge pain for the website and application teams that are managing HTTPS records. It was easy to move HTTP records around with a simple URL redirect. HTTPS redirects, on the other hand, require changing the URL…

5 SLA metrics you should be monitoring

7 min read - In business and beyond, communication is king. Successful service level agreements (SLAs) operate on this principle, laying the foundation for successful provider-customer relationships. A service level agreement (SLA) is a key component of technology vendor contracts that describes the terms of service between a service provider and a customer. SLAs describe the level of performance to be expected, how performance will be measured and repercussions if levels are not met. SLAs make sure that all stakeholders understand the service agreement…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters