ArchiveorgSoftwareA tool for secrets management, encryption as a service, and privileged access management Please note: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault, please responsibly disclose by contacting us at Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein![1]. Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.The key features of Vault are:Secure Secret Storage: Arbitrary key/value secrets can be storedin Vault. Vault encrypts these secrets prior to writing them to persistentstorage, so gaining access to the raw storage isn't enough to accessyour secrets. Vault can write to disk, Consul[2],and more.Dynamic Secrets: Vault can generate secrets on-demand for somesystems, such as AWS or SQL databases. For example, when an applicationneeds to access an S3 bucket, it asks Vault for credentials, and Vaultwill generate an AWS keypair with valid permissions on demand. Aftercreating these dynamic secrets, Vault will also automatically revoke themafter the lease is up.Data Encryption: Vault can encrypt and decrypt data without storingit. This allows security teams to define encryption parameters anddevelopers to store encrypted data in a location such as SQL withouthaving to design their own encryption methods.Leasing and Renewal: All secrets in Vault have a lease associatedwith it. At the end of the lease, Vault will automatically revoke thatsecret. Clients are able to renew leases via built-in renew APIs.Revocation: Vault has built-in support for secret revocation. Vaultcan revoke not only single secrets, but a tree of secrets, for exampleall secrets read by a specific user, or all secrets of a particular type.Revocation assists in key rolling as well as locking down systems in thecase of an intrusion.Documentation, Getting Started, and Certification ExamsDocumentation is available on the Vault website[3].If you're new to Vault and want to get started with security automation, pleasecheck out our Getting Started guides[4]on HashiCorp's learning platform. There are also additional guides[5]to continue your learning.Show off your Vault knowledge by passing a certification exam. Visit thecertification page[6]for information about exams and find study materials[7]on HashiCorp's learning platform.Developing VaultIf you wish to work on Vault itself or any of its built-in systems, you'llfirst need Go installed on your machine. Go version1.13.7+ is required.For local dev first make sure Go is properly installed, including setting up aGOPATH[8]. Ensure that $GOPATH/bin is inyour path as some distributions bundle old version of build tools. Next, clone thisrepository. Vault uses Go Modules[9],so it is recommended that you clone the repository outside of the GOPATH.You can then download any required build tools by bootstrapping your environment:sh$ make bootstrap...To compile a development version of Vault, run make or make dev. This willput the Vault binary in the bin and $GOPATH/bin folders:sh$ make dev...$ bin/vault...To compile a development version of Vault with the UI, run make static-dist dev-ui. This willput the Vault binary in the bin and $GOPATH/bin folders:sh$ make static-dist dev-ui...$ bin/vault...To run tests, type make test. Note: this requires Docker to be installed. Ifthis exits with exit status 0, then everything is working!sh$ make test...If you're developing a specific package, you can run tests for just thatpackage by specifying the TEST variable. For example below, onlyvault package tests will be$ make test TEST=./vault...Acceptance TestsVault has comprehensive acceptance tests[10]covering most of the features of the secret and auth methods.If you're working on a feature of a secret or auth method and want toverify it is functioning (and also hasn't broken anything else), we recommendrunning the acceptance tests.Warning: The acceptance tests create/destroy/modify real resources, whichmay incur real costs in some cases. In the presence of a bug, it is technicallypossible that broken backends could leave dangling data behind. Therefore,please run the acceptance tests at your own risk. At the very least,we recommend running them in their own private account for whatever backendyou're testing.To run the acceptance tests, invoke make testacc:sh$ make testacc TEST=./builtin/logical/consul...The TEST variable is required, and you should specify the folder where thebackend is. The TESTARGS variable is recommended to filter down to a specificresource to test, since testing all of them at once can sometimes take a verylong time.Acceptance tests typically require other environment variables to be set forthings such as access keys. The test itself should error early and tellyou what to set, so it is not documented here.For more information on Vault Enterprise features, visit the Vault Enterprise site[11]. To restore the repository download the bundle wget and run: git clone hashicorp-vault_-_2020-09-15_17-00-13.bundle Source:[12]Uploader: hashicorp[13]Upload date: 2020-09-15 References^ Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein! (^ Consul (^ Vault website (^ Getting Started guides (^ additional guides (^ certification page (^ study materials (^ GOPATH (^ Go Modules (^ acceptance tests (^ Vault Enterprise site (^ (^ hashicorp (

weiterlesen: RSS Quelle öffnen