AWS Vulnerability Management: Benefits and Best Practices

This guide unpacks AWS vulnerability management, detailing benefits, best practices, and services. Learn how to craft an effective policy, tackle common risks, and strengthen your cloud defenses.

Cloud-based systems remain under constant attack from hackers, cybercriminals, and other malicious forces. According to Amazon, MadPot faces 750 million attacks daily, and another service of AWS identified  2.7 trillion attempts to scan vulnerabilities on EC2 instances within a year. These numbers indicate the need for organizations to strengthen their security in environments that use Amazon Web Services (AWS). The multi-layered approach framework requires attention to people, processes, and technology to cover all levels of the stack. This is where AWS vulnerability management becomes handy as it offers real-time scanning, detection, and remediation of new threats.

In this article, we will provide more information about AWS vulnerability management and its role in organizations, regardless of their size. You will find out why it is important to be proactive in a world that revolves around the cloud. We will also see how AWS inherently handles vulnerabilities and other services that can be utilized to enhance the security of your cloud. You will also discover essential steps for formulating an AWS vulnerability management policy and see how AWS vulnerability remediation unfolds in real-world scenarios. Last but not least, we will reveal how SentinelOne can complement your defense strategy and provide a more integrated level of protection.

What Is AWS Vulnerability Management?

AWS vulnerability management entails the identification, assessment, and remediation of security risks that are inherent in AWS environments and solutions. It involves regularly inspecting cloud resources including EC2 instances, S3 buckets, Lambda functions, and managed databases for misconfigurations, applications with known vulnerabilities, and lack of security measures. This systematic approach guarantees that the newly identified or well-known weaknesses are addressed accordingly.

A sound approach does not end with detection, and it should also incorporate an intelligence feed, automated patching where feasible, and strict change control. Incorporating technology, compliance requirements, and internal controls, AWS vulnerability management offers a structure to protect an organization from both random and sophisticated threats. Finally, it ensures that cloud operations are secure despite the dynamic nature of threats in the environment.

Why is AWS Vulnerability Management Important?

Given the constantly evolving nature of cloud environments, it is crucial to perform a comprehensive security review of the cloud infrastructure. Recent research reveals that 16% of organizations experience a cyberattack every six days, while 49% of the companies have faced at least one cyberattack in the last year. More alarming was the fact that, according to the survey, 40% of the companies said that such incidents cost them up to EUR 1.86 million. To address these risks, AWS vulnerability management helps you establish regular scans and patch cycles as part of your security plan.

1. Continuous Monitoring for Emerging Threats: Cloud infrastructures are dynamic since teams create new instances or services on the fly. In such a dynamic environment, the scans conducted on a monthly basis or even weekly may fail to capture important windows of exposure. A well-executed program adheres to AWS vulnerability management best practices by employing automated, continuous monitoring. This approach provides real-time awareness, which means that security teams have the information they require to act promptly.
2. Targeted Remediation Efforts: It is important to understand that not all weaknesses are on the same level of vulnerability. By adopting a structured AWS vulnerability remediation process, organizations can prioritize high-impact threats before addressing lesser issues. This systematic approach helps in avoiding situations where time is spent on beautifying the product while major weaknesses are left unaddressed. Essentially, it is the process of turning the collected data from a scanner into the subsequent course of action.
3. Reduced Risk of Data Breaches: Security breaches usually arise from vulnerabilities such as unpatched systems and improper system configurations. Incorporating an AWS vulnerability management policy helps standardize patch and configuration protocols across your cloud assets. This way, enforcing a set of rules helps to maintain a high level of security consistent across the organization, minimizing the risk that some important piece of information could be leaked due to a minor vulnerability.
4. Enhanced Compliance Posture: Regulations like PCI DSS, HIPAA, and GDPR demand diligent control over system vulnerabilities. These requirements are met by automated tools and structured scanning schedules. Documenting each step helps demonstrate compliance during audits, showcasing how AWS vulnerability management tools uphold recognized standards. This clear audit trail is beneficial in building trust with customers, partners, and regulatory authorities.
5. Cost Effectiveness in the Long Run: Identifying threats before they become critical can help organizations reduce the costs of handling incidents and losses from downtime. While integrating scanning solutions may seem costly at first, the benefits come into focus as threats are addressed effectively. In addition, a strong AWS vulnerability management strategy can be easily aligned with current IT frameworks, thus reducing the marginal costs for specialized personnel and equipment.

