Data managed by Brainboard
Last updated
Was this helpful?
Last updated
Was this helpful?
Brainboard helps you build and manage cloud infrastructures, which means there are areas where either information are manipulated and/or stored.
Data manipulated: Brainboard will use this information to do some actions but doesn't store it.
Data stored: means that Brainboard keeps this information for future execution.
It also depends on the offering you have the information manipulated and stored are not the same.
Please refer to the if you want to understand all the possibilities you have to use Brainboard.
Here are the types of data used by Brainboard:
Cloud architectures: are the design of your cloud infrastructure.
Cloud resources: all the resources that you use from you preferred cloud provider(s) and their configurations.
.
Secrets: you can choose to store the secrets in your preferred vault solution like AWS KMS, Azure key-vault or HashiCorp Vault and only refer to it through data sources or variables.
If you deploy through Brainboard, these secrets will be shared with the runner that will provision the infrastructure.
.
: contains either your GitHub connection or personal git tokens. It may also include the names of your repository and files.
: these credentials allow you to provision or destroy the infrastructure.
Users personal information: We only store the following information about our users:
First name
Last name
Email address
Organization name
Pipeline information: it contains information about the provisioning of your infrastructure and the deployment workflow you have.
All information stored in Brainboard are encrypted at rest and at transit.
There are 3 scenarios where data is accessed by Brainboard:
In this scenario:
You design your cloud infrastructure in Brainboard
Generate the Terraform code in Brainboard
Then, you push the generated code into your preferred git repository
Data manipulated by Brainboard:
Architecture diagram.
Cloud resources and their configuration.
Variables.
Credentials to access git repo, unless you want to manually download the code and push it from your laptop.
Data stored by Brainboard:
Architecture diagram as a JSON structure. Not as a diagram.
Cloud resources and their configuration.
Variables.
Credentials to access git repo.
In this scenario:
You design your cloud infrastructure in Brainboard
Generate the Terraform code in Brainboard
Do a Terraform plan or trigger the pipeline for the plan in Brainboard
Once your architecture is validated, you push the generated code into your preferred git repository
Data manipulated by Brainboard:
Architecture diagram.
Cloud resources and their configuration.
Variables.
Terraform state file.
If you use a remote backend, Brainboard needs to access it to run some Terraform actions like plan, apply or destroy.
Credentials to access git repo, unless you want to manually download the code and push it from your laptop.
Cloud provider(s) credentials with at least read-only privilege.
Data stored by Brainboard:
Architecture diagram as a JSON structure. Not as a diagram.
Cloud resources and their configuration.
Variables.
Credentials to access git repo.
Cloud provider(s) credentials with at least read-only privilege.
In this scenario:
You design your cloud infrastructure in Brainboard
Generate the Terraform code in Brainboard
You may want to push the generated code into your preferred git repository
Deploy with Brainboard, either with apply or using our CI/CD engine to trigger your pipelines
Data manipulated by Brainboard:
Architecture diagram.
Cloud resources and their configuration.
Variables.
Terraform state file.
Cloud provider(s) credentials with read-write privilege.
Credentials to access git repo, unless you want to manually download the code and push it from your laptop.
Data stored by Brainboard:
Architecture diagram as a JSON structure. Not as a diagram.
Cloud resources and their configuration.
Variables.
Cloud provider(s) credentials with read-write privilege.
Credentials to access git repo.
Reach out to our security team if you have any question related to the security of your data at security@brainboard.co.
