Gardener

Projects that follow the best practices below can voluntarily self-certify and show that they've achieved an Open Source Security Foundation (OpenSSF) best practices badge.

If this is your project, please show your badge status on your project page! The badge status looks like this: Badge level for project 1822 is passing Here is how to embed it:

These are the Silver level criteria. You can also view the Passing or Gold level criteria.

        

 Basics 17/17 ●

  • Identification

    Gardener Kubernetes Engine offers a fast and production-ready deployment of certified Kubernetes clusters at all major cloud providers. Deliver any infrastructure reliably, consistently and cost-effectively. Gardener includes a dashboard, a command line client and an API.

  • Prerequisites


    Enough for a badge!

    The project MUST achieve a passing level badge. [achieve_passing]

  • Basic project website content


    Enough for a badge!

    The information on how to contribute MUST include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) [contribution_requirements]

    https://gardener.cloud/docs/contribute/


  • Project oversight


    Enough for a badge!

    The project SHOULD have a legal mechanism where all developers of non-trivial amounts of project software assert that they are legally authorized to make these contributions. The most common and easily-implemented approach for doing this is by using a Developer Certificate of Origin (DCO), where users add "signed-off-by" in their commits and the project links to the DCO website. However, this MAY be implemented as a Contributor License Agreement (CLA), or other legal mechanism. (URL required) [dco]

    https://cla-assistant.io/gardener/gardener


    Enough for a badge!

    The project MUST clearly define and document its project governance model (the way it makes decisions, including key roles). (URL required) [governance]

    https://github.com/gardener/documentation/blob/master/GOVERNANCE.md


    Enough for a badge!

    The project MUST adopt a code of conduct and post it in a standard location. (URL required) [code_of_conduct]

    https://gardener.cloud/docs/contribute/#code-of-conduct


    Enough for a badge!

    The project MUST clearly define and publicly document the key roles in the project and their responsibilities, including any tasks those roles must perform. It MUST be clear who has which role(s), though this might not be documented in the same way. (URL required) [roles_responsibilities]

    https://github.com/gardener/documentation/blob/master/GOVERNANCE.md#roles


    Enough for a badge!

    The project MUST be able to continue with minimal interruption if any one person dies, is incapacitated, or is otherwise unable or unwilling to continue support of the project. In particular, the project MUST be able to create and close issues, accept proposed changes, and release versions of software, within a week of confirmation of the loss of support from any one individual. This MAY be done by ensuring someone else has any necessary keys, passwords, and legal rights to continue the project. Individuals who run a FLOSS project MAY do this by providing keys in a lockbox and a will providing any needed legal rights (e.g., for DNS names). (URL required) [access_continuity]

    The Gardener project is quite large. https://github.com/orgs/gardener/people There is no task which cannot be executed if any one person is incapacitated or killed


    Enough for a badge!

    The project SHOULD have a "bus factor" of 2 or more. (URL required) [bus_factor]

    The Gardener project is quite large. All teams have at least two maintainers https://github.com/orgs/gardener/teams.


  • Documentation


    Enough for a badge!

    The project MUST have a documented roadmap that describes what the project intends to do and not do for at least the next year. (URL required) [documentation_roadmap]

    Gardener Enhancement Proposals (GEP): https://github.com/gardener/gardener/tree/master/docs/proposals


    Enough for a badge!

    The project MUST include documentation of the architecture (aka high-level design) of the software produced by the project. If the project does not produce software, select "not applicable" (N/A). (URL required) [documentation_architecture]

    https://gardener.cloud/docs/gardener/concepts/architecture/


    Enough for a badge!

    The project MUST document what the user can and cannot expect in terms of security from the software produced by the project (its "security requirements"). (URL required) [documentation_security]
    1. https://gardener.cloud/docs/tutorials/ search for security
    2. As described in the Gardener Security Release Process: https://github.com/gardener/documentation/blob/master/security-release-process.md users can expect that the Gardener project team reduces the total time users are vulnerable to publicly known exploits as much as possible.

    Enough for a badge!

    The project MUST provide a "quick start" guide for new users to help them quickly do something with the software. (URL required) [documentation_quick_start]

    https://github.com/gardener/garden-setup


    Enough for a badge!

    The project MUST make an effort to keep the documentation consistent with the current version of the project results (including software produced by the project). Any known documentation defects making it inconsistent MUST be fixed. If the documentation is generally current, but erroneously includes some older information that is no longer true, just treat that as a defect, then track and fix as usual. [documentation_current]

    The Gardener project team members who are maintaining https://gardener.cloud and https://gardener.cloud/blog/ constantly keep the documentation consistent with the current version of the project results (including software produced by the project) https://github.com/gardener/gardener/releases https://github.com/gardener/dashboard/releases https://github.com/gardener/gardenctl/releases


    Enough for a badge!

    The project repository front page and/or website MUST identify and hyperlink to any achievements, including this best practices badge, within 48 hours of public recognition that the achievement has been attained. (URL required) [documentation_achievements]

    https://github.com/gardener/gardener/releases https://github.com/gardener/dashboard/releases https://github.com/gardener/gardenctl/releases


  • Accessibility and internationalization


    Enough for a badge!

    The project (both project sites and project results) SHOULD follow accessibility best practices so that persons with disabilities can still participate in the project and use the project results where it is reasonable to do so. [accessibility_best_practices]

    Gardener project and its content is hosted on GitHub, GitHub Accessibility is described here: https://accessibility.github.com/

    The project result is API-driven and consequently the full functionality is available from keyboard. Gardener Dashboard is a optional UI only.


    Enough for a badge!

    The software produced by the project SHOULD be internationalized to enable easy localization for the target audience's culture, region, or language. If internationalization (i18n) does not apply (e.g., the software doesn't generate text intended for end-users and doesn't sort human-readable text), select "not applicable" (N/A). [internationalization]

    the software doesn't generate text intended for end-users


  • Other


    Enough for a badge!

    If the project sites (website, repository, and download URLs) store passwords for authentication of external users, the passwords MUST be stored as iterated hashes with a per-user salt by using a key stretching (iterated) algorithm (e.g., Argon2id, Bcrypt, Scrypt, or PBKDF2). If the project sites do not store passwords for this purpose, select "not applicable" (N/A). [sites_password_security]

    the project sites do not store passwords for this purpose


  • Previous versions


    Enough for a badge!

    The project MUST maintain the most often used older versions of the product or provide an upgrade path to newer versions. If the upgrade path is difficult, the project MUST document how to perform the upgrade (e.g., the interfaces that have changed and detailed suggested steps to help upgrade). [maintenance_or_update]

    Gardener versions policy is described here: https://github.com/gardener/gardener/blob/master/docs/deployment/version_skew_policy.md Every Gardener release (project result) contains release notes providing further information on the upgrade path: https://github.com/gardener/gardener/releases


  • Coding standards


    Enough for a badge!

    The project MUST identify the specific coding style guides for the primary languages it uses, and require that contributions generally comply with it. (URL required) [coding_standards]

    Relevant coding style guidelines are mentioned here: https://gardener.cloud/docs/contribute/#contributing Formatting guidelines for Gardener documentation: https://gardener.cloud/docs/contribute/20_documentation/20_formatting_guide/ Style guidelines for Gardener documentation: https://gardener.cloud/docs/contribute/20_documentation/40_style_guide/


    Enough for a badge!

    The project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s). [coding_standards_enforced]

    Gardener project enforces coding styles if possible, e.g. via linting in GoLang, see https://github.com/gardener/gardener/blob/master/.golangci.yaml


  • Working build system


    Enough for a badge!

    Build systems for native binaries MUST honor the relevant compiler and linker (environment) variables passed in to them (e.g., CC, CFLAGS, CXX, CXXFLAGS, and LDFLAGS) and pass them to compiler and linker invocations. A build system MAY extend them with additional flags; it MUST NOT simply replace provided values with its own. If no native binaries are being generated, select "not applicable" (N/A). [build_standard_variables]

    Gardener uses Go build running in multi stage docker build, see: https://github.com/gardener/gardener/blob/master/Dockerfile


    Enough for a badge!

    The build and installation system SHOULD preserve debugging information if they are requested in the relevant flags (e.g., "install -s" is not used). If there is no build or installation system (e.g., typical JavaScript libraries), select "not applicable" (N/A). [build_preserve_debug]

    Gardener uses Go build running in multi stage docker build, see: https://github.com/gardener/gardener/blob/master/Dockerfile


    Enough for a badge!

    The build system for the software produced by the project MUST NOT recursively build subdirectories if there are cross-dependencies in the subdirectories. If there is no build or installation system (e.g., typical JavaScript libraries), select "not applicable" (N/A). [build_non_recursive]

    the Gardener components are built independent from each other into separate container images


    Enough for a badge!

    The project MUST be able to repeat the process of generating information from source files and get exactly the same bit-for-bit result. If no building occurs (e.g., scripting languages where the source code is used directly instead of being compiled), select "not applicable" (N/A). [build_repeatable]

    The Gardener project is not able to repeat the process of generating information from source files and get exactly the same bit-for-bit result. But we are able to reproduce semantically equivalent results: We have dependencies in source tree, we do not modify our container images after release, we tag the source state with a GitHub release


  • Installation system


    Enough for a badge!

    The project MUST provide a way to easily install and uninstall the software produced by the project using a commonly-used convention. [installation_common]

    An easy way to install Gardener for the purpose of "having a look into it" is described at https://github.com/gardener/garden-setup . Further deployment documentation can be found at https://github.com/gardener/gardener/blob/master/docs/README.md#deployment .


    Enough for a badge!

    The installation system for end-users MUST honor standard conventions for selecting the location where built artifacts are written to at installation time. For example, if it installs files on a POSIX system it MUST honor the DESTDIR environment variable. If there is no installation system or no standard convention, select "not applicable" (N/A). [installation_standard_variables]

    Gardener project results are following the OCI image specification.


    Enough for a badge!

    The project MUST provide a way for potential developers to quickly install all the project results and support environment necessary to make changes, including the tests and test environment. This MUST be performed with a commonly-used convention. [installation_development_quick]

    Guidance for potential developers to get started contributing to the project can be found here - https://github.com/gardener/gardener/blob/master/docs/README.md#development


  • Externally-maintained components


    Enough for a badge!

    The project MUST list external dependencies in a computer-processable way. (URL required) [external_dependencies]

    External dependencies can be found and processed (yaml) for each Gardener release (release asset called component descriptor) e.g. https://github.com/gardener/gardener/releases/latest/download/github.com_gardener_gardener.component_descriptor.cnudie.yaml


    Enough for a badge!

    Projects MUST monitor or periodically check their external dependencies (including convenience copies) to detect known vulnerabilities, and fix exploitable vulnerabilities or verify them as unexploitable. [dependency_monitoring]

    The Gardener project leverages Black Duck Binary Analysis fka Protecode to detect known vulnerabilities, and fix exploitable vulnerabilities or verify them as unexploitable


    Enough for a badge!

    The project MUST either:
    1. make it easy to identify and update reused externally-maintained components; or
    2. use the standard components provided by the system or programming language.
    Then, if a vulnerability is found in a reused component, it will be easy to update that component. [updateable_reused_components]

    Gardener provides a mechanism to auto update the Kubernetes version and the underlying host OS version


    Enough for a badge!

    The project SHOULD avoid using deprecated or obsolete functions and APIs where FLOSS alternatives are available in the set of technology it uses (its "technology stack") and to a supermajority of the users the project supports (so that users have ready access to the alternative). [interfaces_current]

    Gardener Project is quite depending on Kubernetes, the support Kubernetes versions are described here: https://github.com/gardener/gardener/blob/master/docs/usage/supported_k8s_versions.md .

    Other OSS dependencies are regularly assessed.


  • Automated test suite


    Enough for a badge!

    An automated test suite MUST be applied on each check-in to a shared repository for at least one branch. This test suite MUST produce a report on test success or failure. [automated_integration_testing]

    Gardener project defines the testing strategy and guideline here - https://gardener.cloud/docs/gardener/development/testing/ . The project relies on GitHub automation for testing and produces test reports accordingly.


    Enough for a badge!

    The project MUST add regression tests to an automated test suite for at least 50% of the bugs fixed within the last six months. [regression_tests_added50]

    regression test are only added to an automated test suite when it is necessary or when the bugs are security related.


    Not enough for a badge.

    The project MUST have FLOSS automated test suite(s) that provide at least 80% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language. [test_statement_coverage80]

    planned: with https://golang.org/cmd/cover/ we get already >50% statement coverage. Missing is: 1. continuous statement coverage automation 2. >80% statement coverage


  • New functionality testing


    Enough for a badge!

    The project MUST have a formal written policy that as major new functionality is added, tests for the new functionality MUST be added to an automated test suite. [test_policy_mandated]

    https://github.com/gardener/documentation/blob/master/CONTRIBUTING.md#pull-request-checklist


    Enough for a badge!

    The project MUST include, in its documented instructions for change proposals, the policy that tests are to be added for major new functionality. [tests_documented_added]

    https://github.com/gardener/documentation/blob/master/CONTRIBUTING.md#pull-request-checklist


  • Warning flags


    Enough for a badge!

    Projects MUST be maximally strict with warnings in the software produced by the project, where practical. [warnings_strict]

    There is evidence that the Gardener project is striving to enable warning flags where it can, so that errors are detected early. Example: a shoot resource definition cannot be uploaded when it contains an error.


  • Secure development knowledge


    Enough for a badge!

    The project MUST implement secure design principles (from "know_secure_design"), where applicable. If the project is not producing software, select "not applicable" (N/A). [implement_secure_design]

    The Gardener architecture itself https://gardener.cloud/docs/gardener/concepts/architecture/ is an implementation of secure design principles like introducing additional trust boundaries


  • Use basic good cryptographic practices

    Note that some software does not need to use cryptographic mechanisms. If your project produces software that (1) includes, activates, or enables encryption functionality, and (2) might be released from the United States (US) to outside the US or to a non-US-citizen, you may be legally required to take a few extra steps. Typically this just involves sending an email. For more information, see the encryption section of Understanding Open Source Technology & US Export Controls.

    Enough for a badge!

    The default security mechanisms within the software produced by the project MUST NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). [crypto_weaknesses]

    Gardener project ensures wanted and acceptable cipher suites, for example see https://github.com/gardener/gardener/blob/master/pkg/utils/kubernetes/tls_cipher_suites.go


    Enough for a badge!

    The project SHOULD support multiple cryptographic algorithms, so users can quickly switch if one is broken. Common symmetric key algorithms include AES, Twofish, and Serpent. Common cryptographic hash algorithm alternatives include SHA-2 (including SHA-224, SHA-256, SHA-384 AND SHA-512) and SHA-3. [crypto_algorithm_agility]

    https://github.com/gardener/gardener/pull/428/files


    Enough for a badge!

    The project MUST support storing authentication credentials (such as passwords and dynamic tokens) and private cryptographic keys in files that are separate from other information (such as configuration files, databases, and logs), and permit users to update and replace them without code recompilation. If the project never processes authentication credentials and private cryptographic keys, select "not applicable" (N/A). [crypto_credential_agility]

    Gardener project relies on standard Kubernetes means (secrets), see https://kubernetes.io/docs/concepts/configuration/secret/


    Enough for a badge!

    The software produced by the project SHOULD support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 SHOULD be disabled by default, and only enabled if the user specifically configures it. If the software produced by the project does not support network communications, select "not applicable" (N/A). [crypto_used_network]

    Gardener project relies on standard Kubernetes means, all API communication in the cluster is encrypted by default with TLS, see https://kubernetes.io/docs/tasks/administer-cluster/securing-a-cluster/#use-transport-layer-security-tls-for-all-api-traffic


    Enough for a badge!

    The software produced by the project SHOULD, if it supports or uses TLS, support at least TLS version 1.2. Note that the predecessor of TLS was called SSL. If the software does not use TLS, select "not applicable" (N/A). [crypto_tls12]

    Gardener supports at least TLS version 1.2


    Enough for a badge!

    The software produced by the project MUST, if it supports TLS, perform TLS certificate verification by default when using TLS, including on subresources. If the software does not use TLS, select "not applicable" (N/A). [crypto_certificate_verification]

    In Gardener project, the certificate management and verification is documented and implemented here - https://github.com/gardener/cert-management


    Enough for a badge!

    The software produced by the project MUST, if it supports TLS, perform certificate verification before sending HTTP headers with private information (such as secure cookies). If the software does not use TLS, select "not applicable" (N/A). [crypto_verification_private]

    In Gardener project, the certificate management and verification is documented and implemented here - https://github.com/gardener/cert-management


  • Secure release


    Enough for a badge!

    The project MUST cryptographically sign releases of the project results intended for widespread use, and there MUST be a documented process explaining to users how they can obtain the public signing keys and verify the signature(s). The private key for these signature(s) MUST NOT be on site(s) used to directly distribute the software to the public. If releases are not intended for widespread use, select "not applicable" (N/A). [signed_releases]

    each container image contains cryptographically hashes, following the OCI spec https://github.com/opencontainers/image-spec#oci-image-format-specification


    Barely enough for a badge.

    It is SUGGESTED that in the version control system, each important version tag (a tag that is part of a major release, minor release, or fixes publicly noted vulnerabilities) be cryptographically signed and verifiable as described in signed_releases. [version_tags_signed]

    via SAP's Repository Based Shipment Channel, SAP customers and partners can download cryptographically signed images of Gardener releases: https://shipments.pages.repositories.sap.ondemand.com/docs/shipment.html (restricted access). To provide cryptographically signed images of Gardener releases has not been a Gardener community requirement so far, besides the CII badge silver level compliance.


  • Other security issues


    Enough for a badge!

    The project results MUST check all inputs from potentially untrusted sources to ensure they are valid (an *allowlist*), and reject invalid inputs, if there are any restrictions on the data at all. [input_validation]

    Gardener is entirely API-driven and extends the K8s API concepts. All API clients must be authenticated and every API call is expected to pass an authorization check. Consequently, the Gardener API server is secured against untrusted sources.


    Enough for a badge!

    Hardening mechanisms SHOULD be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities. [hardening]

    Gardener has introduced several network policies and did according community communication https://groups.google.com/forum/#!topic/gardener/Pom2Y70cDpw


    Enough for a badge!

    The project MUST provide an assurance case that justifies why its security requirements are met. The assurance case MUST include: a description of the threat model, clear identification of trust boundaries, an argument that secure design principles have been applied, and an argument that common implementation security weaknesses have been countered. (URL required) [assurance_case]

    Gardener complies with DISA STIGs for Kubernetes. For every release we check that Gardener is able of creating a hardened shoot reconfirming that the configurations which are not secure by default (as per https://gardener.cloud/docs/guides/security-and-compliance/kubernetes-hardening/) are still possible and work as expected.


  • Static code analysis


    Enough for a badge!

    The project MUST use at least one static analysis tool with rules or approaches to look for common vulnerabilities in the analyzed language or environment, if there is at least one FLOSS tool that can implement this criterion in the selected language. [static_analysis_common_vulnerabilities]

    Gardener leverages CheckMarx


  • Dynamic code analysis


    Enough for a badge!

    If the software produced by the project includes software written using a memory-unsafe language (e.g., C or C++), then at least one dynamic tool (e.g., a fuzzer or web application scanner) MUST be routinely used in combination with a mechanism to detect memory safety problems such as buffer overwrites. If the project does not produce software written in a memory-unsafe language, choose "not applicable" (N/A). [dynamic_analysis_unsafe]

    the project does not produce software written in a memory-unsafe language (Go)



This data is available under the Creative Commons Attribution version 3.0 or later license (CC-BY-3.0+). All are free to share and adapt the data, but must give appropriate credit. Please credit Frederik Thormaehlen and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Frederik Thormaehlen.
Entry created on 2018-05-03 10:38:14 UTC, last updated on 2024-04-08 08:36:26 UTC. Last lost passing badge on 2023-12-06 08:32:42 UTC. Last achieved passing badge on 2023-12-06 08:33:09 UTC.

Back