Oracle Solaris Security Policy
| Profile ID | (default) |
|---|
Revision History
Current version: 1.13942
- accepted
Platforms
- cpe:/o:oracle:solaris:11
Table of Contents
- Verify the OS configuration
- Verify file system information.
- Enable required services
- Tune kernel and network parameters
- Verify user configuration
- Check various system configuration items
- Verify audit configuration
Checklist
| contains 210 rules |
Verify the OS configurationgroup
The Oracle Solaris OS is installed with packages from a repository.
The packages must arrive on the target system unmodified,
and a set of protections for default services and
executables be put in place.
In this section, you verify package integrity, ensure that the booted system is protected, and verify that default OS protections are in place. |
| contains 3 rules |
Package integrity is verifiedruleRun 'pkg verify' to check that all installed Oracle Solaris software matches the packaging database and that ownership, permissions and content are correct. Remediation description:
'pkg verify' has produced errors.
Rerun the command and evaluate the errors.
As appropriate, based on errors found,
you should run 'pkg fix <package-fmri>'
See the pkg(1) man page.
|
The OS version is currentruleSystems should be kept up to date to ensure that the latest security and operational updates are installed. You can run 'pkg update -n' to check the current state of the system against the configured repositories. Remediation description:
The system is not up to date. Update the system.
|
Package signature checking is globally activatedrulePackage signature checking should be globally activated. Remediation description:
The package signature policy should not be set to "ignore".
See the pkg(1) man page.
|
Verify file system information.group
Oracle Solaris uses the ZFS file system by default.
ZFS is robust, scalable, and easy to administer.
ZFS can lay out filesystems over multiple devices,
keeps the file system state consistent on disk,
and verifies the data and metadata
by using a user-selectable checksum algorithm.
ZFS filesystems can hold zettabytes of data,
and this data can be encrypted, compressed, mirrored,
and backed up easily.
|
| contains 16 rules |
All local filesystems are ZFSruleZFS is the default filesystem for Oracle Solaris. On most systems other filesystem types should not be mounted. See the zfs(7FS) man page. Remediation description:
Unmount any foreign file systems, such as UFS and HSFS.
See the umount(1M) man page.
|
Find and list files with extended attributesruleOracle Solaris implements extended attributes as files in an "extended attribute" name space visible only by using extended attribute aware commands. It is possible for attackers or malicious users to hide information in the extended attribute name space. Oracle Solaris currently does not ship any files with extended attributes. See the runat(1) and fsattr(5) man pages. Remediation description:
Remove files with extended attributes
or remove extended attributes from files.
|
Find and list files with no known ownerruleFiles with no owner should be removed. Accounts that are closed should be archived and removed from the system. Remediation description:
Remove unowned files.
If the files were owned by an account that is closed,
archive the files before removing them.
See the rm(1) man page.
|
Find and list .forward filesrule.forward files can provide easy transport of information outside the firewall or outside the user's home directory. Remediation description:
Remove inappropriate .forward files
|
Find and list .netrc filesruleThe .netrc file contains data for logging in to a remote host over the network for file transfers by FTP. Remediation description:
Remove unneeded .netrc files
|
Permissions on User .netrc Files are correctruleThe .netrc file contains login credentials to remote systems for file transfers by FTP. The permissions should be set to disallow read access by group and others. See the chmod(1) man page. Remediation description:
If .netrc files are allowed, remove group and other permissions.
|
Permissions on User "." (Hidden) Files are correctruleHidden files in a user's home directory should be owned by the user. Directories should allow read-write-execute (rwx) permissions to the user only. Files should allow read-write (rw) permissions to the user only. Remediation description:
Change permissions on a user's hidden files to 600
and change permissions on a users hidden directories to 700.
|
Find and list world writable filesruleWorld-writable files are unprotected files. Modification and removal of a file should be limited to the owner of the file. Remediation description:
Protect the files from being modified by a non-owner.
See the chmod(1M) man page.
|
Find and list suid and sgid files other than those in standard Oracle Solaris packagesrulePrograms that set the UID and GID offer entry points for malicious code. Remediation description:
Remove files that have the setuid or setgid bit set, or remove the bit.
|
Find and list .rhosts filesrule.rhosts files can provide easy access to remote hosts by bypassing the password requirement. These files should be removed. Remediation description:
While rhosts-based login is also preventable on the remote host,
it is best to remove any .rhosts files from user's home directories.
|
swap(1M) is encryptedruleSwap space, either a ZFS volume or raw device, should be encrypted. Encryption ensures that any sensitive data, such as user passwords, are protected if the system needs to swap those pages out to disk. See the swap(1M) man page. Remediation description:
To edit the vfstab file, you must become an administrator
with the solaris.admin.edit/etc/vfstab authorization.
The root role has this authorization.
Specify the encrypted option in vfstab(4) for the swap device entry. |
Non-root ZFS filesystems are encryptedruleAll ZFS file systems that are not the root file system should be encrypted. Encryption must be applied at filesystem creation. You must remember the encryption passphrase. Store it in a safe place. See the zfs(1M) and zfs_encrypt(1M) man pages. Remediation description:
Back up any data needed from any unencrypted non-root file system.
Unmount and destroy those offending file systems.
Re-create the file systems with encryption on
(default algorithm is aes-128-ccm).
Remember the passphrase!
Restore data (preserved earlier) to the file systems.
|
A size limit is set on tmpfs(7FS)ruleThe size of the tmpfs file system is not limited by default. To avoid a performance impact, you can limit the size of each tmpfs mount. See the mount_tmpfs(1M) and vfstab(4) man pages. Remediation description:
To edit the vfstab file, you must become an administrator
with the solaris.admin.edit/etc/vfstab authorization.
To reboot the system, you must be assigned
the Maintenance and Repair rights profile.
The root role has all of these rights.
Set a limit on the tmpfs file system in the /etc/vfstab file, then reboot the system. For more information, see the Security Guidelines (http://www.oracle.com/pls/topic/lookup?ctx=solaris11&id=SYSADV7). |
World-writable directories have sticky bit setruleThe sticky bit on a directory prevents files in a world-writable directory from being deleted or moved by anyone except the owner of the file, or root. This is useful in directories that are common to many users, such as the /tmp directory. Remediation description:
Set the sticky bit on any world-writable directories.
See the chmod(1M) man page.
|
coreadm(1M) configuration is correctruleCore dumps can contain sensitive data. Protections can include file permissions and logging core dump events. See the coreadm(1m) and chmod(1M) man pages. Remediation description:
Locate the directory and protect the core dumps.
Protections include file permissions and logging.
|
/etc/motd and /etc/issue contain appropriate policy textruleThe /etc/issue and /etc/motd (message of the day) files are designed to hold system and security information. The contents of the /etc/issue file are displayed prior to the login prompt on the console, or in a window if the file is called from the GNOME Display Manager (gdm). Several applications call this file, such as Secure Shell and FTP. The /etc/motd contents are displayed after login. By default, the /etc/motd file exists while the /etc/issue file does not. See the issue(4), gdm(1M), and sshd_config(4) man pages. Remediation description:
Edit the /etc/motd file and create and edit the /etc/issue file
to add the security policy text that your legal department supplies.
An administrator with the Administrator Message Edit rights profile
can edit these files.
|
Enable required servicesgroup
The Service Management Facility (SMF) provides
an infrastructure to ease application
and system service management.
SMF augments the traditional UNIX startup scripts,
init run levels, and configuration files.
Management information for each service is stored
in a configuration repository,
which provides a simplified way to manage each service.
|
| contains 117 rules |
Service svc:/system/coreadm is enabledruleThe coreadm service manages the core files that are produced by processes that terminate abnormally. See the core(4) and coreadm(1M) man pages. Remediation description:
Use coreadm(1M) to configure the coreadm service,
then enable the service.
|
Service svc:/system/cron is enabledruleThe cron service manages the cron(1M) command, which runs processes that execute commands at specified dates and times. See the at(1), crontab(1), and cron(1M) man pages. Remediation description:
Configure your cron services, then enable the service.
|
Use of the cron(1M) and at(1) daemons is restrictedruleThe cron(1M) and at(1) daemons execute commands at specified dates and times. Only qualified accounts should be allowed to run commands at arbitrary times on the system. Remediation description:In order to restrict cron(1M) and at(1) properly, the file /etc/cron.d/cron.allow should exist and have only one entry for root. In addition, the file /etc/cron.d/at.allow should exist and be empty.To manually remediate failure on this check, run the following commands.
|
Service svc:/system/cryptosvc is enabledruleThe cryptosvc service manages the use of cryptographic mechanisms from the Cryptographic Framework feature of Oracle Solaris. See the cryptoadm(1M) man page. Remediation description:
Enable the cryptosvc service.
|
Service svc:/system/dbus is enabledruleThe dbus service manages the D-Bus message bus daemon. Programs use the message bus daemon to exchange messages with one another. For example, the Hardware Abstraction Layer (HAL) uses dbus. See the dbus-daemon(1) and hal(5) man pages. Remediation description:
Enable the dbus service.
|
Service svc:/system/hal is enabled in global zoneruleThe Hardware Abstraction Layer (HAL) service manages dynamic hardware configuration changes. See the hal(5) man page. This service only runs in the global zone. Remediation description:
Enable the hal service.
|
Service svc:/system/identity:domain is enabledruleThe identity:domain service instance manages system identity. See the domainname(1M) man page. Remediation description:
Enable the identity:domain service.
|
Service svc:/system/intrd is enabled in global zoneruleThe interrupt balancer (intrd) service monitors the assignments between interrupts and CPUs to ensure optimal performance. See the intrd(1M) man page. This service only runs in the global zone. Remediation description:
Enable the intrd service.
|
Service svc:/system/keymap is enabled in global zoneruleThe keymap service manages the default configuration of the keyboard. See the kbd(1) man page. This service only runs in the global zone. Remediation description:
Enable the keymap service.
|
Service svc:/system/picl is enabled in global zoneruleThe platform information and control (picl) service manages the publishing of platform configuration information that can respond to client requests for information about the configuration. See the picld(1M) and prtcpicl(1M) man pages. This service only runs in the global zone. Remediation description:
Enable the picl service.
|
Service svc:/system/scheduler is enabled in global zoneruleThe system/scheduler service manages the process scheduler. See the dispadmin(1M) man page. This service only runs in the global zone. Remediation description:
Enable the system/scheduler service.
|
Service svc:/system/system-log is enabledruleThe system-log service reads and forwards system messages to the appropriate log files or users. See the syslogd(1M) and rsyslogd(1M) man pages. Remediation description:
The system-log service has two instances, rsyslog and default.
The rsyslog instance is installed with the pkg:/system/rsyslog package.
Enable the system-log:rsyslog or system-log:default service.
|
Service svc:/system/utmp is enabledruleThe utmp service manages a table of processes, detects when a process has terminated, and updates the table. See the utmpd(1M) man page. Remediation description:
Enable the utmp service.
|
Service svc:/system/zones is enabled in global zoneruleThe zones service manages the autoboot and graceful shutdown of zones. See the zones(5) and zonecfg(1M) man pages. This service only runs in the global zone. Remediation description:
Enable the zones service.
|
Service svc:/system/zones-install is enabledruleThe zones-install service manages the auto-installation of zones. Remediation description:
Enable the zones-install service.
|
Service svc:/network/rpc/bind is enabledruleThe rpc/bind service manages the conversion of RPC program numbers to universal addresses. See the rpcbind(1M) man page. Remediation description:
Enable the rpc/bind service.
|
Service svc:/system/name-service/switch is enabledruleThe name-service/switch service manages the databases that contain information about hosts, users, and groups. See the nsswitch.conf(4) man page. Remediation description:
Enable the name-service/switch service.
|
Service svc:/system/name-service/cache is enabledruleThe name-service/cache service manages the caching of name service information. See the nscd(1M) man page. Remediation description:
Enable the name-service/cache service.
|
Service svc:/network/nfs/status is disabled or not installedruleThe NFS status monitor service interacts with lockd(1M) to provide the crash and recovery functions for the locking services on NFS. Remediation description:
Disable this service if the system is not an NFS client or server.
|
Service svc:/network/nfs/nlockmgr is disabled or not installedruleThe NFS lock manager supports record locking operations on NFS files in NFSv2 and NFSv3. See the lockd(1M) and sharectl(1M) man pages. Remediation description:
Disable the service if you are either
1) not using NFS at all or 2) using NFSv4.
|
Service svc:/network/nfs/client:default is in disabled staterule
The NFS client service is needed only
if the system is mounting NFS file systems specified in /etc/vfstab.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/nfs/server:default is in disabled staterule
The NFS Server service handles client file system
requests over NFS version 2, 3, and 4.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/nfs/fedfs-client:default is in disabled staterule
The Federated Filesystem (FedFS) client service
manages defaults and connection information for LDAP servers
that store FedFS information.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/nfs/rquota is disabled or not installedruleThe remote quota server returns quotas for a user of a local file system which is mounted over NFS. The results are used by quota(1M) to display user quotas for remote file systems. The rquotad(1M) daemon is normally invoked by inetd(1M). Remediation description:
Disable the rquota service.
It provides information about the network
to potentially malicious users.
|
Service svc:/network/nfs/cbd:default is in disabled staterule
The NFS cbd service manages communication endpoints
for the NFS Version 4 protocol.
The nfs4cbd(1M) daemon runs on the NFS Version 4 client
and creates a listener port for callbacks.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/nfs/mapid:default is in disabled staterule
The NFS user and group ID mapping daemon service
maps to and from NFS version 4 owner and owner_group
identification attributes and local UID and GID numbers used by
both the NFS version 4 client and server.
See the nfsmapid(1M) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/smb/client is disabled or not installedruleThe SMB/CIFS client allows an Oracle Solaris system to natively mount file systems by means of SMB shares from SMB enabled servers such as a Windows system. See the mount_smbfs(1M) man page. Remediation description:
Uninstall the pkg:/system/file-system/smb package
or disable the service.
|
Service svc:/network/ftp:default is in disabled staterule
The FTP service provides unencrypted file transfer service
and uses plain text authentication.
The secure copy program (scp(1)) program should be used
instead of FTP as it provides encrypted authentication
and file transfer.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/ssh:default is in disabled staterule
The ssh service manages the Secure Shell (ssh) daemon,
which provides secure encrypted communications
between two untrusted hosts over an insecure network.
By default, ssh is the only network service
that can send and receive network packets
on a newly-installed Oracle Solaris system.
See the sshd(1M) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/smtp:sendmail is enabledruleThe sendmail service should be running. Otherwise, important system mail to root will not be delivered. If receipt of remote mail is not required, sendmail should be in local_only mode. See check OSC-68505-sendmail-local-only to verify that sendmail is running in local_only mode. See the sendmail(1M) man page. Remediation description:
Enable the smtp:sendmail service.
|
Service svc:/network/sendmail-client is enabledruleThe sendmail-client service manages email on a client. The sendmail-client service needs to be running to ensure delivery of mail to local accounts such as root. See the sendmail(1M) man page. Remediation description:
Enable the sendmail-client service.
|
Service svc:/network/inetd is enabledruleThe inetd service manages the restarting of inet services. See the inetd(1M) man page. Remediation description:
Enable the inetd service.
|
Service svc:/system/filesystem/autofs:default is in disabled staterule
The autofs service manages
the mount points for the automount(1M) daemon.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/system/filesystem/rmvolmgr is disabled or not installedruleThe removable volume manager is a HAL-aware volume manager that can automatically mount and unmount removable media and hot-pluggable storage. Users might import malicious programs, or transfer sensitive data off the system. See the rmvolmgr(1M) man page. This service only runs in the global zone. Remediation description:
Disable the remote volume manager service.
|
Service svc:/system/filesystem/rmvolmgr is enabledruleThe removable volume manager is a HAL-aware volume manager that can automatically mount and unmount removable media and hot-pluggable storage. Users might import malicious programs, or transfer sensitive data off the system. See the rmvolmgr(1M) man page. Remediation description:
Enable the remote volume manager service.
|
Service svc:/system/power management is enabled in global zoneruleThe system/power service manages the power management configuration of an Oracle Solaris system. See the poweradm(1M) man page. This service only runs in the global zone. Remediation description:
Enable the power management service.
|
Service svc:/network/dns/multicast:default is in disabled staterule
Multicast DNS (mDNS) implements DNS in a small network
where no conventional DNS server has been installed.
DNS Service Discovery (DNS-SD) extends multicast DNS
to also provide simple service discovery (network browsing).
This service is disabled by default,
because while it can ease finding hosts and servers,
it can also provide information about the network to malicious users.
See the named(1M) and mdnsd(1M) man pages.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/dhcp-server:default is in disabled staterule
By default, the dhcp-server service is not installed.
If you are not using this system as a DHCP server,
you should not install or enable the service.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/ntp is enabled and properly configured as a clientruleThe Network Time Protocol daemon should be enabled and properly configured as a client. The /etc/inet/ntp.conf file must include at least one server definition. The file should also contain the line "restrict default ignore" to prevent the client from also acting as a server. Remediation description:
The ntp service should be installed on all systems
where security and compliance is desired.
If it is not installed on your system,
install it using 'pkg install service/network/ntp'.
Then configure the service properly as a client and enable the service.
|
Service svc:/network/rarp:default is in disabled staterule
This legacy service responds
to DARPA reverse address resolution protocol (RARP) requests.
Historically, RARP was used by machines at boot time
to discover their Internet Protocol (IP) address.
By default, this service is not installed.
See the rarpd(1M) and rarp(7P) man pages.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/slp:default is in disabled staterule
This legacy service provides common server functionality
for the Service Location Protocol (SLP) versions 1 and 2,
as defined by IETF in RFC 2165 and RFC 2608.
SLP discovers and selects network services.
By default, this service is not enabled.
See the slpd(1M), slp.conf(4), and slp(7P) man pages.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/security/kadmin:default is in disabled staterule
The Kerberos administration daemon service runs
on the master key distribution center (KDC),
which stores the principal and policy databases.
This service should not be run on a system that is not a KDC.
See the kadmind(1M) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/security/krb5_prop:default is in disabled staterule
The Kerberos propagation daemon runs on slave KDC servers
to update the database from the master KDC.
See the kpropd(1M) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/security/krb5kdc:default is in disabled staterule
The Kerberos key distribution center service manages
Kerberos tickets on the master and slave KDCs.
See the krb5kdc(1M) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/application/management/net-snmp:default is in disabled staterule
The Simple Network Management Protocol (SNMP)
is a widely used protocol for monitoring
the health and welfare of network equipment.
The net-snmp SNMP daemon processes requests
from SNMP management software.
See the snmpd(8) and snmp_config(5) man pages.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/application/cups/in-lpd:default is in disabled staterule
This service supports the CUPS Line Printer Daemon (LPD)
for legacy client systems that use the LPD protocol.
By default, this service is not installed.
See the cups-lpd(8) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/application/stosreg is enabled in global zoneruleThe service tag OS registry inserter (stosreg) service manages the service tag registry. See the stclient(1M) man page. This service only runs in the global zone. Remediation description:
Enable the stosreg service.
|
Service svc:/system/ocm is enabledruleThe Oracle Configuration Manager (ocm) service collects configuration information and uploads it to the Oracle repository. See the configCCR(1M) man page. Remediation description:
Enable the ocm service.
|
Service svc:/network/finger is disabled or not installedruleThis legacy service enables users to display information about local and remote users. By default, this service is not installed as part of solaris-small-server. It is however installed as part of solaris-large-server. This service is almost never needed and either should be removed or at least, disabled. See the fingerd(1M) and finger(1) man pages. Remediation description:
Uninstall the pkg:/service/network/finger and
pkg:/network/finger packages or disable the service.
|
Service svc:/network/login:rlogin is disabled or not installedruleThis legacy service enables users to log in remotely. By default, this service is not installed as part of solaris-small-server. See the rlogind(1M) and rlogin(1) man pages. Remediation description:
Uninstall the pkg:/service/network/legacy-remote-utilities package
or disable the service.
|
Service svc:/network/login:klogin is disabled or not installedruleThis service enables users to log in remotely with Kerberos authentication. By default, this service is not installed. See the rlogind(1M) and rlogin(1) man pages. Remediation description:
Uninstall the pkg:/service/network/legacy-remote-utilities package
or disable the service.
|
Service svc:/network/login:eklogin is disabled or not installedruleThis service enables users to log in remotely with Kerberos authentication over an encrypted line. By default, this service is not installed. See the rlogind(1M) and rlogin(1) man pages. Remediation description:
Uninstall the pkg:/service/network/legacy-remote-utilities package
or disable the service.
|
Service svc:/network/shell:default is disabled or not installedruleThe remote shell daemon provides remote execution facilities with authentication based on Kerberos V5 or privileged port numbers. The Secure Shell service, svc:/network/ssh, is the best choice for remote execution. See the rshd(1M) and sshd(1M) man pages. Remediation description:
Disable this service or uninstall the package.
To view the contents of the package,
run the 'pkg contents legacy-remote-utilities' command.
|
Service svc:/network/shell:kshell is disabled or not installedruleThe remote shell daemon provides remote execution facilities with authentication based on Kerberos V5 or privileged port numbers. The Secure Shell service, svc:/network/ssh, is the best choice for remote execution. See the rshd(1M) and sshd(1M) man pages. Remediation description:
Disable this service or uninstall the package.
To view the contents of the package,
run the 'pkg contents legacy-remote-utilities' command.
|
Service svc:/network/telnet is disabled or not installedruleThis legacy service supports the DARPA standard TELNET virtual terminal protocol to connect to a remote system over the TELNET port. By default, this service is not installed. See the telnetd(1M) and telnet(1) man pages. Remediation description:
Uninstall the telnet packages or disable the service.
|
Service svc:/network/uucp is disabled or not installedruleThis legacy service, UNIX to UNIX copy, provides a user interface for requesting file copy operations, typically used when constant connectivity is not possible. By default, this service is not installed. See the uucpd(1M) and uucp(1C) man pages. Remediation description:
Uninstall the uucp package or disable the service.
|
Service svc:/network/chargen:stream is disabled or not installedruleThis legacy service provides the server side of the Character Generator Protocol (RFC 864) for TCP. See the in.chargend(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/chargen:dgram is disabled or not installedruleThis legacy service provides the server side of the Character Generator Protocol (RFC 864) for UDP. See the in.chargend(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/daytime:stream is disabled or not installedruleThis legacy service provides the server side of the Daytime Protocol (RFC 867) for TCP. See the in.daytimed(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/daytime:dgram is disabled or not installedruleThis legacy service provides the server side of the Daytime Protocol (RFC 867) for UDP. See the in.daytimed(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/discard:stream is disabled or not installedruleThis legacy service provides the server side of the Discard Protocol (RFC 863) for TCP. See the in.discardd(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/discard:dgram is disabled or not installedruleThis legacy service provides the server side of the Discard Protocol (RFC 863) for UDP. See the in.discardd(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/echo:stream is disabled or not installedruleThis legacy service provides the server side of the Echo Protocol (RFC 862) for TCP. See the in.echod(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/echo:dgram is disabled or not installedruleThis legacy service provides the server side of the Echo Protocol (RFC 862) for UDP. See the in.echod(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/time:stream is disabled or not installedruleThis legacy service provides the server side of the Time Protocol (RFC 868) for TCP. See the in.timed(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/time:dgram is disabled or not installedruleThis legacy service provides the server side of the Time Protocol (RFC 868) for UDP. See the in.timed(1M) man page. Remediation description:
Remove the legacy-network-services package.
To view the contents of the package,
run the 'pkg contents legacy-network-services' command.
|
Service svc:/network/comsat is disabled or not installedruleThis legacy service process listens for reports of incoming mail and notifies interested users. By default, this service is not installed as part of solaris-small-server. See the comsat(1M) man page. Remediation description:
Uninstall the pkg:/service/network/comsat package
or disable the service.
|
Service svc:/network/rexec is disabled or not installedruleThis legacy service provides remote execution facilities with authentication based on user names and passwords. See the in.rexecd(1M) and rexec(3C) man pages. Remediation description:
Disable the rexec service.
You can also uninstall the legacy-remote-utilities package.
To view the contents of the package,
run the 'pkg contents legacy-remote-utilities' command.
|
Service svc:/network/talk is disabled or not installedruleThis legacy program enables two-way, screen-oriented communication. For more information, see the talk(1) and mesg(1) man pages. Remediation description:
Disable talk(1) by using the mesg(1) command.
|
Service svc:/network/stdiscover is disabled or not installedruleThis legacy program is used to locate the service tag listener. For more information, see the in.stdiscover(1M) man page. Remediation description:
Disable the stdiscover service.
|
Service svc:/network/stlisten is disabled or not installedruleThis legacy program is used to listen for discovery probes. See the in.stlisten(1M) man page. Remediation description:
Disable the stlisten service.
|
Service svc:/network/rpc/gss is disabledruleThe generic security service (gss) service manages the generation and validation of Generic Security Service Application Program Interface (GSS-API) security tokens. The gssd(1M) daemon operates between the kernel rpc and the GSS-API. Remediation description:
Disable the rpc/gss service.
|
Service svc:/network/rpc/gss is enabledruleThe generic security service (gss) service manages the generation and validation of Generic Security Service Application Program Interface (GSS-API) security tokens. The gssd(1M) daemon operates between the kernel rpc and the GSS-API. Remediation description:
Enable the rpc/gss service.
|
Service svc:/network/rpc/gss is enabled if and only if Kerberos is configuredruleThe generic security service (gss) service manages the generation and validation of Generic Security Service Application Program Interface (GSS-API) security tokens. The gssd(1M) daemon operates between the kernel rpc and the GSS-API. Kerberos uses this service. Remediation description:
Disable the rpc/gss service
if Kerberos is not configured and not in use.
|
Service svc:/network/rpc/mdcommd is disabled, or not installedrulerpc.mdcommd is an rpc(4) daemon that functions as a server process. rpc.mdcommd manages communication among hosts participating in a multi-node disk set configuration. rpc.mdcommd is invoked by inetd(1M). Remediation description:
Disable the rpc.mdcommd service.
|
Service svc:/network/rpc/mdcommd is enabledrulerpc.mdcommd(1M) is an rpc(4) daemon that functions as a server process. rpc.mdcommd(1M) manages communication among hosts participating in a multi-node disk set configuration. rpc.mdcommd is invoked by inetd(1M). Remediation description:
Enable the rpc.mdcommd service.
|
Service svc:/network/rpc/smserver is disabled or not installedruleThis program is used to access removable media devices. See the rpc.smserverd(1M) man page. Remediation description:
Disable the smserver service.
|
Service svc:/network/rpc/smserver is enabledruleThis program is used to access removable media devices. See the rpc.smserverd(1M) man page. Remediation description:
Enable the smserver service.
|
Service svc:/network/security/ktkt_warn is disabled or not installedruleThe Kerberos V5 warning messages daemon on Kerberos clients can warn users when their Kerberos tickets are about to expire and can renew the tickets before they expire. By default, this service is disabled. If the system is Kerberos client, then this service should be enabled. See the ktkt_warnd(1M) man page. Remediation description:
On systems that are not part of a Kerberos realm,
uninstall any Kerberos packages.
Disable this service on all systems in a Kerberos realm
that are not KDCs.`
|
Service svc:/network/security/ktkt_warn is enabledruleThe Kerberos V5 warning messages daemon on Kerberos clients can warn users when their Kerberos tickets are about to expire and can renew the tickets before they expire. By default, this service is disabled. See the ktkt_warnd(1M) man page. Remediation description:
Enable this service on all systems in a Kerberos realm.
On systems that are not part of a Kerberos realms, remove the package.
|
Service svc:/network/rpc/rstat is disabled or not installedruleThis legacy service displays performance data from a remote system. By default, this service is not installed. See the rstatd(1M) and rstat(3RPC) man pages. Remediation description:
Uninstall the pkg:/service/network/legacy-remote-utilities package
or disable the service.
|
Service svc:/network/rpc/rusers is disabled or not installedruleThis legacy service displays information about users on a remote system. By default, this service is not installed. See the rusersd(1M) and rusers(1) man pages. Remediation description:
Uninstall the pkg:/service/network/legacy-remote-utilities package
or disable the service.
|
Service svc:/network/rpc/meta is disabled or not installedruleThis legacy service uses an rpc(4) daemon to manage local copies of metadevice diskset information. By default, this service is not installed. See the rpc.metad(1M) man page. Remediation description:
Uninstall the package or disable the service.
|
Service svc:/network/rpc/metamed is disabled or not installedruleThis legacy service manages mediator information for 2-string high availability configurations. See the rpc.metamedd(1M) man page. Remediation description:
Uninstall the package or disable the service.
|
Service svc:/network/rpc/metamh is disabled or not installedruleThis legacy service uses an rpc(4) daemon to manage multi-hosted disks. By default, this service is not installed. See the rpc.metamhd(1M) man page. Remediation description:
Uninstall the package or disable the service.
|
Service svc:/network/rpc/rex is disabled or not installedruleThis program is the Oracle Solaris RPC server for remote program execution. If this service is enabled, the daemon is started by inetd(1M) whenever a remote execution request is made. See the rpc.rexd(1M) man page. Remediation description:
Disable the rex service.
|
Service svc:/network/rpc/spray is disabled or not installedruleThis program is a server that records the packets sent by spray(1M). See the rpc.sprayd(1M) man page. Remediation description:
Disable the spray service.
|
Service svc:/network/rpc/wall is disabled or not installedruleThis program broadcasts messages to all logged-in users. See the rpc.rwalld(1M) and wall(1M) man pages. Remediation description:
Disable the wall service.
|
Service svc:/system/avahi-bridge-dsd is disabled or not installedruleThis program provides an object-oriented interface to DBUS-enabled applications. See the avahi-daemon-bridge-dsd(1) man page. Remediation description:
Disable the avahi-bridge-dsd service.
|
Service cde-ttdbserver is enabled, or not installedruleThe rpc.ttdbserver service is part of the Common Desktop Environment (CDE) which predates the use of GNOME in Solaris. If you are running CDE, then you should enable its services. You should have good reasons to choose CDE over GNOME as your desktop environment. Remediation description:
If installed, this service should be enabled.
|
Service svc:/application/graphical-login/gdm:default is in disabled staterule
The GNOME Display Manager manages the displays on a system,
including the console display, attached displays, XDMCP displays,
and virtual terminals.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service cde-calendar-manager is enabled, or not installedruleThe cde-calendar-manager service is part of the Common Desktop Environment (CDE) which predates the use of GNOME in Solaris. If you are running CDE, then you should enable its services. You should have good reasons to choose CDE over GNOME as your desktop environment. Remediation description:
If installed, this service should be enabled.
|
Service svc:/application/x11/xfs is disabled or not installedruleThis program provides fonts to X Window System display servers. The server is usually run by inetd(1M). See the xfs(1) and fsadmin(1) man pages. Remediation description:
Disable the xfs service.
|
Service xvnc-inetd is enabled, or not installedruleThe xvnc-inetd service runs the X VNC server from inetd(1M). See the Xvnc(1) man page. Remediation description:
To run Xvnc from inetd, this service must be enabled.
|
The GNOME desktop has suitable screensaver settingsruleThe timeout parameter for the xscreensaver application specifies the amount of time that the keyboard and mouse can be inactive before a password-protected screensaver appears. See the xscreensaver(1) man page. Remediation description:
A screensaver timeout provides protection for a desktop
that has not been locked by an absent user.
To help prevent session hijacking,
the timeout value should be set to a fairly short interval.
|
The NIS client service is disabled or not installedruleBy default, NIS client software is not installed. NIS is an RPC-based naming service that does not conform to current security requirements, so can be less secure than the LDAP naming service. See the nis(5) and ypbind(1M) man pages. Remediation description:
Disable the NIS client service
if it is not on a network with an NIS server.
|
The NIS server service is disabled or not installedruleBy default, NIS server software is not installed. NIS is an RPC-based naming service that does not conform to current security requirements, that can be less secure than the LDAP naming service. See the nis(5) and ypserv(1M) man pages. Remediation description:
Disable the NIS server service
if it is not being used to distribute
system and user configuration information.
|
The r-protocols services are disabled in PAMruleBy default, legacy services such as the r-protocols, rlogin(1) and rsh(1), are not installed. Their services, however, are defined in /etc/pam.d. See the pam.d(4) man page. Remediation description:
If you remove the service definitions from /etc/pam.d,
these services would use the "other" service
if these legacy services were enabled.
Therefore, specify pam_deny.so.1 as the module
for the authentication stack for the r-protocol services
in the /etc/pam.d directory.
|
Service svc:/network/http:apache22 is in disabled staterule
This program provides Apache web server services
by using the Apache hypertext transfer protocol (http).
See the httpd(8) man page.
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
Service svc:/network/rpc/keyserv is disabled or not installedrulekeyserv is a daemon that is used for storing the private encryption keys of each user logged into the system. These encryption keys are used for accessing secure network services such as secure NFS. For more information, see the keyserv(1M) man page. Remediation description:
Disable the keyserv service.
|
Service svc:/network/rpc/keyserv cannot use the nobody user keyruleThe value of ENABLE_NOBODY_KEYS is YES by default. See the keyserv(1M) man page. Remediation description:
Edit the /etc/default/keyserv file to change the value
of ENABLE_NOBODY_KEYS to NO.
|
ssh(1) is the only service binding a listener to non-loopback addressesruleBy default, ssh(1) is the only network service that can send and receive network packets on a newly-installed Oracle Solaris system. Of course, most useful servers will have some additional service such as a web server on port 80, etc. Also, rpcbind, if it is online, should be configured to listen only for local connections. See the sshd(1M) and rpcbind(1M) man pages. Remediation description:Disable any unneeded services listening on the network.
# svcadm disable <FMRI for unneeded service>
Additionally, rpcbind should be set to local only mode so that it does not respond to remote requests, using:
# /usr/sbin/svccfg -s svc:/network/rpc/bind:default setprop config/local_only = boolean: true
# svcadm refresh svc:/network/rpc/bind:default
|
ssh(1) requires passwordsruleLogins without a password put the system at risk. In the default remote login service, Secure Shell, the PermitEmptyPasswords parameter in the /etc/ssh/sshd_config file should remain set to no. See the sshd_config(4) man page. Remediation description:
Ensure that PermitEmptyPasswords value
in the /etc/ssh/sshd_config file has not been changed.
The default value is no.
If you reset the value, restart the ssh service.
|
rhost-based authentication in ssh(1) is disabledrulerhost-based authentication in Secure Shell allows users to remotely log in without supplying a password. The IgnoreRhosts parameter specifies whether .rhosts and .shosts files can be used rather than a password. See the sshd_config(4) and hosts.equiv(4) man pages. Remediation description:
Ensure that the default value of IgnoreRhosts has not been changed.
If the parameter is not in the /etc/ssh/sshd_config file,
the value is yes.
If IgnoreRhosts is in the file, set its value to yes.
Secure Shell parameters are case-sensitive.
If you reset the value, restart the ssh service.
|
root login by using ssh(1) is disabledruleBy default, remote root logins are not permitted because root is a role and roles cannot log in. If root has been changed to a user, the default value of the PermitRootLogin parameter in the /etc/ssh/sshd_config file prevents root from remotely logging in. See the sshd_config(4) man page. Remediation description:
If root is a user on your system,
ensure that the value of PermitRootLogin has not been changed to yes.
If you reset the value, restart the ssh service.
|
Service svc:/network/smtp:sendmail only listens on loopbackruleCheck that sendmail listens in local_only mode. This is also called listens on loopback. See the sendmail(1M) and svccfg(1M) man pages Remediation description:
Set the service to listen in local_only mode.
|
The umask(1) for SMF services is 022ruleFiles that the Service Management Facility (SMF) creates should be created with 644 file permissions. Remediation description:
Set the umask for SMF services to 022.
|
ssh(1) does not forward X11ruleThe X11Forwarding parameter in the /etc/ssh/sshd_config file specifies whether users can forward an X Window session through an encrypted tunnel. This parameter allows the remote user to display windows remotely over Secure Shell. See the sshd_config(1M) and X(5) man pages. Remediation description:
By default, X11Forwarding is set to yes.
X11Forwarding could permit a malicious user
to secretly open an X11 connection to a different client
and perform unobtrusive activities such as keystroke monitoring.
If the remote window display is not required, disable or restrict it,
then restart the ssh service.
|
Consecutive login attempts for ssh(1) are limitedruleBy default, the MaxAuthTries parameter in the /etc/ssh/sshd_config file is set to 6. This parameter specifies the maximum number of authentication attempts that the server permits before ending the connection. By restricting the number of failed authentication attempts, Secure Shell lessens the effectiveness of brute-force login attempts. It is important to note that setting MaxAuthTries to 6 actually provides only 3 failed login attempts because of the way SSH counts failures. See the sshd_config(4) man page. Remediation description:
Set the MaxAuthTries parameter in the /etc/ssh/sshd_config file
to the value that site security requires, then restart the ssh service.
|
gdm(1M) does not accept logins without passwordsruleAutomatic logins are a known security risk for other than public kiosks. By default, GNOME automatic login is disallowed, so users must supply a password. Automatic and Timed login is controlled by the entries in /etc/gdm/custom.conf See the gdm(1M) man page. Remediation description:
Ensure that GNOME automatic login has not been enabled.
If it has, remove the lines from /etc/gdm/custom.conf
|
The ftp(1) banner shows a suitable security messageruleThe banner informs users who are attempting to access the system that the system is monitored. Note that the pkg:/service/network/ftp package must be installed for ftp to work. Remediation description:
The ftp banner shows the security message
in the /etc/issue file prior to login.
See the proftpd(1M) man page.
|
The gdm(1M) banner shows a suitable security messageruleThe banner informs users who are attempting to access the system that the system is monitored. The banner uses the /etc/issue file. See the issue(4) and gdm(1M) man pages. Remediation description:
Modify the /etc/gdm/Init/Default file to display a dialog box
with the contents of the /etc/issue file.
zenity(1) displays simple GNOME dialogs.
|
The ssh(1) banner shows a suitable security messageruleBy default, the ssh(1) banner displays the contents of the /etc/issue file. See the issue(4) and sshd_config(4) man pages. Remediation description:
Ensure that the Banner value in the sshd_config(4) file
is not commented out.
|
The telnet(1) banner shows a suitable security messageruleThe telnetd(1M) DARPA TELNET protocol server is a legacy service that does not conform to current security requirements. By default, this service is not installed, and systems use the ssh(1M) protocol to communicate. Remediation description:
If telnet is installed, the default banner is empty.
Make sure that the banner contains a suitable security message
or is empty.
Alternatively, uninstall the package.
|
ftp(1) is restricted to a specific set of usersruleFTP file transfers should not be available to all users, and must require qualified users to supply their names and password. In general, system users should not be allowed to use FTP. This check verifies that system accounts are included in the /etc/ftpd/ftpusers file so that they are not allowed to use FTP. See the ftp(1) man page. Remediation description:
The file /etc/ftpd/ftpusers is used to prohibit users
from using the FTP service.
As a minimum, this file should include all system users,
such as 'root', 'bin', 'adm', etc.
|
The tcp_wrappers feature is enabledruleTCP wrappers provides a way of implementing access controls by checking the address of a host that is requesting a particular network service against an ACL. Requests are granted or denied accordingly. TCP wrappers also logs host requests for network services, which is a useful monitoring function. The ssh(1) and sendmail(1M) services are configured to use TCP wrappers. Network services that might be placed under access control include proftpd(8) and rpcbind(1M). See the tcpd(1M) man page. Remediation description:
For most TCP services, see the Network Administration Guide
(http://www.oracle.com/pls/topic/lookup?ctx=solaris11&id=NWIPA).
For FTP, see the Security Guidelines
(http://www.oracle.com/pls/topic/lookup?ctx=solaris11&id=SYSADV7).
|
Files written in ftp(1) sessions have a suitable umaskruleThe FTP server does not necessarily use the user's system file creation mask. Setting the FTP umask ensures that files transmitted over FTP use a strong file creation umask. See the umask(1) and proftpd(8) man pages. Remediation description:
Set a strong default file creation mask for files
that are created by the FTP server.
|
Tune kernel and network parametersgroup
Oracle Solaris is a multithreaded, scalable UNIX
operating system that runs on SPARC and x86 processors.
It is self-adjusting to system load and requires minimal tuning.
Kernel and network variables are tuned to secure values by default.
In some cases, however, tuning is necessary.
In this section, you verify that a TCP/IP kernel variable is still set to its default value, and that you modify network tunables for security reasons. |
| contains 17 rules |
Directed broadcasts are not forwardedruleBy default, Oracle Solaris forwards broadcast packets. To reduce the possibility of broadcast flooding, change the default. Note that you are also disabling broadcast pings. Remediation description:
Directed broadcasts are manged using the ipadm command.
See the ipadm(1M) man page.
|
Responses to ICMP netmask requests are disabledruleTo prevent the dissemination of information about the network topology, disable these responses if they are currently enabled. Remediation description:
Responses to ICMP netmask requests are managed using the ipadm command.
See the ipadm(1M) man page.
|
Responses to ICMP broadcast timestamp requests are disabledruleTo prevent the dissemination of information about the network topology, disable these responses if they are currently enabled. Remediation description:
Responses to ICMP broadcast timestamp requests are managed
using the ipadm command.
See the ipadm(1M) man page.
|
Responses to ICMP timestamp requests are disabledruleThe default value removes additional CPU demands on systems and prevents the dissemination of information about the network. Remediation description:
Responses to ICMP timestamp requests are managed using
the ipadm command.
See the ipadm(1M) man page.
|
Source-routed packets are not forwardedruleTo prevent DOS attacks from spoofed packets, ensure that source-routed packets are not forwarded. The default is not to forward them. Remediation description:
Forwarding of source-routed packets is managed using the ipadm command.
See the ipadm(1M) man page.
|
TCP reverse source routing is disabledruleThe default value prevents packets from bypassing network security measures. Source-routed packets allow the source of the packet to suggest a path different from the path configured on the router. Note - This parameter might be set to 1 for diagnostic purposes. After diagnosis is complete, return the value to 0. Remediation description:
TCP reverse source routing is managed using the ipadm command.
See the ipadm(1M) man page.
|
The maximum number of half-open TCP connections is set to the defaultruleSetting the maximum half-open TCP connections to 4096 per IP address per port helps to defend against SYN flood denial of service attacks. 1024 is the default. Remediation description:
The maximum number of half-open TCP connections is managed
using the ipadm command.
See the ipadm(1M) man page.
|
The maximum number of waiting TCP connections is set to the defaultruleSetting the maximun number of queued incoming connections TCP to at least 1024 can help prevent certain Distributed Denial of Service (DDoS) attacks. The default is 128. Remediation description:
The maximum number of waiting TCP connections is managed
using the ipadm command.
See the ipadm(1M) man page.
|
Responses to echo requests on multicast addresses are disabledruleTo prevent the dissemination of information about the network topology, disable these responses. Remediation description:
Responses to echo requests are managed using the ipadm command.
See the ipadm(1M) man page.
|
Responses to ICMP echo requests on broadcast addresses are disabledruleTo prevent the dissemination of information about the network topology, disable these responses if they are currently enabled. Remediation description:
Responses to ICMP echo requests on broadcast addresses are managed
using the ipadm command.
See the ipadm(1M) man page.
|
Strict multihoming is enabledruleFor systems that are gateways to other domains, such as a firewall or a VPN node, strict multihoming must be enabled. The hostmodel property controls the send and receive behavior for IP packets on a multihomed system. Remediation description:
Strict multihoming should be set to "1"
so that packets don't get accepted on a different interface.
The default is "0"
|
ICMP redirects are disabledruleRouters use ICMP redirect messages to inform hosts of more direct routes to a destination. An illicit ICMP redirect message could result in a man-in-the-middle attack. Remediation description:
ICMP redirects are managed using the ipadm command.
See the ipadm(1M) man page.
|
Improved sequential generation for TCP packet sequence numberingruleEnsure that the TCP initial sequence number generation parameter complies with RFC 6528 (http://www.ietf.org/rfc/rfc6528.txt). Remediation description:
TCP initial sequence number generation parameters are set in the
/etc/default/inetinit file using the TCP_STRONG_ISS parameter
which should be set to 1 by default.
The Recommended, more secure, value of 2 will also pass this check.
|
Strong TCP packet sequence numberingruleEnsure that the TCP initial sequence number generation parameter complies with RFC 6528 (http://www.ietf.org/rfc/rfc6528.txt). Remediation description:
TCP initial sequence number generation parameters are set in the
/etc/default/inetinit file using the TCP_STRONG_ISS parameter
which should be set to 2.
|
Routing daemons are disabledruleSystems in a secure datacenter should not need automatic routing reconfiguration. Remediation description:
List all routing services and daemons by running routeadm(1M) command.
Stop running any routing configuration daemons by using svcadm to
disable the services associated with them.
The route(1M) command can be used to establish any static
routes needed for the system.
|
The maximum number of half-open TCP connections is at least 4096ruleSetting the maximum half-open TCP connections to 4096 per IP address per port helps to defend against SYN flood denial of service attacks. Remediation description:
The maximum number of half-open TCP connections is managed
using the ipadm command.
See the ipadm(1M) man page.
|
The maximum number of waiting TCP connections is set to at least 1024ruleSetting the maximun number of queued incoming connections TCP to at least 1024 can help prevent certain Distributed Denial of Service (DDoS) attacks. Remediation description:
The maximum number of waiting TCP connections is managed
using the ipadm command.
See the ipadm(1M) man page.
|
Verify user configurationgroup
Each user at a site must have a unique login and ID,
and be assigned a home directory.
User passwords must be as secure as possible,
and their files at creation must be protected
from modification by other users.
User configuration should protect regular users
and prevent or discourage malicious users.
|
| contains 40 rules |
DICTIONBDIR is set to /var/passwdruleDICTIONBDIR in the /etc/default/passwd file points to the /var/passwd dictionary by default. A password dictionary can strengthen users' password selection by preventing the use of common words or letter combinations. The passwd command performs dictionary lookups in the dictionary that DICTIONBDIR indicates. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file,
set the DICTIONBDIR variable to /var/passwd.
|
Passwords are hashed with a secure algorithmruleThe hash used is determined by values of CRYPT_ALGORITHMS_ALLOW and CRYPT_DEFAULT set in /etc/security/policy.conf file. The value for SHA-256 is "5", and the value for SHA-512 is "6". To confirm properly set, the second field in the /etc/shadow file indicates the algorithm that was used to create the password hash. If the algorithm is set to SHA-256, the entry begins with "$5$" If the algorithm is set to SHA-512, the entry begins with "$6$" See the crypt.conf(4) and policy.conf(4) man pages. Remediation description:
Save the /etc/security/policy.conf file to a new name.
Edit original policy.conf file to accept 5 (and 6 if desired) as values
for allowed algorithms, and 5 (or 6 if desired, and if added as allowed)
as the value for the default algorithm.
Set the password for your users, or set a deadline for password change.
After setting the password, or after the deadline, verify the $5$ or $6$
prefix for the second field of the users' entries in /etc/shadow file.
Once verified, you can safely remove the saved policy.conf file.
|
Password history does not log any passwordsruleHISTORY in the /etc/default/passwd file prevents users from using similar passwords within the HISTORY value. The default value, 0, allows users to reuse passwords immediately. Remediation description:
In the /etc/default/passwd file, leave the HISTORY variable set to 0.
|
Password history logs the last ten passwordsruleHISTORY in the /etc/default/passwd file prevents users from using similar passwords within the HISTORY value. If MINWEEKS is set to 3 and HISTORY is set to 10, passwords are checked for reuse for ten months. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file, set the HISTORY variable to 10.
|
Passwords allow repeat charactersruleMAXREPEATS in the `/etc/default/passwd file allows users to repeat characters in passwords. The default is 0, which permits repeated characters. Any other value indicates how many characters can be repeated. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file, set the MAXREPEATS variable to 0.
|
Passwords must have at least 2 alphabetic charactersrule
MINALPHA in the /etc/default/passwd file indicates
the minimum number of alphabetic characters that passwords must contain.
Alphabetic characters provide more values
than numeric or special characters, so allow for more variation.
The default value is 2.
Edit the /etc/default/passwd file, set the MINALPHA parameter to the policy minimum password alphabetic character count, which is 2.
# pfedit /etc/default/passwd
MINALPHA=2
|
Passwords must differ by at least 3 charactersrule
MINDIFF in the /etc/default/passwd file indicates
the minimum number of characters that a password
must differ from the previous value.
Edit the /etc/default/passwd file, set the MINDIFF parameter to the policy minimum password character difference, which is 3.
# pfedit /etc/default/passwd
MINDIFF=3
|
Passwords require at least 0 digitsrule
MINDIGIT in the /etc/default/passwd file indicates
the minimum number of digits that a password must contain.
Digits provide some protection against dictionary-based
password attacks.
The default is 0.
Edit the /etc/default/passwd file, set the MINDIGIT parameter to the policy minimum password digit count, which is 0.
# pfedit /etc/default/passwd
MINDIGIT=0
|
Passwords must have at least 0 lower-case charactersrule
MINLOWER in the /etc/default/passwd file indicates
the minimum number of lower-case characters that a password must have.
Edit the /etc/default/passwd file, set the MINLOWER parameter to the policy minimum password lower-case character count, which is 0.
# pfedit /etc/default/passwd
MINLOWER=0
|
Passwords require at least 1 non-alphabetic charactersrule
MINNONALPHA in the /etc/default/passwd file indicates
the minimum number of non-alphabetic characters
that a password must contain.
Non-alphabetic characters provide
some protection against dictionary-based password attacks.
The default is 0.
Edit the /etc/default/passwd file, set the MINNONALPHA parameter to the policy minimum password non-alphabetic character count, which is 1.
# pfedit /etc/default/passwd
MINNONALPHA=1
|
Passwords must have at least 0 special charactersrule
MINSPECIAL in the /etc/default/passwd file indicates
the minimum number of special characters that a password must have.
Edit the /etc/default/passwd file, set the MINSPECIAL parameter to the policy minimum password special character count, which is 0.
# pfedit /etc/default/passwd
MINSPECIAL=0
|
Passwords require at least 0 upper-case charactersrule
MINUPPER in the /etc/default/passwd file indicates
the minimum number of upper-case letters that a password must contain.
Upper-case letters provide some protection
against dictionary-based password attacks.
The default is 0.
Edit the /etc/default/passwd file, set the MINUPPER parameter to the policy minimum password upper-case character count, which is 0.
# pfedit /etc/default/passwd
MINUPPER=0
|
Passwords cannot be changed for at least three weeksruleMINWEEKS in the /etc/default/passwd file indicates the minimum number of weeks before a password can be changed. This value prevents users from reusing a password quickly. The default is unspecified. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file, set the MINWEEKS variable to 3.
|
Passwords must be changed at least every 13 weeksruleMAXWEEKS in the /etc/default/passwd file indicates the maximum number of weeks that a password can be used. This value is a balance between users remembering a new password and malicious users attacking long-term passwords. The default is unspecified. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file, set the MAXWEEKS variable to 13.
|
NAMECHECK for passwords is set to YESruleNAMECHECK in the /etc/default/passwd file indicates whether login names are checked in the files naming service. The default, YES, prevents malicious users from using a login name that is not in a local file. See the passwd(1) man page. Remediation description:
In the /etc/default/passwd file, set the NAMECHECK variable to YES.
|
Passwords must be at least 8 characters longrule
PASSLENGTH in the /etc/default/passwd file indicates
the minimum number of characters that a password must contain.
A longer password length plus a strong password hashing algorithm
provides some protection against password attacks.
Edit the /etc/default/passwd file, set the PASSLENGTH parameter to the policy minimum password length, which is 8.
# pfedit /etc/default/passwd
PASSLENGTH=8
|
Passwords allow whitespaceruleWHITESPACE in the /etc/default/login file indicates whether passwords can include the space character. The space character provides some protection against dictionary-based password attacks. The default is YES. See the passwd(1) man page. Remediation description:
In the /etc/default/login file, set the WHITESPACE variable to YES.
|
root is a roleruleBy default, root is a role. Roles cannot log in directly. Rather, a user logs in and then assumes the root role, thus providing an audit trail of who is operating as root. See the roles(1), user_attr(4), and usermod(1M) man pages. Remediation description:
If root is of type user in the /etc/user_attr file,
change the account back to a role account.
|
Role details are unchangedruleOracle Solaris ships with Role Based Access Control (RBAC). This feature enables administrators to delegate specific, limited, additional privileges and authorizations to individual users to administer parts of the system without giving them access to the root account. The provided rights databases should not be changed directly. To add rights to roles, use the roleadd and rolemod commands. These commands add entries to the /etc/user_attr file. See the profiles(1), auths(1), roles(1), rbac(5), roleadd(1M), rolemod(1M), and user_attr(4) man pages. Remediation description:
The files in /etc/user_attr.d/ should not be changed;
changes and additions should be made
using the roleadd(1M), rolemod(1M), profiles(1), auths(1),
and usermod(1M) commands.
|
Logins require passwordsrulePASSREQ in the /etc/default/login file indicates whether logins require passwords. Passwords are required for defense against computer attacks. The default is YES. See the login(1) man page. Remediation description:
In the /etc/default/login file, set the PASSREQ variable to YES.
|
shadow(4) password fields are not emptyruleThe second field in the /etc/shadow file contains passwords. When creating roles, you can easily forget to assign a password. See the shadow(4) and passwd(1) man pages. Remediation description:
Assign a password, or remove the account.
When creating roles, you can easily forget to assign a password.
|
Local users are assigned home directoriesruleUsers need a place to store and create files. A home directory enables a user to place configuration files, such as the .profile file, and ongoing work in a directory that is owned by the user. Remediation description:
Local users should have a local home directory created
automatically when useradd(1M) is run with the correct options.
Run 'useradd -D' to see the default "basedir" home directory location.
See the useradd(1M) man page.
|
root is the only user with UID=0ruleThe UID of 0 has superuser privileges. Only root should have those privileges. Remediation description:
Either remove additional UID=0 accounts
or assign different UIDs to them.
|
All groups specified in /etc/passwd are defined in /etc/groupruleUsers are assigned to at least one group and can be assigned to secondary groups. All groups must be defined in the /etc/group file. Remediation description:
All groups which are assigned to users must be defined in /etc/group.
See the man pages for group(4), groupadd(1M), groupmod(1M),
and groupdel(1M).
|
Home directories for all users existruleUsers need a place to store and create files. A home directory enables a user to place configuration files, such as the .profile file, and ongoing work in a directory that is owned by the user. Remediation description:
Local users should have a local home directory created
automatically when useradd(1M) is run with the correct options.
Run 'useradd -D' to see the default "basedir" home directory location.
See the useradd(1M) man page.
|
Reserved system accounts remain unusedruleAccounts whose ID is 100 or less are system accounts. These accounts should not be replaced or reconfigured. Remediation description:
Users should not be assigned UIDs less than 100
and existing system accounts should not be renamed or renumbered.
Undo any changes that have made involving these accounts.
See the usermod(1M) man page.
|
User home directories have appropriate permissionsruleHome directories must be writable and searchable by their owners. Typically, other users do not have rights to modify those files or add files to the user's home directory. Remediation description:
User home directories should have permissions of 750
to prevent other users
from having inappropriate access to their files.
|
User home directory ownership is correctruleThe user must own the user's home directory. Remediation description:
Home directory ownership can be changed or set
using the chown(1) command.
See the chown(1) man page.
|
Find and list duplicate GIDsruleGroups, like users, are unique. Duplicate group IDs must be removed. Remediation description:
When duplicate GIDs are identified,
use groupmod or groupdel to eliminate the duplicates.
See the man pages for group(4), groupadd(1M), groupmod(1M),
and groupdel(1M).
|
Find and list duplicate group namesruleGroups, like users, are unique. Duplicate group names must be removed. Remediation description:
When duplicate group names are identified,
use groupmod or groupdel to eliminate the duplicates.
See the man pages for group(4), groupadd(1M), groupmod(1M),
and groupdel(1M).
|
Find and list duplicate UIDsruleUsers are identified by IDs, which must be unique. Duplicate user IDs must be removed. Remediation description:
When duplicate UIDs are identified,
use usermod or userdel to eliminate the duplicates.
See the man pages for passwd(4), useradd(1M), usermod(1M),
and userdel(1M).
|
Find and list duplicate usernamesruleUsers log in by name, which must be unique. Duplicate user names must be removed. Remediation description:
When duplicate user names are identified,
use usermod or userdel to eliminate the duplicates.
See the man pages for passwd(4), useradd(1M), usermod(1M),
and userdel(1M).
|
Default system accounts are lockedruleOracle Solaris is installed with correctly configured system accounts. These accounts should not be modified. Remediation description:
Certain system accounts, such as aiuser, dladm, etc.
are shipped as "locked" and should remain that way.
Use 'passwd -l' to lock accounts that need to be locked.
|
Default system accounts are no-loginruleOracle Solaris is installed with correctly configured system accounts. These accounts should not be modified. Remediation description:
Certain system accounts, such as adm, bin, and daemon,
are shipped as "no-login" accounts and should remain that way.
Use 'passwd -N' to change accounts to "no-login".
|
Root passwords are hashed with a secure algorithmruleThe second field in the /etc/shadow file indicates the algorithm that was used to create the password hash. If the entry begins with "$5$", then password is hashed with SHA-256 algorithm. If the entry begins with "$6$", then password is hashed with SHA-512 algorithm. See the crypt.conf(4) and policy.conf(4) man pages. Remediation description:
Save the /etc/security/policy.conf file to a new name.
Edit original policy.conf file to accept 5 and 6 as values for allowed
algorithms, and either 5 or 6 as the value for the default algorithm.
Set the password for root, and verify a prefix of either $5$ or $6$
for the second field of root's entry in the /etc/shadow file.
Once verified, it is safe to remove the saved copy of policy.conf file.
|
The root PATH variable is correctruleThe root PATH variable should not include the current directory (.), or any paths not related to administration. Remediation description:
Check root's path as root with 'echo $PATH'.
root's PATH typically should not include the current directory (".")
or empty ("::").
By default root's PATH is set based on the SUPATH variable value
in the /etc/default/login file to SUPATH=/usr/bin:/usr/sbin.
Additionally, all directories in root's PATH must not be group or other writable. |
Service svc:/network/ipfilter is enabledruleIP Filter is a host-based firewall that provides stateful packet filtering and network address translation (NAT). Packet filtering provides basic protection against network-based attacks. IP Filter also includes stateless packet filtering and can create and manage address pools. See the ipf(1M) and ipfilter(5) man pages. Remediation description:Enable the IP Filter service with SMF. Also, insure that you have a reasonable rule-set for the server in question. This check looks for at least one rule that starts with "block" keyword, which should appear in most realistic rule-sets. See the ipf(1M) ipf(4) and ipfilter(5) man pages for examples.
|
Service svc:/network/firewall is enabledrulePacket Filter is a host-based firewall that provides stateful packet filtering and network address translation (NAT). Packet filtering provides basic protection against network-based attacks. Packet Filter also includes stateless packet filtering and can create and manage address pools. See the pfctl(1M) and pf.conf(5) man pages. Remediation description:Enable the PF firewall service with SMF. Also, ensure that you have a reasonable rule set for the server in question. This check looks for at least one rule that starts with the "block" keyword, which should appear in most production rule sets. See the pfctl(1M) and pf.conf(5) man pages for examples.
|
mesg(1) prevents talk(1) and write(1) access to remote terminalsruleThis program controls whether users can send messages by using write(1), talk(1) or other utilities to a terminal device. See the mesg(1) man page. Remediation description:Configure your system to deny remote users permission to send messages to the terminal. To manually remediate a failure on this check, run the following commands.
|
Inactive user accounts will be locked after 35 daysruleInactive user accounts can provide a back door into the system. User accounts should be locked after a period of inactivity. Remediation description:
Inactive user accounts can be locked in a number of ways.
MAXWEEKS can be set in the /etc/default/passwd file;
alternatively, defaults can be set using useradd.
See the useradd(1M), passwd(1), and passwd(4) man pages.
|
Check various system configuration itemsgroup |
| contains 13 rules |
The default user UMASK is 022ruleUMASK in the /etc/default/login file indicates the permissions on user files at creation. This value should not allow group or world write. The default value is 022, which allows group and world to read files owned by a user. See the login(1) man page. Remediation description:
In the /etc/default/login file, set the UMASK variable to 022.
|
Find and list remote consolesruleRemote consoles can be a source of unauthorized access. A system console should be kept physically secure and no unauthorized consoles should be defined. The "consadm -p" command displays alternate consoles across reboots. If none are defined, the command displays no output. See the consadm(1M) man page. Remediation description:
View the state of all console logins.
Disable terminal logins that are unnecessary.
See the svcs(1) and svcadm(1M) man pages.
|
root access is console-onlyruleThe root account should not be able to log in remotely, and its actions should be monitored. See the login(1) man page. Remediation description:
Ensure that the default value of CONSOLE=/dev/console
has not been changed in the /etc/default/login file.
|
DISABLETIME is set for loginsruleDISABLETIME in the /etc/default/login file is set to 20 by default. Any value greater than zero indicates the seconds before a login prompt appears after RETRIES failed login attempts. This delay can mitigate rapid-fire, brute force attacks on passwords. See the login(1) man page. Remediation description:
In the /etc/default/login file, set the DISABLETIME variable to 20.
|
SLEEPTIME following an invalid login attempt is set to 4ruleSLEEPTIME in the /etc/default/login file is set to 4 by default. This number indicates the number of seconds that elapse before the "login incorrect" message appears after an incorrect password is typed. The maximum number is 5. This delay can mitigate rapid-fire, brute force attacks on passwords. See the login(1) man page. Remediation description:
In the /etc/default/login file, set the SLEEPTIME variable to 4.
|
Name services are set to all local (files) onlyruleThe operating system uses a number of databases of information about hosts, users (passwd(4), shadow(4), and user_attr(4)), and groups. Data for these can come from a variety of sources: hostnames and host addresses, for example, can be found in /etc/hosts, NIS, LDAP, DNS, or Multicast DNS. Systems in restricted environments may be more secure if these entries are restricted to only local files, but such restriction will vary per your circumstances. See the nsswitch.conf(4) man page for more information. Remediation description:If the system does not need to use remote name services, make sure that the name service is set to local files only. The check will not pass unless all name services are set to "files" in /etc/nsswitch.conf. If your configuration demands that you have non-local name services, then you may want to turn this check off for this profile. You can also see the nsswitch.conf(4) man page for detailed information on how to configure your name services. Below are some examples of the commands to run for in order to configure a name service to local files only:
# svccfg -s name-service/switch setprop config/default = string: "files"
# svccfg -s name-service/switch setprop config/host = string: "files"
# svccfg -s name-service/switch setprop config/passwd = string: "files"
# svccfg -s name-service/switch setprop config/group = string: "files"
# svccfg -s name-service/switch:default refresh
|
Address Space Layout Randomization (ASLR) is enabledrule
Oracle Solaris tags many of its userland binaries
to enable Address Space Layout Randomization (ASLR).
ASLR randomizes the starting address of key parts of an address space.
This security defense mechanism can cause
Return Oriented Programming (ROP) attacks to fail
when they try to exploit software vulnerabilities.
See the sxadm(1M) man page.
Restore ASLR to the default configuration.
To manually remediate this failure, perform the following actions:
|
Booting the system should require a passwordruleThe GRUB menu, the BIOS, and the eeprom should be password-protected to prevent configuration by unauthorized users. The BIOS protections prevent booting from an external device, such as a USB flash drive. Remediation description:
On an x86, create passwords for the BIOS and the GRUB menu.
On SPARC, protect the eeprom with a password.
|
Stacks are non-executablerule
Programs read and write data on the stack.
Typically, they execute from read-only portions of memory
that are specifically designated for code.
Some attacks that cause buffers on the stack to overflow
try to insert new code on the stack and cause the program to execute it.
This security extension removes execute permission from the stack memory,
preventing these attacks from succeeding.
See the sxadm(1M) man page.
To manually remediate this failure, perform the following actions:
|
Heaps are non-executablerulePrograms read and write data on the heap. Typically, they execute from read-only portions of memory that are specifically designated for code. Some attacks that cause buffers on the heap to overflow try to insert new code on the heap and cause the program to execute it. Removing execute permission from the heap memory prevents these attacks from succeeding. Properly written programs may function correctly without using executable heaps, but some older programs may rely on heap execution. Setting model=tagged-files (or default) ensures that unexpected heap execution attempts are prevented and enabling the nxheap log ensures that such attempts are recorded. Remediation description:To manually remediate this failure, perform the following actions:
|
Remote serial logins are disabledruleSerial logins can be a source of unauthorized access. Login services should not be enabled for serial ports that are not required to support the purpose of the system. Remediation description:
View the state of all console logins.
Disable terminal logins that are unnecessary.
See the svcs(1) and svcadm(1M) man pages.
|
Service svc:/network/ldap/client:default is in disabled staterule
The ldap client service is required to connect
to an LDAP server. See ldapclient(1M)
To manually remediate this failure, set the service state to disabled using the appropriate command.
|
ldap client transport uses tls:any protocolruleThe ldap client transport should use tls:any protocol. |
Verify audit configurationgroup
Auditing is the collecting of data
about the use of system resources.
The audit data provides a record of security-related system events.
This data can then be used to assign responsibility for actions
that take place on a host.
|
| contains 4 rules |
Check all default audit propertiesruleCheck all default audit properties |
The auditd(1M) daemon is enabledruleAuditing is a service, svc:/system/auditd, that is enabled by default and should not be disabled. See the audit(1M) man page. Remediation description:
An administrator with the Audit Control rights profile
can enable auditing.
Configure auditing per the Audit Parameters and Role Audit tests,
then enable or refresh auditing.
|
Audit parameters are set to recommended valuesruleAt minimum, events in the lo class are audited and audit policy is set to argv,cnt. Add audit classes and policy per your site's security requirements. See the auditconfig(1M) man page. Remediation description:An administrator with the Audit Configuration rights profile can get and set audit parameters. This check validates that auditing is enabled for a recommended set of audit flags and root audit flags. To manually remediate a failure on this check, you run the following commands:
|
All roles are audited with the "cusa" audit classruleThe cusa audit class contains events that cover administrative actions that could affect the system's security posture. See the audit_class(4), audit_event(4), rolemod(1M), and userattr(1) man pages. Remediation description:
Check that all roles are being audited with the cusa audit class.
By default, only the root role can set audit flags
for individual accounts.
|