JBoss process owner interactive access must be restricted.

From JBoss EAP 6.3 Security Technical Implementation Guide

Associated with: CCI-000381

SV-76751r1_rule JBoss process owner interactive access must be restricted.

Vulnerability discussion

JBoss does not require admin rights to operate and should be run as a regular user. In addition, if the user account was to be compromised and the account was allowed interactive logon rights, this would increase the risk and attack surface against the JBoss system. The right to interactively log on to the system using the JBoss account should be limited according to the OS capabilities.

Check content

Identify the user account used to run the JBoss server. Use relevant OS commands to determine logon rights to the system. This account should not have full shell/interactive access to the system. If the user account used to operate JBoss can log on interactively, this is a finding.

Fix text

Use the relevant OS commands to restrict JBoss user account from interactively logging on to the console of the JBoss system. For Windows systems, use GPO. For UNIX like systems using ssh DenyUsers or follow established procedure for restricting access.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.