STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to JBoss Enterprise Application Platform 6.3 Security Technical Implementation Guide

V-213542

CAT II (Medium)

Production JBoss servers must not allow automatic application deployment.

Rule ID

SV-213542r961461_rule

STIG

JBoss Enterprise Application Platform 6.3 Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001813

Discussion

When dealing with access restrictions pertaining to change control, it should be noted that any changes to the software and/or application server configuration can potentially have significant effects on the overall security of the system. Access restrictions for changes also include application software libraries. If the application server provides automatic code deployment capability, (where updates to applications hosted on the application server are automatically performed, usually by the developers' IDE tool), it must also provide a capability to restrict the use of automatic application deployment. Automatic code deployments are allowable in a development environment, but not in production.

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 command:

ls /subsystem=deployment-scanner/scanner=default

If "scan-enabled"=true, this is a finding.

Fix Text

Determine the JBoss server configuration as being either standalone or domain.

Launch the relevant jboss-cli management interface substituting standalone or domain for <CONFIG>

<JBOSS_HOME>/<CONFIG>/bin/jboss-cli

connect to the server and run the command:

/subsystem=deployment-scanner/scanner=default:write-attribute(name=scan-enabled,value=false)