diff --git a/website/source/partnerships.html.erb b/website/source/partnerships.html.erb deleted file mode 100644 index 1e75963ea..000000000 --- a/website/source/partnerships.html.erb +++ /dev/null @@ -1,134 +0,0 @@ ---- -layout: "inner" -page_title: "Community" -description: |- - Vault is an open source project with a growing community. ---- - -

Vault Integration Program

- -

- The Vault Integration Program (VIP) enables vendors to build integrations with HashiCorp Vault that are officially tested and approved by HashiCorp. The program is intended to be largely self-service, with links to code samples, documentation and clearly defined integration steps. -

- -

Types of Vault Integrations

- -

-By leveraging Vault's plugin system, vendors are able to build extensible secrets, authentication, and audit plugins to extend Vault's functionality. These integrations can be done with the OSS (open-source) version of Vault. Hardware Security Module (HSM) integrations need to be tested against Vault Enterprise since the HSM functionality is only supported in the Vault Enterprise version. -

- -

-Authentication Methods: Auth methods are the components in Vault that perform authentication and are responsible for assigning identity and a set of policies to a user. -

- -

-Vault Secrets Engine: Secrets engines are components which store, generate, or encrypt data. Secrets engines are incredibly flexible, so it is easiest to think about them in terms of their function. Secrets engines are provided some set of data, they take some action on that data, and they return a result. -

- -

-Audit Devices: Audit devices are the components in Vault that keep a detailed log of all requests and response to Vault. Because every operation with Vault is an API request/response, the audit log contains every authenticated interaction with Vault, including errors. (no plugin interface - built into Vault Core. Leave it there - no reqs yet but expect some soon) -

- -

- -Hardware Security Module (HSM): HSM support is a feature of Vault Enterprise that takes advantage of HSMs to provide Master Key Wrapping, Automatic Unsealing and Seal Wrapping via the PKCS#11 protocol ver. 2.2+. -

- -

- -Cloud / Third Party Autounseal Integration: Non-PKCS#11 integrations with secure external data stores (e.g.: AWS KMS, Azure Key Vault) to provide Autounsealing and Seal-Wrapping. -

- -

- -Storage Backend: A storage backend is a durable storage location where Vault stores its information. -

- -

Development Process

- -

The Vault integration development process is described into the steps below. By following these steps, Vault integrations can be developed alongside HashiCorp to ensure new integrations are reviewed, certified and released as quickly as possible.

- -
    -
  1. Engage: Initial contact between vendor and HashiCorp
    2. -
  2. Enable: Documentation, code samples and best practices for developing the integration
    3. -
  3. Develop and Test: Integration development and testing by vendor
    4. -
  4. Review/Certification: HashiCorp code review and certification of integration
    5. -
  5. Release: Vault integration released
    6. -
  6. Support: Ongoing maintenance and support of the integration by the vendor.
    7. -
- -

1. Engage

-

-Please begin by completing Vault Integration Program webform to tell us about your company and the Vault integration you’re interested in. -

- -

2. Enable

-

-Here are links to resources, documentation, examples and best practices to guide you through the Vault integration development and testing process: -

- -

General Vault Plugin Development:

- - -

Secrets Engines

- - -

Authentication Methods

-