How AWS Handles Vulnerability Management?

Although the security of cloud deployments is the user’s responsibility, AWS operates under a shared responsibility model. This means that AWS owns the physical infrastructure, the actual hardware and software, as well as some fundamental security responsibilities.

From the customer side, you are still expected to apply guest OS patches, enforce application security, and set up each service correctly. However, there are numerous resources and services in AWS that can support teams in implementing proper AWS vulnerability management.

1. Shared Responsibility Model: AWS provides a clear understanding of which security responsibilities are the responsibility of the platform and which are the responsibilities of the customer. For example, AWS protects the physical infrastructure and the underlying network; however, clients are responsible for applying patches to their virtual machines and enforcing compliance settings. While this division helps to make planning easier, it also underlines the importance of clear role differentiation. Customers who think that AWS takes care of all aspects can end up overlooking some important tasks.
2. Security Bulletins and Advisories: AWS often releases alerts on newly emerging threats that may pose a risk to its services. These advisories describe the type of vulnerability, its possible consequences, and the measures that should be taken to mitigate the risks. Aligning your AWS vulnerability management policy with these insights helps ensure your environment stays ahead of emerging threats. These bulletins should be acted upon as soon as possible to prevent massive occurrences.
3. Built-In Encryption and Logging: AWS does not have a silver bullet, but it has native encryption features for services like S3, EBS, RDS, CloudTrail, and CloudWatch logs. These integrated features supplement AWS vulnerability management by providing additional layers of visibility and data security. Encryption of resources and logging helps to minimize the impact of the attack in case an attacker gets through the perimeter defenses.
4. AWS Compliance Programs: AWS complies with industry standards, such as ISO 27001, SOC 2, and FedRAMP, which provide users with confidence in the underlying foundations. However, it is the responsibility of each user to manage the upper layers of the stack. Applying AWS compliance documentation helps to speed up the process of developing your own risk assessment plan. This synergy of third-party audits and internal scrutiny enriches a comprehensive AWS vulnerability remediation pipeline.
5. Integration with Security Automation: As with any other environment, working in the cloud is most effective when certain processes are automated. AWS best practices state that Infrastructure should be treated as Code (IaC) for the purpose of automation and security validation. Many AWS vulnerability management tools integrate seamlessly with these IaC frameworks. This alignment means that new instances are set up with secure configurations, and known vulnerabilities are identified when the instances are being built.

AWS Security Services for Vulnerability Management

To support vulnerability management in AWS, Amazon provides a range of niche services. These tools integrate natively with one another, streamlining detection and AWS vulnerability remediation across your cloud environment. Here are some fundamental services to consider—understanding which to use and how can greatly enhance your security:

1. AWS Security Hub: AWS Security Hub is a centralized service for security and compliance that collects and consolidates security assessments from various AWS services and third-party applications. It allows the teams to see risks at the account and regional level in one place. It helps to organize the work and prioritize the important problems that should be solved in the first place. For organizations following AWS vulnerability management best practices, Security Hub offers a streamlined vantage point for both detection and reporting. It also enhances governance efforts through compliance checks against standards such as the CIS benchmarks.
2. Amazon Inspector: The inspector is a key player in identifying common AWS vulnerabilities within EC2 instances and container images. It evaluates every aspect, from network settings to installed software, and assigns a risk severity level to each vulnerability found. Specifically, teams can include Inspector scans into CI/CD pipelines to receive near-real-time insights on newly created or updated resources. This approach aligns with the concept of left-shifting in security. When integrated with a formal AWS vulnerability management policy, Inspector fosters continuous improvement, reducing the window for attackers to exploit known weaknesses.
3. AWS Shield: AWS Shield is majorly concentrated on Distributed-Denial-of-Service (DDoS) protection that helps protect web applications against network and application layer attacks. The Standard tier provides protection against most floods, while the Advanced tier provides additional analysis and coverage of attack costs. Although it does not replace more granular AWS vulnerability management tools, Shield’s specialized focus on DDoS prevention closes a major gap. When used in conjunction with other services, it creates a layered protection that can handle availability challenges, which are part of any cloud security strategy.
4. AWS WAF (Web Application Firewall): AWS WAF blocks web traffic that is potentially threatening by analyzing HTTP and HTTPS requests. Users can encode their own rules or use predefined rulesets that cover the most common threats, such as SQL injection and cross-site scripting. From an AWS vulnerability remediation standpoint, WAF can act as a temporary shield against exploits targeting newly discovered flaws. When combined with continuous scanning, WAF enables organizations to monitor threats as they come in while simultaneously addressing the issues at the application level.
5. GuardDuty: GuardDuty is a threat intelligence and machine learning-powered security service that can identify suspicious activity in AWS log data, including unusual API activity, reconnaissance, or instances that have been compromised. Since it scans through CloudTrail, VPC Flow Logs, and DNS logs, it uncovers patterns that may not be detected by other scanning tools. As a service within an AWS vulnerability management ecosystem, GuardDuty deals with runtime threats as opposed to configuration or patching. This synergy provides coverage for both vulnerabilities that are stationary and threats that are already active.
6. AWS IAM (Identity and Access Management): Although primarily a permissions framework, IAM’s configuration intricacies make it pivotal to AWS vulnerability management best practices. Limiting the privileges and regularly changing the access codes are effective measures against both internal and external threats. Separating users into at least as many groups as there are privilege levels minimizes the potential harm an attacker can do if they obtain legitimate credentials. Using IAM’s detailed policy controls in conjunction with scanning services, it is possible to identify accounts that are not compliant with security standards. When effectively implemented, IAM supports a strong governance foundation for cloud environments.

