Guide to the Secure Configuration of Debian 8
with profile Profile for ANSSI DAT-NT28 Minimal LevelThis profile contains items to be applied systematically.
https://www.open-scap.org/security-policies/scap-security-guide
Providing system administrators with such guidance informs them how to securely configure systems under their control in a variety of network roles. Policy makers and baseline creators can use this catalog of settings, with its associated references to higher-level security control catalogs, in order to assist them in security baseline creation. This guide is a italics="catalog, not a checklist," and satisfaction of every item is not likely to be possible or sensible in many operational scenarios. However, the XCCDF format enables granular selection and adjustment of settings, and their association with OVAL and OCIL content provides an automated checking capability. Transformations of this document, and its associated automated checking content, are capable of providing baselines that meet a diverse set of policy objectives. Some example XCCDF italics="Profiles", which are selections of items that form checklists and can be used as baselines, are available with this guide. They can be processed, in an automated fashion, with tools that support the Security Content Automation Protocol (SCAP). The DISA STIG for Debian 8, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
Profile Title | Profile for ANSSI DAT-NT28 Minimal Level |
---|---|
Profile ID | xccdf_org.ssgproject.content_profile_anssi_np_nt28_minimal |
Revision History
Current version: 0.1.39
- draft (as of 2018-07-26)
Platforms
- cpe:/o:debianproject:debian:8
Table of Contents
Checklist
contains 16 rules | ||||||||||||||||||
Services [ref]groupThe best protection against vulnerable software is running less software. This section describes how to review
the software which Debian 8 installs on a system and disable software which is not needed. It
then enumerates the software packages installed on a default Debian 8 system and provides guidance about which
ones can be safely disabled.
| ||||||||||||||||||
contains 6 rules | ||||||||||||||||||
Deprecated services [ref]groupSome deprecated software services impact the overall system security due to their behavior (leak of confidentiality in network exchange, usage as uncontrolled communication channel, risk associated with the service due to its old age, etc. | ||||||||||||||||||
contains 4 rules | ||||||||||||||||||
Uninstall the nis package [ref]ruleThe support for Yellowpages should not be installed unless it is required. Rationale:NIS is the historical SUN service for central account management, more and more replaced by LDAP. NIS does not support efficiently security constraints, ACL, etc. and should not be used. Severity: low Identifiers: CCE-
| ||||||||||||||||||
Uninstall the inet-based telnet server [ref]ruleThe inet-based telnet daemon should be uninstalled. Rationale:telnet allows clear text communications, and does not protect any data transmission between client and server. Any confidential data can be listened and no integrity checking is made. Severity: high Identifiers: CCE- References: NT007(R03), AC-17(8), CM-7
| ||||||||||||||||||
Uninstall the ssl compliant telnet server [ref]ruleThe telnet daemon, even with ssl support, should be uninstalled. Rationale:telnet, even with ssl support, should not be installed. When remote shell is required, up-to-date ssh daemon can be used. Severity: high Identifiers: CCE- References: NT007(R02), AC-17(8), CM-7
| ||||||||||||||||||
Uninstall the telnet server [ref]ruleThe telnet daemon should be uninstalled. Rationale:telnet allows clear text communications, and does not protect any data transmission between client and server. Any confidential data can be listened and no integrity checking is made. Severity: high Identifiers: CCE- References: NT007(R03), AC-17(8), CM-7
| ||||||||||||||||||
APT service configuration [ref]groupThe apt service manage the package management and update of the whole system. Its configuration need to be properly defined to ensure efficient security updates, packages and repository authentication and proper lifecycle management. | ||||||||||||||||||
contains 2 rules | ||||||||||||||||||
Disable unauthenticated repositories in APT configuration [ref]ruleUnauthenticated repositories should not be used for updates. Rationale:Repositories hosts all packages that will be intsalled on the system during update. If a repository is not authenticated, the associated packages can't be trusted, and then should not be installed localy. Severity: unknown References: NT28(R15) | ||||||||||||||||||
Ensure that official distribution repositories are used [ref]ruleCheck that official Debian repositories, including security repository, are configured in apt. Rationale:The Debian distribution deliver DSA (Debian Security Announce), through the official Debian security repository, to correct various vulnerabilities impacting the Debian packages. Using the official repositories is the best way to ensure that the Debian updates are integrated soon enough. Severity: unknown References: NT28(R15) | ||||||||||||||||||
System Settings [ref]groupContains rules that check correct system settings. | ||||||||||||||||||
contains 10 rules | ||||||||||||||||||
Configure Syslog [ref]groupThe syslog service has been the default Unix logging mechanism for
many years. It has a number of downsides, including inconsistent log format,
lack of authentication for received messages, and lack of authentication,
encryption, or reliable transport for messages sent over a network. However,
due to its long history, syslog is a de facto standard which is supported by
almost all Unix applications.
| ||||||||||||||||||
contains 4 rules | ||||||||||||||||||
contains 2 rules | ||||||||||||||||||
Ensure syslog-ng is Installed [ref]rulesyslog-ng can be installed in replacement of rsyslog.
The # apt-get install syslog-ng-coreRationale: The syslog-ng-core package provides the syslog-ng daemon, which provides system logging services. Severity: medium References: NT28(R46), NT28(R5), 5.1.1, CCI-001311, CCI-001312, AU-9(2) | ||||||||||||||||||
Enable syslog-ng Service [ref]ruleThe $ sudo chkconfig --level 2345 syslog-ng onRationale: The Severity: medium References: NT28(R46), NT28(R5), 5.1.2, CCI-001311, CCI-001312, CCI-001557, CCI-001851, AU-4(1), AU-12 | ||||||||||||||||||
Enable rsyslog Service [ref]ruleThe $ sudo chkconfig --level 2345 rsyslog onRationale: The Severity: medium References: NT28(R46), NT28(R5), 5.1.2, CCI-001311, CCI-001312, CCI-001557, CCI-001851, AU-4(1), AU-12
| ||||||||||||||||||
Ensure rsyslog is Installed [ref]ruleRsyslog is installed by default.
The # apt-get install rsyslogRationale: The rsyslog package provides the rsyslog daemon, which provides system logging services. Severity: medium References: NT28(R46), NT28(R5), 5.1.1, CCI-001311, CCI-001312, AU-9(2)
| ||||||||||||||||||
Access Control using sudo [ref]group
| ||||||||||||||||||
contains 2 rules | ||||||||||||||||||
Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate [ref]ruleThe sudo Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
Severity: medium | ||||||||||||||||||
Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD [ref]ruleThe sudo Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
Severity: medium | ||||||||||||||||||
File Permissions and Masks [ref]groupTraditional Unix security relies heavily on file and
directory permissions to prevent unauthorized users from reading or
modifying files to which they should not have access.
$ mount -t xfs | awk '{print $3}'For any systems that use a different local filesystem type, modify this command as appropriate. | ||||||||||||||||||
contains 4 rules | ||||||||||||||||||
Verify Permissions on Important Files and Directories [ref]groupPermissions for many files on a system must be set restrictively to ensure sensitive information is properly protected. This section discusses important permission restrictions which can be verified to ensure that no harmful discrepancies have arisen. | ||||||||||||||||||
contains 4 rules | ||||||||||||||||||
Verify Permissions on Files with Local Account Information and Credentials [ref]groupThe default restrictive permissions for files which act as
important security databases such as | ||||||||||||||||||
contains 4 rules | ||||||||||||||||||
Verify Permissions and ownership on group File [ref]rule
To properly set the permissions of $ sudo chmod 0644 /etc/passwdTo properly set the owner of /etc/passwd , run the command:
$ sudo chown root /etc/passwdTo properly set the group owner of /etc/passwd , run the command:
$ sudo chgrp root /etc/passwdRationale: The Severity: medium References: AC-6
| ||||||||||||||||||
Verify Permissions and ownership on shadow File [ref]rule
To properly set the permissions of $ sudo chmod 0640 /etc/shadowTo properly set the owner of /etc/shadow , run the command:
$ sudo chown root /etc/shadowTo properly set the group owner of /etc/shadow , run the command:
$ sudo chgrp shadow /etc/shadowRationale: The Severity: medium
| ||||||||||||||||||
Verify Permissions and ownership on gshadow File [ref]rule
To properly set the permissions of $ sudo chmod 0640 /etc/gshadowTo properly set the owner of /etc/gshadow , run the command:
$ sudo chown root /etc/gshadowTo properly set the group owner of /etc/gshadow , run the command:
$ sudo chgrp shadow /etc/gshadowRationale: The Severity: medium
| ||||||||||||||||||
Verify Permissions and ownership on passwd File [ref]rule
To properly set the permissions of $ sudo chmod 0644 /etc/passwdTo properly set the owner of /etc/passwd , run the command:
$ sudo chown root /etc/passwdTo properly set the group owner of /etc/passwd , run the command:
$ sudo chgrp root /etc/passwdRationale: The Severity: medium References: AC-6
|