{"id":5489,"date":"2024-09-26T09:34:36","date_gmt":"2024-09-26T14:34:36","guid":{"rendered":"https:\/\/www.darkreading.com\/application-security\/managing-devops-security-posture-escape-stone-age"},"modified":"2024-09-26T09:34:36","modified_gmt":"2024-09-26T14:34:36","slug":"moving-devops-security-out-of-the-stone-age","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/09\/26\/moving-devops-security-out-of-the-stone-age\/","title":{"rendered":"Moving DevOps Security Out of the ‘Stone Age’"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

Combining software development, deployment, and operations pipelines into DevOps teams promises increased efficiency, easier and more frequent updates, and higher-quality applications. Yet the complexity of the infrastructure has also led to a growing attack surface that is hard to monitor and maintain.<\/span><\/p>\n

On the development side, the average organization uses four to nine different programming languages, deals with millions of new packages and images every year, and has to remediate thousands of vulnerabilities in the most common open source components, according to <\/span>JFrog’s “Software Supply Chain State of the Union 2024” report<\/a><\/span>. At the other end of the DevOps pipeline, two-thirds of companies have delayed deployment of an application due to Kubernetes security concerns, and nearly half (46%) had actual security incidents, according to <\/span>Red Hat’s 2024 “The State of Kubernetes” security report<\/a><\/span>.<\/span><\/p>\n

Cybersecurity professionals aiming to secure the application pipeline have to pay attention to the software being written by developers, the open source components imported by developers, the containers and cloud infrastructure used to deploy software, and the build tools used to make the software, says Jeff Williams, chief technology officer and co-founder of Contrast Security, a software security firm.<\/span><\/p>\n

“The problem is it’s such a huge attack surface,” he says. “It’s not just your pipeline. It’s all the other code that goes into developing software \u2014 it’s IDEs and test tools and performance suites. … Any one of them is capable of subverting the code that your developers are building and producing.”<\/span><\/p>\n

Gaining an integrated view of the entire DevOps pipeline, from development to application deployment, is increasingly important. Software components \u2014 not just open source libraries but <\/span>Docker containers<\/a><\/span> and <\/span>other infrastructure assets<\/a><\/span> \u2014 often have vulnerable code, increasing risk. Third-party tools can be compromised \u2014 remember <\/span>Codecov’s breach<\/a><\/span> \u2014 allowing malicious code to be injected into projects under development. Cloud infrastructure and storage can be misconfigured or improperly protected, a la <\/span>Snowflake instances<\/a><\/span>.<\/span><\/p>\n

Having good visibility into the state of the DevOps software pipeline and deployment infrastructure is critical, says Josh Lemos, chief information security officer at DevOps provider GitLab (and no relation to the author).<\/span><\/p>\n

“There are two really important trains that need to run,” he says. “One is you need the development and packaging security, compliance, and attestation of all of your build artifacts in one of those trains or work streams. The other is the deployment monitoring and orchestration of those things in your production environments.”<\/span><\/p>\n

Write, Use, Buy, Build<\/h2>\n

Overall, DevOps security teams need to protect four areas that are open to attack. The first and second areas are most obvious to developers: the code that they write and the software components that they use, says Contrast Security’s Williams.<\/span><\/p>\n

“We’ve been talking about [that code] since the beginning of OWASP,” he says. “If you have bugs in the code you write, people exploit them, and you get breached. It’s not good.”<\/span><\/p>\n

Companies also have to pay attention to the code that they buy or, through a service, use indirectly. Finally, they need to secure the applications and services that are used to build and deploy software \u2014the IDEs, test tools, performance suites, and instrumentation.<\/span><\/p>\n

“Any one of those is capable of subverting the final code,” Williams says, adding that most DevOps teams do not pay attention to the full attack surface posed by their pipelines and software supply chains. “I think we’re still in the Stone Age when it comes to real supply chain security.”<\/span><\/p>\n

While the vast majority of companies (87%) are building or moving applications to cloud-native, 59% did not understand the security implications of doing so and have suffered a security issue as a result. Predictably, the collection of common security incidents are as varied as the infrastructure needed to produce and deploy software: Network breaches, API vulnerabilities, certificate misconfigurations, cluster misconfigurations, and vulnerabilities in containers are among the top causes of security incidents, according to a <\/span>November 2023 survey of cloud-native application security issues<\/a><\/span>.<\/span><\/p>\n

Even companies that are monitoring parts of their DevOps pipelines are not getting good coverage, says Williams.<\/span><\/p>\n

“It’s not everywhere, and almost nothing covers part of the DevOps like developer workstations and IDEs and testing frameworks and plug-ins,” he says. “I mean, there’s a universe of code that nobody’s monitoring, and most organizations are not really thinking about this problem.”<\/span><\/p>\n

Questioning Your DevOps Infrastructure<\/h2>\n

For most companies, ensuring that they have visibility into the entire pipeline is essential. Monitoring can warn when a retired package is suddenly revived in the repository by an untrusted party, or when secrets are included in code that might otherwise be pushed to a repository, or when a Docker image has significant amounts of unused software.<\/span><\/p>\n

Companies need to have continuous monitoring of each step in the pipeline, says Paul Davis, field CISO at software supply chain provider JFrog.<\/span><\/p>\n

“[Knowing] what’s going … and [seeing that] a package has gone bad in production, or that I need to roll back a package because somebody’s come with a new vulnerability, that ease of use [and visibility] into the attack surface \u2014 that insight and that traceability \u2014 is key for me,” he says.<\/span><\/p>\n

Companies should also take action around four specific areas of their DevOps infrastructure, according to GitLab’s Lemos. First, the identities of any developer, ops specialist, device, or service that takes part in the pipeline should be logged. Companies should also maintain a list of software artifacts that they are using, which ones have vulnerabilities, and maintain a private repository, if possible. The build systems should be frequently tested and any automated triggers \u2014 such as changes to third-party software that triggers a build \u2014 should be analyzed for potential security implications. Finally, the entire pipeline should be architected to minimize the impact \u2014 that is, the “blast radius” \u2014 of a compromise, he says.<\/span><\/p>\n

“The best thing I’ve seen companies do as a first step is to get to some known good design patterns,” Lemos says. “The more of that that you can abstract away from [bad security practices], the more successful your security program will be, the less churn and load you’ll have, and the more reusable your code becomes.”<\/span><\/p>\n

The Promise and Peril of AI<\/h2>\n

The breadth of the DevOps attack surface also represents an opportunity for automation and the assistance of artificial intelligence (AI). DevOps already gains much of its agility and speed through automation, with configuration- and infrastructure-as-code dominating because expressing architecture as files allows repeatability for operations, while analyzing the instructions allows for more secure infrastructure.<\/span><\/p>\n

Yet when it comes to security, most companies are holding back on adoption, says Laurent Gil, chief product officer for Kubernetes automation platform CAST AI.<\/span><\/p>\n

“Almost every security company offers automation in some form, and yet nobody is using it,” he says. “[Security teams] should know that it’s OK to use automation to either block things that should be blocked or to auto-remediate when you find something that contains vulnerabilities.”<\/span><\/p>\n

Yet AI development also brings new ways of working with code and data \u2014 an attack surface area that is not fully understood and for which DevOps teams are not ready, Lemos says.<\/span><\/p>\n

“There is the possibility to do really old-style attacks because you’re combining data and content into a model,” he says. “A model with a pickle file that gets consumed into a data scientist’s workstation, if they deserialize it and it has a payload, they’ve just invited some malicious code into their environment.”<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Combining software development, deployment, and operations pipelines into DevOps teams<\/p>\n","protected":false},"author":12,"featured_media":5490,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-5489","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=1920%2C1080&ssl=1",1920,1080,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=1920%2C1080&ssl=1",1920,1080,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/09\/moving-devops-security-out-of-the-stone-age.jpg?fit=1920%2C1080&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5489","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=5489"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5489\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/5490"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=5489"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=5489"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=5489"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}