terraform-provider-power-platform

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 8714 is passing Here is how to embed it:

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

        

 Basics 2/5

  • Identification

    Power Platform Terraform Provider

  • Prerequisites


    The project MUST achieve a silver level badge. [achieve_silver]

  • Project oversight


    Mradi LAZIMA uwe na "bus factor" ya 2 au zaidi. (URL required) [bus_factor]

    Mradi LAZIMA uwe na angalau wachangiaji wawili wasiohusika. (URL required) [contributors_unassociated]

  • Other


    The project MUST include a license statement in each source file. This MAY be done by including the following inside a comment near the beginning of each file: SPDX-License-Identifier: [SPDX license expression for project]. [license_per_file]

  • Public version-controlled source repository


    The project's source repository MUST use a common distributed version control software (e.g., git or mercurial). [repo_distributed]

    Repository on GitHub, which uses git. git is distributed.



    The project MUST clearly identify small tasks that can be performed by new or casual contributors. (URL required) [small_tasks]

    Issues marked with the “good first issue” label (e.g., Issue #712) identify tasks suitable for new or casual contributors, meeting the small-tasks criterion. https://github.com/microsoft/terraform-provider-power-platform/labels/good%20first%20issue



    The project MUST require two-factor authentication (2FA) for developers for changing a central repository or accessing sensitive data (such as private vulnerability reports). This 2FA mechanism MAY use mechanisms without cryptographic mechanisms such as SMS, though that is not recommended. [require_2FA]

    Warning: Requires lengthier justification.



    The project's two-factor authentication (2FA) SHOULD use cryptographic mechanisms to prevent impersonation. Short Message Service (SMS) based 2FA, by itself, does NOT meet this criterion, since it is not encrypted. [secure_2FA]

  • Coding standards


    Mradi LAZIMA uandike mahitaji yake ya kukagua msimbo, pamoja na jinsi ukaguzi wa nambari unafanywa, nini lazima ichunguzwe, na nini kinachohitajika ili ikubalike. (URL required) [code_review_standards]


    The project MUST have at least 50% of all proposed modifications reviewed before release by a person other than the author, to determine if it is a worthwhile modification and free of known issues which would argue against its inclusion [two_person_review]

  • Working build system


    The project MUST have a reproducible build. If no building occurs (e.g., scripting languages where the source code is used directly instead of being compiled), select "not applicable" (N/A). (URL required) [build_reproducible]

    The GoReleaser configuration fixes mod_timestamp to the commit time, sets -trimpath, and builds with CGO_ENABLED=0, producing bit-for-bit identical binaries whenever the same commit and toolchain are rebuilt—meeting the reproducible-build criterion. https://github.com/microsoft/terraform-provider-power-platform/blob/main/.goreleaser.yml#L12-L19


  • Automated test suite


    A test suite MUST be invocable in a standard way for that language. (URL required) [test_invocation]

    The project MUST implement continuous integration, where new or changed code is frequently integrated into a central code repository and automated tests are run on the result. (URL required) [test_continuous_integration]

    Every push and pull-request triggers the “Terraform Provider Checks” GitHub Actions workflow, which builds the provider and runs its automated test suite—providing continuous integration on the central repository. https://github.com/microsoft/terraform-provider-power-platform/actions/workflows/terraform-provider-checks.yml



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

    Although Codecov reports statement coverage for each build, the current overall coverage is below the 90 % threshold required by this criterion, so the project does not yet meet the higher coverage target.



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

  • 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.

    The software produced by the project MUST 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 MUST 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]

    All network traffic is made over Microsoft Power Platform REST endpoints, which are HTTPS-only (TLS 1.2+); the provider exposes no option to use plain HTTP or other insecure protocols. https://registry.terraform.io/providers/microsoft/power-platform/latest/docs#authenticating-to-power-platform



    The software produced by the project MUST, 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]

    Every API call is made over HTTPS endpoints that require TLS 1.2 or later; no HTTP fallback is available. https://registry.terraform.io/providers/microsoft/power-platform/latest/docs#authentication-options


  • Secured delivery against man-in-the-middle (MITM) attacks


    The project website, repository (if accessible via the web), and download site (if separate) MUST include key hardening headers with nonpermissive values. (URL required) [hardened_site]

    The repository is hosted on GitHub, whose platform responses include the required hardening headers—CSP, HSTS, X-Content-Type-Options = nosniff, and X-Frame-Options = deny—so visitors receive these protections automatically. https://securityheaders.com/?q=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterraform-provider-power-platform


  • Other security issues


    The project MUST have performed a security review within the last 5 years. This review MUST consider the security requirements and security boundary. [security_review]


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

    Release binaries are built with Go 1.22 using the flags -trimpath (strips source-path leakage) and CGO_ENABLED=0, which yields position-independent, RELRO-protected, statically linked PIE executables compiled by a memory-safe language. These defaults give stack canaries, ASLR, RELRO, and NX by design—hardening the binary even without extra C flags. https://github.com/microsoft/terraform-provider-power-platform/blob/main/.goreleaser.yml#L12-L19


  • Dynamic code analysis


    The project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release. [dynamic_analysis]


    The project SHOULD include many run-time assertions in the software it produces and check those assertions during dynamic analysis. [dynamic_analysis_enable_assertions]

    Warning: Requires lengthier justification.



This data is available under the Community Data License Agreement – Permissive, Version 2.0 (CDLA-Permissive-2.0). This means that a Data Recipient may share the Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. Please credit Matt Dotson and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Matt Dotson.
Entry created on 2024-03-26 23:43:05 UTC, last updated on 2025-04-26 07:54:20 UTC. Last achieved passing badge on 2024-03-27 04:40:06 UTC.

Back