Guide to the Secure Configuration of JBoss EAP 6
with profile STIG for JBoss Enterprise Application Platform 6This is a *draft* profile for STIG. This profile is being developed under the DoD consensus model to become a STIG in coordination with DISA FSO.
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 DISA STIG for JBoss EAP 6, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
Profile Title | STIG for JBoss Enterprise Application Platform 6 |
---|---|
Profile ID | xccdf_org.ssgproject.content_profile_stig-eap6-upstream |
Revision History
Current version: 0.1.34
- draft (as of 2017-07-03)
Platforms
- cpe:/a:redhat:jboss_enterprise_application_platform:6.0.0
Table of Contents
Checklist
contains 1 rule |
Auditing [ref]groupAuditing rules |
contains 1 rule |
JBoss servers must be configured to roll over and transfer logs on a minimum weekly basis. [ref]ruleInformation stored in one location is vulnerable to accidental or incidental deletion or alteration. Protecting log data is important during a forensic investigation to ensure investigators can track and understand what may have occurred. Off-loading should be set up as a scheduled task but can be configured to be run manually, if other processes during the off-loading are manual. Off-loading is a common process in information systems with limited log storage capacity. Rationale:Logs preservation and size limits can be implicitly incurred via periodic log rolling Severity: medium Identifiers: CCE- |