Security Assurance
Security is a priority for all modern cloud applications, and as such, DataStax has implemented several protocols to ensure security remains a priority.
DataStax Software Development Security Program
The DataStax Software Development Security Program (DSDSP) is DataStax's methodology to build security into our products. As part of our on-boarding process, all newly-hired software engineers are required to take online secure coding training from SAFECode.
Read More About SAFECodeModules taken depend on the product area in which the developer works:
Secure Coding Standards
DataStax has a software development policy that requires code reviews on all code before it is checked into our code repository. This policy includes a review for security-related issues.
Expert/External Review
DataStax has retained external security experts to code review our security features. Based on their analysis, we made improvements and added features such as support for off-server key storage. External validation is an ongoing process that we use to double-check our own efforts.
Code Scanning and Vulnerability Monitoring
The DataStax Test Engineering team routinely scans our software with the SRC:CLR product to itemize the content of our software and match publicly known vulnerabilities to code. In addition to scanning our codebase, DataStax monitors the National Vulnerability Database and US-CERT activity. The results of code scans and NVD and US-CERT monitoring are fed back into the development team for review and, if applicable, patches are created. The Vulnerability Reporting tab contains a list of recently identified issues and their disposition.
Best Practices
DataStax Enterprise provides standard security and advanced features, which allow you to build security in your application stack. Relevant features include:
Corporate Security
DataStax Enterprise (DataStax Enterprise server, DataStax OpsCenter, DataStax DevCenter, DataStax Developer Studio, and the DataStax Drivers) is provided to customers as a software bundle to be self-deployed by customers on their choice of hardware or cloud platform. As such, DataStax and its employees do not have direct access to the data a customer has stored in DataStax Enterprise or to any production customer systems.
In the course of offering support and services, it may be necessary for DataStax employees to have limited access or visibility to customer production systems or technical log files. Access to this information is at the sole discretion and invitation of the customer.
Physical Data Center Security
DataStax maintains small engineering data centers co-located with developers for use in product development and testing. No customer data is stored in any system running in these datacenters. The data centers are secured by a physical key, electronic access key or both. Electronic access is logged and monitored. A video camera records motion and access to the DataStax datacenter located at DataStax headquarters. An alarm system is installed at all on-premises datacenters and DataStax headquarters.
Physical Headquarters Security
DataStax headquarters is protected by a security station with security personnel at the front desk lobby. Key fob security badges are required for building access and elevator floor access during non-business hours at DataStax headquarters. Key fob security badges are surrendered and deactivated upon employee termination.
System Security
DataStax enforces the rule of least privilege for IT systems. Access to designated systems is limited to personnel for whom access is required based on job function. Data on DataStax customers is restricted to individuals who require system access to perform job functions. Access lists for key corporate systems are audited quarterly. Access to all systems is deleted or suspended upon termination of employment. Only secure transfer protocols (SFTP, SSH etc.) are used to transfer data from one system endpoint to another.
Employee Background Checks
DataStax conducts criminal background checks on all of its employees prior to commencement of employment.
Laptop and Mobile Device Security
Employee computers are password protected and the default configuration for such devices causes the devices to be automatically locked after 10 minutes of inactivity. All employee computers are installed with anti-virus software. Employees are provided with a tool to backup/sync company data to either a physical local location or to cloud storage. Each employee receives a laptop computer with an assigned unique company asset tag for identification. DataStax employees are required to contact IT in an event of laptop theft or loss.
Breach Notifications
DataStax will notify customers of any security breach which involved their data as soon as practicable, but no later than twenty-four hours after DataStax becomes aware of it. This applies to information stored in its own systems as well as the systems of its vendors.
Information Systems
DataStax uses several cloud-based technology vendors to support company operations. These vendors have separate security policies that govern the protection of DataStax data in their possession. Relevant vendors and their security policies are listed below.
DataStax uses Google Apps for Business for internal messaging and document handling. Google provides security and privacy for its services as outlined in their Security and Privacy documentation. In addition, DataStax implements Google services following best practices such as:
DataStax uses Workday for HR and Finance needs. Workday security documentation can be found on their security page.
DataStax uses the Salesforce.com CRM system. Salesforce security documentation can be found on their security page.
DataStax uses Pantheon for web hosting. Pantheon security documentation can be found on their security page.
DataStax uses Inversoft for website identity management. Inversoft privacy documentation can be found on their privacy page.
Engineering Systems
All systems in the datacenter operate behind a firewall. The firewall and switch firmware/operating systems are upgraded to the latest version every six (6) months to apply the latest security patches. Emergency upgrades are done in an event that a critical patch is released. HTTPS and SSH are the only protocols available to access the firewall. DataStax on-premises systems are accessible via an industry-recognized VPN client.
DataStax uses hosted Atlassian JIRA for tracking defects and enhancements. Atlassian security policies can be found here Atlassian Security and here Privacy Policy.
DataStax uses Zendesk for tracking customer support tickets. Zendesk security documentation can be found on their security page and in this privacy statement.
DataStax uses Github for source code control. Github security documentation can be found on their security page.
DataStax uses Rackspace for server hosting. Rackspace security documentation can be found on their security page.
DataStax uses Amazon AWS for server hosting. AWS security documentation can be found on their security page.
DataStax uses Microsoft Azure for server hosting. AWS security documentation can be found on their security page.
Vulnerability Handling
An important strategy DataStax uses in building secure applications and secure web experiences is to respond to vulnerability reports. The information you submit is taken very seriously and appreciated at the highest levels.
You can submit your findings using the link below.
Reporting a Vulnerability
DataStax Enterprise incorporates code from several Apache Software Foundation (ASF) projects, such as Apache Cassandra™, Apache Spark, and Apache Solr. Vulnerabilities affecting ASF software products should also be reported directly to the project. Details on reporting those vulnerabilities to the ASF can be found here.
DataStax follows a vulnerability handling process similar to that of the Apache Foundation.
- The reporter reports the vulnerability privately to DataStax.
- The appropriate project's security team works privately with the reporter to resolve the vulnerability.
- A new release or patch of the DataStax product that includes the fix is produced.
- The vulnerability is publicly announced and the patched software made available.
Security Notices
