Rackspace Private Cloud Security White Paper
Rackspace® Private Cloud Security White Paper
Security is a very complex topic for every organization. Challenges can include legislative requirements and internal procedures spanning across both the physical, logical, and virtual layers. Although the uniqueness of customer's needs can be endless, Rackspace Private Cloud is designed with the flexibility to meet these needs.
The key to having a well-secured environment is not just identifying the risks, but ensuring the appropriate controls are in place and that they are being actively monitored. While Rackspace Private Cloud provides the flexibility, Fanatical Support® brings best-practices and experience in managing the infrastructure to help achieve customer's control objectives.
This document will provide an introductory understanding of:
- Security configuration options available within Rackspace Private Cloud
- Security of customer's Rackspace Private Cloud if hosted at Rackspace
- Security of customer's Rackspace Private Cloud if hosted within a customer's datacenter
- Security and Fanatical Support service
- For a Rackspace Private Cloud hosted at Rackspace
- For a Rackspace Private Cloud hosted with a customer's datacenter
Users reading this should have a basic understanding of the following concepts; if not some reference links are provided:
- Familiarity with the components of Rackspace Private Cloud and Rackspace Public Cloud
- Security Industry standards and regulations including: ISO 27001, SSAE16, FISMA, HIPAA
- Difference between Software-, Platform-, and Infrastructure-as-a-service
Please note that Rackspace provides various levels and types of Rackspace Private Cloud Support Services, not all information in this White Paper will apply to all such services. For more detail about which Rackspace Private Cloud Services can meet your needs, please contact a sales associate.
Rackspace Private Cloud Security Configuration Options
OpenStack offers a variety of options on how to secure a cloud.
Within the Rackspace Private Cloud, identities can be authenticated using either internal or external authentication protocols like: LDAP and Active Directory. This allows enterprises to reuse their existing infrastructure.
Rackspace Private Cloud provides preconfigured roles and role assignment. Roles provide fine-grained authorization over specific actions and are assigned to identified users. Customers can define custom roles to meet specific compliance or operational needs, e.g. segregation of duties. These are defined within each of the cloud components.
For example, a 'Cloud Operator' role might be configured to:
- Add a new nova compute guest VM
- Add additional storage to a zone
- View an availability zone but not create one
Host Operating Systems
Rackspace Private Cloud recommends hardening the host Operating Systems. Many current Private Cloud customers currently do this and the Rackspace Private Cloud team will collaborate with customers to recommend a strategy based upon current corporate standards.
Guest/VM Operating Systems
The OpenStack Image Service (based on the Glance project), as implemented in the Rackspace Private Cloud, can be integrated into an Enterprise's existing change management and image release process. This allows the use of an organizations existing, hardened images. Please consult with the Rackspace Private Cloud team for a list of the latest supported base Operating Systems.
A core element of OpenStack is its support for multi-tenancy. Rackspace Private Cloud leverages this by initially installing a configuration that ensures isolation between tenants. Tenant isolation can be used to prevent unrestricted communication between business units or application domains. This best practice safeguards against cross-VLAN communication by restricting ingress traffic based on destination port and source IPs. If desired, configurations are also possible that could allow inter-VLAN communication. Rackspace Private Cloud Architects will work with customers to understand their needs and recommend an appropriate solution.
Similarly, this practice also extends down into the storage platform by leveraging the OpenStack Identity security service.
Rackspace Private Cloud recommends separating management and internal service traffic onto separate networks. Internally, OpenStack internal communications are performed as RESTful API calls that can be secured via SSL/TLS certifications.
Looking forward, OpenStack's security groups are actively advancing Firewall-as-a-Service and other OpenStack networking features enabling multiple levels of software defined network isolation.
Fanatical Support for Private Cloud
Fanatical Support for Private Cloud starts with a team that has expert knowledge in OpenStack, applies that knowledge to a customer's specific platform needs, implements the cloud while complying with a customer's compliance standards, and continues with a Support team monitoring the health of the environment.
Rackspace Hosting's policies and procedures set a high standard that each employee, consultant, and third-party service provider is required to follow. These corporate standards cover key functions like:
- password based access
- password expiration
- automatic workstation locking
- documented change management and escalation procedures
- onboarding training
- VPN-base access
- access that are monitored and independently audited
Rackspace maintains documented operational procedures for both infrastructure operations and customer-facing support functions. Newly provisioned infrastructure undergoes appropriate testing procedures to limit exposure to any hardware failure. Documented procedures and configuration version controls provide protection from errors during configuration. Changes to an existing infrastructure are controlled by a technical change management policy, which enforces best practice change management controls including impact/risk assessment, customer sign off, and back-out planning.
Rackspace Hosting participates in and maintains the following audit reports, certifications, and documentation:
- SSAE 16 / ISAE 3402 (formerly SAS70 Type II) Audit Reports
- Safe Harbor Self-Certification
- ISO 27001 Certification(s)
- PCI Attestation of Compliance & PCI DSS Validated Service Provider
- CDSA Certification
- SOC2 Data Centers in Security & Availability Report
- SOC3 Data Centers in Security & Availability Report
Whether the cloud is hosted at a Rackspace datacenter or at a customer's datacenter, the support team will adhere to both Rackspace's corporate as well as the customer's policies and procedures. The Rackspace team will work with customers to determine the appropriate level of access and proper delineation of responsibilities to support the Private Cloud including identifying any logistical steps needed.
Below is an example of key functions and responsibilities based upon where the Rackspace Private Cloud (RPC) is deployed
Hosted @ Rackspace
Hosted @ Customer DC
Hardware & Data Center
RPC Host OS
Backup (Host OS)
Cloud Capacity Planning
Guest OS Imaging Creation and Patching
Should a Private Cloud be deployed at a customer's datacenter and supported by Rackspace, the Rackspace Support team is willing to work with customers to understand their specific security standards and derive a solution that meets or exceeds those standards.
Rackspace Private Cloud allows 3rd party encryption tools to be used throughout the infrastructure, including SSL/TLS certifications and file/database encryption, giving customers flexibility to reuse their current encryption tools. While no solution is prescribed, Rackspace Implementation teams will work with customers to provide guidance on how to integrate these.
Rackspace Private Cloud is integrated with Rackspace Managed Backup service, giving customers the ability to securely back up Host Machine information.
Operationally, the Rackspace Private Cloud Support Team can actively monitor the cloud environment and proactively reach out to customers when actions are required. Rackspace recommends and most customers wish to provide an approval prior to any changes being made.
For Private Clouds hosted at a Rackspace Data Center, physical security concerns are addressed across the data center and network.
Rackspace Private Cloud is available inRackspacedatacenters globally. Rackspace data centers physical security capabilities include:
- Two-factor authentication required to access all data center facilities.
- Electromechanical locks controlled by biometric authentication (hand geometry or fingerprint scanner) and key-card/badge.
- Access to secure sub-areas allocation on a role-specific basis
- Authorized Rackspace personnel's access to the facilities is reviewed on a monthly basis by management
- Termination and role-change control procedures are in place so that any physical or logical access rights are removed in a timely manner when access is no longer necessary or appropriate
- Closed circuit video surveillance is installed at all entrance points on the interior and exterior of the buildings that house data centers. Cameras are monitored 24x7x365 by on-site security personnel and support data retention for 90 days.
- Sensitive equipment such as information processing facilities, including customer servers, is housed in secure sub-areas within each data center's secure perimeter and is subject to additional controls
- Centralized Security Management Systems are deployed at all data centers to control the Electronic Access Control Systems and closed circuit television networks.
Rackspace data centers are operational 24x7x365 and are manned around-the-clock by a security team and engineering/operations personnel. Appropriate additional perimeter defense measures, such as walls, fencing, gates and anti-vehicle controls are in place at Rackspace data centers. The delivery and loading bays at all Rackspace data centers are separate areas secured by defined procedures and security controls.
Unauthorized visitors are not permitted access to the data centers. Authorized data center visitors are required to abide by the following rules:
- Authorized approvers must specifically grant visitor access to the data centers at least 24 hours before the scheduled visit
- Visitors must have a valid reasons for entering the data center
- Visitors must sign the visitor's log, present a valid photo ID, and specify the reason for visiting and a Rackspace point of contact
- Visitor badges differ in appearance from Rackspace employee badges and do not provide any control over doors, locks, etc.
- All visitor access is logged. This policy applies equally to Rackspace employees not assigned to the data center.
- Visitors, including Rackspace customers, are strictly forbidden from accessing the data halls themselves and other secure sub areas.
- Visitors must be escorted at all times while at any Rackspace Facility.
- Data center management performs a monthly audit of security and visitor access logs
Whether deployed at Rackspace or within a customer's data center, network security is as equally important as physical security and encryption. Open Stack Neutron Network component is a software defined networks that provides enhanced flexibility on how to manage your virtual network. Security over these networks can be applied in a variety of ways. Rackspace Private Cloud Architects and Support team will work with customers to help identify and develop an appropriate solution to meet their current and future needs.
Network Security within a Rackspace Datacenter
All Rackspace network infrastructure devices are located in a physically secure data center with controlled access. All visitors or authorized contractors are logged and escorted. Local console access to network devices is restricted to authorized individuals and requires access to the physical location as well as the correct username and password for console login. While Rackspace utilizes a wireless infrastructure for corporate connectivity, wireless access points are not permitted in the data halls where the cloud infrastructure resides and regular scans are performed to identify and neutralize rogue access points.
Administrative access to the networking devices underlying the cloud infrastructure is controlled via industry standard practices (TACACS+) and is subject to appropriate logging and monitoring, records of which are retained for one year. Logical access to cloud infrastructure network devices is only provided to those Rackspace employees with a business requirement for such access, and is subject to permissions change control including independent managerial authorization and timely revocation of access rights. SSL is used to encrypt administrative sessions.
Implementing new cloud environments is performed according to standardized procedures in order to minimize the risk of accidental insecure network provisioning.
Rackspace maintains strict policies on the use of network services. The network services underlying our cloud infrastructure are subject to DDoS/DoS mitigation and network policy enforcement controls, ensuring the best possible quality of connection to the customer's cloud environment and maximizing the stability of the environment. These include anti-spoofing controls and IP prefix-lists, as well as Unicast Reverse Path Forwarding (URPF) protocols in place at edge routers in data centers hosting cloud environments.
Recommended Customer Controls
When hosted at Rackspace, Rackspace infrastructure controls are designed to protect cloud resources from attack within the environment, appropriately control and provide assurance over Rackspace access to customer cloud resources. The customer should seek to protect their cloud resources and hosted data with measures overlaying Rackspace infrastructure controls as appropriate to their data's sensitivity and criticality as informed by a formal risk assessment.
Customers are the primary owner of their data and maintain sole visibility over its specific security requirements. Accordingly, customers are responsible for classifying their data and applying appropriate risk mitigation controls. Customer's sensitive data should be encrypted for storage in order to preserve confidentiality. Rackspace recommends that data being transmitted to and from the cloud should be subject to encryption appropriate to its requirements, for example the use of TLS or a secure VPN.
Rackspace Private Cloud customers can interact with the environment at an administrative level via API. Aion is required in order to use them. Customer applications that interface with APIs should undergo adequate security testing and maintain best practice application security controls including communication with our SSL protected API endpoints via HTTPS. Customers should consider tightly restricting access to API keys and account credentials to those employees with a legitimate business requirement, as well as segregating duties to maintain accountability.
As primary system administrator of the cloud resources, the customer is responsible for managing user accounts creation, provisioning and destruction, password policies, server level account authentication mechanisms, etc. Rackspace recommends that customers integrate their Private Cloud with their organizational Single-sign on (SSO) domain if available in order to simplify this task.
Copyright © 2013 Rackspace US, Inc.
This Rackspace® Private Cloud Security White Paper is for informational purposes only and is provided “AS IS.” The information set forth in this White Paper is intended as a guide and not as a step-by-step process, and does not represent an assessment of any specific compliance with laws or regulations or constitute advice. We strongly recommend that you engage additional expertise in order to further evaluate applicable requirements for your specific environment.
RACKSPACE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS DOCUMENT AND RESERVES THE RIGHT TO MAKE CHANGES TO SPECIFICATIONS AND PRODUCT/SERVICES DESCRIPTION AT ANY TIME WITHOUT NOTICE. RACKSPACE RESERVES THE RIGHT TO DISCONTINUE OR MAKE CHANGES TO ITS SERVICES OFFERINGS AT ANY TIME WITHOUT NOTICE. USERS MUST TAKE FULL RESPONSIBILITY FOR APPLICATION OF ANY SERVICES AND/OR PROCESSES MENTIONED HEREIN. EXCEPT AS SET FORTH IN RACKSPACE GENERAL TERMS AND CONDITIONS, CLOUD TERMS OF SERVICE AND/OR OTHER AGREEMENT YOU SIGN WITH RACKSPACE, RACKSPACE ASSUMES NO LIABILITY WHATSOEVER, AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO ITS SERVICES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
ALTHOUGH PART OF THE WHITE PAPER EXPLAINS HOW RACKSPACE SERVICES MAY WORK WITH THIRD PARTY PRODUCTS, THE INFORMATION CONTAINED IN THE WHITE PAPER IS NOT DESIGNED TO WORK WITH ALL SCENARIOS. ANY USE OR CHANGES TO THIRD PARTY PRODUCTS AND/OR CONFIGURATIONS SHOULD BE MADE AT THE DISCRETION OF YOUR ADMINISTRATORS AND SUBJECT TO THE APPLICABLE TERMS AND CONDITIONS OF SUCH THIRD PARTY. RACKSPACE DOES NOT PROVIDE TECHNICAL SUPPORT FOR THIRD PARTY PRODUCTS, OTHER THAN SPECIFIED IN YOUR HOSTING SERVICES OR OTHER AGREEMENT YOU HAVE WITH RACKSPACE AND RACKSPACE ACCEPTS NO RESPONSIBILITY FOR THIRD-PARTY PRODUCTS.
Except as expressly provided in any written license agreement from Rackspace, the furnishing of this document does not give you any license to patents, trademarks, copyrights, or other intellectual property.
Rackspace, Rackspace logo and, Fanatical Support and any other Rackspace product/service names used in this document are either registered service marks or service marks of Rackspace US, Inc. in the United States and other countries. OpenStack is either a registered trademark or trademark of OpenStack Foundation in the United States and/or other states.
Third-party trademarks and tradenames appearing in this document are the property of their respective owners. Such third-party trademarks have been printed in caps or initial caps and are used for referential purposes only. We do not intend our use or display of other companies' tradenames, trademarks, or service marks to imply a relationship with, or endorsement or sponsorship of us by, these other companies.
© 2015 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER