[{"data":1,"prerenderedAt":525},["ShallowReactive",2],{"/ja-jp/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles":3,"footer-ja-jp":33,"the-source-banner-ja-jp":400,"the-source-navigation-ja-jp":406,"article-site-categories-ja-jp":429,"the-source-newsletter-ja-jp":431,"how-to-strengthen-security-by-applying-devsecops-principles-the-source-source-cta-ja-jp":6,"how-to-strengthen-security-by-applying-devsecops-principles-article-hero-category-ja-jp":438,"how-to-strengthen-security-by-applying-devsecops-principles-category-ja-jp":464,"how-to-strengthen-security-by-applying-devsecops-principles-article-hero-author-ja-jp":477,"how-to-strengthen-security-by-applying-devsecops-principles-the-source-resources-ja-jp":498},{"id":4,"title":5,"body":6,"category":7,"config":8,"content":13,"description":6,"extension":24,"meta":25,"navigation":26,"path":27,"seo":28,"slug":29,"stem":30,"type":31,"__hash__":32},"theSource/ja-jp/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles.yml","How To Strengthen Security By Applying Devsecops Principles",null,"security",{"layout":9,"template":10,"author":11,"featured":12},"the-source","TheSourceArticle","ncregan",false,{"title":14,"date":15,"description":16,"timeToRead":17,"heroImage":18,"keyTakeaways":19,"articleBody":23},"DevSecOpsの原則を採り入れてセキュリティを強化する方法","2023-02-23","DevSecOpsの原則を採り入れる方法と、それによって得られるメリットについてご紹介します。","4分で読めます","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464433/bdwagz0bt5bpgghjkout.png",[20,21,22],"DevSecOpsはセキュリティをSDLCに統合し、デリバリーを遅らせることなく、安全なアプリの開発を実現します。","DevSecOpsによる自動化によって、セキュリティが強化され、脅威の検出と対応が効率化されます。","DevSecOpsにおけるコラボレーションによって、統一されたアプローチで、安全なソフトウェア開発を迅速に進められるようになります。","DevSecOpsの原則に従えば、企業は迅速かつ効率的に価値を提供しながら、アプリケーションを悪意のある人物から確実に保護できます。この記事では、DevSecOpsの原則について詳しく説明し、最先端のセキュリティ対策を実現する上でどのように役立つかをご紹介します。それでは詳しく見ていきましょう。\n\n## DevSecOps とは？\n[DevSecOps](/topics/devsecops/)は、開発、セキュリティ、オペレーションの3原則を組み合わせたソフトウェア開発アプローチです。DevSecOpsを採用すると、チームは迅速かつ効率的に価値を提供しながら、安全で信頼性の高い製品を作成できます。DevSecOpsの実装を成功させるには、品質やセキュリティを妥協せずに、市場投入までの時間を短縮することを目指して、継続的インテグレーションや自動化、テストを行う必要があります。\n\n## DevSecOpsの原則の概要\n開発チームは[DevSecOpsの原則](/blog/4-must-know-devops-principles/)に従って統合されたセキュリティテストを実施することで、安全かつ信頼性の高いアプリケーションを迅速に開発できます。DevSecOpsアプローチを実践すると、初期設計から継続的なデリバリー、そして継続的デプロイメントまで、ソフトウェア開発ライフサイクル（SDLC）にセキュリティが統合されます。これにより、システムの脆弱性を悪用した悪意のある人物によるセキュリティ漏洩の発生を防ぎ、サイバー攻撃の全体的なリスクを低減できます。\n\nDevSecOpsの原則とは、具体的には以下のとおりです。\n\n### 自動化と統合\n自動化と統合は、DevSecOpsにおいて重要な考え方です。セキュリティプロセスの自動化によって、安全で信頼性の高いアプリケーションの開発を支援すると同時に、今後発生しうる悪質な攻撃のリスクを低減します。開発サイクル中に複数のタイミングでセキュリティ対策を設定して実行し、継続的なセキュリティを適用することで、セキュリティの実践を簡素化および最適化できます。\n\n### 継続的なデリバリーと継続的なデプロイ\n継続的なデリバリーとデプロイは、潜在的な脅威に迅速に対応し、悪意のある人物からソフトウェアサプライチェーンを保護できるようにするもう1つの方法です。[自動化されたプロセスを用いてアプリケーションを継続的にデプロイする](/blog/cd-solution-overview/)ことで、アプリケーションのセキュリティと品質を維持しながら、新機能や新製品を迅速に開発できるようにします。\n\n### セキュリティへの協調的なアプローチ\nセキュリティは、DevSecOpsの中核と言えます。アプリケーションの安全性と信頼性を確保するには、複数のセキュリティチェックを継続的に実施しつつ、[高度に協調的なアプローチ](/ja-jp/topics/version-control/software-team-collaboration/)を取ることが求められます。開発プロセスに携わるすべての関係者がセキュリティプロセスに取り組む必要があります。\n\nセキュリティチームはデベロッパーと協力しながら、アプリケーションの設計時に[適切なセキュリティ制御](/topics/devsecops/devsecops-security-checklist/)が組み込まれていること、またセキュリティの脆弱性が最小限であることを確認する必要があります。それと同時に、オペレーションチームはアプリケーションを安全にデプロイし、モニタリングするために、セキュリティチームと連携しなければなりません。\n\n### SDLCのすべてのステージでセキュリティを実装\nSDLCのすべてのステージでセキュリティ対策を導入することで、品質を妥協せずに、安全なアプリケーションを効率的に開発できます。設計から開発、デプロイまで、[ライフサイクルのすべてのステージ](/blog/top-10-gitlab-hacks/)をカバーすることが重要です。\n\n効果的にこのプロセスを実施するためには、デベロッパーが適切なセキュリティ制御が実装されたアプリケーションを設計した上で、オペレーションチームがアプリケーションを安全にデプロイし、モニタリングする必要があります。\n\n### 積極的なモニタリングと対応戦略\nアプリケーションのライフサイクルを通じてセキュリティを維持するためには、積極的なモニタリングと対応戦略を立てることが不可欠です。[モニタリング](/blog/working-with-performance-metrics/)を行うには、潜在的な脆弱性を特定し、発生時にチームに通知する自動化されたツールをデプロイします。\n\nこれにより、リスクが最小限に抑えられ、組織全体において一貫性を確保できます。包括的な対応戦略を採用することで、問題が悪化してセキュリティリスクとなる前に特定し、解決できます。\n\n## DevSecOpsの導入によって得られるメリット\nDevSecOpsを導入すると、組織は以下のような多くのメリットを得られます。\n1. 安全なソフトウェアを提供できるため、顧客との信頼関係を構築しやすくなります。\n2. 悪意のある人物によるシステムの脆弱性の悪用を防止できるとともに、システムのセキュリティが向上します。\n3. DevSecOpsの開発手法により、最高レベルのセキュリティを確保しながら、迅速に価値を提供できます。\n4. 設計からデプロイまで、ソフトウェア開発パイプラインにセキュリティ対策を組み込むことで、チームは潜在的なリスクをすばやく特定して対処できるため、悪質な攻撃のリスクを低減できます。\n5. DevSecOpsを導入することで、組織は潜在的な脅威を事前に特定して対処し、市場での競争力を維持できます。\n\n[DevSecOpsの導入](/blog/whats-next-for-devsecops/)は、迅速かつ効率的に価値を提供しながら、悪質な攻撃からシステムを保護したいと考えている組織にとって不可欠です。さらに、SDLCにセキュリティを統合することで、新規アプリケーションの安全性を最初から確保できます。DevSecOpsの文化とアプローチを浸透させることで、ソフトウェア開発プロセスの全体的な効率と品質が最大限に高まります。","yml",{},true,"/ja-jp/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles",{"title":14,"description":16,"ogImage":18},"how-to-strengthen-security-by-applying-devsecops-principles","ja-jp/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles","article","nwEJtPM6YbJgwizE8Stvf2hwcmTJScRMQ8-aAKm5GBI",{"data":34},{"text":35,"config":36,"items":41,"minimal":392},"GitはSoftware Freedom Conservancyの商標です。当社は「GitLab」をライセンスに基づいて使用しています",{"twitter":37,"facebook":38,"youtube":39,"linkedin":40},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[42,100,176,257,335],{"title":43,"links":44,"subMenu":61},"価格",[45,51,56],{"text":46,"config":47},"プランの表示",{"href":48,"dataGaName":49,"dataGaLocation":50},"/ja-jp/pricing/","view plans","footer",{"text":52,"config":53},"Premiumを選ぶ理由",{"href":54,"dataGaName":55,"dataGaLocation":50},"/ja-jp/pricing/premium/","why premium",{"text":57,"config":58},"Ultimateを選ぶ理由",{"href":59,"dataGaName":60,"dataGaLocation":50},"/ja-jp/pricing/ultimate/","why ultimate",[62],{"title":63,"links":64},"お問い合わせ",[65,70,75,80,85,90,95],{"text":66,"config":67},"営業担当へのお問い合わせ",{"href":68,"dataGaName":69,"dataGaLocation":50},"/ja-jp/sales/","sales",{"text":71,"config":72},"サポートポータル",{"href":73,"dataGaName":74,"dataGaLocation":50},"https://support.gitlab.com/hc/en-us","support portal",{"text":76,"config":77},"カスタマーポータル",{"href":78,"dataGaName":79,"dataGaLocation":50},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":81,"config":82},"ステータス",{"href":83,"dataGaName":84,"dataGaLocation":50},"https://status.gitlab.com/","status",{"text":86,"config":87},"利用規約",{"href":88,"dataGaName":89,"dataGaLocation":50},"/terms/","terms of use",{"text":91,"config":92},"プライバシーに関する声明",{"href":93,"dataGaName":94,"dataGaLocation":50},"/ja-jp/privacy/","privacy statement",{"text":96,"config":97},"Cookie設定",{"dataGaName":98,"dataGaLocation":50,"id":99,"isOneTrustButton":26},"cookie preferences","ot-sdk-btn",{"title":101,"links":102,"subMenu":133},"プラットフォーム",[103,108,113,118,123,128],{"text":104,"config":105},"プラットフォームを詳しく見る",{"href":106,"dataGaName":107,"dataGaLocation":50},"/ja-jp/platform/","platform",{"text":109,"config":110},"Duo Agent Platform",{"href":111,"dataGaName":112,"dataGaLocation":50},"/ja-jp/gitlab-duo-agent-platform/","duo agent platform",{"text":114,"config":115},"CI/CD",{"href":116,"dataGaName":117,"dataGaLocation":50},"/ja-jp/solutions/continuous-integration/","ci/cd",{"text":119,"config":120},"Orbitコンテキストグラフ",{"href":121,"dataGaName":122,"dataGaLocation":50},"/ja-jp/gitlab-orbit/","orbit",{"text":124,"config":125},"シークレット管理",{"href":126,"dataGaName":127,"dataGaLocation":50},"/ja-jp/gitlab-secrets-manager/","secrets management",{"text":129,"config":130},"GitLabが選ばれる理由",{"href":131,"dataGaName":132,"dataGaLocation":50},"/ja-jp/why-gitlab/","why gitlab",[134],{"title":135,"links":136},"トピック",[137,141,146,151,156,161,166,171],{"text":114,"config":138},{"href":139,"dataGaName":140,"dataGaLocation":50},"/ja-jp/topics/ci-cd/","cicd",{"text":142,"config":143},"GitOps",{"href":144,"dataGaName":145,"dataGaLocation":50},"/ja-jp/topics/gitops/","gitops",{"text":147,"config":148},"DevOps",{"href":149,"dataGaName":150,"dataGaLocation":50},"/ja-jp/topics/devops/","devops",{"text":152,"config":153},"バージョン管理",{"href":154,"dataGaName":155,"dataGaLocation":50},"/ja-jp/topics/version-control/","version control",{"text":157,"config":158},"DevSecOps",{"href":159,"dataGaName":160,"dataGaLocation":50},"/ja-jp/topics/devsecops/","devsecops",{"text":162,"config":163},"クラウドネイティブ",{"href":164,"dataGaName":165,"dataGaLocation":50},"/ja-jp/topics/cloud-native/","cloud native",{"text":167,"config":168},"コーディングのためのAI",{"href":169,"dataGaName":170,"dataGaLocation":50},"/ja-jp/topics/devops/ai-for-coding/","ai for coding",{"text":172,"config":173},"エージェント型AI",{"href":174,"dataGaName":175,"dataGaLocation":50},"/ja-jp/topics/agentic-ai/","agentic ai",{"title":177,"links":178},"ソリューション",[179,184,189,194,199,204,209,214,219,224,229,234,239,242,247,252],{"text":180,"config":181},"DevOpsモダナイゼーション",{"href":182,"dataGaName":183,"dataGaLocation":50},"/ja-jp/assessments/devops-modernization-assessment/","devops modernization",{"text":185,"config":186},"セキュリティモダナイゼーション",{"href":187,"dataGaName":188,"dataGaLocation":50},"/ja-jp/assessments/security-modernization-assessment/","security modernization",{"text":190,"config":191},"AIモダナイゼーション",{"href":192,"dataGaName":193,"dataGaLocation":50},"/ja-jp/assessments/ai-modernization-assessment/","ai modernization",{"text":195,"config":196},"金融サービス",{"href":197,"dataGaName":198,"dataGaLocation":50},"/ja-jp/solutions/finance/","financial services",{"text":200,"config":201},"公共機関",{"href":202,"dataGaName":203,"dataGaLocation":50},"/ja-jp/solutions/public-sector/","public sector",{"text":205,"config":206},"通信",{"href":207,"dataGaName":208,"dataGaLocation":50},"/ja-jp/solutions/telecommunications/","telecommunications",{"text":210,"config":211},"自動車",{"href":212,"dataGaName":213,"dataGaLocation":50},"/ja-jp/solutions/automotive/","automotive",{"text":215,"config":216},"教育",{"href":217,"dataGaName":218,"dataGaLocation":50},"/ja-jp/solutions/education/","education",{"text":220,"config":221},"航空宇宙",{"href":222,"dataGaName":223,"dataGaLocation":50},"/ja-jp/solutions/aerospace/","aerospace",{"text":225,"config":226},"エンタープライズ",{"href":227,"dataGaName":228,"dataGaLocation":50},"/ja-jp/enterprise/","enterprise",{"text":230,"config":231},"スモールビジネス",{"href":232,"dataGaName":233,"dataGaLocation":50},"/ja-jp/small-business/","small business",{"text":235,"config":236},"スタートアップ",{"href":237,"dataGaName":238,"dataGaLocation":50},"/ja-jp/solutions/startups/","startups",{"text":142,"config":240},{"href":241,"dataGaName":145,"dataGaLocation":50},"/ja-jp/solutions/gitops/",{"text":243,"config":244},"ソフトウェアコンポジション解析",{"href":245,"dataGaName":246,"dataGaLocation":50},"/ja-jp/solutions/supply-chain/","software composition analysis",{"text":248,"config":249},"バリューストリーム管理",{"href":250,"dataGaName":251,"dataGaLocation":50},"/ja-jp/solutions/visibility-measurement/","value stream management",{"text":253,"config":254},"すべてのソリューション",{"href":255,"dataGaName":256,"dataGaLocation":50},"/ja-jp/solutions/","all solutions",{"title":258,"links":259},"リソース",[260,265,270,275,280,285,290,295,300,305,310,315,320,325,330],{"text":261,"config":262},"インストール",{"href":263,"dataGaName":264,"dataGaLocation":50},"/ja-jp/install/","install",{"text":266,"config":267},"クイックスタートガイド",{"href":268,"dataGaName":269,"dataGaLocation":50},"/ja-jp/get-started/","quick setup checklists",{"text":271,"config":272},"製品ドキュメント",{"href":273,"dataGaName":274,"dataGaLocation":50},"https://docs.gitlab.com/ja-jp","docs",{"text":276,"config":277},"GitLab University",{"href":278,"dataGaName":279,"dataGaLocation":50},"https://university.gitlab.com/","university",{"text":281,"config":282},"技術デモ",{"href":283,"dataGaName":284,"dataGaLocation":50},"/ja-jp/gitlab-technical-demo-series/","demo series",{"text":286,"config":287},"インタラクティブデモ",{"href":288,"dataGaName":289,"dataGaLocation":50},"/ja-jp/demo-hub/","demo hub",{"text":291,"config":292},"GitLabサービス",{"href":293,"dataGaName":294,"dataGaLocation":50},"/ja-jp/services/","services",{"text":296,"config":297},"ブログ",{"href":298,"dataGaName":299,"dataGaLocation":50},"/ja-jp/blog/","blog",{"text":301,"config":302},"コミュニティ",{"href":303,"dataGaName":304,"dataGaLocation":50},"/community/","community",{"text":306,"config":307},"お客様事例",{"href":308,"dataGaName":309,"dataGaLocation":50},"/ja-jp/customers/","customers",{"text":311,"config":312},"パートナー",{"href":313,"dataGaName":314,"dataGaLocation":50},"/ja-jp/partners/","partners",{"text":316,"config":317},"イベント",{"href":318,"dataGaName":319,"dataGaLocation":50},"/events/","events",{"text":321,"config":322},"ニュースレター",{"href":323,"dataGaName":324,"dataGaLocation":50},"/company/contact/#contact-forms","newsletter",{"text":326,"config":327},"最新リリース",{"href":328,"dataGaName":329,"dataGaLocation":50},"/ja-jp/whats-new/","whats new",{"text":331,"config":332},"すべてのリソース",{"href":333,"dataGaName":334,"dataGaLocation":50},"/ja-jp/resources/","all resources",{"title":336,"links":337},"会社情報",[338,343,348,353,358,363,368,373,378,382,387],{"text":339,"config":340},"GitLabについて",{"href":341,"dataGaName":342,"dataGaLocation":50},"/ja-jp/company/","company",{"text":344,"config":345},"採用情報",{"href":346,"dataGaName":347,"dataGaLocation":50},"/jobs/","jobs",{"text":349,"config":350},"プレス",{"href":351,"dataGaName":352,"dataGaLocation":50},"/press/","press",{"text":354,"config":355},"ハンドブック",{"href":356,"dataGaName":357,"dataGaLocation":50},"https://handbook.gitlab.com/","handbook",{"text":359,"config":360},"経営陣",{"href":361,"dataGaName":362,"dataGaLocation":50},"/company/team/e-group/","leadership",{"text":364,"config":365},"投資家向け情報",{"href":366,"dataGaName":367,"dataGaLocation":50},"https://ir.gitlab.com/overview/default.aspx","investor relations",{"text":369,"config":370},"トラストセンター",{"href":371,"dataGaName":372,"dataGaLocation":50},"/ja-jp/security/","trust center",{"text":374,"config":375},"AI Transparency Center",{"href":376,"dataGaName":377,"dataGaLocation":50},"/ja-jp/ai-transparency-center/","ai transparency center",{"text":379,"config":380},"Sustainability",{"href":381,"dataGaName":379,"dataGaLocation":50},"/sustainability/",{"text":383,"config":384},"ダイバーシティ、インクルージョン、ビロンギング（DIB）",{"href":385,"dataGaName":386,"dataGaLocation":50},"/ja-jp/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":388,"config":389},"現代奴隷制の透明性に関する声明",{"href":390,"dataGaName":391,"dataGaLocation":50},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":393},[394,396,398],{"text":86,"config":395},{"href":88,"dataGaName":89,"dataGaLocation":50},{"text":96,"config":397},{"dataGaName":98,"dataGaLocation":50,"id":99,"isOneTrustButton":26},{"text":91,"config":399},{"href":93,"dataGaName":94,"dataGaLocation":50},{"visibility":26,"title":401,"button":402},"The Intelligent Software Development Era: How AI is reshaping DevSecOps teams",{"config":403,"text":405},{"href":404},"/ja-jp/developer-survey/japan/","Get the research report",{"logo":407,"subscribeLink":412,"navItems":416},{"altText":408,"config":409},"the source logo",{"src":410,"href":411},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/ja-jp/the-source/",{"text":413,"config":414},"購読する",{"href":415},"#subscribe",[417,421,425],{"text":418,"config":419},"人工知能",{"href":420},"/ja-jp/the-source/ai/",{"text":422,"config":423},"セキュリティとコンプライアンス",{"href":424},"/ja-jp/the-source/security/",{"text":426,"config":427},"プラットフォームとインフラストラクチャ",{"href":428},"/ja-jp/the-source/platform/",{"categoryNames":430},{"ai":418,"platform":426,"security":422},{"title":432,"description":433,"submitMessage":434,"formData":435},"The Sourceニュースレター","ソフトウェア開発の未来への洞察に関する最新情報を入手しましょう。","The Sourceのニュースレターへの登録が完了しました。",{"config":436},{"formId":437,"formName":324,"hideRequiredLabel":26},28467,{"id":439,"title":440,"body":6,"category":6,"config":441,"content":442,"description":6,"extension":24,"meta":458,"navigation":26,"path":459,"seo":460,"slug":7,"stem":461,"testContent":6,"type":462,"__hash__":463},"pages/ja-jp/the-source/security/index.yml","",{"layout":9},[443,450],{"componentName":444,"componentContent":445},"TheSourceCategoryHero",{"title":422,"description":446,"image":447},"進化するセキュリティ脅威とコンプライアンス要件に対応するための最新情報をお届けします。",{"config":448},{"src":449},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463273/aplkxrvwpii26xao5yhi.png",{"componentName":451,"componentContent":452},"TheSourceCategoryMainSection",{"config":453},{"sourceCTAs":454},[455,456,457],"source-lp-guide-to-dynamic-sboms","source-lp-a-field-guide-to-threat-vectors-in-the-software-supply-chain","application-security-in-the-digital-age",{},"/ja-jp/the-source/security",{"title":422,"description":446,"ogImage":440},"ja-jp/the-source/security/index","category","LdkNmpSN4IQ6BbGSqZS7AwRiPaalH_hSrFUQoOJA1UY",{"id":439,"title":440,"body":6,"category":6,"config":465,"content":466,"description":6,"extension":24,"meta":475,"navigation":26,"path":459,"seo":476,"slug":7,"stem":461,"testContent":6,"type":462,"__hash__":463},{"layout":9},[467,471],{"componentName":444,"componentContent":468},{"title":422,"description":446,"image":469},{"config":470},{"src":449},{"componentName":451,"componentContent":472},{"config":473},{"sourceCTAs":474},[455,456,457],{},{"title":422,"description":446,"ogImage":440},{"id":478,"title":479,"body":6,"category":6,"config":480,"content":481,"description":6,"extension":24,"meta":492,"navigation":26,"path":493,"seo":494,"slug":11,"stem":495,"testContent":6,"type":496,"__hash__":497},"theSourceAuthors/ja-jp/the-source/authors/ncregan.yml","Ncregan",{"layout":9},[482,490],{"componentName":483,"componentContent":484},"TheSourceAuthorHero",{"config":485,"name":486,"headshot":487},{"gitlabHandle":11},"Niall Cregan",{"altText":486,"config":488},{"src":489},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463431/yrtwodocb4cu3j7lkhyo.png",{"componentName":491},"TheSourceArticlesList",{},"/ja-jp/the-source/authors/ncregan",{"title":486},"ja-jp/the-source/authors/ncregan","author","3ORGYneKJd4gk7O8MKWMjz3WIHhKIZ3J1Gx848wV4lU",[499,509,516],{"config":500,"title":501,"description":502,"link":503},{"slug":457},"デジタル時代のアプリケーション・セキュリティ","[世界各地のDevSecOpsの専門家5,000名を対象に行った調査結果](https://about.gitlab.com/ja-jp/developer-survey/2024/security-compliance/)を読み、組織がアタックサーフェス（攻撃対象領域）の増加にどのように取り組んでいるか、またセキュリティとAIに対する姿勢がどのように変化しているかをご覧ください。",{"text":504,"config":505},"レポートを読む",{"href":506,"dataGaName":507,"dataGaLocation":508},"/ja-jp/developer-survey/2024/security-compliance/","Application Security in the Digital Age","thesource",{"config":510,"title":511,"link":512},{"slug":456},"ソフトウェアサプライチェーンにおける脅威ベクターのフィールドガイド",{"config":513},{"href":514,"dataGaName":515,"dataGaLocation":508},"/the-source/security/field-guide-to-threat-vectors-in-the-software-supply-chain/","A field guide to threat vectors in the software supply chain",{"config":517,"title":518,"description":519,"link":520},{"slug":455},"GitLab動的SBOMガイド： 最新のソフトウェア開発に不可欠な要素","ソフトウェア部品表（SBOM）を使用して、これまで認識されていなかった組織リスクを可視化する方法をご紹介します。",{"text":521,"config":522},"ガイドを読む",{"href":523,"dataGaName":524,"dataGaLocation":508},"/the-source/security/guide-to-dynamic-sboms/","Guide to Dynamic SBOMs",1794911811619]