Common Vulnerabilities in AWS Environments

It is worth noting that AWS offers many integrated measures to protect organizations, and they can still overlook some significant vulnerabilities. Some are due to user misconfigurations, outdated software, and insufficient internal processes that need to be implemented. Knowing these common AWS vulnerabilities is vital for prioritizing and conducting targeted scans. Now, let us discuss some of the common challenges that security teams face when working in the AWS environment.

1. Misconfigured S3 Buckets: S3 buckets that are publicly accessible constitute a recurring issue in cloud configurations. Administrators might accidentally grant read or write permissions to everyone, which may lead to data theft or data contamination. Private buckets can also be misconfigured, and they may not have encryption or appropriate Access Control Lists (ACLs). Under an organized AWS vulnerability management structure, teams actively search for misconfigurations and quickly point out potentially dangerous open buckets. Adjusting these settings significantly minimizes the risk of a large-scale leak of sensitive data.
2. Weak IAM Policies and Access Controls: IAM determines what access users and groups have in the AWS environment. For example, overly liberal policies such as allowing many employees to have administrative rights make lateral movement or data exfiltration easy if an attacker gains access to the victim organization’s credentials. Analyzing the IAM logs through GuardDuty or Security Hub can also help identify any unusual activity. Aligning IAM with an AWS vulnerability management policy ensures consistent checks of user permissions, enforcing least privilege principles. This decreases the number of potential avenues of attack exponentially.
3. Insecure EC2 Instances: Managers may fail to remember to set up firewalls, encrypt data, or install the latest intrusion detection software. In particular, open ports could be used as entry points by hackers who take advantage of such an opportunity to attack a network. Tools like Amazon Inspector help in discovering these gaps, listing them among “common AWS vulnerabilities.” Through patching, scanning, and monitoring, organizations strengthen EC2 workloads with a safety net, guaranteeing that every instance is secure to the minimum.
4. Unpatched Applications and OS Vulnerabilities: Many operating on EC2 instances, container images, and even serverless environments are different software packages that need updates periodically. Overlooking patching schedules may cause severe vulnerabilities. Embracing consistent AWS vulnerability remediation procedures helps keep these systems up-to-date. Tools like Inspector or third-party applications can indicate which OS versions are outdated and need to be patched so that teams can act quickly. Scanning for vulnerabilities and applying patches on a routine basis reduces the exposure time that hackers have to exploit these vulnerabilities.
5. Lack of Network Segmentation: Flat network architectures facilitate the movement of attackers, once they have breached the network, to any service. Dividing your VPC into smaller subnets with stringent routing policies ensures that workloads are contained in the event of a breach. Although, with the concept not exclusively limited to AWS, network segmentation is particularly important in a multi-account environment. Implementing a layered approach to AWS vulnerability management means that if an instance or container has been compromised, the impact will be minimal. Segmentation, when done properly, in conjunction with monitoring, can be a sound defense mechanism.

