Security architecture

Nexo introduces a policy enforcement point between database clients and MongoDB. That position creates two connection legs and several trust boundaries that must be configured deliberately.

Trust boundaries

• Client to Nexo data plane.
• Nexo data plane to MongoDB.
• Operator to Nexo management interfaces.
• Control plane to deployed runtime.
• Runtime to configured secret sources and telemetry destinations.

Security goals

• Authenticate administrative users and deployed environments.
• Protect data in transit according to the configured TLS mode.
• Keep credentials out of source, logs, and pipeline definitions.
• Limit database and platform privileges.
• Make configuration changes attributable and reviewable.
• Fail visibly when required security configuration cannot be applied.

Nexo does not automatically make an application compliant with a regulation or standard. Security outcomes depend on product configuration, customer infrastructure, application behavior, and operating procedures.