The Top 4 in a Linux Environment
Download ACSC Protect Notice, The Top 4 in a Linux Environment (PDF), April 2016
- This document has been developed by the Australian Signals Directorate (ASD) to assist organisations understand how the Top 4 strategies of ASD’s Strategies to Mitigate Targeted Cyber Intrusions can be implemented in a Linux environment.
- While this document refers specifically to Linux environments, the guidance presented is equally applicable to all Unix-style environments.
- This document is intended for cyber security professionals as well as ICT decision-makers, architects, designers and support staff responsible for Linux assets on their corporate network.
Implementing the Top 4 on Linux
- The Top 4 strategy that poses the most challenge on Linux is application whitelisting, while the remaining three strategies can be implemented in a similar manner to Microsoft Windows.
- While Linux doesn't natively offer application whitelisting functionality, and the choices for application whitelisting on Linux are sparse compared to Microsoft Windows, a small number of vendors do offer third-party application whitelisting solutions. However, organisations need to consider the specific Linux distributions they are using and how application whitelisting solutions may impact other security controls. For example, deploying the latest kernel updates may be problematic on certain Linux distributions if the application whitelisting solutions don’t support the latest kernel version and may be especially problematic in environments where custom kernels are in use.
Application and operating system patching
- Patching Linux is easy to achieve when combined with locally hosted repositories and scheduled scripts. Some Linux distributions now provide administrative servers that allow control of machines from a centralised location to push updates as necessary. This can enhance the ability of an organisation to efficiently and effectively manage their change management process while ensuring timely patching occurs. Linux system administrators should check with their vendor if they are unsure how to best handle application and operating system patching in a Linux environment.
Restricting administrative privileges
- Restricting administrative privileges in a Linux environment can be achieved through a combination of controlling the number of users with administrative privileges, controlling the access that those users have and auditing the actions of those users.
- Determining the number of users with administrative privileges on Linux machines is relatively simple. Auditing the number of users with the ability to elevate permissions, or having privileged accounts, can be achieved by listing groups and group memberships of users on each Linux machine to check which users belong to each group. The 'sudoers' group and any other specific admin groups for a given distribution must be considered when conducting this audit. Additionally, organisations should ensure users do not have a user ID (UID) or group ID (GID) of 0, which would grant that specific user root access on that machine.
- In addition to minimising the number of users with administrative privileges, organisations should ensure they enforce a policy of using the sudo command when administering Linux servers as opposed to logging in locally or remotely with an administrative account. This will not only prevent the use of shared accounts, but also enhance the ability of an organisation to audit administrative access and encourage system administrator accountability.
General hardening for Linux
- Given the difficulty in implementing application whitelisting on Linux, the following strategies can be implemented to assist with reducing the residual risk of the exploitation of Linux machines. Note, this list is not exhaustive and does not take into account specific use cases or differences between Linux distributions.
- Use unique restricted users for key at-risk services (eg, Apache software runs under a restricted ‘apache’ user role).
- Apply additional forms of security policy enforcement such as SELinux or AppArmor.
- Implement appropriately hardened security configurations, and permissions of key configuration files (eg, /etc/security/access.conf, /etc/hosts, /etc/nsswitch.conf).
- Use the 'noexec' parameter to mount partitions which users have write access to.
- Implement software-based firewalls for both internal and external network interfaces.
- Perform tasks with least privileges.
- Centralise auditing and analysis of system and application logs.
- Disable unrequired operating system functionality.
- Implement specific configurations based on server role (eg, running Apache webserver, harden as per Apache hardening guide).
- As far as practical, implement vendor security guidance for specific Linux distributions.
- Given the difficulty in implementing application whitelisting on Linux, organisations may choose to address as a higher priority application and operating system patching, restricting administrative privileges and implementing general system hardening measures.
The Australian Government Information Security Manual (ISM) assists in the protection of official government information that is processed, stored or communicated by Australian government systems.
ASD's Strategies to Mitigate Targeted Cyber Intrusions complements the advice in the ISM.
Red Hat Enterprise Linux 7 provides additional guidance on hardening Linux in their Security Guide and SELinux User’s and Administrator’s Guide.
SUSE Linux Enterprise Server 12 provides additional guidance on hardening SUSE in their Security Guide.
Canonical provides additional guidance on hardening Ubuntu in their Basic Ubuntu Security Guide and Ubuntu Server Guide: Security.
Australian government customers with questions regarding this advice can contact ASD Advice and Assistance.
Australian businesses and other private sector organisations seeking further information should contact CERT Australia.