Welcome to the SIMP documentation!¶
This is the documentation for the 6.2.0-RC1 release of SIMP, which is compatible with CentOS and Red Hat Enterprise Linux (RHEL). This guide will walk a user through the process of installing and managing a SIMP system. It also provides a mapping of security features to security requirements, which can be used to document a system’s security conformance.
The System Integrity Management Platform (SIMP) is an Open Source framework designed around the concept that individuals and organizations should not need to repeat the work of automating the basic components of their operating system infrastructure.
By using the Puppet automation stack, SIMP is working toward the concept of a self-healing infrastructure that, when used with a consistent configuration management process, will allow users to have confidence that their systems not only start in compliance but remain in compliance over time.
Finally, SIMP has a goal of remaining flexible enough to properly maintain your operational infrastructure. To this end, where possible, the SIMP components are written to allow all security-related capabilities to be easily adjusted to meet the needs of individual applications.
Level of Knowledge¶
SIMP is designed for use by system administrators or users with a strong background using Linux operating systems. The core applications that make up SIMP and require prerequisite knowledge are:
- Puppet - 4.0 or later
- Domain Name System (DNS) - BIND 9
- Dynamic Host Configuration Protocol (DHCP) - Internet Systems Consortium (ISC) DHCP
- Lightweight Directory Access Protocol (LDAP) - OpenLDAP
- RedHat Kickstart (including all tools behind it) - Trivial File Transfer Protocol (TFTP), PXELinux, etc.
- Yellowdog Updater, Modified (YUM)
- Rsyslog Version 3+
- Internet Protocol Tables (IPtables) (Basic knowledge of the rules)
- Auditd (Basic knowledge of how the daemon works)
- Advanced Intrusion Detection Environment (AIDE) (Basic knowledge of the rules)
- Basic X.509-based PKI Key Management
SIMP does as much initial setup and configuration of these tools as possible. However, without at least some understanding, you will be unable to tailor a SIMP system to fit the desired environment. A general understanding of how to control and manipulate these tools from the command line interface (CLI) will be necessary, as SIMP does not come stock with a graphical user interface (GUI).
Knowledge of scripting and Ruby programming will also help to further customize a SIMP install but is not required for routine use.
- 1. For the Impatient
- 2. Changelog
- 3. Getting Started
- 3.1. Introduction
- 3.2. Known OS Compatibility
- 3.3. Installing SIMP From An ISO
- 3.4. SIMP on Amazon Web Services
- 3.5. Installing SIMP From A Repository
- 3.6. Preparing For Non-RPM Install
- 3.7. Installing SIMP Using r10k or Code Manager
- 3.8. Building a SIMP ISO
- 3.9. Installing SIMP from an ISO
- 3.10. Initial Configuration
- 4. User Guide
- 5. Contributing to SIMP
- 6. Security Concept of Operations
- 7. Security Control Mapping
- 8. Vulnerability Supplement
- 9. Help
- 10. License
- 11. Contact
- 12. Glossary of Terms