You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Plans for next generation linux desktop support.

 

Desktop Linux Distributions supported at SLAC

  1. Ubuntu 16.04 LTS, codename "Xenial Xerus"

    1. Long term support (LTS) releases are for 5 years. 

    2. 16.04 = YY.MM of release date (released April 2016)
    3. End of Life date is April 2021

    4. It is possible to upgrade (complete reinstall not required) from one LTS distro to the next (eg, 14.04 -> 16.04)

  2. CentOS 7
    1. 10 year support lifetime
    2. End of Life date is June 2024
    3. Red Hat sponsors the CentOS project: in 2014 CentOS officially joined forces with Red Hat

Desktop Linux Authentication Configuration

  • Windows Active Directory will be used for authentication
  • This aligns with the SCS long term plan to reduce dependence on Unix Heimdal Kerberos

 

 

Security Services/Features needed

These are taken directly from the SLAC MinSec Policy (which has 11 items that match the 11 items below)

These will be configured using Chef Configuration Management and Compliance scanning/reporting

  1. Anti-virus Software
    1. Install and configure ClamAV (optional, since not in moderate enclave)
  2. Application Patches
    1. Configure automatic updates for Applications via apt/yum config
  3. Authentication
    1. Kerberos and SSH will be configured and used for encrypted authentication
    2. Use Chef Compliance to scan for any enabled insecure server protocols such as telnet and ftp
  4. Logging
    1. Configure syslog to log to central syslog server, and enable logging locally to /var/log/everything
  5. Network Services
    1. Check for inappropriate network services via Chef Compliance
  6. Operating System Patches
    1. Configure automatic updates for OS patches via apt/yum 
  7. Passwords
    1. To deal with any local accounts that might get created on the desktop, we will configure local password quality checks and policies (expiration time, etc) according to SLAC password policy.  Ideally Microsoft AD accounts will be used and no local accounts will be required.
    2. Global account password policies are handled by Active Directory, not the local desktop configuration.  Windows AD passwords will be changed in the same way they are being done now.
  8. Baseline Security Configuration
    1. CIS Level 1 Workstation Profile will be used (modified where appropriate)
    2. Chef Compliance scanning can report on compliance level for our baseline
    3. PDFs are available for the CIS Benchmarks for Ubuntu 16.04 and CentOS 7
  9. Training
    1. No additional changes needed (same SLAC Training Assignments are required)
  10. Security Scanning
    1. Local scanner account will be enabled to allow authenticated Nessus scans by Cyber Security team
  11. Banner
    1. The SLAC DOE login banner will be configured

Additional Operating System Configuration needed

These will be configured using Chef Configuration Management and Compliance scanning/reporting

  1. NTP client
  2. DNS client
  3. logrotate
  4. mailgateway (mail client)
  5. sudo
  6. shells
  7. unixadmins (sets up unix-admin logins and scanner account)
  8. root (manage root password and root home environment)

 

Reference Documents

  • No labels