Challenges in AWS Vulnerability Management

Despite the availability of tools and guides provided by AWS, teams often encounter challenges when adopting cloud-oriented security measures. They include everything from the size and complexity of today’s infrastructures to highly technical regulatory requirements. By having a clear discussion of these challenges, AWS vulnerability management programs can be realistic and feasible. Here are five main issues that organizations must confront:

1. Rapidly Evolving Cloud Environments: Auto-Scaling Groups and Container Orchestration, as well as DevOps pipelines, can create or delete resources within minutes. It is possible that traditional scanning may not be able to identify the occurrence of such instances adequately and in a timely manner. Adapting to this ephemeral nature demands automated AWS vulnerability management tools integrated seamlessly into your CI/CD pipeline. In its absence, security is a long way off from keeping up with high-speed rollouts.
2. Cross-Functional Knowledge Gaps: AWS environments combine network engineering, development, and compliance expertise. Security personnel may not have specialized knowledge of cloud computing, while developers may not pay enough attention to security with their primary focus on functionality. Bridging this gap requires a robust training regimen and a well-documented AWS vulnerability management policy. Integrating security into different teams promotes the ownership of security by ensuring that every team is aware of the security consequences of their work.
3. Tool Overload and Integration Issues: Many services promise to address common AWS vulnerabilities, but not all integrate smoothly. Working on multiple consoles or managing multiple dashboards is not a good idea, as the alerts may go unnoticed while the data remains incomplete. Establishing a centralized platform like Security Hub or a third-party aggregator can unify findings from different AWS vulnerability management tools. This consolidation is necessary to ensure that results are consistent across the board and that remediation can be efficiently executed.
4. Budgetary and Resource Constraints: Comprehensive scanning solutions, DDoS protection, and specialized labor could be costly. Smaller organizations may avoid investing in advanced capabilities, which may lead to a fragmented system. To support these expenditures to the senior leadership, one must consider the potential costs of a breach. By adopting a staged rollout of essential services, teams can balance robust AWS vulnerability remediation with financial realities.
5. Navigating Compliance Complexities: While AWS provides ample support for compliance, it is the user’s responsibility to ensure compliance and adhere to the rules and regulations. Compliance with international standards, such as HIPAA, PCI DSS, or GDPR, requires documentation and regular assessments. Even the most experienced security practitioners find it challenging to navigate through overlapping regulations. To ensure that your AWS vulnerability management blueprint is not derailed by fines and reputational loss, integrating a dynamic compliance strategy and reporting channels is recommended.

Best Practices for AWS Vulnerability Management

A robust approach relies on native AWS features along with organizational processes that emphasize continuous improvement of security measures. By following guidelines informed by both industry standards and AWS vulnerability management best practices, businesses can transform vulnerability identification and remediation into a predictable, optimized cycle. Below are five proven strategies:

1. Implement Automated Scanning and Alerting: In high-speed cloud environments, manual scans do not cover areas that are most vulnerable. Automate where possible, using services like Amazon Inspector or integrating third-party scanners into your CI/CD pipeline. Integrate Slack, Jira, or any other collaboration tool, and alerts should integrate with it. By setting threshold-based warnings, you focus on critical incidents first, aligning scanning efforts with AWS vulnerability management best practices.
2. Prioritize Remediation Based on Severity: The severity of the risk is different for each vulnerability, as not all vulnerabilities are the same. Give a score to each of the findings using the Common Vulnerability Scoring System (CVSS) or an organization-specific scoring system. A patch should be applied to immediate security issues or temporary WAF rules used, and less severe items should go into future sprints. This systematic approach, coupled with formal AWS vulnerability remediation steps, ensures efficient use of limited resources.
3. Principle of Least Privilege: Limiting access is a fundamental part of cloud security. This eliminates the possibility of widespread vulnerabilities because IAM policies should only allow as much access as each role needs. Further efforts to improve the environment include performing regular audits to remove any excess privileges. By weaving these checks into your AWS vulnerability management policy, you ensure that permissions remain up-to-date as the organization evolves.
4. Adopt Proper Documentation: The ability to perform logging via CloudTrail, VPC Flow Logs, and CloudWatch is essential for analyzing incidents and maintaining compliance. In particular, GuardDuty analyzes these logs to detect anomalous behaviors. In this way, suspicious behavior is correlated with the known weaknesses to have a better understanding of what kind of attacks might be performed. Consistent log reviews align well with AWS vulnerability management best practices, enabling early detection and swift response.
5. Conduct Regular Security Training: Human skills are also important—they cannot be closed by new technologies alone. Offer targeted workshops for DevOps, operations, and security staff, showing them how to use AWS vulnerability management tools effectively. Focus on the realistic threat scenarios that can be replicated in the lab environment to improve effectiveness. Employees are the backbone and bring theory to practice, making the daily functioning of the organization effective.

