...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Anti-Virus Considerations
Anchor | ||||
---|---|---|---|---|
|
You may choose any proven anti-virus product. One option is ClamAV.
...
CentOS (command line):
Install and use the yum-security plugin.
To install the plugin run:
...
borderColor | green |
---|---|
borderStyle | solid |
For UT devices running RHEL or CentOS installations, Cisco AMP - (only for UT systems) is another option. Please email help@ece.utexas.edu and provide the UT asset tag number (silver sticker The Property of The University of Texas at Austin) for further details. Your system will need to be verified it is property of the University.
Anchor | ||||
---|---|---|---|---|
|
Applying Security Updates
CentOS (command line):
Install and use the yum-security plugin.
To install the plugin run:
Panel | ||||
---|---|---|---|---|
| ||||
sudo yum install yum-security |
To list all updates that are security relevant, and get a reutrn code on whether there are security updates use:
...
Panel | ||||
---|---|---|---|---|
| ||||
sudo apt-get upgrade |
Anchor | ||
---|---|---|
|
|
Change SSH Default Port
...
Depending on your Linux distribution, the configuration file for SSH may reside in different locations. Please perform a simple web search for instructions on how to change the port used by SSH on your specific Linux distribution. Below is an example that may guide you through the process.
...
# What ports, IPs and protocols we listen for
Port 491522002
It is recommended that a commonly known port number or a port number currently in use by another application is not selected. This may cause technical issues with port allocation in the future. A good secure range of ports you may want to use are ports from 49152 through 65535.
...
- Verify SSH is listening on the new port by connecting to it. Note how the port number now needs to be declared.
ssh username@hostname -p 491522002
...
Anchor | ||||
---|---|---|---|---|
|
Configure NTP Server
The Information Security Office (ISO) has been proactively scanning systems on the UT wired network for outdated versions of the NTP (Network Time Protocol) service running. Systems running a vulnerable version of NTP can be compromised, thus begin participation in NTP-based distributed denial of service (DDOS) attacks targeting various endpoints across the internet. This ultimately leads to an inordinate amount of network usage from the system, and it will be identified from the ISO and the ITS-Networking group.
...
Panel | ||||
---|---|---|---|---|
| ||||
Example 1: edit /etc/inet/ntp.client -> ntp.conf added: #added for DDoS prevention - don't allow any machine, except those w/o flags Example 2 (with additional comments): # Permit time synchronization with our time source, but do not #restrict default kod nomodify notrap nopeer noquery
# Permit all access over the loopback interface. This could restrict 127.0.0.1 ~~~~~~~~`` default servers are commented out # Use public servers from the pool.ntp.org project. |
Anchor | ||
---|---|---|
|
|
Configure Portmap (RPC) Service
...
Panel | ||||
---|---|---|---|---|
| ||||
|
...
Many distributions of Linux offer various distributions such as desktop, workstation, or server editions. Please ensure you understand the differences in each edition and what additional services are installed/running by default in each addition. Keep in mind unknown services running without proper configuration are vulnerable and lead system compromises.
Also, be sure the edition chosen offers a long-term support life cycle. For example, Ubuntu publishes the current life cycle for their latest distributions. If you run Ubuntu, or are considering Ubuntu, refer to the product support life cycle below.
Source: https://wiki.ubuntu.com/LTSA system allows its portmap service to be queried from the public Internet. Portmapper is an RPC service, which always listens on tcp and udp 111, and is used to map other RPC
services (such as nfs, nlockmgr, quotad, mountd, etc.) to their corresponding port number on the server. When a remote host makes an RPC call to that server, it first consults with
portmap to determine where the RPC server is listening.Querying portmapper is a small request (~82 bytes via UDP) which generates a large response (7x to 28x amplification), which
makes it a good candidate for DDoS attacks--especially considering its prevalence among virtually all modern Unix systems.
Portmap must be restricted from the public internet with access controls or authentication.
The Prevention
--------------
Panel | ||||
---|---|---|---|---|
| ||||
Option 1: Uninstall NFS server, NFS client, and Portmapper (RPCbind) Open a command-line terminal and then type the following command: $ sudo apt-get --purge remove nfs-kernel-server nfs-common rpcbind
Option 2: Portmap lockdown via TCP Wrapper **Note** Solaris system TCP Wrappers not are enabled by default. Open a command-line terminal and enter the following commands to enable rpcbind TCP Wrappers:
# svcadm refresh rpc/bind (Continue following the instructions below) For all other Linux systems: Open a command-line terminal and then type the following command: $ sudo nano /etc/hosts.allowAdd the following lines: rpcbind: 146.6.101.0/255.255.255.0 Save the changes made to the file. Type the following command: $ sudo nano /etc/hosts.deny Add the following lines: rpcbind: ALL Save the changes made to the file. |
Anchor | ||||
---|---|---|---|---|
|
Distribution Updates
Many distributions of Linux offer various distributions such as desktop, workstation, or server editions. Please ensure you understand the differences in each edition and what additional services are installed/running by default in each addition. Keep in mind unknown services running without proper configuration are vulnerable and lead system compromises.
Also, be sure the edition chosen offers a long-term support life cycle. For example, Ubuntu publishes the current life cycle for their latest distributions. If you run Ubuntu, or are considering Ubuntu, refer to the product support life cycle below.
Source: https://wiki.ubuntu.com/LTS
Anchor | ||||
---|---|---|---|---|
|
Enable Firewall
Ubuntu: https://help.ubuntu.com/community/UFW
RHEL/CentOS: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-using_firewalls
Anchor | ||||
---|---|---|---|---|
|
Encryption: LUKS
Encryption is mandatory for all desktops and laptops with a Linux non-server operating system.
Refer to documentation at - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-encryption
Note: It is preferred that encryption is enabled during the installation of the operating system. Initiating encryption after the system has been deployed will wipe all the user's data.
Anchor | ||||
---|---|---|---|---|
|
Implement Deny Hosts
DenyHosts is a script intended to be run by Linux system administrators to help prevent SSH server attacks (also known as dictionary based attacks and brute force attacks) - http://denyhosts.sourceforge.net/
...
/etc/hosts.allow
sshd:hostname (allowed name of machine or IP address)
and /etc/hosts.deny
sshd:ALL
Anchor | ||||
---|---|---|---|---|
|
Limit SSH Access to Campus Network
...
Example of IP Tables configuration that will only allow UT campus networks to access a system remotely via SSH. The networks listed below include various wired, wireless, and VPN networks.
Note: To access these systems from off-campus, users will need to utilize the UT VPN client available at https://vpn.utexas.edu
Panel |
---|
:INPUT ACCEPT [0:0] |
Anchor | ||||
---|---|---|---|---|
|
Password Complexity
On most Linux systems, you can use PAM to enforce password complexity. If you have a file in RHEL/CentOS named /etc/pam.d/system-auth-ac
Example: Modify pam passwd requirements, length of 12 with special, upper, and lower cases plus a number:
/etc/pam.d/system-auth-ac
#password requisite pam_cracklib.so try_first_pass retry=3 type=
password requisite pam_cracklib.so try_first_pass retry=3 minlen=10 ucredit=-1 dcredit=-1 ocredit=-1 lcredit=-1
/etc/login.defs
PASS_MAX_DAYS 9999999
PASS_MIN_DAYS 0
PASS_MIN_LEN 12
PASS_WARN_AGE 7
To change some of the defaults at user creation time
/etc/default/useradd
GROUP=1000 <-setting a default group doesn't seem to work. specify with useradd -g <groupname> <username>
#HOME=/home
HOME=/group/users
INACTIVE=-1
EXPIRE=
SHELL=/bin/bash
SKEL=/etc/skel
#CREATE_MAIL_SPOOL=yes
CREATE_MAIL_SPOOL=no
Anchor | ||||
---|---|---|---|---|
|
System Accounts
Files/Directory Permissions/Access
- Enable system accounting (install package sysstat).
- Integrity checking of system accounts, group memberships, and their associated privileges should be enabled and tested.
- Check in /etc/sudoers to see who has sudo rights
- Check in /etc/groups to see what groups your users belong to
- Check in /etc/passwd and/or /etc/shadow for blank passwords
- All administrator or root access must be logged.
System Access, Authentication, and Authorization
- Enable the terminal security file to restrict root logins to system console only. Do not allow root logins via SSH.
- Ensure the following are set in /etc/pam.d/other:
auth required pam_deny.so
auth required pam_warn.so
account required pam_deny.so
account required pam_warn.so
password required pam_deny.so
password required pam_warn.so
session required pam_deny.so
session required pam_warn.so
session required pam_deny.so
Warn will report alerts to syslog.