Shared Responsibility

SingleStore Helios has built in security controls that make it a secure environment to run customer workloads. However the responsibility of keeping it secure is shared between the user and SingleStore. SingleStore Helios is designed with strong security by default so that there is minimal overhead on the user. The default configuration includes encryption at rest, encryption in transit, removal of public access, and deployment within strong network boundaries. Users are responsible for configuring the necessary levels of control which is based on the security posture of their organization.

Shared Responsibility Model

The following table outlines the responsibilities of the customer and SingleStore for a SingleStore Helios deployment in Managed regions:

Cloud Infrastructure Physical Security

Customer

  • Select the cloud provider and the region of choice.

SingleStore

  • Provision the requested clusters in a private network.

  • Provision all additional configurations described by users.

  • Secure the infrastructure and networks using best practices.

Customer Data, Accounts, and Identities

Customer

  • Create and manage customer data.

  • Add user accounts and access using identities.

SingleStore

  • Provide secure access and storage to customer data.

  • Provide secure connectivity to the platform to ensure confidentiality, integrity, and authentication for customer data in motion.

Network Isolation and Connectivity

Customer

  • Configure the network connectivity, including Firewall, DNS, Private Networking, and IP allowlisting between the user and SingleStore account.

SingleStore

  • Enforce network security restrictions as per configurations made by the customer.

  • Provision resource for private networking.

SingleStore Database Access

Customer

  • Configure user authentication.

  • Add roles and privileges for users.

  • Manage certifications and JWKS setups for clusters.

  • Manage IAM roles on cloud resources to be used by SingleStore Helios.

SingleStore

  • Provide Role-Based Access Control (RBAC) as part of the platform.

  • Provide integration with MFA and other SSO tools.

  • Provide secure identity management capabilities and access to user accounts on the platform.

  • Support secure token-based authentication/authorization.

API Controls/Access

Customer

  • Manage and configure API keys.

SingleStore

  • Generate API keys.

  • Implement API access.

Data Encryption (in Transit and at Rest)

Customer-Managed Encryption Keys (CMEK) is only supported on Managed regions.

Customer

  • Set the TLS version to be used.

  • For CMEK: Configure cloud provider KMS and key policy according to the customer’s own requirements, and then manually configure CMEK on SingleStore Helios.

SingleStore

  • Enable default encryption of data at rest and in motion with cloud provider managed keys.

  • Connect to the KMS and use keys for encryption at rest.

  • For CMEK: Connect to the customer-specified KMS and use keys for encryption of data at rest.

Granular Auditing

Customer

  • Configure audit levels and audit log destinations.

SingleStore

  • Stream audit logs to external resources based on user configuration.

  • Enable audit logging for the database automatically.

  • Monitor the platform's audit logs.

Performance Monitoring/Alerting

Customer

  • Configure real-time alerts and performance thresholds.

  • Configure external tools for monitoring and alerting.

  • Access to metrics and logs via Grafana dashboards.

SingleStore

  • Configure performance analysis and monitoring capabilities.

  • Monitor the platform’s performance logs and alerts.

Security Patches and Maintenance

Customer

  • Ensure that the client software used to interact with the platform is up-to-date and patched.

SingleStore

  • Automatically apply security patches and updates.

  • Run internal vulnerability and patch management processes.

High Availability and Disaster Recovery

Customer

  • Can create and manage own custom backups in accordance with internal backup and disaster recovery policy.

  • Configure backup and recovery capabilities and provisions supported by the platform.

SingleStore

  • SingleStore stores data in durable object storage for recovery in case of unexpected disaster.

  • SingleStore provides self-serve recovery steps (based on the purchased edition).

  • Implement automated failover and replication mechanisms.

Application Security

Customer

  • Validate and check user-defined functions (UDFs) and code written to interface with external functions for security issues.

  • Validate the security of third-party services to leverage on SingleStore Helios computing capabilities or through integrations.

  • Secure system access for users both inside and outside the customer's environment.

SingleStore

  • Provide a secure operating and computing environment.

  • Run incident detection and response mechanisms internally.

  • Manage network egress and ingress at the network layer and control access to data.

  • Validate the security of the software supply chain used by CI/CD procedures and tools.

Secrets

Customer

  • Ensure proper access control to secrets configured within the platform.

  • Manage the lifecycle of secrets as well as their end-to-end distribution.

SingleStore

  • Securely store and encrypt customer secrets.

Compliance

Customer

  • Configure the environment(s) to meet the requirements for the customer’s own compliance and regulatory needs.

  • If the customer needs to store and manage PHI data on SingleStore Helios, a BAA must be set up with SingleStore.

SingleStore

  • Maintain compliance and uphold Information Security and Data Protection standards and requirements that apply to our product and business (namely ISO27001 and SOC 2 Type II).

  • Support compliance inheritance of HIPAA.

AI Usage

Customer

  • Ensure secure deployment of Generative AI applications and the responsible use of data leveraged in AI-powered features provided by SingleStore.

  • Implement human oversight in AI-enabled business workflows.

  • Where selection of underlying AI models is required, it is the customer's responsibility to make and validate the choice.

SingleStore

  • Provide a secure platform for enabling Generative AI applications that seamlessly integrate with SingleStore.

  • Ensure compliance with data protection and regulatory standards, with continuous monitoring and adaptation as AI-related regulations evolve.

  • Evaluate Generative AI technology to assess bias, security vulnerabilities, accuracy, and safety.

Responsibility Matrix

The following can be used as a quick reference to the shared responsibilities of the customer and SingleStore.

Cloud Management

Action

SingleStore

Customer

VPC

EC2 instance management

Kubernetes management

S3 buckets management

SingleStore provisioning

Upgrades and Security

Action

SingleStore

Customer

SingleStore upgrades

Software vulnerability remediation

Infrastructure vulnerability remediation

Scaling

Networking

Action

SingleStore

Customer

External Routing

K8 internal Routing

Firewall

DNS

Load Balancer

Access Control

Action

SingleStore

Customer

IAM role, service accounts

Access control and auditing

Availability

Action

SingleStore

Customer

DR

Availability (SLA)

Support

Action

SingleStore

Customer

Logging

Audit logging

Monitoring

Break glass

Last modified:

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.