How to Build and Apply an AWS Vulnerability Management Policy?

A formal AWS vulnerability management policy provides the guiding framework that keeps security efforts consistent and auditable. This is not just a document; it should grow with your cloud presence and include new services, linked solutions, and compliance requirements. Here is a step-by-step guide on how to develop and sustain the policy for your organization:

1. Define Scope and Objectives: The first step is to know all the AWS accounts, regions, and services that can be controlled by the organization. Explain whether or not it is possible to use the policy for third-party services that are hosted on AWS. This should include the setting of measurable goals, for instance, maximum allowable downtime or the time it should take to patch an application. This lays a foundation for a policy that is well understood by technical teams as well as business leaders.
2. Select Appropriate Tools and Methods: Choose scanning solutions that integrate smoothly with your environment, whether native AWS services like Inspector or specialized AWS vulnerability management tools from external vendors. Ensure that the tools correspond with your threat detection strategy; it can be constant monitoring, running scans at specific intervals, or both. Outline the approach in your policy and make certain that each asset type is addressed.
3. Establish Roles and Responsibilities: Assign accountability at every step, from scanning to final AWS vulnerability remediation. While patching is generally the responsibility of DevOps teams, security analysts are expected to analyze the results and report any significant findings. Define the roles of managers, engineers, and compliance officers to eliminate confusion between the positions. The utilization of a clear RACI matrix can greatly simplify the process of collaboration.
4. Implement Formal Processes and Workflows: Be specific about how frequent scans are done, where the findings are kept, and how alerts are managed. Set up conditions that call for notifications or other corrective actions to be taken automatically. This systematic approach guarantees that no instance or container is overlooked and that all are handled systematically. Build periodic policy reviews to reflect the dynamic nature of common AWS vulnerabilities and emerging threats.
5. Review, Update, and Communicate Regularly: It is always important to update policies as they become ineffective when kept unchanged for a long time. Frequency should be at least quarterly or semi-annual, as new security incidents, changes in AWS releases, and compliance updates may require adjustments to the guidelines. Communicate policy changes through memorandums or training sessions to ensure that everyone is on the same page. This continuous refinement is what distinguishes a one-off document from a living security framework.

SentinelOne for AWS Vulnerability Management

SentinelOne for AWS is built to optimize enterprise protection for AWS environments. Powered by AI, the platform offers a unified code-to-cloud security solution that secures your cloud, endpoints, and identities.

It integrates smoothly with AWS services to provide real-time threat detection, protection, and response, so your cloud stays secure. With full visibility across your AWS setup, you get clear insights and automated solutions to quickly find and fix issues.

As a trusted AWS partner with over 20 integrations—including Amazon Security Lake, AppFabric, and Guard Duty—SentinelOne helps you boost security and simplify operations. It works with key AWS services like EC2, EKS, and S3, so deployment is easy and security stays strong.

SentinelOne actively scans secrets in real-time, detecting more than 750 types across platforms, such as BitBucket, GitHub, and GitLab. Catching these leaks before they happen, it stops cloud credentials from slipping through in private repositories. This helps with cutting down on potential data exposure. It detects misconfigurations across Infrastructure as Code (IaC) templates, such as Terraform and CloudFormation, enforcing shift-left security to catch AWS vulnerabilities early in development.

By adopting an Offensive Security approach, SentinelOne minimizes false positives. It thus provides SOC teams with only actionable and verified threats. It also reduces alert fatigue and increases operational efficiency.

You can write your own custom policies for threat detection and event analysis, enabling users to query, search, and enforce new security rules tailored to your organization’s specific environments.

Book a free live demo.

Conclusion

