Guide to the Secure Configuration of Red Hat OpenStack Platform 10
https://www.open-scap.org/security-policies/scap-security-guide
scap-security-guide
package which is developed at
https://www.open-scap.org/security-policies/scap-security-guide.
Providing system administrators with such guidance informs them how to securely configure systems under their control in a variety of network roles. Policy makers and baseline creators can use this catalog of settings, with its associated references to higher-level security control catalogs, in order to assist them in security baseline creation. This guide is a catalog, not a checklist, and satisfaction of every item is not likely to be possible or sensible in many operational scenarios. However, the XCCDF format enables granular selection and adjustment of settings, and their association with OVAL and OCIL content provides an automated checking capability. Transformations of this document, and its associated automated checking content, are capable of providing baselines that meet a diverse set of policy objectives. Some example XCCDF Profiles, which are selections of items that form checklists and can be used as baselines, are available with this guide. They can be processed, in an automated fashion, with tools that support the Security Content Automation Protocol (SCAP). The NIST National Checklist Program (NCP), which provides required settings for the United States Government, is one example of a baseline created from this guidance.
Profile Information
Profile ID | (default) |
---|
CPE Platforms
- cpe:/a:redhat:openstack:10
Revision History
Current version: 0.1.51
- draft (as of 2020-07-20)
Table of Contents
- Remediation functions used by the SCAP Security Guide Project
- OpenStack
- Nova STIG Checklist
- Neutron STIG Checklist
- Cinder STIG Checklist
- Horizon STIG Checklist
- Keystone STIG Checklist
- Introduction
Checklist
Group Guide to the Secure Configuration of Red Hat OpenStack Platform 10 | |
Group Remediation functions used by the SCAP Security Guide Project | |
[ref] XCCDF form of the various remediation functions as used by remediation scripts from the SCAP Security Guide Project. | |
Group OpenStack | |
[ref] TODO TODO TODO | |
Group Nova STIG Checklist | |
[ref] High level overview of Nova STIG settings to go here! | |
Group Neutron STIG Checklist | |
[ref] High level overview of Neutron STIG settings to go here! | |
Group Cinder STIG Checklist | |
[ref] High level overview of Cinder STIG settings to go here! | |
Group Horizon STIG Checklist | |
[ref] High level overview of Horizon STIG settings to go here! | |
Group Keystone STIG Checklist | |
[ref] High level overview of Keystone STIG settings to go here! | |
Group Introduction | |
[ref] The purpose of this guidance is to provide security configuration recommendations and baselines for Red Hat OpenStack Platform 10. The guide is intended for system and/or application administrators. Readers are assumed to possess basic system administration skills for the application's operating systems, as well as some familiarity with the product's documentation and administration conventions. Some instructions within this guide are complex. All directions should be followed completely and with understanding of their effects in order to avoid serious adverse effects on the system and its security. | |
Group How to Use This Guide | |
[ref] Readers should heed the following points when using the guide. | |
Group Test in Non-Production Environment | |
[ref] This guidance should always be tested in a non-production environment before deployment. This test environment should simulate the setup in which the system will be deployed as closely as possible. | |
Group Formatting Conventions | |
[ref]
Commands intended for shell execution, as well as configuration file text,
are featured in a | |
Group Read Sections Completely and in Order | |
[ref] Each section may build on information and recommendations discussed in prior sections. Each section should be read and understood completely; instructions should never be blindly applied. Relevant discussion may occur after instructions for an action. | |
Group Reboot Required | |
[ref] A system or service reboot is implicitly required after some actions in order to complete the reconfiguration of the system. In many cases, the changes will not take effect until a reboot is performed. In order to ensure that changes are applied properly and to test functionality, always reboot the system after applying a set of recommendations from this guide. | |
Group Root Shell Environment Assumed | |
[ref]
Most of the actions listed in this document are written with the
assumption that they will be executed by the root user running the
| |
Group General Principles | |
[ref] The following general principles motivate much of the advice in this guide and should also influence any configuration decisions that are not explicitly covered. | |
Group Run Different Network Services on Separate Systems | |
[ref] Whenever possible, a server should be dedicated to serving exactly one network service. This limits the number of other services that can be compromised in the event that an attacker is able to successfully exploit a software flaw in one network service. | |
Group Encrypt Transmitted Data Whenever Possible | |
[ref] Data transmitted over a network, whether wired or wireless, is susceptible to passive monitoring. Whenever practical solutions for encrypting such data exist, they should be applied. Even if data is expected to be transmitted only over a local network, it should still be encrypted. Encrypting authentication data, such as passwords, is particularly important. Networks of Red Hat OpenStack Platform 10 machines can and should be configured so that no unencrypted authentication data is ever transmitted between machines. | |
Group Least Privilege | |
[ref]
Grant the least privilege necessary for user accounts and software to perform tasks.
For example, | |
Group Configure Security Tools to Improve System Robustness | |
[ref] Several tools exist which can be effectively used to improve a system's resistance to and detection of unknown attacks. These tools can improve robustness against attack at the cost of relatively little configuration effort. |