Volerro Policies

Volerro Security Policy Document

Volerro's information security policy is centered on protecting the confidentiality, integrity, and availability of customer’s data collected through the Volerro service and through the Volerro Application Programmer’s Interface (API). To achieve this goal this policy is implemented using industry leading providers and security best practices.

Volerro hosts its service using Amazon Web Services (AWS). The following is an overview of the security dimensions provided by AWS:

  1. Certifications and Accreditations. AWS has in the past successfully completed multiple SAS70 Type II audits, and as of September 30, 2011 publishes a Service Organization Controls 1 (SOC 1) report, published under both the SSAE 16 and the ISAE 3402 professional standards. In addition, AWS has achieved ISO 27001 certification, has been successfully validated as a Level 1 service provider under the Payment Card Industry (PCI) Data Security Standard (DSS), and has completed the control implementation and independent security testing required to operate at the FISMA-Moderate level. We will continue to obtain the appropriate security certifications and conduct audits to demonstrate the security of our infrastructure and services. For more information on risk and compliance activities in the AWS cloud, consult the Amazon Web Services: Risk and Compliance whitepaper.
  2. Physical Security. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. AWS infrastructure is housed in Amazon-controlled data centers throughout the world. Only those within Amazon who have a legitimate business need to have such information know the actual location of these data centers, and the data centers themselves are secured with a variety of physical controls to prevent unauthorized access.
  3. Secure Services. Each of the services within the AWS cloud is architected to be secure and contains a number of capabilities that restrict unauthorized access or usage without sacrificing the flexibility that customers demand. For more information about the security capabilities of each service in the AWS cloud, consult the Amazon Web Services: Overview of Security Processes whitepaper.
  4. Data Privacy. AWS enables users to encrypt their personal or business data within the AWS cloud and publishes backup and redundancy procedures for services so that customers can gain greater understanding of how their data flows throughout AWS. For more information on the data privacy and backup procedures for each service in the AWS cloud, consult the Amazon Web Services: Overview of Security Processes whitepaper referenced above.

Volerro Security with AWS

Volerro extends the secure service provided by AWS by:

Securing Access to our Development Environment

Volerro’s development environment is remotely accessed using the most secure processes currently available in the marketplace. Only our development and systems management employees have access to our environment.

We control our staffs access using:

  1. Hardware Enabled Multi-Factor Authentication: AWS MFA uses an authentication device that continually generates random, six-digit, single-use authentication codes. With AWS MFA enabled, when a user signs in to an AWS website, they will be prompted for their username and password (the first factor – what they know), as well as for an authentication code from their AWS MFA device (the second factor – what they have). All AWS websites that require sign in, such as the AWS Management Console, are integrated with AWS MFA. Volerro uses hardware based MFA for all access to our environment.
  2. Access Credential Rotation: Our developers rotate their access credentials and keys on a schedule to provide additional security. Credential rotation is done for each individual employee on a varying calendar schedule.

Securing Access to Our Application During Customer Transmission

Customer access to the volerro site is encrypted. Our service is only accessible via port 443 using an HTTPS connection. Clear HTTP is not allowed. Our customer connections are secured by ensuring that:

  1. Connection to the Volerro service is via SSL 3.0/TLS 1.0, using global step-up certificates from Geotrust, ensuring that our users have a secure connection from their browsers to our service
  2. Individual user sessions are identified and re-verified with each transaction, using a unique token created at login

Securing Customer Data Storage

Customer passwords are protected from compromise.

  1. Customer passwords are never transmitted via un-secured protocols. Web-based forms that ask for passwords are protected using SSL/TLS.
  2. Passwords stored in a database or file are rendered unreadable using a cryptographically strong salted hash algorithm.
  3. Administrators never ask a user for their password via email or over the phone.
  4. All external applications that interact with the API use a token based authentication protocol such as OAuth.

Customer Data is Secured Along Multiple Dimensions

  1. Redundancy and Replication: Volerro uses Amazon Elastic Block Storage (EBS) volumes to store customer transactional data. Volerro uses Amazon S3 storage for point in time back up of customer data and to store files for Volerro’s file sharing application. Each EBS storage volume is automatically replicated to prevent data loss due to failure of any single hardware component.
  2. Backup and Fail Over: Our EBS storage volumes enable point in time snapshots to be persisted to our S3 long term storage. Volerro uses these point in time snapshots throughout the day to backup our data system-wide. Our application data is separated from customer transactional data using independent EBS Storage volumes. Volerro runs identical database instances in multiple Amazon regions and replicates across these regions using a high speed, encrypted link. If one region is affected, our production environment fails over to our secondary region.
  3. No Direct Access to Data Stores: Volerro’s S3 and EBS data stores may only be accessed through our production instances programmatically. There are no internal or external addressing mechanisms to access these storage blocks. Data is moved into and out of these stores exclusively through our application. For this reason, our file sharing application provides no url/uri to a file. Shared files reside in a separate S3 “bucket” (an independent storage unit) and pass through our application while being downloaded or uploaded. Our database servers are configured by amazon’s virtual machines instances to use internal, unpublished connections to our application servers.

Testing and Monitoring our Systems using AWS and Third Party Tools

In addition to the monitoring and penetration testing provided by Amazon Web Services (AWS), Volerro employs third party services to monitor out system performance and perform regular security testing.

We use Core CloudInspect to perform regular system-wide security tests. Our testing procedures:

  1. Proactively verify the security of Volerro’s AWS deployments against real, current attack techniques
  2. Safely pinpoint and validate critical OS and services vulnerabilities with no false positives
  3. Measure our susceptibility to SQL injection, cross-site scripting, and other web application attacks
  4. Validate security controls required by PCI, HIPAA and other compliance mandates
  5. Certify our systems before they go live and frequently test to reconfirm security posture over time