[{"data":1,"prerenderedAt":516},["ShallowReactive",2],{"/en-us/the-source/security/security-its-more-than-culture-addressing-the-root-cause-of-common-security":3,"footer-en-us":49,"the-source-banner-en-us":383,"the-source-navigation-en-us":389,"article-site-categories-en-us":412,"the-source-newsletter-en-us":414,"security-its-more-than-culture-addressing-the-root-cause-of-common-security-article-hero-category-en-us":421,"security-its-more-than-culture-addressing-the-root-cause-of-common-security-the-source-source-cta-en-us":446,"security-its-more-than-culture-addressing-the-root-cause-of-common-security-article-hero-author-en-us":456,"security-its-more-than-culture-addressing-the-root-cause-of-common-security-category-en-us":480,"security-its-more-than-culture-addressing-the-root-cause-of-common-security-the-source-resources-en-us":493},{"id":4,"title":5,"body":6,"category":7,"config":8,"content":14,"description":6,"extension":41,"meta":42,"navigation":12,"path":43,"seo":44,"slug":45,"stem":46,"type":47,"__hash__":48},"theSource/en-us/the-source/security/security-its-more-than-culture-addressing-the-root-cause-of-common-security.yml","Security Its More Than Culture Addressing The Root Cause Of Common Security",null,"security",{"layout":9,"template":10,"author":11,"featured":12,"sourceCTA":13},"the-source","TheSourceArticle","josh-lemos",true,"application-security-in-the-digital-age",{"title":15,"date":16,"description":17,"timeToRead":18,"heroImage":19,"keyTakeaways":20,"articleBody":24,"faq":25},"Addressing the root cause of common security frustrations","2024-10-29","Security frustrations are often framed as a cultural issue — but leaders also need to focus on issues like tech stack complexity and vulnerability management.","5 min read","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464489/mragusmxl1wz8ozdaoml.png",[21,22,23],"The shift to authenticated scanning in vulnerability management heightens effectiveness but may divert engineering efforts towards non-critical tasks, creating a division between security and engineering teams.","A minimalist approach to software development can minimize dependencies, reduce scanner noise, and lighten the developer's load, contributing to improved software security.","Adopting a \"paved roads\" approach, which involves tested and assured design patterns based on repeatable use cases, can reduce the burden on engineering teams and increase security.","This year, GitLab’s [annual survey of DevSecOps professionals](https://about.gitlab.com/developer-survey/) uncovered several issues related to organizational culture that could be preventing deeper alignment between engineering and security teams. A majority (58%) of security respondents said they have difficulty getting development to prioritize remediation of vulnerabilities, and 52% reported that red tape often slows their efforts to quickly fix vulnerabilities. In addition, security respondents pointed to several specific frustrations related to their jobs, including difficulty understanding security findings, excessive false positives, and testing happening late in the software development process.\n\n[DevSecOps](/topics/devsecops/) promises better integration between engineering and security, but it’s clear that frustrations and misalignment persist. That’s because these challenges are symptoms of a larger problem with how organizations view security, as well as how teams work together and how they allocate time to security.\n\n## Escaping the vulnerability hamster wheel\n\nVulnerability scanning surfaces all potential vulnerabilities - however, just because a software package has a common vulnerability or exposure (CVE) doesn’t mean it’s reachable or exploitable. Security teams and developers alike are still triaging and filtering through vulnerability findings that have grown exponentially over the years since authenticated vulnerability scanning became the norm.\n\nThe move to authenticated scanning has improved the effectiveness of security programs in many ways, but it’s also put developers on an endless hamster wheel of fixing things that don’t matter. When teams waste their efforts on patches that don’t address an exploitable vulnerability, they are diverted from more critical tasks, such as patching vulnerable and exploitable flaws. That’s the source of much of the division between security and engineering teams today.\n\nSo, how can organizations address the root cause of these issues and promote better integration between engineering and security? Here are three ways to prevent common security frustrations at the source.\n\n### 1. Silence the noise, focus on actionable high-fidelity signals\n\nExcessive false positives were the second highest rated frustration identified by security respondents in our survey. False positives are clearly a challenge, but they are often a vulnerability management problem in disguise.\n\nIf an organization sees many false positives, that could be a sign that they haven’t done all they can to ensure their security findings are high-fidelity. Organizations should narrow the focus of their security efforts to what matters. That means traditional static application security testing (SAST) solutions are likely insufficient. SAST is a powerful tool but loses much of its value if the results are unmanageable or lack appropriate context. For SAST to be most effective, it must be used [seamlessly with other security and development tools and be accessible to developers](https://about.gitlab.com/blog/oxeye-joins-gitlab-to-advance-application-security-capabilities/).\n\nAnother issue is that most scanning tools have a very narrow context window for understanding vulnerability findings. This is one of the areas where AI can help with [AI-powered features that explain security vulnerabilities](https://about.gitlab.com/the-source/ai/understand-and-resolve-vulnerabilities-with-ai-powered-gitlab-duo/).\n\n### 2. Minimize the tech stack, minimize the attack surface\n\nStaying focused on what matters doesn’t just apply to security testing - it should start with how an organization builds software in the first place.\n\nAlthough AI promises to help simplify software development processes, [our survey suggests that many organizations still have a long road ahead](https://about.gitlab.com/the-source/platform/3-surprising-findings-from-our-2024-global-devsecops-survey/). In fact, respondents who are using AI were significantly more likely than those not using AI to want to consolidate their toolchain, suggesting that the proliferation of different point solutions running different AI models could be adding complexity, not taking it away.\n\nThe ever-increasing complexity of organizations’ tech stacks is a major contributor to security frustrations. Some complexity is unavoidable when building large, multi-faceted software systems. However, organizations should take steps to avoid complexity resulting from suboptimal design decisions, such as difficult-to-maintain code and redundant dependencies. This unnecessary complexity creates a larger attack surface and generates more security scan findings for teams to sort through, prioritize, and address.\n\nOrganizations should approach development through the lens of software minimization - that is, being intentional about the tools they adopt and what they decide to build into their codebases. This will help minimize dependencies, improve the security of the software supply chain, reduce scanner noise, and ease the burden on developers to fix non-critical issues.\n\n### 3. Normalize paved roads\n\nSecurity testing happening too late in the software development lifecycle was another one of the top frustrations identified by our survey respondents. Teams might be frustrated when they want to ship something and it gets delayed because a vulnerability is detected late - but in many cases it might not have been possible to detect that vulnerability any earlier. What is possible, however, is operationalizing easily deployable, reusable security components, limiting the variables and potential vulnerabilities.\n\nTeams can avoid late-stage surprises by embracing [tested and assured design patterns based on repeatable use cases](https://about.gitlab.com/the-source/platform/how-devops-and-platform-engineering-turbocharge-efficiency/): the “paved roads” approach. A paved road is a recommended path, including a curated set of tools, processes, and components, that teams can follow to build secure applications more efficiently - for example, using GitOps to version and deploy well-architected and tested Infrastructure as Code that deploys at scale for all workloads.\n\nAdopting paved roads potentially removes some flexibility, but ultimately reduces the operational burden and rework on engineering teams and increases security. This needs to be a collaborative effort between security and development. Security can help to design paved roads, but engineering has to be involved to operate and maintain them as part of the codebase.\n\n## Security is a domain, not a team{class=\"no-anchor\"}\n\nWe’re already seeing security as a practice shift into engineering teams, and we can expect the boundaries between the two to continue to blur. However, with the rapid adoption of AI and the corresponding acceleration of software development - 66% of our survey respondents said they are releasing software twice as fast or faster than last year - it will be critical for organizations to establish systems and frameworks that optimize for the greatest security benefit. That’s why the idea of a cultural disconnect between development and security isn’t the whole story. Fostering a culture of collaboration is essential, but security and engineering teams must also work together to rethink foundational aspects of software development, such as optimizing existing codebases and building scalable engineering-centric solutions that can be seamlessly adopted by technical teams across the organization.",[26,29,32,35,38],{"header":27,"content":28},"What is the “paved roads” approach to security, and why is it effective?","The [\"paved roads\" or \"golden path\" approach](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/) standardizes security best practices by providing pre-approved tools, design patterns, and infrastructure configurations that teams can follow. By using reusable, well-tested security components, organizations reduce late-stage security surprises, streamline development, and ensure applications are secure by default. This approach balances flexibility with security assurance.",{"header":30,"content":31},"How does toolchain complexity contribute to security risks?","A fragmented toolchain increases security risks by creating a larger attack surface, introducing redundant dependencies, and making security oversight more difficult. Many organizations are now consolidating their tech stacks to reduce complexity and improve security outcomes. A DevSecOps platform can help unify security, development, and operations, minimizing inefficiencies and reducing security blind spots.",{"header":33,"content":34},"Why is security shifting from a separate team to an engineering practice?","Security is increasingly being embedded within development teams to align with modern DevSecOps practices. As software releases accelerate, security must be built into the development process rather than treated as an afterthought. Organizations that integrate security into engineering workflows — through automation, AI-driven insights, and security-aware coding practices — achieve stronger, more scalable security outcomes.",{"header":36,"content":37},"How can organizations reduce security-related false positives?","False positives can be minimized by refining security testing tools, ensuring they provide actionable and high-confidence findings. AI-powered vulnerability analysis can help contextualize security issues and filter out irrelevant alerts. Additionally, consolidating security tools within a DevSecOps platform can improve accuracy by correlating security data across multiple sources.",{"header":39,"content":40},"Why do security teams struggle to get vulnerabilities prioritized?","Security teams often face challenges in getting vulnerabilities addressed because developers are overwhelmed by excessive security alerts, many of which are false positives. Without clear prioritization, teams waste time fixing non-exploitable issues instead of focusing on critical vulnerabilities. A more efficient approach involves using AI-powered security tools to surface high-fidelity signals and integrating security seamlessly into development workflows.","yml",{},"/en-us/the-source/security/security-its-more-than-culture-addressing-the-root-cause-of-common-security",{"title":15,"description":17,"ogImage":19},"security-its-more-than-culture-addressing-the-root-cause-of-common-security","en-us/the-source/security/security-its-more-than-culture-addressing-the-root-cause-of-common-security","article","WSN8lvb30h1Wys7rCfzlgGfw0XGGPdcRIMEEZFtJW1o",{"data":50},{"text":51,"source":52,"edit":58,"contribute":63,"config":68,"items":73,"minimal":372},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":53,"config":54},"View page source",{"href":55,"dataGaName":56,"dataGaLocation":57},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":59,"config":60},"Edit this page",{"href":61,"dataGaName":62,"dataGaLocation":57},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":64,"config":65},"Please contribute",{"href":66,"dataGaName":67,"dataGaLocation":57},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":69,"facebook":70,"youtube":71,"linkedin":72},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[74,131,188,247,310],{"title":75,"links":76,"subMenu":92},"Pricing",[77,82,87],{"text":78,"config":79},"View plans",{"href":80,"dataGaName":81,"dataGaLocation":57},"/pricing/","view plans",{"text":83,"config":84},"Why Premium?",{"href":85,"dataGaName":86,"dataGaLocation":57},"/pricing/premium/","why premium",{"text":88,"config":89},"Why Ultimate?",{"href":90,"dataGaName":91,"dataGaLocation":57},"/pricing/ultimate/","why ultimate",[93],{"title":94,"links":95},"Contact Us",[96,101,106,111,116,121,126],{"text":97,"config":98},"Contact sales",{"href":99,"dataGaName":100,"dataGaLocation":57},"/sales/","sales",{"text":102,"config":103},"Support portal",{"href":104,"dataGaName":105,"dataGaLocation":57},"https://support.gitlab.com","support portal",{"text":107,"config":108},"Customer portal",{"href":109,"dataGaName":110,"dataGaLocation":57},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":112,"config":113},"Status",{"href":114,"dataGaName":115,"dataGaLocation":57},"https://status.gitlab.com/","status",{"text":117,"config":118},"Terms of use",{"href":119,"dataGaName":120,"dataGaLocation":57},"/terms/","terms of use",{"text":122,"config":123},"Privacy statement",{"href":124,"dataGaName":125,"dataGaLocation":57},"/privacy/","privacy statement",{"text":127,"config":128},"Cookie preferences",{"dataGaName":129,"dataGaLocation":57,"id":130,"isOneTrustButton":12},"cookie preferences","ot-sdk-btn",{"title":132,"links":133,"subMenu":144},"Product",[134,139],{"text":135,"config":136},"DevSecOps platform",{"href":137,"dataGaName":138,"dataGaLocation":57},"/platform/","devsecops platform",{"text":140,"config":141},"AI-Assisted Development",{"href":142,"dataGaName":143,"dataGaLocation":57},"/gitlab-duo/","ai-assisted development",[145],{"title":146,"links":147},"Topics",[148,153,158,163,168,173,178,183],{"text":149,"config":150},"CICD",{"href":151,"dataGaName":152,"dataGaLocation":57},"/topics/ci-cd/","cicd",{"text":154,"config":155},"GitOps",{"href":156,"dataGaName":157,"dataGaLocation":57},"/topics/gitops/","gitops",{"text":159,"config":160},"DevOps",{"href":161,"dataGaName":162,"dataGaLocation":57},"/topics/devops/","devops",{"text":164,"config":165},"Version Control",{"href":166,"dataGaName":167,"dataGaLocation":57},"/topics/version-control/","version control",{"text":169,"config":170},"DevSecOps",{"href":171,"dataGaName":172,"dataGaLocation":57},"/topics/devsecops/","devsecops",{"text":174,"config":175},"Cloud Native",{"href":176,"dataGaName":177,"dataGaLocation":57},"/topics/cloud-native/","cloud native",{"text":179,"config":180},"AI for Coding",{"href":181,"dataGaName":182,"dataGaLocation":57},"/topics/devops/ai-for-coding/","ai for coding",{"text":184,"config":185},"Agentic AI",{"href":186,"dataGaName":187,"dataGaLocation":57},"/topics/agentic-ai/","agentic ai",{"title":189,"links":190},"Solutions",[191,195,200,205,210,214,219,222,227,232,237,242],{"text":192,"config":193},"Application Security Testing",{"href":194,"dataGaName":192,"dataGaLocation":57},"/solutions/application-security-testing/",{"text":196,"config":197},"Automated software delivery",{"href":198,"dataGaName":199,"dataGaLocation":57},"/solutions/delivery-automation/","automated software delivery",{"text":201,"config":202},"Agile development",{"href":203,"dataGaName":204,"dataGaLocation":57},"/solutions/agile-delivery/","agile delivery",{"text":206,"config":207},"SCM",{"href":208,"dataGaName":209,"dataGaLocation":57},"/solutions/source-code-management/","source code management",{"text":149,"config":211},{"href":212,"dataGaName":213,"dataGaLocation":57},"/solutions/continuous-integration/","continuous integration & delivery",{"text":215,"config":216},"Value stream management",{"href":217,"dataGaName":218,"dataGaLocation":57},"/solutions/value-stream-management/","value stream management",{"text":154,"config":220},{"href":221,"dataGaName":157,"dataGaLocation":57},"/solutions/gitops/",{"text":223,"config":224},"Enterprise",{"href":225,"dataGaName":226,"dataGaLocation":57},"/enterprise/","enterprise",{"text":228,"config":229},"Small business",{"href":230,"dataGaName":231,"dataGaLocation":57},"/small-business/","small business",{"text":233,"config":234},"Public sector",{"href":235,"dataGaName":236,"dataGaLocation":57},"/solutions/public-sector/","public sector",{"text":238,"config":239},"Education",{"href":240,"dataGaName":241,"dataGaLocation":57},"/solutions/education/","education",{"text":243,"config":244},"Financial services",{"href":245,"dataGaName":246,"dataGaLocation":57},"/solutions/finance/","financial services",{"title":248,"links":249},"Resources",[250,255,260,265,270,275,280,285,290,295,300,305],{"text":251,"config":252},"Install",{"href":253,"dataGaName":254,"dataGaLocation":57},"/install/","install",{"text":256,"config":257},"Quick start guides",{"href":258,"dataGaName":259,"dataGaLocation":57},"/get-started/","quick setup checklists",{"text":261,"config":262},"Learn",{"href":263,"dataGaName":264,"dataGaLocation":57},"https://university.gitlab.com/","learn",{"text":266,"config":267},"Product documentation",{"href":268,"dataGaName":269,"dataGaLocation":57},"https://docs.gitlab.com/","docs",{"text":271,"config":272},"Blog",{"href":273,"dataGaName":274,"dataGaLocation":57},"/blog/","blog",{"text":276,"config":277},"Customer success stories",{"href":278,"dataGaName":279,"dataGaLocation":57},"/customers/","customer success stories",{"text":281,"config":282},"Remote",{"href":283,"dataGaName":284,"dataGaLocation":57},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":286,"config":287},"GitLab Services",{"href":288,"dataGaName":289,"dataGaLocation":57},"/services/","services",{"text":291,"config":292},"Community",{"href":293,"dataGaName":294,"dataGaLocation":57},"/community/","community",{"text":296,"config":297},"Forum",{"href":298,"dataGaName":299,"dataGaLocation":57},"https://forum.gitlab.com/","forum",{"text":301,"config":302},"Events",{"href":303,"dataGaName":304,"dataGaLocation":57},"/events/","events",{"text":306,"config":307},"Partners",{"href":308,"dataGaName":309,"dataGaLocation":57},"/partners/","partners",{"title":311,"links":312},"Company",[313,318,323,328,333,338,343,347,352,357,362,367],{"text":314,"config":315},"About",{"href":316,"dataGaName":317,"dataGaLocation":57},"/company/","company",{"text":319,"config":320},"Jobs",{"href":321,"dataGaName":322,"dataGaLocation":57},"/jobs/","jobs",{"text":324,"config":325},"Leadership",{"href":326,"dataGaName":327,"dataGaLocation":57},"/company/team/e-group/","leadership",{"text":329,"config":330},"Team",{"href":331,"dataGaName":332,"dataGaLocation":57},"/company/team/","team",{"text":334,"config":335},"Handbook",{"href":336,"dataGaName":337,"dataGaLocation":57},"https://handbook.gitlab.com/","handbook",{"text":339,"config":340},"Investor relations",{"href":341,"dataGaName":342,"dataGaLocation":57},"https://ir.gitlab.com/","investor relations",{"text":344,"config":345},"Sustainability",{"href":346,"dataGaName":344,"dataGaLocation":57},"/sustainability/",{"text":348,"config":349},"Diversity, inclusion and belonging (DIB)",{"href":350,"dataGaName":351,"dataGaLocation":57},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":353,"config":354},"Trust Center",{"href":355,"dataGaName":356,"dataGaLocation":57},"/security/","trust center",{"text":358,"config":359},"Newsletter",{"href":360,"dataGaName":361,"dataGaLocation":57},"/company/contact/#contact-forms","newsletter",{"text":363,"config":364},"Press",{"href":365,"dataGaName":366,"dataGaLocation":57},"/press/","press",{"text":368,"config":369},"Modern Slavery Transparency Statement",{"href":370,"dataGaName":371,"dataGaLocation":57},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":373},[374,377,380],{"text":375,"config":376},"Terms",{"href":119,"dataGaName":120,"dataGaLocation":57},{"text":378,"config":379},"Cookies",{"dataGaName":129,"dataGaLocation":57,"id":130,"isOneTrustButton":12},{"text":381,"config":382},"Privacy",{"href":124,"dataGaName":125,"dataGaLocation":57},{"visibility":12,"title":384,"button":385},"The Intelligent Software Development Era: How AI is reshaping DevSecOps teams",{"config":386,"text":388},{"href":387},"/developer-survey/","Get the research report",{"logo":390,"subscribeLink":395,"navItems":399},{"altText":391,"config":392},"the source logo",{"src":393,"href":394},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":396,"config":397},"Subscribe",{"href":398},"#subscribe",[400,404,408],{"text":401,"config":402},"Artificial Intelligence",{"href":403},"/the-source/ai/",{"text":405,"config":406},"Security & Compliance",{"href":407},"/the-source/security/",{"text":409,"config":410},"Platform & Infrastructure",{"href":411},"/the-source/platform/",{"categoryNames":413},{"ai":401,"platform":409,"security":405},{"title":415,"description":416,"submitMessage":417,"formData":418},"The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":419},{"formId":420,"formName":361,"hideRequiredLabel":12},1077,{"id":422,"title":423,"body":6,"category":6,"config":424,"content":425,"description":6,"extension":41,"meta":440,"navigation":12,"path":441,"seo":442,"slug":7,"stem":443,"testContent":6,"type":444,"__hash__":445},"pages/en-us/the-source/security/index.yml","",{"layout":9},[426,433],{"componentName":427,"type":427,"componentContent":428},"TheSourceCategoryHero",{"title":405,"description":429,"image":430},"Get up to speed on how organizations can ensure they're staying on top of evolving security threats and compliance requirements.",{"config":431},{"src":432},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463273/aplkxrvwpii26xao5yhi.png",{"componentName":434,"type":434,"componentContent":435},"TheSourceCategoryMainSection",{"config":436},{"sourceCTAs":437},[438,439,13],"source-lp-guide-to-dynamic-sboms","source-lp-devsecops-the-key-to-modern-security-resilience",{},"/en-us/the-source/security",{"title":405,"description":429,"ogImage":432},"en-us/the-source/security/index","category","Yz-XSZ2w3Zg4r2_4aWlzq2kmfduukECmMNfXD6Ha26w",{"config":447,"title":448,"description":449,"link":450},{"slug":13},"Application security in the digital age","Read our survey findings from more than 5,000 DevSecOps professionals worldwide for insights on how organizations are grappling with increasing attack surfaces and changing attitudes towards security and AI.",{"text":451,"config":452},"Read the report",{"href":453,"dataGaName":454,"dataGaLocation":455},"/developer-survey/2024/security-compliance/","Application Security in the Digital Age","thesource",{"id":457,"title":458,"body":6,"category":6,"config":459,"content":460,"description":6,"extension":41,"meta":474,"navigation":12,"path":475,"seo":476,"slug":11,"stem":477,"testContent":6,"type":478,"__hash__":479},"theSourceAuthors/en-us/the-source/authors/josh-lemos.yml","Josh Lemos",{"layout":9},[461,472],{"componentName":462,"type":462,"componentContent":463},"TheSourceAuthorHero",{"config":464,"name":458,"role":467,"bio":468,"headshot":469},{"gitlabHandle":465,"linkedInProfileUrl":466},"joshlemos","https://www.linkedin.com/in/joshlemos/","Chief Information Security Officer","Josh Lemos is the Chief Information Security Officer at GitLab Inc., where he brings 20 years of experience leading information security teams to his role. He is responsible for establishing and maintaining the enterprise vision, strategy, and program to ensure information assets and technologies are adequately protected, fortifying the Gitlab DevSecOps platform and ensuring the highest level of security for customers.",{"altText":458,"config":470},{"src":471},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463405/f4rqtiecakrekvxfhqar.jpg",{"componentName":473,"type":473},"TheSourceArticlesList",{},"/en-us/the-source/authors/josh-lemos",{"title":458},"en-us/the-source/authors/josh-lemos","author","Kzh9L_9H8IeYxDNNFgPiZ3BBOSdgaHIyKFkhllwdLjI",{"id":422,"title":423,"body":6,"category":6,"config":481,"content":482,"description":6,"extension":41,"meta":491,"navigation":12,"path":441,"seo":492,"slug":7,"stem":443,"testContent":6,"type":444,"__hash__":445},{"layout":9},[483,487],{"componentName":427,"type":427,"componentContent":484},{"title":405,"description":429,"image":485},{"config":486},{"src":432},{"componentName":434,"type":434,"componentContent":488},{"config":489},{"sourceCTAs":490},[438,439,13],{},{"title":405,"description":429,"ogImage":432},[494,498,507],{"config":495,"title":448,"description":449,"link":496},{"slug":13},{"text":451,"config":497},{"href":453,"dataGaName":454,"dataGaLocation":455},{"config":499,"title":500,"description":501,"link":502},{"slug":439},"DevSecOps: The key to modern security resilience","Learn how embedding security in development can slash incident response time by 720x and save millions in security costs annually.",{"text":503,"config":504},"Download the guide",{"href":505,"dataGaName":506,"dataGaLocation":455},"/the-source/security/devsecops-the-key-to-modern-security-resilience/","DevSecOps the key to modern security resilience",{"config":508,"title":509,"description":510,"link":511},{"slug":438},"Guide to dynamic SBOMs: An integral element of modern software development","Learn how to gain visibility into previously unidentified organizational risks with a software bill of materials (SBOM).",{"text":512,"config":513},"Read the guide",{"href":514,"dataGaName":515,"dataGaLocation":455},"/the-source/security/guide-to-dynamic-sboms/","Guide to Dynamic SBOMs",1772652114915]