JBoss Enterprise Application Platform 6.3 STIG Version Comparison

There are 18 differences between versions v2 r3 (Jan. 27, 2022) (the "left" version) and v2 r5 (Oct. 24, 2024) (the "right" version).

Check JBOS-AS-000035 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

The JBoss server must be configured with Role Based Access Controls.

Check Content

Log on to the OS of the JBoss server with OS permissions that allow access to JBoss. Using the relevant OS commands and syntax, cd to the <JBOSS_HOME>/bin/ folder. Run the jboss-cli script. Connect to the server and authenticate. Run the following command: For standalone servers: "ls /core-service=management/access=authorization/" For managed domain installations: "ls installations, target the domain-management resource (the core management service for the entire domain): "ls /host=master/core-service=management/access=authorization/" If /core-service=management/access=authorization/" If the "provider" attribute is not set to "rbac", this is a finding. finding. (Default, the access control is "provider=simple")

Discussion

By default, the JBoss server is not configured to utilize role based access controls (RBAC). RBAC provides the capability to restrict user access to their designated management role, thereby limiting access to only the JBoss functionality that they are supposed to have. Without RBAC, the JBoss server is not able to enforce authorized access according to role.

Fix

Run the following command. <JBOSS_HOME>/bin/jboss-cli.sh -c -> connect -> cd /core-service=management/access-authorization :write-attribute(name=provider, value=rbac) Restart JBoss. Map users to roles by running the following command. Upper-case Uppercase words are variables. role-mapping=ROLENAME/include=ALIAS:add(name-USERNAME, type=USER ROLE)