The ypbind service must not be running if no network services utilizing it are enabled.

From VMware vRealize Automation 7.x SLES Security Technical Implementation Guide

Part of SRG-OS-000096-GPOS-00050

Associated with: CCI-000382

SV-100285r1_rule The ypbind service must not be running if no network services utilizing it are enabled.

Vulnerability discussion

Disabling the "ypbind" service ensures the system is not acting as a client in a NIS or NIS+ domain when not required.

Check content

If network services are using the "ypbind" service, this is not applicable. To check that the "ypbind" service is disabled in system boot configuration, run the following command: # chkconfig "ypbind" --list Output should indicate the "ypbind" service has either not been installed, or has been disabled at all run levels, as shown in the example below: ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off Run the following command to verify "ypbind" is disabled through current runtime configuration: # service ypbind status If the service is disabled the command will return the following output: Checking for service ypbind unused If the service is running, this is a finding.

Fix text

The "ypbind" service can be disabled with the following command: # chkconfig ypbind off

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.

Powered by sagemincer