With cloud infrastructures growing in size and complexity, AWS vulnerability management remains a critical cog in the wheel for any organization’s security framework. Preventative, strategic, and scheduled security updates and policy compliance constitute a defensive strategy that reduces vulnerability. In this manner, using the tools and processes AWS offers, in addition to known best practices, organizations can stay up-to-date with emerging threats and compliance requirements. However, real success also requires decentralization of security responsibility and the involvement of all stakeholders, starting with DevOps and ending with the leadership. This way, an enterprise is in a position to close loopholes that the bad guys love to exploit.

Adopting an AWS vulnerability management policy does not mean halting innovation or complicating workflows. In contrast, the right approach helps in automating routine activities, defining responsibilities, and improving the general development and operation processes. These benefits are further compounded by solutions such as SentinelOne Singularity™, as it introduces threat detection and automated response into the equation, filling any gaps left by native AWS functions. When integrated, these solutions provide a single, continuous security platform that can protect data and applications.

Are you ready to enhance your AWS security plan? Contact SentinelOne today to get a solution that has been designed to meet the security needs of your organization in the cloud environment.

FAQs on AWS Vulnerability Management

What is vulnerability management in AWS?

AWS vulnerability management scans AWS workloads to look for potential vulnerabilities and unintended network exposures. It looks automatically at Amazon EC2 instances, containers, Lambda functions, and also involves managing SBOM exports. A part of AWS vulnerability management is implementing shift-left security, prioritizing remediation, and meeting compliance requirements.

What are the common vulnerabilities in AWS environments?

Some of the most common AWS vulnerabilities include misconfigured S3 buckets with excessive public permissions that can be used for data theft or contamination, and weak IAM policies that grant unnecessary access rights. Some of the other prevalent problems are insecure EC2 instances, unpatched applications and operating systems with known vulnerabilities, and weak network segmentation that grants lateral movement in the environment. These vulnerabilities typically result from user configuration errors, outdated software, and the absence of internal security processes.

How do I perform a vulnerability scan on AWS?

To scan for vulnerabilities in AWS, utilize Amazon Inspector for programmatic assessment of EC2 instances and container images. Implement recurring scans through the AWS Security Hub to consolidate findings across multiple services. Employ other third-party scanning tools that are integrated with AWS APIs for full coverage. Ensure scans verify configurations, network settings, and installed programs against established databases of vulnerabilities. Follow AWS best practices by treating Infrastructure as Code for automated security validation.

How can I detect misconfigurations in AWS?

Identify AWS misconfigurations using AWS Security Hub to consolidate security findings across accounts and services. Use the Amazon Inspector to detect EC2 instance and container image configuration vulnerabilities. Utilize IAM Access Analyzer to detect shared resources with external parties. Use continuous monitoring using CloudWatch and CloudTrail to monitor changes in resource configurations. Periodic auditing against compliance standards such as CIS benchmarks can help you in detecting deviations from security norms.

How can organizations implement a vulnerability management policy in AWS?

Organizations need to implement an AWS vulnerability management policy by first defining security responsibilities clearly in the shared responsibility model. Implement continuous monitoring with automated scanners like Inspector and Security Hub. Implement a risk-based prioritized vulnerability system. Implement standardized remediation procedures for common issues. Include vulnerability scanning in CI/CD pipelines and enforce regular patching cycles. Implement documentation to demonstrate compliance during audits.

What steps should I take after detecting a vulnerability in AWS?

Once a vulnerability is identified, first determine its severity and possible impact on your AWS environment. Remediate according to risk, with critical vulnerabilities remediated immediately. Temporarily mitigate using AWS WAF rules if instant patching is not feasible. Document the vulnerability and remediation process used. Test validation to ensure remediation. Update security policies to avoid future similar vulnerabilities and don’t forget to report to affected stakeholders.

How to Automate AWS Vulnerability Management in CI/CD Pipelines?

Automate AWS vulnerability management in CI/CD pipelines by integrating Amazon Inspector scans into your build process. Implement security testing as code using Infrastructure as Code (IaC) validation tools. Configure automated security checks that can fail builds when critical vulnerabilities are detected. Use AWS CodeBuild and CodePipeline with security plugins to enforce compliance requirements. Create feedback loops that provide developers with immediate security insights. You can also use SentinelOne for AWS to automate AWS vulnerability management across CI/CD pipelines.