Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

security overview #489

Closed
wants to merge 4 commits into from
Closed

security overview #489

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
03b2e7a
security architecture
fiquick Oct 11, 2024
e25cabe
edits
fiquick Oct 11, 2024
0527abe
Update modules/ROOT/pages/platform/security/secure-connections.adoc
fiquick Oct 17, 2024
548d069
Update modules/ROOT/pages/platform/security/secure-connections.adoc
fiquick Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 23 additions & 4 deletions modules/ROOT/pages/platform/security/secure-connections.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,36 @@
[[aura-reference-security]]
= Secure connections
:description: VPC boundaries enable you to operate within an isolated section of the service.
:description: Secure, isolated infrastructure with fine-grained access control, encryption, compliance, and key security features like SSO and Customer Managed Encryption keys.

label:AuraDB-Virtual-Dedicated-Cloud[]
label:AuraDS-Enterprise[]

== Introduction to the security architecture

AuraDB Virtual Dedicated Cloud users 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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this described anywhere?

All traffic passing through the Aura console, your VPC, and the VPC provisioned by Neo4j is encrypted both at rest.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both at rest and? In transit?

By operating within your own VPC, you are protected from external traffic.


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.
Comment on lines +17 to +22
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


== VPC isolation

label:AuraDB-Virtual-Dedicated-Cloud[]
label:AuraDS-Enterprise[]

VPC boundaries enable you to operate within an isolated section of the service.
AuraDB Virtual Dedicated Cloud and AuraDS Enterprise run in a dedicated cloud Account (AWS), Subscription (Azure) or Project (GCP) to achieve complete isolation for your deployment.

Additional VPC boundaries enable you to operate within an isolated section of the service, where your processing, networking, and storage are further protected.

The Aura Console runs in a separate VPC, separate from the rest of Aura.
Additional VPC boundaries enable you to operate within an isolated section of the service, where your processing, networking, and storage are further protected.
The Aura console runs in a separate VPC, separate from the rest of Aura.

== Network access

Expand Down