awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

add more clarity to e2ee notice

Browse Source
This commit is contained in:
Maidul Islam
2024-02-27 13:45:31 -05:00
parent 2f6f713c98
commit 5d64398e58
1 changed files with 10 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/documentation/platform/project-upgrade.mdx
View File

@@ -4,22 +4,18 @@ title: "Enhancing Security and Usability: Project Upgrades"
At Infisical, we're constantly striving to elevate the security and usability standards of our platform to better serve our users.
With this commitment in mind, we're excited to introduce our latest addition, Non-E2EE projects, aimed at addressing two significant issues while enhancing overall project management.
With this commitment in mind, we're excited to introduce our latest addition, non-E2EE projects, aimed at addressing two significant issues while enhancing how clients interact with Infisical programmatically.
Previously, users encountered a challenge wherein projects risked becoming inaccessible if the project creator departed or deleted their account.
Additionally, our API lacked the capability to interact with projects seamlessly.
These obstacles made automations and collaberation a painful experience for a majority of our users.
Previously, users encountered a challenge where projects risked becoming inaccessible if the project creator deleted their account.
Additionally, our API lacked the capability to interact with projects without dealing with complex cryptographic operations.
These obstacles made API driven automation and collaboration a painful experience for a majority of our users.
To overcome these limitations, our upgrade focuses on disabling end-to-end encryption (E2EE) for projects.
While this may raise eyebrows, it's essential to understand that this decision is a strategic move towards adopting industry-standard methods for securely storing sensitive information.
While this may raise eyebrows, it's important to understand that this decision is a strategic move to make Infisical easer to use and interact with.
But what does this mean for our users? Essentially nothing, there are no changes required on your end. Rest assured, all sensitive data remains encrypted at rest, ensuring robust protection against unauthorized access. Instead, this transition opens doors to implementing alternative security measures, paving the way for a more automated and streamlined experience within Infisical.
But what does this mean for our users? Essentially nothing, there are no changes required on your end.
Rest assured, all sensitive data remains encrypted at rest according to the latest industry standards.
Our commitment to security remains unwavering, and this upgrade is a testament to our dedication to delivering on our promises in both security and usability when it comes to secrets management.
By relinquishing E2EE, we're embracing a future where security protocols align with evolving industry standards.
This shift not only fortifies our platform but also empowers users with enhanced functionality and accessibility.
Our commitment to security remains unwavering, and this upgrade is a testament to our dedication to delivering on our promises in both security and usability.
Furthermore, as part of our commitment to providing a secure and user-friendly environment,
we are pleased to announce that all future projects created on Infisical will have end-to-end encryption (E2EE) disabled by default.
This proactive measure ensures consistency across all projects, aligning with our vision of adopting industry-standard security practices. With E2EE disabled from the outset,
users can seamlessly navigate their projects with confidence, knowing that their data is protected while enjoying enhanced collaboration and management capabilities.
To increase consistency with existing and future integrations, all projects created on Infisical from now on will have end-to-end encryption (E2EE) disabled by default.
This will not only reduce confusion for end users, but will also make the Infisical API seamless to use.