security overview #489
Closed
security overview #489
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
I think we need to rethink this section. It is useful to give an introduction to the security architecture in AuraDB, but it needs to be a) its own subchapter as it introduces not only secure connections but alos SSO and encryption, and b) more concise and less repetitive.
Also, we don't refer to users as customers in the docs and we are not trying to sell anything.
| 100% of AuraDB Virtual Dedicated Cloud customers operate within a Virtual Private Cloud (VPC) isolated architecture with a dedicated infrastructure. | ||
|
|
||
| AuraDB offers fine-grained access control to the database with built-in Role-Based Access Control (RBAC) at the database level, similar to what can be configured in a self-managed Neo4j environment. | ||
| All traffic passing through the Aura console, your VPC, and the VPC provisioned by Neo4j is encrypted both at rest. |
There was a problem hiding this comment.
Both at rest and? In transit?
Comment on lines
+18
to
+23
| Features such as Single Sign-On (SSO) via OpenID Connect (OIDC) and Customer Managed Encryption (CMK) keys address the security and compliance needs of many of our customers. | ||
| SSO has been one of the most requested features, and CMK was introduced in 2024 which has been validated by large, trusted enterprises. | ||
|
|
||
| Security log forwarding, now generally available, has been validated by security auditors and meets the requirements of customer security audits. | ||
| Our ongoing compliance efforts are a priority, starting with ISO 27001 certification, and extending to SOC 1 and SOC 2 compliance. | ||
| HIPAA compliance has also been recently achieved. |
There was a problem hiding this comment.
Suggested change
| Features such as Single Sign-On (SSO) via OpenID Connect (OIDC) and Customer Managed Encryption (CMK) keys address the security and compliance needs of many of our customers. | |
| SSO has been one of the most requested features, and CMK was introduced in 2024 which has been validated by large, trusted enterprises. | |
| Security log forwarding, now generally available, has been validated by security auditors and meets the requirements of customer security audits. | |
| Our ongoing compliance efforts are a priority, starting with ISO 27001 certification, and extending to SOC 1 and SOC 2 compliance. | |
| HIPAA compliance has also been recently achieved. |
Too much marketing.
|
|
||
| 100% of AuraDB Virtual Dedicated Cloud customers operate within a Virtual Private Cloud (VPC) isolated architecture with a dedicated infrastructure. | ||
|
|
||
| AuraDB offers fine-grained access control to the database with built-in Role-Based Access Control (RBAC) at the database level, similar to what can be configured in a self-managed Neo4j environment. |
There was a problem hiding this comment.
Is this described anywhere?
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
|
Closing and putting into a word doc - intro to security |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding an intro section to the existing security docs