04/23/2025 | Press release | Distributed by Public on 04/23/2025 07:18
IT leaders face mounting challenges in securing complex tech stacks amid evolving threats, performance demands, and compliance pressures. But unifying observability and security can help balance these competing priorities. Through real-world examples like IngressNightmare and Log4Shell, discover key capabilities of unified observability that help teams deliver performance, reliability, security, and compliance without compromising innovation.
"The best defense is a good offense." With the threat surfaces of modern IT environments always expanding, taking the initiative can be the most effective way to protect your business rather than passively waiting to react to a threat or attack.
Technical leaders bear the ultimate responsibility for the security outcomes of increasingly complex tech stacks. Breaches risk financial loss and reputational damage. But it's IT teams who face the daily challenge of securing these dynamic environments and meeting compliance and performance requirements. Teams also need room to innovate and adopt new tools that address evolving organizational needs.
Balancing these competing demands is no small task. Decision-makers must accommodate flexibility and creativity while maintaining a foundation of security and stability. They must also consider business imperatives, including cost management and sustainability goals, all without compromising the quality of technology services.
As a leader, how can you get ahead of these challenges, and what capabilities do you need to strike the right balance? Unifying observability signals and context with security capabilities is a crucial advantage for teams that must simultaneously deliver security, performance, compliance, and business objectives.
Modern tech stacks consist of a myriad services that address specific needs at every stage. But these services, which span hybrid and multi-cloud environments, also introduce ever-expanding attack surfaces. While microservices, container orchestration, and broader DevSecOps practices have transformed software delivery, they also present some very real challenges.
Balancing these priorities demands a leadership mindset that simultaneously helps teams innovate while assisting the organization in meeting its performance, compliance, and cost obligations. Striking this balance also requires some key capabilities.
The challenge for technical leaders comes down to this question: How do you offer your teams the tools and freedoms they need to be creative while maintaining the guardrails that protect applications and stabilize operations?
The answer lies in creating an operating environment that integrates security, performance, and compliance capabilities at every layer.
Comprehensive observability of every layer-from infrastructure to user experience-is vital for identifying IT and security risks, optimizing performance, and providing context to link IT with business goals.
Observability facilitates runtime vulnerability analytics and application protection so teams can monitor vulnerabilities in real time, catch anomalies early, and safeguard against threats. Teams must operationalize those security findings so developers who need to fix them know exactly what to do and which security finding to focus on. Prioritizing context-based risk by combining observability and security is the best way to close the door to exploits, which represent the number one entry point (38%) for successful intrusions.
Effective security management of cloud and Kubernetes environments includes assessing misconfigurations and practices that don't meet regulatory compliance standards and security guidelines. As with vulnerabilities, SREs need awareness of these configuration issues and ideally have a system that can automatically generate the code fix for the configuration-as-code files they work with daily. Automating remediation decreases uncertainty about what to do and drastically reduces time spent on determining the fix.
Developers need tools that help them understand how code behaves in production, enabling them to integrate security into the development lifecycle.
Strong platform engineering and SRE practices can standardize workflows, simplify toolsets, and meet reliability targets while giving teams the autonomy to build innovative solutions.
Sustainability has become a top concern for many organizations. Teams need tools that provide visibility into the environmental impact of workloads to help reduce emissions.
Regulatory compliance is increasingly important for organizations in just about every region of the world. Automated compliance solutions help teams meet fast-changing regulatory requirements and reporting timelines while minimizing manual overhead.
These capabilities, delivered through an integrated AI-based platform, create an operating environment that fosters both innovation and security.
End-to-end observability in context with performance metrics, user experience, and business metrics, offers a unique benefit to an organization's security posture management. By integrating data from all channels on a single platform using automatic and customizable instrumentation, teams have access to the data they need to act quickly and confidently.
A unified observability platform integrates data from the full stack to enable use cases that span performance, application security, and business outcomes.With comprehensive observability in context, developers and SREs can quickly identify exposed vulnerabilities. Likewise, security teams can immediately pinpoint threats so they can focus on what matters most.
Vulnerabilities-and the exploits that follow them-are a fact of life. A few recent examples demonstrate how an observability platform approach to security can mean the difference between real harm with a long recovery or nipping a zero-day vulnerability in the bud with little or no downtime.
The VMSA-2025-0004 advisory consists of three Common Vulnerabilities and Exposures (CVEs) that represent unique risks to virtualized and containerized environments. With specialized virtualization security posture management (VSPM) capabilities, teams can quickly detect the VMSA-2025-0004 vulnerabilities and automate remediation.
Navigate to Vulnerabilities: One step in using security and performance data to find VMSA-2025-0004-related vulnerabilities.The IngressNightmare cluster of vulnerabilities affect the mechanisms that allow external traffic to access services within a Kubernetes cluster. By exploiting a chain of multiple flaws, an attacker can use remote code execution (RCE) to upload and execute a file and inject arbitrary code to take over the whole cluster. With access to full Kubernetes logs, metrics, and trace data in a causal data lakehouse, teams can detect vulnerable instances and surface signs of compromise for quick remediation.
Instances of ingress-nginx affected by the NGINX vulnerability IngressNightmare.The Apache Struts 2 vulnerability affected the widely used Java framework for web applications, Apache Struts 2. Also an RCE vulnerability, CVE-2024-53677 allowed attackers to manipulate file upload parameters, leading to unauthorized file placement. Understanding the mechanics of the file upload systems helped teams find the signatures of these exploits using data lakehouse queries and Runtime Vulnerability Analytics to detect the active use of the vulnerable method within their applications.
An overview of the Apache Struts 2 vulnerability showing how security and performance can converge to identify security risks.Sometimes risk to systems comes in the form of a faulty software update, such as the CrowdStrike "blue screen of death" incident from 2024 that affected Windows servers. With full-stack monitoring and topology mapping, out-of-the-box dashboards, synthetic monitoring, data lakehouse querying, collaborative notebooks, real-user monitoring, and service-level objectives to help prioritize remediation, teams were able to recover in hours.
Systems infected during the CrowdStrike outage.In 2021, the Log4Shell vulnerability exposed applications to RCE exploits through its error logging functions. In this scenario, an attacker could direct the logging function to request an infected resource, then download and execute it, causing system damage or data compromise. To quickly find affected systems and mitigate exposure, teams needed to automatically identify all vulnerable applications and the data systems they depend on and prioritize those that are exposed to the internet.
How a threat actor can exploit the Log4Shell vulnerability.With observability to reveal details of affected systems, a data lakehouse for preserving all data in context, and analysis tools to discover details and threat signatures, organizations were able to quickly prioritize remediation, often avoiding downtime altogether.
In today's business environment, leaders need to give their teams every advantage to anticipate rapid change and emerging threats. Unifying observability and security with a single AI-driven platform delivers those advantages so organizations can balance performance and security with the compliance, cost, and sustainability goals of the business.
Already a Dynatrace customer? Contact us to enable Dynatrace Application Security in a few easy steps.