Stay organized with collectionsSave and categorize content based on your preferences.
This documentation focuses primarily on best practices that support protecting
your software across processes and systems in your software supply chain. It
also includes information about how to implement some of the practices on
Google Cloud.
There are additional considerations for protecting your software that span the
software lifecycle or are foundational development practices that support
software supply chain security. For example:
Controlling physical and remote access to systems.
Implementing audit, monitoring, and feedback mechanisms so that you are able
to quickly identify and respond to threats and non-compliance with policy.
Foundational coding practices including design, input validation, output to
untrusted systems, data processing, code analysis, and cryptography.
Foundational DevOps practices beyond ones mentioned in this documentation,
including technical approaches, team process, and organizational culture.
Adherence to software licenses terms, including open source licenses for
direct and transitive dependencies.
Some open source licenses have restrictive license terms that are problematic
for commercial software. In particular, some licenses require you to release
your source code under the same license as the open source software that you
are reusing. If you want to keep your source code private, it's important
to know the licenses terms of open source software you use.
Increasing awareness about cybersecurity by providing training to employees.
According theState of Cybersecurity 2021, Part 2, a survey of
information security professionals, social engineering was the most frequent
type of attack. Survey respondants also reported that cybersecurity training
and awareness programs had some positive impact (46%) or strong positive
impact (32%) on employee awareness.
Use the resources in the following sections to learn more about these topics.
You can view centralized information about vulnerabilities and possible
risks using these Google Cloud services:
View information about vulnerabilities and threats across your Google Cloud
organization withSecurity Command Center.
Get information about your service usage withRecommender,
including recommendations that can help you to reduce risk. For example,
you can identify IAM principals with excess permissions or
unattended Google Cloud projects.
See theDevOps capabilitiesdocumentation to learn more about DevOps practices that contribute to faster
software delivery and more reliable and secure software.
There are also foundational practices for designing, developing, and testing
code that apply to all programming languages. You also need to evaluate how
you distribute software and the terms of software licenses in all of your
dependencies. The Linux Foundation offers free online training on these topics:
Developing Secure Software: Foundational
software development practices in the context of software supply chain
security. The course focuses on best practices for designing, developing, and
testing code, but also covers topics such as handling vulnerability disclosures,
assurance cases, and considerations for software distribution and deployment.
TheOpen Source Security Foundation(OpenSSF)
created the training.
As you incrementally implement best practices, document the policies for your
organization and incorporate validation of policies into your development,
build, and deployment processes. For example, your company policies might
include criteria for deployment that you implement withBinary Authorization.
Minimum Viable Secure Product, a security
checklist of controls to establish a baseline security posture for a
product. You can use the checklist to establish your minimum security
control requirements and to evaluate software by third-party vendors.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Protect your software supply chain\n\nThis documentation focuses primarily on best practices that support protecting\nyour software across processes and systems in your software supply chain. It\nalso includes information about how to implement some of the practices on\nGoogle Cloud.\n\n- [Safeguarding source integrity](/software-supply-chain-security/docs/safeguard-source)\n- [Safeguarding build integrity](/software-supply-chain-security/docs/safeguard-builds)\n- [Managing dependencies](/software-supply-chain-security/docs/dependencies)\n- [Safeguarding deployments](/software-supply-chain-security/docs/safeguard-deploys)\n\nThere are additional considerations for protecting your software that span the\nsoftware lifecycle or are foundational development practices that support\nsoftware supply chain security. For example:\n\n- Controlling physical and remote access to systems.\n- Implementing audit, monitoring, and feedback mechanisms so that you are able to quickly identify and respond to threats and non-compliance with policy.\n- Foundational coding practices including design, input validation, output to untrusted systems, data processing, code analysis, and cryptography.\n- Foundational DevOps practices beyond ones mentioned in this documentation, including technical approaches, team process, and organizational culture.\n- Adherence to software licenses terms, including open source licenses for\n direct and transitive dependencies.\n\n Some open source licenses have restrictive license terms that are problematic\n for commercial software. In particular, some licenses require you to release\n your source code under the same license as the open source software that you\n are reusing. If you want to keep your source code private, it's important\n to know the licenses terms of open source software you use.\n- Increasing awareness about cybersecurity by providing training to employees.\n According the [State of Cybersecurity 2021, Part 2](https://www.isaca.org/state-of-cybersecurity-2021), a survey of\n information security professionals, social engineering was the most frequent\n type of attack. Survey respondants also reported that cybersecurity training\n and awareness programs had some positive impact (46%) or strong positive\n impact (32%) on employee awareness.\n\nUse the resources in the following sections to learn more about these topics.\n\nSecurity on Google Cloud\n------------------------\n\nLearn about setting up organization structure, authentication and authorization,\nresource hierarchy, networking, logging, detective controls, and more in the\n[Google Cloud enterprise foundations blueprint](/architecture/security-foundations), one of\nthe guides in the\n[Google Cloud security best practices center](/security/best-practices).\n\nYou can view centralized information about vulnerabilities and possible\nrisks using these Google Cloud services:\n\n- View information about vulnerabilities and threats across your Google Cloud organization with [Security Command Center](/security-command-center/docs/security-command-center-overview).\n- Get information about your service usage with [Recommender](/recommender/docs/overview), including recommendations that can help you to reduce risk. For example, you can identify IAM principals with excess permissions or unattended Google Cloud projects.\n\nTo learn more about security on Google Cloud, see the\n[Security section of the Google Cloud web site](/security).\n\nDevOps and software development practices\n-----------------------------------------\n\nSee the [DevOps capabilities](https://dora.dev/devops-capabilities/)\ndocumentation to learn more about DevOps practices that contribute to faster\nsoftware delivery and more reliable and secure software.\n\nThere are also foundational practices for designing, developing, and testing\ncode that apply to all programming languages. You also need to evaluate how\nyou distribute software and the terms of software licenses in all of your\ndependencies. The Linux Foundation offers free online training on these topics:\n\n- [Developing Secure Software](https://training.linuxfoundation.org/training/developing-secure-software-lfd121/): Foundational software development practices in the context of software supply chain security. The course focuses on best practices for designing, developing, and testing code, but also covers topics such as handling vulnerability disclosures, assurance cases, and considerations for software distribution and deployment. The [Open Source Security Foundation](https://openssf.org/) (OpenSSF) created the training.\n- [Open Source Licensing Basics for Developers](https://training.linuxfoundation.org/training/open-source-licensing-basics-for-software-developers/) Learn about licenses and copyright for open source projects.\n- [Introduction to Open Source License Compliance Management](https://training.linuxfoundation.org/training/introduction-to-open-source-license-compliance-management-lfc193/) Learn about building an open source compliance program for your organization.\n\nDeveloping your policies\n------------------------\n\nAs you incrementally implement best practices, document the policies for your\norganization and incorporate validation of policies into your development,\nbuild, and deployment processes. For example, your company policies might\ninclude criteria for deployment that you implement with [Binary Authorization](/binary-authorization/docs/overview).\n\n- [Minimum Viable Secure Product](https://mvsp.dev), a security checklist of controls to establish a baseline security posture for a product. You can use the checklist to establish your minimum security control requirements and to evaluate software by third-party vendors.\n- NIST [Security and Privacy Controls for Information Systems and Organizations](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final) publication (SP 800-53)."]]