From 5ec78a327921a8d05ee16d31dd65cfa364ef680d Mon Sep 17 00:00:00 2001 From: Automated Update Date: Sat, 20 Jul 2024 00:05:15 +0000 Subject: [PATCH] Update Benchmarks --- ...untu_18-04_LTS_STIG_V2R15_Manual-xccdf.xml | 3706 +++++++++++++ ..._CounterACT_NDM_STIG_V1R2_Manual-xccdf.xml | 540 ++ ...ficeSystem_2013_STIG_V2R2_Manual-xccdf.xml | 225 + ...owerPoint_2010_STIG_V1R11_Manual-xccdf.xml | 269 + ...PowerPoint_2013_STIG_V1R7_Manual-xccdf.xml | 266 + ...S_Project_2010_STIG_V1R10_Manual-xccdf.xml | 89 + ...MS_Project_2013_STIG_V1R5_Manual-xccdf.xml | 98 + ...Publisher_2010_STIG_V1R12_Manual-xccdf.xml | 110 + ..._Publisher_2013_STIG_V1R6_Manual-xccdf.xml | 105 + ...r_2014_Database_STIG_V1R7_Manual-xccdf.xml | 1813 ++++++ ...r_2014_Instance_STIG_V2R4_Manual-xccdf.xml | 3245 +++++++++++ ...U_MS_Visio_2013_STIG_V1R5_Manual-xccdf.xml | 91 + .../DISA/U_RHEL_7_STIG_V3R15_Manual-xccdf.xml | 4849 +++++++++++++++++ .../DISA/U_SLES_15_STIG_V2R1_Manual-xccdf.xml | 4464 +++++++++++++++ .../DISA/U_VPN_SRG_V3R1_Manual-xccdf.xml | 579 ++ stigs.json | 989 ++-- 16 files changed, 20999 insertions(+), 439 deletions(-) create mode 100644 benchmarks/DISA/U_CAN_Ubuntu_18-04_LTS_STIG_V2R15_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_ForeScout_CounterACT_NDM_STIG_V1R2_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_OfficeSystem_2013_STIG_V2R2_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_PowerPoint_2010_STIG_V1R11_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_PowerPoint_2013_STIG_V1R7_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_Project_2010_STIG_V1R10_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_Project_2013_STIG_V1R5_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_Publisher_2010_STIG_V1R12_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_Publisher_2013_STIG_V1R6_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_SQL_Server_2014_Database_STIG_V1R7_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_SQL_Server_2014_Instance_STIG_V2R4_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_MS_Visio_2013_STIG_V1R5_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_RHEL_7_STIG_V3R15_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_SLES_15_STIG_V2R1_Manual-xccdf.xml create mode 100644 benchmarks/DISA/U_VPN_SRG_V3R1_Manual-xccdf.xml diff --git a/benchmarks/DISA/U_CAN_Ubuntu_18-04_LTS_STIG_V2R15_Manual-xccdf.xml b/benchmarks/DISA/U_CAN_Ubuntu_18-04_LTS_STIG_V2R15_Manual-xccdf.xml new file mode 100644 index 000000000..6e2dd69a0 --- /dev/null +++ b/benchmarks/DISA/U_CAN_Ubuntu_18-04_LTS_STIG_V2R15_Manual-xccdf.xml @@ -0,0 +1,3706 @@ +acceptedCanonical Ubuntu 18.04 LTS Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 15 Benchmark Date: 24 Jul 20243.51.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>UBTU-18-010000Ubuntu operating systems booted with a BIOS must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. + +Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100519SV-109623CCI-000213Configure the system to require a password for authentication upon booting into single-user and maintenance modes. + +Generate an encrypted (grub) password for root with the following command: +$ grub-mkpasswd-pbkdf2 +Enter Password: +Reenter Password: +PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG + +Using the hash from the output, modify the "/etc/grub.d/40_custom" file with the following command to add a boot password: +$ sudo sed -i '$i set superusers=\"root\"\npassword_pbkdf2 root <hash>' /etc/grub.d/40_custom + +where <hash> is the hash generated by grub-mkpasswd-pbdkf2 command. + +Configure grub to only require a password when accessing the bootloader: +$ sudo sed -i -E 's/^CLASS="[^"]*/& --unrestricted/' /etc/grub.d/10_linux + +Generate an updated "grub.conf" file with the new password by using the following command: +$ update-grubVerify that an encrypted root password is set. This is only applicable on systems that use a basic Input/Output System BIOS. + +Run the following command to verify the encrypted password is set: +$ grep –i password /boot/grub/grub.cfg + +password_pbkdf2 root grub.pbkdf2.sha512.10000.MFU48934NJA87HF8NSD34493GDHF84NG + +If the root password entry does not begin with “password_pbkdf2”, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>UBTU-18-010001Ubuntu operating systems booted with United Extensible Firmware Interface (UEFI) implemented must require authentication upon booting into single-user mode and maintenance.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. + +Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100521SV-109625CCI-000213Configure the system to require a password for authentication upon booting into single-user and maintenance modes. + +Generate an encrypted (grub) password for root with the following command: +$ grub-mkpasswd-pbkdf2 +Enter Password: +Reenter Password: +PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG + +Using the hash from the output, modify the "/etc/grub.d/40_custom" file with the following command to add a boot password: +$ sudo sed -i '$i set superusers=\"root\"\npassword_pbkdf2 root <hash>' /etc/grub.d/40_custom + +where <hash> is the hash generated by grub-mkpasswd-pbdkf2 command. + +Configure grub to only require a password when accessing the bootloader: +$ sudo sed -i -E 's/^CLASS="[^"]*/& --unrestricted/' /etc/grub.d/10_linux + +Generate an updated "grub.conf" file with the new password by using the following command: +$ grub-mkconfig -o /boot/efi/EFI/ubuntu/grub.cfgVerify that an encrypted root password is set. This is only applicable on Ubuntu operating systems that use UEFI. + +Run the following command to verify the encrypted password is set: +$ grep -i password /boot/efi/EFI/ubuntu/grub.cfg +password_pbkdf2 root grub.pbkdf2.sha512.10000.VeryLongString + +If the root password entry does not begin with “password_pbkdf2”, this is a finding.SRG-OS-000254-GPOS-00095<GroupDescription></GroupDescription>UBTU-18-010002The Ubuntu operating system must initiate session audits at system startup.<VulnDiscussion>If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100523SV-109627CCI-001464Configure the Ubuntu operating system to produce audit records at system startup. + +Edit /etc/default/grub file and add "audit=1" to the GRUB_CMDLINE_LINUX option. + +To update the grub config file run, + +sudo update-grubVerify the Ubuntu operating system enables auditing at system startup. + +Check that the auditing is enabled in grub with the following command: + +grep "^\s*linux" /boot/grub/grub.cfg + +linux /vmlinuz-4.15.0-55-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash $vt_handoff audit=1 +linux /vmlinuz-4.15.0-55-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset audit=1 + +If any linux lines do not contain "audit=1", this is a finding.SRG-OS-000185-GPOS-00079<GroupDescription></GroupDescription>UBTU-18-010003Ubuntu operating systems handling data requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.<VulnDiscussion>Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system. + +This requirement addresses protection of user-generated data, as well as Ubuntu operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109629V-100525CCI-001199CCI-002475CCI-002476To encrypt an entire partition, dedicate a partition for encryption in the partition layout. + +Note: Encrypting a partition in an already-installed system is more difficult because the existing partitions must be resized and changed.If there is a documented and approved reason for not having data-at-rest encryption, this requirement is Not Applicable. + +Verify the Ubuntu operating system prevents unauthorized disclosure or modification of all information requiring at rest protection by using disk encryption. + +Determine the partition layout for the system with the following command: + +#sudo fdisk -l +(..) +Disk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors +Units: sectors of 1 * 512 = 512 bytes +Sector size (logical/physical): 512 bytes / 512 bytes +I/O size (minimum/optimal): 512 bytes / 512 bytes +Disklabel type: gpt +Disk identifier: 83298450-B4E3-4B19-A9E4-7DF147A5FEFB + +Device Start End Sectors Size Type +/dev/vda1 2048 4095 2048 1M BIOS boot +/dev/vda2 4096 2101247 2097152 1G Linux filesystem +/dev/vda3 2101248 31455231 29353984 14G Linux filesystem +(...) + +Verify that the system partitions are all encrypted with the following command: + +# more /etc/crypttab + +Every persistent disk partition present must have an entry in the file. If any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) are not listed, this is a finding.SRG-OS-000478-GPOS-00223<GroupDescription></GroupDescription>UBTU-18-010005The Ubuntu operating system must implement NIST FIPS-validated cryptography to protect classified information and for the following: to provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. + +Satisfies: SRG-OS-000478-GPOS-00223, SRG-OS-000396-GPOS-00176</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100527SV-109631CCI-002450Configure the system to run in FIPS mode. Add "fips=1" to the kernel parameter during the Ubuntu operating systems install. + +Enabling a FIPS mode on a pre-existing system involves a number of modifications to the Ubuntu operating system. Refer to the Ubuntu Server 18.04 FIPS 140-2 security policy document for instructions. A subscription to the "Ubuntu Pro" plan is required to obtain the FIPS Kernel cryptographic modules and enable FIPS.Verify the system is configured to run in FIPS mode. + +Check that the system is configured to run in FIPS mode with the following command: + +# grep -i 1 /proc/sys/crypto/fips_enabled +1 + +If a value of "1" is not returned, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>UBTU-18-010006The Ubuntu operating system must immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.<VulnDiscussion>If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109633V-100529CCI-001855Edit /etc/audit/auditd.conf and set the space_left_action parameter to "exec" or "email". + +If the space_left_action parameter is set to "email" set the action_mail_acct parameter to an e-mail address for the System Administrator (SA) and Information System Security Officer (ISSO). + +If the space_left_action parameter is set to "exec", make sure the command being execute notifies the System Administrator (SA) and Information System Security Officer (ISSO). + +Edit /etc/audit/auditd.conf and set the space_left parameter to be, at least, 25% of the repository maximum audit record storage capacity.Verify the Ubuntu operating system notifies the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. + +Check that the Ubuntu operating system notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity with the following command: + +# sudo grep ^space_left_action /etc/audit/auditd.conf + +space_left_action email + +# sudo grep ^space_left /etc/audit/auditd.conf + +space_left 250000 + +If the "space_left" parameter is missing, set to blanks or set to a value less than 25% of the space free in the allocated audit record storage, this is a finding. + +If the "space_left_action" parameter is missing or set to blanks, this is a finding. + +If the "space_left_action" is set to "syslog", the system logs the event, but does not generate a notification, so this is a finding. + +If the "space_left_action" is set to "exec", the system executes a designated script. If this script informs the SA of the event, this is not a finding. + +If the "space_left_action" is set to "email" check the value of the "action_mail_acct" parameter with the following command: + +# sudo grep action_mail_acct /etc/audit/auditd.conf + +action_mail_acct root@localhost + +The "action_mail_acct" parameter, if missing, defaults to "root". If the "action_mail_acct parameter" is not set to the e-mail address of the system administrator(s) and/or ISSO, this is a finding. + +Note: If the email address of the system administrator is on a remote system a mail package must be available.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>UBTU-18-010007The Ubuntu operating system audit event multiplexor must be configured to off-load audit logs onto a different system in real time, if the system is interconnected.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100531SV-109635CCI-001851Configure the audit event multiplexor to off-load audit records to a different system or storage media from the system being audited. + +Install the audisp-remote plugin: + +# sudo apt-get install audispd-plugins -y + +Set the audisp-remote plugin as active, by editing the /etc/audisp/plugins.d/au-remote.conf file: + +# sudo sed -i -E 's/active\s*=\s*no/active = yes/' /etc/audisp/plugins.d/au-remote.conf + +Set the address of the remote machine, by editing the /etc/audisp/audisp-remote.conf file: + +# sudo sed -i -E 's/(remote_server\s*=).*/\1 <remote addr>/' audisp-remote.conf + +where <remote addr> must be substituted by the address of the remote server receiving the audit log. + +Make the audit service reload its configuration files: + +# sudo systemctl restart auditd.serviceVerify the audit event multiplexor is configured to off-load audit records to a different system or storage media from the system being audited. + +Check that audisp-remote plugin is installed: + +# sudo dpkg -s audispd-plugins + +If status is "not installed", this is a finding. + +Check that the records are being off-loaded to a remote server with the following command: + +# sudo grep -i active /etc/audisp/plugins.d/au-remote.conf + +active = yes + +If "active" is not set to "yes", or the line is commented out, this is a finding. + +Check that audisp-remote plugin is configured to send audit logs to a different system: + +# sudo grep -i ^remote_server /etc/audisp/audisp-remote.conf + +remote_server = 192.168.122.126 + +If the remote_server parameter is not set or is set with a local address, or is set with invalid address, this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>UBTU-18-010008The Ubuntu operating system must have a crontab script running weekly to off-load audit events of standalone systems.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109637V-100533CCI-001851Create a script which off-loads audit logs to external media and runs weekly. + +Script must be located into the /etc/cron.weekly directory.Verify there is a script which off-loads audit data and if that script runs weekly. + +Check if there is a script in the /etc/cron.weekly directory which off-loads audit data: + +# sudo ls /etc/cron.weekly + +audit-offload + +Check if the script inside the file does offloading of audit logs to an external media. + +If the script file does not exist or if the script file doesn't offload audit logs, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>UBTU-18-010016Advance package Tool (APT) must be configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.<VulnDiscussion>Changes to any software components can have significant effects on the overall security of the Ubuntu operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. + +Accordingly, patches, service packs, device drivers, or Ubuntu operating system components must be signed with a certificate recognized and approved by the organization. + +Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The Ubuntu operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109639V-100535CCI-001749Configure Advance package Tool (APT) to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. + +Remove/Update any APT configuration file that contain the variable "AllowUnauthenticated" to "false", or remove "AllowUnauthenticated" entirely from each file. Below is an example of setting the "AllowUnauthenticated" variable to "false": + +APT::Get::AllowUnauthenticated "false";Verify that Advance package Tool (APT) is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. + +Check that the "AllowUnauthenticated" variable is not set at all or set to "false" with the following command: + +# grep AllowUnauthenticated /etc/apt/apt.conf.d/* +/etc/apt/apt.conf.d/01-vendor-Ubuntu:APT::Get::AllowUnauthenticated "false"; + +If any of the files returned from the command with "AllowUnauthenticated" set to "true", this is a finding.SRG-OS-000437-GPOS-00194<GroupDescription></GroupDescription>UBTU-18-010017The Ubuntu operating system must be configured so that Advance package Tool (APT) removes all software components after updated versions have been installed.<VulnDiscussion>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109641V-100537CCI-002617Configure APT to remove all software components after updated versions have been installed. + +Add or updated the following options to the "/etc/apt/apt.conf.d/50unattended-upgrades" file: + +Unattended-Upgrade::Remove-Unused-Dependencies "true"; +Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";Verify Advance package Tool (APT) is configured to remove all software components after updated versions have been installed. + +Check that APT is configured to remove all software components after updating with the following command: + +# grep -i remove-unused /etc/apt/apt.conf.d/50unattended-upgrades +Unattended-Upgrade::Remove-Unused-Dependencies "true"; +Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; + +If the "::Remove-Unused-Dependencies" and "::Remove-Unused-Kernel-Packages" parameters are not set to "true", or are missing, or are commented out, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>UBTU-18-010018The Ubuntu operating system must not have the Network Information Service (NIS) package installed.<VulnDiscussion>Removing the Network Information Service (NIS) package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109643V-100539CCI-000381Configure the Ubuntu operating system to disable non-essential capabilities by removing the Network Information Service (NIS) package from the system with the following command: + +# sudo apt-get remove nisVerify that the Network Information Service (NIS) package is not installed on the Ubuntu operating system. + +Check to see if the NIS package is installed with the following command: + +# dpkg -l | grep nis + +If the NIS package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>UBTU-18-010019The Ubuntu operating system must not have the rsh-server package installed.<VulnDiscussion>It is detrimental for Ubuntu operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. + +Ubuntu operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). + +The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication. + +If a privileged user were to log on using this service, the privileged user password could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100541SV-109645CCI-000381Configure the Ubuntu operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command: + +# sudo apt-get remove rsh-serverCheck to see if the rsh-server package is installed with the following command: + +# dpkg -l | grep rsh-server + +If the rsh-server package is installed, this is a finding.SRG-OS-000191-GPOS-00080<GroupDescription></GroupDescription>UBTU-18-010021The Ubuntu operating system must deploy Endpoint Security for Linux Threat Prevention (ENSLTP).<VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. + +To support this requirement, the Ubuntu operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools, as specified in the requirement.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109649V-100545CCI-001233Configure the Ubuntu operating system to use ENSLTP. + +Install the mcafeetp package via the ePO server.Check that the "mcafeetp" package has been installed: + +# dpkg -l | grep -i mcafeetp + +If the "mcafeetp" package is not installed, this is a finding. + +Check that the daemon is running: + +# /opt/McAfee/ens/tp/init/mfetpd-control.sh status + +If the daemon is not running, this is a finding.SRG-OS-000269-GPOS-00103<GroupDescription></GroupDescription>UBTU-18-010022The Ubuntu operating system must be configured to preserve log records from failure events.<VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. + +Preserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109651V-100547CCI-001665Configure the log service to collect failure events. + +Install the log service (if the log service is not already installed) with the following command: + +# sudo apt-get install rsyslog + +Enable the log service with the following command: + +# sudo systemctl enable rsyslog + +Restart the log service with the following command: + +# sudo systemctl restart rsyslogVerify the log service is configured to collect system failure events. + +Check that the log service is installed properly with the following command: + +# dpkg -l | grep rsyslog + +ii rsyslog 8.32.0-1ubuntu4 amd64 reliable system and kernel logging daemon + +If the "rsyslog" package is not installed, this is a finding. + +Check that the log service is enabled with the following command: + +# sudo systemctl is-enabled rsyslog + +enabled + +If the command above returns "disabled", this is a finding. + +Check that the log service is properly running and active on the system with the following command: + +# systemctl is-active rsyslog + +active + +If the command above returns "inactive", this is a finding.SRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>UBTU-18-010023The Ubuntu operating system must have an application firewall installed in order to control remote access methods.<VulnDiscussion>Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best. + +Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Ubuntu operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100549SV-109653CCI-002314Install the Uncomplicated Firewall by using the following command: + +# sudo apt-get install ufwVerify that the Uncomplicated Firewall is installed. + +Check that the Uncomplicated Firewall is installed with the following command: + +# dpkg -l | grep ufw + +ii ufw 0.35-0Ubuntu2 + +If the "ufw" package is not installed, ask the System Administrator is another application firewall is installed. If no application firewall is installed this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>UBTU-18-010025The Ubuntu operating system audit event multiplexor must be configured to off-load audit logs onto a different system or storage media from the system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109655V-100551CCI-001851Configure the audit event multiplexor to off-load audit records to a different system or storage media from the system being audited. + +Install the audisp-remote plugin: + +# sudo apt-get install audispd-plugins -y + +Set the audisp-remote plugin as active, by editing the /etc/audisp/plugins.d/au-remote.conf file: + +# sudo sed -i -E 's/active\s*=\s*no/active = yes/' /etc/audisp/plugins.d/au-remote.conf + +Set the address of the remote machine, by editing the /etc/audisp/audisp-remote.conf file: + +# sudo sed -i -E 's/(remote_server\s*=).*/\1 <remote addr>/' audisp-remote.conf + +where <remote addr> must be substituted by the address of the remote server receiving the audit log. + +Make the audit service reload its configuration files: + +# sudo systemctl restart auditd.serviceVerify the audit event multiplexor is configured to off-load audit records to a different system or storage media from the system being audited. + +Check that audisp-remote plugin is installed: + +# sudo dpkg -s audispd-plugins + +If status is "not installed", verify that another method to off-load audit logs has been implemented. + +Check that the records are being off-loaded to a remote server with the following command: + +# sudo grep -i active /etc/audisp/plugins.d/au-remote.conf + +active = yes + +If "active" is not set to "yes", or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or storage media. + +If there is no evidence that the system is configured to off-load audit logs to a different system or storage media, this is a finding.SRG-OS-000383-GPOS-00166<GroupDescription></GroupDescription>UBTU-18-010030The Ubuntu operating system must be configured such that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day.<VulnDiscussion>If cached authentication information is out-of-date, the validity of the authentication information may be questionable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100553SV-109657CCI-002007Configure Pluggable Authentication Module (PAM) to prohibit the use of cached authentications after one day. Add or change the following line in "/etc/sssd/sssd.conf" just below the line "[pam]". + +offline_credentials_expiration = 1 + +Note: It is valid for this configuration to be in a file with a name that ends with ".conf" and does not begin with a "." in the /etc/sssd/conf.d/ directory instead of the /etc/sssd/sssd.conf file.If smart card authentication is not being used on the system this item is Not Applicable. + +Verify that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day. + +Check that PAM prohibits the use of cached authentications after one day with the following command: + +# sudo grep offline_credentials_expiration /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf + +offline_credentials_expiration = 1 + +If "offline_credentials_expiration" is not set to a value of "1", in /etc/sssd/sssd.conf or in a file with a name ending in .conf in the /etc/sssd/conf.d/ directory, this is a finding.SRG-OS-000480-GPOS-00226<GroupDescription></GroupDescription>UBTU-18-010031The Ubuntu operating system must enforce a delay of at least 4 seconds between logon prompts following a failed logon attempt.<VulnDiscussion>Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100555SV-109659CCI-000366Configure the Ubuntu operating system to enforce a delay of at least 4 seconds between logon prompts following a failed logon attempt. + +Edit the file "/etc/pam.d/common-auth" and set the parameter "pam_faildelay" to a value of 4000000 or greater: + +auth required pam_faildelay.so delay=4000000Verify the Ubuntu operating system enforces a delay of at least 4 seconds between logon prompts following a failed logon attempt. + +Check that the Ubuntu operating system enforces a delay of at least 4 seconds between logon prompts with the following command: + +# grep pam_faildelay /etc/pam.d/common-auth + +auth required pam_faildelay.so delay=4000000 + +If the line is not present, or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010032The Ubuntu operating system must display the date and time of the last successful account logon upon logon.<VulnDiscussion>Configuring the Ubuntu operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. + +Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109661V-100557CCI-000052Configure the Ubuntu operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/postlogin-ac". + +Add the following line to the top of "/etc/pam.d/login": + +session required pam_lastlog.so showfailedVerify users are provided with feedback on when account accesses last occurred. + +Check that "pam_lastlog" is used and not silent with the following command: + +# grep pam_lastlog /etc/pam.d/login + +session required pam_lastlog.so showfailed + +If "pam_lastlog" is missing from "/etc/pam.d/login" file, is not "required", or the "silent" option is present, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>UBTU-18-010033The Ubuntu operating system must be configured so that three consecutive invalid logon attempts by a user automatically locks the account until released by an administrator.<VulnDiscussion>By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. +Satisfies: SRG-OS-000329-GPOS-00128</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109663V-100559CCI-000044CCI-002238Configure the Ubuntu operating system to utilize the "pam_faillock" module. + +Edit the /etc/pam.d/common-auth file. + +Add the following lines below the "auth" definition for pam_unix.so: +auth [default=die] pam_faillock.so authfail +auth sufficient pam_faillock.so authsucc + +Configure the "pam_faillock" module to use the following options: + +Edit the /etc/security/faillock.conf file and add/update the following keywords and values: +audit +silent +deny = 3 +fail_interval = 900 +unlock_time = 0Verify that the Ubuntu operating system utilizes the "pam_faillock" module with the following command: +$ grep faillock /etc/pam.d/common-auth + +auth [default=die] pam_faillock.so authfail +auth sufficient pam_faillock.so authsucc + +If the pam_faillock.so module is not present in the "/etc/pam.d/common-auth" file, this is a finding. + +Verify the pam_faillock module is configured to use the following options: +$ sudo egrep 'silent|audit|deny|fail_interval| unlock_time' /etc/security/faillock.conf + +audit +silent +deny = 3 +fail_interval = 900 +unlock_time = 0 + +If the "silent" keyword is missing or commented out, this is a finding. +If the "audit" keyword is missing or commented out, this is a finding. +If the "deny" keyword is missing, commented out, or set to a value greater than 3, this is a finding. +If the "fail_interval" keyword is missing, commented out, or set to a value greater than 900, this is a finding. +If the "unlock_time" keyword is missing, commented out, or is not set to 0, this is a finding.SRG-OS-000024-GPOS-00007<GroupDescription></GroupDescription>UBTU-18-010035The Ubuntu operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local access to the system via a graphical user logon.<VulnDiscussion>The banner must be acknowledged by the user prior to allowing the user access to the operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. + +To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100561SV-109665CCI-000050Edit the /etc/gdm3/greeter.dconf-defaults file. + +Uncomment (remove the leading '#' characters) the following 3 configuration lines: + +[org/gnome/login-screen] + +banner-message-enable=true +banner-message-text='Welcome' + +Note: the lines are all near the bottom of the file but they are not adjacent to each other. + +Edit the banner-message-text='Welcome' line to contain the appropriate banner message text as shown below: + +banner-message-text='You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.' + +Note that it is similar to the text in /etc/issue but it is all on a single line and the newline characters have been replaced with \n. + +# sudo dconf update +# sudo systemctl restart gdm3Verify the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon. +Note: If the system does not have Graphical User Interface installed, this requirement is Not Applicable. + +Check that the operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text with the command: + +# grep banner-message-enable /etc/gdm3/greeter.dconf-defaults + +banner-message-enable=true + +If the line is commented out or set to "false", this is a finding. + +# grep banner-message-text /etc/gdm3/greeter.dconf-defaults + +banner-message-text="You are accessing a U.S. Government \(USG\) Information System \(IS\) that is provided for USG-authorized use only.\s+By using this IS \(which includes any device attached to this IS\), you consent to the following conditions:\s+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct \(PM\), law enforcement \(LE\), and counterintelligence \(CI\) investigations.\s+-At any time, the USG may inspect and seize data stored on this IS.\s+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\s+-This IS includes security measures \(e.g., authentication and access controls\) to protect USG interests--not for your personal benefit or privacy.\s+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +If the banner-message-text is missing, commented out, or the text does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.SRG-OS-000109-GPOS-00056<GroupDescription></GroupDescription>UBTU-18-010036The Ubuntu operating system must prevent direct login into the root account.<VulnDiscussion>To assure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated. + +A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account. + +For example, the UNIX and Windows operating systems offer a 'switch user' capability allowing users to authenticate with their individual credentials and, when needed, 'switch' to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. + +Users (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the operating system without identification or authentication. + +Requiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109667V-100563CCI-000770Configure the Ubuntu operating system to prevent direct logins to the root account by performing the following operations: + +sudo passwd -l rootVerify the Ubuntu operating system prevents direct logins to the root account. + +Check that the Ubuntu operating system prevents direct logins to the root account with the following command: + +# sudo passwd -S root + +root L 11/11/2017 0 99999 7 -1 + +If the output does not contain "L" in the second field to indicate the account is locked, this is a finding.SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>UBTU-18-010037The Ubuntu operating system must be configured so that only users who need access to security functions are part of the sudo group.<VulnDiscussion>An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. + +Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. + +Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. + +The Ubuntu operating system restricts access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109669V-100565CCI-001084Configure the sudo group with only members requiring access to security functions. + +To remove a user from the sudo group run: + +sudo gpasswd -d <username> sudoVerify that the sudo group has only members who should have access to security functions. + +# grep sudo /etc/group + +sudo:x:27:foo + +If the sudo group contains users not needing access to security functions, this is a finding.SRG-OS-000228-GPOS-00088<GroupDescription></GroupDescription>UBTU-18-010038The Ubuntu operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting any publically accessible connection to the system.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the Ubuntu operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. + +System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. + +The banner must be formatted in accordance with applicable DoD policy: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +Satisfies: SRG-OS-000228-GPOS-00088, SRG-OS-000023-GPOS-00006</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100567SV-109671CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure the Ubuntu operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via SSH logon. + +Edit the SSH daemon configuration "/etc/ssh/sshd_config" file. Uncomment the banner keyword and configure it to point to the file that contains the correct banner. An example of this configure is below: + +Banner /etc/issue + +Either create the file containing the banner, or replace the text in the file with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +In order for the changes to take effect, the SSH daemon must be restarted. + +# sudo systemctl restart sshd.serviceVerify the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a ssh logon. + +Check that the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a ssh logon with the following command: + +# grep -i banner /etc/ssh/sshd_config + +Banner /etc/issue + +The command will return the banner option along with the name of the file that contains the ssh banner. If the line is commented out, this is a finding. + +Check the specified banner file to check that it matches the Standard Mandatory DoD Notice and Consent Banner exactly: + +# cat /etc/issue + +“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” + +If the banner text does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>UBTU-18-010100The Ubuntu operating system must enforce password complexity by requiring that at least one upper-case character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100571SV-109675CCI-000192Add or update the "/etc/security/pwquality.conf" file to contain the "ucredit" parameter: + +ucredit=-1Verify the Ubuntu operating system enforces password complexity by requiring that at least one upper-case character be used. + +Determine if the field "ucredit" is set in the "/etc/security/pwquality.conf" file with the following command: + +# grep -i "ucredit" /etc/security/pwquality.conf +ucredit=-1 + +If the "ucredit" parameter is greater than "-1", or is commented out, this is a finding.SRG-OS-000070-GPOS-00038<GroupDescription></GroupDescription>UBTU-18-010101The Ubuntu operating system must enforce password complexity by requiring that at least one lower-case character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100573SV-109677CCI-000193Add or update the "/etc/security/pwquality.conf" file to contain the "lcredit" parameter: + +lcredit=-1Verify the Ubuntu operating system enforces password complexity by requiring that at least one lower-case character be used. + +Determine if the field "lcredit" is set in the "/etc/security/pwquality.conf" file with the following command: + +# grep -i "lcredit" /etc/security/pwquality.conf +lcredit=-1 + +If the "lcredit" parameter is greater than "-1", or is commented out, this is a finding.SRG-OS-000071-GPOS-00039<GroupDescription></GroupDescription>UBTU-18-010102The Ubuntu operating system must enforce password complexity by requiring that at least one numeric character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109679V-100575CCI-000194Configure the Ubuntu operating system to enforce password complexity by requiring that at least one numeric character be used. + +Add or update the "/etc/security/pwquality.conf" file to contain the "dcredit" parameter: + +dcredit=-1Verify the Ubuntu operating system enforces password complexity by requiring that at least one numeric character be used. + +Determine if the field "dcredit" is set in the "/etc/security/pwquality.conf" file with the following command: + +# grep -i "dcredit" /etc/security/pwquality.conf +dcredit=-1 + +If the "dcredit" parameter is greater than "-1", or is commented out, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>UBTU-18-010103The Ubuntu operating system must require the change of at least 8 characters when passwords are changed.<VulnDiscussion>If the Ubuntu operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. + +The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. + +If the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least 8 characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109681V-100577CCI-000195Configure the Ubuntu operating system to require the change of at least 8 characters when passwords are changed. + +Add or update the "/etc/security/pwquality.conf" file to include the "difok=8" parameter: + +difok=8Verify the Ubuntu operating system requires the change of at least 8 characters when passwords are changed. + +Determine if the field "difok" is set in the "/etc/security/pwquality.conf" file with the following command: + +# grep -i "difok" /etc/security/pwquality.conf +difok=8 + +If the "difok" parameter is less than "8", or is commented out, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>UBTU-18-010104The Ubuntu operating system must encrypt all stored passwords with a FIPS 140-2 approved cryptographic hashing algorithm.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109683V-100579CCI-000196Configure the Ubuntu operating system to encrypt all stored passwords. + +Edit/Modify the following line in the "/etc/login.defs" file and set "ENCRYPT_METHOD" to SHA512. + +ENCRYPT_METHOD SHA512Verify that the shadow password suite configuration is set to encrypt password with a FIPS 140-2 approved cryptographic hashing algorithm. + +Check the hashing algorithm that is being used to hash passwords with the following command: + +# cat /etc/login.defs | grep -i crypt + +ENCRYPT_METHOD SHA512 + +If "ENCRYPT_METHOD" does not equal SHA512 or greater, this is a finding.SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>UBTU-18-010105The Ubuntu operating system must not have the telnet package installed.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100581SV-109685CCI-000197Remove the telnet package from the Ubuntu operating system by running the following command: + +# sudo apt-get remove telnetdVerify that the telnet package is not installed on the Ubuntu operating system. + +Check that the telnet daemon is not installed on the Ubuntu operating system by running the following command: + +# dpkg -l | grep telnetd + +If the package is installed, this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>UBTU-18-010106The Ubuntu operating system must enforce 24 hours/1 day as the minimum password lifetime. Passwords for new users must have a 24 hours/1 day minimum password lifetime restriction.<VulnDiscussion>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109687V-100583CCI-000198Configure the Ubuntu operating system to enforce a 24 hours/1 day minimum password lifetime. + +Add, or modify the following line in the "/etc/login.defs" file: + +PASS_MIN_DAYS 1Verify that the Ubuntu operating system enforces a 24 hours/1 day minimum password lifetime for new user accounts by running the following command: + +# grep -i pass_min_days /etc/login.defs + +PASS_MIN_DAYS 1 + +If the "PASS_MIN_DAYS" parameter value is less than 1, or commented out, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>UBTU-18-010107The Ubuntu operating system must enforce a 60-day maximum password lifetime restriction. Passwords for new users must have a 60-day maximum password lifetime restriction.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100585SV-109689CCI-000199Configure the Ubuntu operating system to enforce a 60-day maximum password lifetime. + +Add, or modify the following line in the "/etc/login.defs" file: + +PASS_MAX_DAYS 60Verify that the Ubuntu operating system enforces a 60-day maximum password lifetime for new user accounts by running the following command: + +# grep -i pass_max_days /etc/login.defs +PASS_MAX_DAYS 60 + +If the "PASS_MAX_DAYS" parameter value is less than 60, or commented out, this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>UBTU-18-010108The Ubuntu operating system must prohibit password reuse for a minimum of five generations.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100587SV-109691CCI-000200Configure the Ubuntu operating system prevents passwords from being reused for a minimum of five generations. + +Add, or modify the "remember" parameter value to the following line in "/etc/pam.d/common-password" file: + +password [success=1 default=ignore] pam_unix.so sha512 shadow remember=5 rounds=5000Verify that the Ubuntu operating system prevents passwords from being reused for a minimum of five generations by running the following command: + +# grep -i remember /etc/pam.d/common-password + +password [success=1 default=ignore] pam_unix.so sha512 shadow remember=5 rounds=5000 + +If the "remember" parameter value is not greater than or equal to 5, commented out, or not set at all this is a finding.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>UBTU-18-010109The Ubuntu operating system must enforce a minimum 15-character password length.<VulnDiscussion>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. + +Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100589SV-109693CCI-000205Configure the Ubuntu operating system to enforce a minimum 15-character password length. + +Add, or modify the "minlen" parameter value to the "/etc/security/pwquality.conf" file: + +minlen=15Verify if the pwquality configuration file enforces a minimum 15-character password length, by running the following command: + +# grep -i minlen /etc/security/pwquality.conf + minlen=15 + +If "minlen" parameter value is not 15 or higher, or is commented out, this is a finding.SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>UBTU-18-010110The Ubuntu operating system must employ a FIPS 140-2 approved cryptographic hashing algorithms for all created and stored passwords.<VulnDiscussion>The Ubuntu operating system must use a FIPS-compliant hashing algorithm to securely store the password. The FIPS-compliant hashing algorithm parameters must be selected in order to harden the system against offline attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109695V-100591CCI-000803Configure the Ubuntu operating system to encrypt all stored passwords with a strong cryptographic hash. + +Edit/modify the following line in the file "/etc/pam.d/common-password" file to include the sha512 option for pam_unix.so: + +password [success=1 default=ignore] pam_unix.so obscure sha512 + +Edit/modify /etc/login.defs and set "ENCRYPT_METHOD sha512".Verify that encrypted passwords stored in /etc/shadow use a strong cryptographic hash. + +Check that pam_unix.so auth is configured to use sha512 with the following command: + +# grep password /etc/pam.d/common-password | grep pam_unix + +password [success=1 default=ignore] pam_unix.so obscure sha512 + +If "sha512" is not an option of the output, or is commented out, this is a finding. + +Check that ENCRYPT_METHOD is set to sha512 in /etc/login.defs: + +# grep -i ENCRYPT_METHOD /etc/login.defs + +ENCRYPT_METHOD SHA512 + +If the output does not contain "sha512", or it is commented out, this is a finding.SRG-OS-000380-GPOS-00165<GroupDescription></GroupDescription>UBTU-18-010112The Ubuntu operating system must allow the use of a temporary password for system logons with an immediate change to a permanent password.<VulnDiscussion>Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon. + +Temporary passwords are typically used to allow access when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts which allow the users to log on, yet force them to change the password once they have successfully authenticated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100593SV-109697CCI-002041Create a policy that ensures when a user is created, it is created using a method that forces a user to change their password upon their next login. + +Below are two examples of how to create a user account that requires the user to change their password upon their next login. + +# chage -d 0 [UserName] + +or + +# passwd -e [UserName]Verify a policy exists that ensures when a user account is created, it is created using a method that forces a user to change their password upon their next login. + +If a policy does not exist, this is a finding.SRG-OS-000480-GPOS-00225<GroupDescription></GroupDescription>UBTU-18-010113The Ubuntu operating system must prevent the use of dictionary words for passwords.<VulnDiscussion>If the Ubuntu operating system allows the user to select passwords based on dictionary words, then this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100595SV-109699CCI-000366Configure the Ubuntu operating system to prevent the use of dictionary words for passwords. + +Add or update the following line in the "/etc/security/pwquality.conf" file to include the "dictcheck=1" parameter: + +dictcheck=1Verify that the Ubuntu operating system uses the cracklib library to prevent the use of dictionary words with the following command: + +# grep dictcheck /etc/security/pwquality.conf + +dictcheck=1 + +If the "dictcheck" parameter is not set to "1", or is commented out, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>UBTU-18-010114The Ubuntu operating system must require users to re-authenticate for privilege escalation and changing roles.<VulnDiscussion>Without re-authentication, users may access resources or perform tasks for which they do not have authorization. + +When the Ubuntu operating system provides the capability to escalate a functional capability or change security roles, it is critical the user re-authenticate. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109701V-100597CCI-002038Remove any occurrence of "NOPASSWD" or "!authenticate" found in "/etc/sudoers" file or files in the /etc/sudoers.d directory.Verify that "/etc/sudoers" has no occurrences of "NOPASSWD" or "!authenticate". + +Check that the "/etc/sudoers" file has no occurrences of "NOPASSWD" or "!authenticate" by running the following command: + +# sudo egrep -i '(nopasswd|!authenticate)' /etc/sudoers /etc/sudoers.d/* + +If any occurrences of "NOPASSWD" or "!authenticate" return from the command, this is a finding.SRG-OS-000480-GPOS-00225<GroupDescription></GroupDescription>UBTU-18-010116The Ubuntu Operating system must be configured so that when passwords are changed or new passwords are established, pwquality must be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100599SV-109703CCI-000366Configure the operating system to use "pwquality" to enforce password complexity rules. + +Install the pam_pwquality package by using the following command: + +# apt-get install libpam-pwquality -y + +Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): + +enforcing = 1 + +Add the following line to "/etc/pam.d/common-password" (or modify the line to have the required value): + +password requisite pam_pwquality.so retry=3 enforce_for_root + +Note: The value of "retry" should be between "1" and "3".Verify the Ubuntu operating system has the libpam-pwquality package installed, by running the following command: + +# dpkg -l libpam-pwquality + +ii libpam-pwquality:amd64 1.4.0-2 amd64 PAM module to check password strength + +If "libpam-pwquality" is not installed, this is a finding. + +Verify the operating system uses "pwquality" to enforce the password complexity rules. + +Verify the pwquality module is being enforced by the Ubuntu Operating System, by running the following command: + +# grep -i enforcing /etc/security/pwquality.conf + +enforcing = 1 + +If the value of "enforcing" is not 1 or the line is commented out, this is a finding. + +Check for the use of "pwquality" with the following command: + +# sudo cat /etc/pam.d/common-password | grep requisite | grep pam_pwquality + +password requisite pam_pwquality.so retry=3 enforce_for_root + +If no output is returned or the line is commented out, this is a finding. +If the value of "retry" is set to "0" or greater than "3", this is a finding. +If "enforce_for_root" is missing from the configuration line, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>UBTU-18-010120The Ubuntu operating system must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources.<VulnDiscussion>Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. + +This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies. + +There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109705V-100601CCI-001090Configure all public directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources. + +Set the sticky bit on all public directories using the command, replace "[Public Directory]" with any directory path missing the sticky bit: + +# sudo chmod +t [Public Directory]Verify that all public (world writeable) directories have the public sticky bit set. + +Find world-writable directories that lack the sticky bit by running the following command: + +# sudo find / -type d -perm -002 ! -perm -1000 + +If any world-writable directories are found missing the sticky bit, this is a finding.SRG-OS-000205-GPOS-00083<GroupDescription></GroupDescription>UBTU-18-010121The Ubuntu operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.<VulnDiscussion>Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. + +Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. + +The /var/log/btmp, /var/log/wtmp, and /var/log/lastlog files have group write and global read permissions to allow for the lastlog function to perform. Limiting the permissions beyond this configuration will result in the failure of functions that rely on the lastlog database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109707V-100603CCI-001312Configured the Ubuntu operating system to set permissions of all log files under /var/log directory to "640" or more restricted, by using the following command: + +Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. + +$ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec chmod 640 '{}' \;Verify the Ubuntu operating system has all system log files under the /var/log directory with a permission set to "640", by using the following command: + +Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. + +$ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec stat -c "%n %a" {} \; + +If the command displays any output, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010122The Ubuntu operating system must configure the /var/log directory to be group-owned by syslog.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100605SV-109709CCI-001314Configure the Ubuntu operating system to have syslog group-own the /var/log directory by running the following command: + +# sudo chgrp syslog /var/logVerify the Ubuntu operating system configures the /var/log directory to be group-owned by syslog. + +Check that the /var/log directory is group owned by syslog with the following command: + +# sudo stat -c "%n %G" /var/log +/var/log syslog + +If the /var/log directory is not group-owned by syslog, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010123The Ubuntu operating system must configure the /var/log directory to be owned by root.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100607SV-109711CCI-001314Configure the Ubuntu operating system to have root own the /var/log directory by running the following command: + +# sudo chown root /var/logVerify the Ubuntu operating system configures the /var/log directory to be owned by root. + +Check that the /var/log directory is owned by root with the following command: + +# sudo stat -c "%n %U" /var/log +/var/log root + +If the /var/log directory is not owned by root, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010124The Ubuntu operating system must configure the /var/log directory to have mode 0755 or less permissive.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100609SV-109713CCI-001314Configure the Ubuntu operating system to have permissions of "0755" for the /var/log directory by running the following command: + +$ sudo chmod 0755 /var/logVerify that the Ubuntu operating system configures the /var/log directory with a mode of "755" or less permissive. + +Check the mode of the /var/log directory with the following command: + +Note: If rsyslog is active and enabled on the operating system, this requirement is not applicable. + +$ stat -c "%n %a" /var/log + +/var/log 755 + +If a value of "755" or less permissive is not returned, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010125The Ubuntu operating system must configure the /var/log/syslog file to be group-owned by adm.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109715V-100611CCI-001314Configure the Ubuntu operating system to have adm group-own the /var/log/syslog file by running the following command: + +# sudo chgrp adm /var/log/syslogVerify that the Ubuntu operating system configures the /var/log/syslog file to be group-owned by adm. + +Check that the /var/log/syslog file is group-owned by adm with the following command: + +# sudo stat -c "%n %G" /var/log/syslog +/var/log/syslog adm + +If the /var/log/syslog file is not group-owned by adm, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010126The Ubuntu operating system must configure /var/log/syslog file to be owned by syslog.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100613SV-109717CCI-001314Configure the Ubuntu operating system to have syslog own the /var/log/syslog file by running the following command: + +# sudo chown syslog /var/log/syslogVerify that the Ubuntu operating system configures the /var/log/syslog file to be owned by syslog. + +Check that the /var/log/syslog file is owned by syslog with the following command: + +# sudo stat -c "%n %U" /var/log/syslog +/var/log/syslog syslog + +If the /var/log/syslog file is not owned by syslog, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>UBTU-18-010127The Ubuntu operating system must configure /var/log/syslog file with mode 0640 or less permissive.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109719V-100615CCI-001314Configure the Ubuntu operating system to have permissions of 0640 o for the /var/log/syslog file by running the following command: + +# sudo chmod 0640 /var/log/syslogVerify that the Ubuntu operating system configures the /var/log/syslog file with mode 0640 or less permissive. + +Check the /var/log/syslog permissions by running the following command: + +# stat -c "%n %a" /var/log/syslog + +/var/log/syslog 640 + +If a value of "640" or less permissive is not returned, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>UBTU-18-010128The Ubuntu operating system must configure audit tools with a mode of 0755 or less permissive.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +The Ubuntu operating system providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. + +Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. + +Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100617SV-109721CCI-001493CCI-001494CCI-001495Configure the audit tools on the Ubuntu operating system to be protected from unauthorized access by setting the correct permissive mode using the following command: + +# sudo chmod 0755 [audit_tool] + +Replace "[audit_tool]" with the audit tool that does not have the correct permissive mode.Verify the audit tools are protected from unauthorized access, deletion, or modification by checking the permissive mode. + +For each audit tool, +/sbin/auditctl, /sbin/aureport, /sbin/ausearch, /sbin/autrace, /sbin/auditd, /sbin/audispd, /sbin/augenrules + +Check the permissions by running the following command: + +# stat -c "%n %a" /sbin/auditctl + +755 /sbin/auditctl + +If any of the audit tools have a mode more permissive than 0755, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>UBTU-18-010129The Ubuntu operating system must configure audit tools to be owned by root.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +The Ubuntu operating system providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. + +Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100619SV-109723CCI-001493Configure the audit tools on the Ubuntu operating system to be owned by root, by running the following command: + +# sudo chown root [audit_tool] + +Replace "[audit_tool]" with each audit tool not owned by root.Verify the Ubuntu operating system configures the audit tools to be owned by root to prevent any unauthorized access, deletion, or modification. + +For each audit tool, +/sbin/auditctl, /sbin/aureport, /sbin/ausearch, /sbin/autrace, /sbin/auditd, /sbin/audispd, /sbin/augenrules + +Check the ownership by running the following command: + +# stat -c "%n %U" /sbin/auditctl + +/sbin/auditctl root + +If any of the audit tools are not owned by root, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>UBTU-18-010130The Ubuntu operating system must configure the audit tools to be group-owned by root.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +The Ubuntu operating system providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. + +Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100621SV-109725CCI-001493Configure the audit tools on the Ubuntu operating system to be group-owned by root, by running the following command: + +# sudo chgrp root [audit_tool] + +Replace "[audit_tool]" with each audit tool not group-owned by root.Verify the Ubuntu operating system configures the audit tools to be group-owned by root to prevent any unauthorized access, deletion, or modification. + +For each audit tools, +/sbin/auditctl, /sbin/aureport, /sbin/ausearch, /sbin/autrace, /sbin/auditd, /sbin/audispd, /sbin/augenrules + +Check the group-owner of each audit tool by running the following commands: + +stat -c "%n %G" /sbin/auditctl + +/sbin/auditctl root + +If any of the audit tools are not group-owned by root, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010133The Ubuntu operating system library files must have mode 0755 or less permissive.<VulnDiscussion>If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100623SV-109727CCI-001499Configure the library files to be protected from unauthorized access. Run the following command: +$ sudo find /lib /lib64 /usr/lib -perm /022 -type f -iname *.so* -exec chmod 755 '{}' \Verify the system-wide shared library files contained in the directories "/lib", "/lib64" and "/usr/lib" have mode 0755 or less permissive. + +Check that the system-wide shared library files have mode 0755 or less permissive with the following command: +$ sudo find /lib /lib64 /usr/lib -perm /022 -type f -exec stat -c "%n %a" '{}' \; +/usr/lib64/pkcs11-spy.so + +If any library files are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010134The Ubuntu operating system library directories must have mode 0755 or less permissive.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109729V-100625CCI-001499Configure the shared library directories to be protected from unauthorized access. Run the following command: + +# sudo find /lib /lib64 /usr/lib -perm /022 -type d -exec chmod 755 '{}' \;Verify the system-wide shared library directories "/lib", "/lib64" and "/usr/lib have mode 0755 or less permissive. + +Check that the system-wide shared library directories have mode 0755 or less permissive with the following command: + +# sudo find /lib /lib64 /usr/lib -perm /022 -type d -exec stat -c "%n %a" '{}' \; + +If any of the aforementioned directories are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010135The Ubuntu operating system library files must be owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109731V-100627CCI-001499Configure the system library files to be protected from unauthorized access. Run the following command: + +# sudo find /lib /usr/lib /lib64 ! -user root -type f -exec chown root '{}' \;Verify the system-wide shared library files contained in the directories "/lib", "/lib64" and "/usr/lib" are owned by root. + +Check that the system-wide shared library files are owned by root with the following command: + +# sudo find /lib /usr/lib /lib64 ! -user root -type f -exec stat -c "%n %U" '{}' \; + +If any system wide library file is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010136The Ubuntu operating system library directories must be owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100629SV-109733CCI-001499Configure the library files and their respective parent directories to be protected from unauthorized access. Run the following command: + +# sudo find /lib /usr/lib /lib64 ! -user root -type d -exec chown root '{}' \;Verify the system-wide shared library directories "/lib", "/lib64" and "/usr/lib" are owned by root. + +Check that the system-wide shared library directories are owned by root with the following command: + +# sudo find /lib /usr/lib /lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; + +If any system wide library directory is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010137The Ubuntu operating system library files must be group-owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100631SV-109735CCI-001499Configure the system library files to be protected from unauthorized access. Run the following command: +$ sudo find /lib /usr/lib /lib64 ! -group root -type f -iname *.so* -exec chgrp root '{}' \;Verify the system-wide library files contained in the directories "/lib", "/lib64" and "/usr/lib" are group-owned by root. + +Check that the system-wide library files are group-owned by root with the following command: +$ sudo find /lib /usr/lib /lib64 ! -group root -type f -exec stat -c "%n %G" '{}' \; + +If any system wide shared library file is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010138The Ubuntu operating system library directories must be group-owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109737V-100633CCI-001499Configure the system library directories to be protected from unauthorized access. Run the following command: + +# sudo find /lib /usr/lib /lib64 ! -group root -type d -exec chgrp root '{}' \;Verify the system-wide library directories "/lib", "/lib64" and "/usr/lib" are group-owned by root. + +Check that the system-wide library directories are group-owned by root with the following command: + +# sudo find /lib /usr/lib /lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; + +If any system wide shared library directory is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010139The Ubuntu operating system must have system commands set to a mode of 0755 or less permissive.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100635SV-109739CCI-001499Configure the system commands to be protected from unauthorized access. Run the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec chmod 755 '{}' \;Verify the system commands contained in the following directories have mode 0755 or less permissive: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Check that the system command files have mode 0755 or less permissive with the following command: + +# find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec stat -c "%n %a" '{}' \; + +If any files are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010140The Ubuntu operating system must have directories that contain system commands set to a mode of 0755 or less permissive.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100637SV-109741CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec chmod -R 755 '{}' \;Verify the system commands directories have mode 0755 or less permissive: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Check that the system command directories have mode 0755 or less permissive with the following command: + +# find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec stat -c "%n %a" '{}' \; + +If any directories are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010141The Ubuntu operating system must have system commands owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109743V-100639CCI-001499Configure the system commands - and their respective parent directories - to be protected from unauthorized access. Run the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec chown root '{}' \;Verify the system commands contained in the following directories are owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Use the following command for the check: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec stat -c "%n %U" '{}' \; + +If any system commands are returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010142The Ubuntu operating system must have directories that contain system commands owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100641SV-109745CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec chown root '{}' \;Verify the system commands directories are owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Use the following command for the check: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec stat -c "%n %U" '{}' \; + +If any system commands directories are returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010143The Ubuntu operating system must have system commands group-owned by root or a system account.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100643SV-109747CCI-001499Configure the system commands to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any system command file not group-owned by "root" or a required system account. + +$ sudo chgrp root [FILE]Verify the system commands contained in the following directories are group-owned by root or a system account: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Run the check with the following command: + +$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type f -exec stat -c "%n %G" '{}' \; + +If any system commands are returned that are not Set Group ID up on execution (SGID) files and group-owned by a required system account, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>UBTU-18-010144The Ubuntu operating system must have directories that contain system commands group-owned by root.<VulnDiscussion>If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109749V-100645CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec chgrp root '{}' \;Verify the system commands directories are group-owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Run the check with the following command: + +# sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec stat -c "%n %G" '{}' \; + +If any system commands directories are returned that are not Set Group ID up on execution (SGID) files and owned by a privileged account, this is a finding.SRG-OS-000266-GPOS-00101<GroupDescription></GroupDescription>UBTU-18-010145The Ubuntu operating system must enforce password complexity by requiring that at least one special character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. + +Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109751V-100647CCI-001619Configure the Ubuntu operating system to enforce password complexity by requiring that at least one special character be used. + +Add or update the following line in the "/etc/security/pwquality.conf" file to include the "ocredit=-1" parameter: + +ocredit=-1Determine if the field "ocredit" is set in the "/etc/security/pwquality.conf" file with the following command: + +# grep -i "ocredit" /etc/security/pwquality.conf +ocredit=-1 + +If the "ocredit" parameter is greater than "-1", or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010150The Ubuntu Operating system must disable the x86 Ctrl-Alt-Delete key sequence if a graphical user interface is installed.<VulnDiscussion>A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the graphical environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109753V-100649CCI-000366Configure the system to disable the Ctrl-Alt-Delete sequence when using a graphical user interface by creating or editing the /etc/dconf/db/local.d/00-disable-CAD file. + +Add the setting to disable the Ctrl-Alt-Delete sequence for the graphical user interface: + +[org/gnome/settings-daemon/plugins/media-keys] +logout='' + +Then update the dconf settings: + +# dconf updateVerify the Ubuntu operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface. + +Check that the "logout" target is not bound to an action with the following command: + +# grep logout /etc/dconf/db/local.d/* + +logout='' + +If the "logout" key is bound to an action, is commented out, or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010151The Ubuntu Operating system must disable the x86 Ctrl-Alt-Delete key sequence.<VulnDiscussion>A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100651SV-109755CCI-000366Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commands: + +$ sudo systemctl disable ctrl-alt-del.target + +$ sudo systemctl mask ctrl-alt-del.target + +And reload the daemon to take effect: + +$ sudo systemctl daemon-reloadVerify the Ubuntu operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed. + +Check that the "ctrl-alt-del.target" (otherwise also known as reboot.target) is not active with the following command: + +$ sudo systemctl status ctrl-alt-del.target +ctrl-alt-del.target +Loaded: masked (/dev/null; bad) +Active: inactive (dead) + +If the "ctrl-alt-del.target" is not masked, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010201The Ubuntu operating system must generate audit records for the use and modification of the tallylog file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109757V-100653CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "tallylog" file occur. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/tallylog -p wa -k logins + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "tallylog" file occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep tallylog + +-w /var/log/tallylog -p wa -k logins + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010202The Ubuntu operating system must generate audit records for the use and modification of faillog file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109759V-100655CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "faillog" file occur. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/faillog -p wa -k logins + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "faillog" file occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep faillog + +-w /var/log/faillog -p wa -k logins + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010203The Ubuntu operating system must generate audit records for the use and modification of the lastlog file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100657SV-109761CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "lastlog" file occur. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/lastlog -p wa -k logins + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "lastlog" file occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep lastlog + +-w /var/log/lastlog -p wa -k logins + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000471-GPOS-00215<GroupDescription></GroupDescription>UBTU-18-010237The Ubuntu operating system must generate audit records for privileged activities or other system-level access.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109763V-100659CCI-000172Configure the Ubuntu operating system to audit privileged activities. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/sudo.log -p wa -k actions + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system audits privileged activities. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep sudo.log + +-w /var/log/sudo.log -p wa -k priv_actions + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Notes: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>UBTU-18-010238The Ubuntu operating system must generate audit records for the /var/log/wtmp file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100661SV-109765CCI-000172Configure the audit system to generate audit events showing start and stop times for user access via the /var/log/wtmp file. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/wtmp -p wa -k logins + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records showing start and stop times for user access to the system via /va/rlog/wtmp. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep '/var/log/wtmp' + +-w /var/log/wtmp -p wa -k logins + +If the command does not return a line matching the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>UBTU-18-010239The Ubuntu operating system must generate audit records for the /var/run/utmp file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100663SV-109767CCI-000172Configure the audit system to generate audit events showing start and stop times for user access via the /var/run/utmp file. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: +-w /var/run/utmp -p wa -k logins + +Note: The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: +$ sudo augenrules --loadVerify the Ubuntu operating system generates audit records showing start and stop times for user access to the system via /var/run/utmp file. + +Check the currently configured audit rules with the following command: +$ sudo auditctl -l | grep '/var/run/utmp' + +-w /var/run/utmp -p wa -k logins + +If the command does not return a line matching the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>UBTU-18-010240The Ubuntu operating system must generate audit records for the /var/log/btmp file.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109769V-100665CCI-000172Configure the audit system to generate audit events showing start and stop times for user access via the /var/log/btmp file. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-w /var/log/btmp -p wa -k logins + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records showing start and stop times for user access to the system via /var/log/btmp file. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep '/var/log/btmp' + +-w /var/log/btmp -p wa -k logins + +If the command does not return a line matching the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000476-GPOS-00221<GroupDescription></GroupDescription>UBTU-18-010244The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000476-GPOS-00221, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000004-GPOS-00004</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109771V-100667CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. + +Add or update the following rule to "/etc/audit/rules.d/stig.rules": + +-w /etc/passwd -p wa -k usergroup_modification + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep passwd + +-w /etc/passwd -p wa -k usergroup_modification + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000476-GPOS-00221<GroupDescription></GroupDescription>UBTU-18-010245The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000476-GPOS-00221, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100669SV-109773CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. + +Add or update the following rule to "/etc/audit/rules.d/stig.rules": + +-w /etc/group -p wa -k usergroup_modification + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep group + +-w /etc/group -p wa -k usergroup_modification + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000476-GPOS-00221<GroupDescription></GroupDescription>UBTU-18-010246The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000476-GPOS-00221, SRG-OS-000463-GPOS-00207, SRG-OS-000458-GPOS-00203, SRG-OS-000303-GPOS-00120, SRG-OS-000241-GPOS-00091, SRG-OS-000240-GPOS-00090, SRG-OS-000239-GPOS-00089</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100671SV-109775CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. + +Add or update the following rule to "/etc/audit/rules.d/stig.rules": + +-w /etc/gshadow -p wa -k usergroup_modification + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep gshadow + +-w /etc/gshadow -p wa -k usergroup_modification + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000476-GPOS-00221<GroupDescription></GroupDescription>UBTU-18-010247The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000476-GPOS-00221, SRG-OS-000463-GPOS-00207, SRG-OS-000458-GPOS-00203, SRG-OS-000303-GPOS-00120, SRG-OS-000241-GPOS-00091, SRG-OS-000240-GPOS-00090, SRG-OS-000239-GPOS-00089</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109777V-100673CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. + +Add or update the following rule to "/etc/audit/rules.d/stig.rules": + +-w /etc/shadow -p wa -k usergroup_modification + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep shadow + +-w /etc/shadow -p wa -k usergroup_modification + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000476-GPOS-00221<GroupDescription></GroupDescription>UBTU-18-010248The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000476-GPOS-00221, SRG-OS-000463-GPOS-00207, SRG-OS-000458-GPOS-00203, SRG-OS-000303-GPOS-00120, SRG-OS-000241-GPOS-00091, SRG-OS-000240-GPOS-00090, SRG-OS-000239-GPOS-00089</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100675SV-109779CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd. + +Add or update the following rule to "/etc/audit/rules.d/stig.rules": + +-w /etc/security/opasswd -p wa -k usergroup_modification + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep opasswd + +-w /etc/security/opasswd -p wa -k usergroup_modification + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000038-GPOS-00016<GroupDescription></GroupDescription>UBTU-18-010250The Ubuntu operating system must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DoD-defined auditable events and actions in near real time.<VulnDiscussion>Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. + +Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. + +Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted. + +Associating event types with detected events in the Ubuntu operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. + +Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000062-GPOS-00031, SRG-OS-000122-GPOS-00063, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000365-GPOS-00152, SRG-OS-000392-GPOS-00172, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109781V-100677CCI-000131CCI-000132CCI-000133CCI-000134CCI-000135CCI-000154CCI-000158CCI-000169CCI-000172CCI-001814CCI-001875CCI-001876CCI-001877CCI-001878CCI-001879CCI-001880CCI-001914CCI-002884Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. + +Install the audit service (if the audit service is not already installed) with the following command: + +# sudo apt-get install auditd + +Enable the audit service with the following command: + +# sudo systemctl enable auditd.service + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the audit service is configured to produce audit records. + +Check that the audit service is installed properly with the following command: + +# dpkg -l | grep auditd + +If the "auditd" package is not installed, this is a finding. + +Check that the audit service is enabled with the following command: + +# systemctl is-enabled auditd.service + +If the command above returns "disabled", this is a finding. + +Check that the audit service is properly running and active on the system with the following command: + +# systemctl is-active auditd.service +active + +If the command above returns "inactive", this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>UBTU-18-010300The Ubuntu operating system must alert the ISSO and SA (at a minimum) in the event of an audit processing failure.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. + +Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. + +This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100679SV-109783CCI-000139Configure "auditd" service to notify the System Administrator (SA) and Information System Security Officer (ISSO) in the event of an audit processing failure. + +Edit the following line in "/etc/audit/auditd.conf" to ensure that administrators are notified via email for those situations: + +action_mail_acct = root + +Restart the auditd service so the changes take effect: +# sudo systemctl restart auditd.serviceVerify that the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) are notified in the event of an audit processing failure. + +Check that the Ubuntu operating system notifies the SA and ISSO (at a minimum) win the event of an audit processing failure with the following command: + +# sudo grep action_mail_acct = root /etc/audit/auditd.conf + +action_mail_acct = root + +If the value of the "action_mail_acct" keyword is not set to "root" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the returned line is commented out, this is a finding.SRG-OS-000047-GPOS-00023<GroupDescription></GroupDescription>UBTU-18-010301The Ubuntu operating system must shut down by default upon audit failure (unless availability is an overriding concern).<VulnDiscussion>It is critical that when the Ubuntu operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. + +When availability is an overriding concern, other approved actions in response to an audit failure are as follows: + +1) If the failure was caused by the lack of audit record storage capacity, the Ubuntu operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. + +2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the Ubuntu operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109785V-100681CCI-000140Configure the Ubuntu operating system to shut down by default upon audit failure (unless availability is an overriding concern). + +Add or update the following line (depending on configuration "disk_full_action" can be set to "SYSLOG", "HALT" or "SINGLE") in "/etc/audit/auditd.conf" file: + +disk_full_action = HALT + +Restart the auditd service so the changes take effect: +# sudo systemctl restart auditd.serviceVerify the Ubuntu operating system takes the appropriate action when the audit storage volume is full. + +Check that the Ubuntu operating system takes the appropriate action when the audit storage volume is full with the following command: + +# sudo grep disk_full_action /etc/audit/auditd.conf + +disk_full_action = HALT + +If the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, this is a finding.SRG-OS-000058-GPOS-00028<GroupDescription></GroupDescription>UBTU-18-010305The Ubuntu operating system must be configured so that audit log files cannot be read or write-accessible by unauthorized users.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. + +Satisfies: SRG-OS-000058-GPOS-00028, SRG-OS-000057-GPOS-00027</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109787V-100683CCI-000162CCI-000163Configure the audit log files to have a mode of "0600" or less permissive. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log files to have a mode of "0600" or less permissive by using the following command: + +# sudo chmod 0600 /var/log/audit/*Verify that the audit log files have a mode of "0600" or less permissive. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the audit log files have a mode of "0600" or less by using the following command: + +# sudo stat -c "%n %a" /var/log/audit/* +/var/log/audit/audit.log 600 + +If the audit log files have a mode more permissive than "0600", this is a finding.SRG-OS-000058-GPOS-00028<GroupDescription></GroupDescription>UBTU-18-010306The Ubuntu operating system must permit only authorized accounts ownership of the audit log files.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. + +Satisfies: SRG-OS-000058-GPOS-00028, SRG-OS-000057-GPOS-00027</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109789V-100685CCI-000162CCI-000163Configure the audit log files to be owned by "root" user. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log files to be owned by "root" user by using the following command: + +# sudo chown root /var/log/audit/*Verify that the audit log files are owned by "root" account. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the audit log files are owned by the "root" user by using the following command: + +# sudo stat -c "%n %U" /var/log/audit/* +/var/log/audit/audit.log root + +If the audit log files are owned by an user other than "root", this is a finding.SRG-OS-000058-GPOS-00028<GroupDescription></GroupDescription>UBTU-18-010307The Ubuntu operating system must permit only authorized groups to own the audit log files.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. + +Satisfies: SRG-OS-000058-GPOS-00028, SRG-OS-000057-GPOS-00027</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109791V-100687CCI-000162CCI-000163Configure the audit log files to be owned by "root" group. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log files to be owned by "root" group by using the following command: + +# sudo chown :root /var/log/audit/*Verify that the audit log files are owned by "root" group. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the audit log files are owned by the "root" group by using the following command: + +# sudo stat -c "%n %G" /var/log/audit/* +/var/log/audit/audit.log root + +If the audit log files are owned by a group other than "root", this is a finding.SRG-OS-000059-GPOS-00029<GroupDescription></GroupDescription>UBTU-18-010308The Ubuntu operating system must be configured so that the audit log directory is not write-accessible by unauthorized users.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109793V-100689CCI-000164Configure the audit log directory to have a mode of "0750" or less permissive. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log directory to have a mode of "0750" or less permissive by using the following command: + +# chmod -R g-w,o-rwx /var/log/auditVerify that the audit log directory has a mode of "0750" or less permissive. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the directory has a mode of "0750" or less by using the following command: + +# sudo stat -c "%n %a" /var/log/audit +/var/log/audit 750 + +If the audit log directory has a mode more permissive than "0750", this is a finding.SRG-OS-000059-GPOS-00029<GroupDescription></GroupDescription>UBTU-18-010309The Ubuntu operating system must allow only authorized accounts to own the audit log directory.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100691SV-109795CCI-000164Configure the audit log directory to be owned by "root" user. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log directory to be owned by "root" user by using the following command: + +# chown -R root /var/log/auditVerify that the audit log directory is owned by "root" account. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the directory is owned by the "root" user by using the following command: + +# sudo stat -c "%n %U" /var/log/audit +/var/log/audit root + +If the audit log directory is owned by an user other than "root", this is a finding.SRG-OS-000059-GPOS-00029<GroupDescription></GroupDescription>UBTU-18-010310The Ubuntu operating system must ensure only authorized groups can own the audit log directory and its underlying files.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. + +To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. + +Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109797V-100693CCI-000164Configure the audit log directory to be owned by "root" group. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, configure the audit log directory to be owned by "root" group by using the following command: + +# chown -R :root /var/log/auditVerify that the audit log directory is owned by "root" group. + +First determine where the audit logs are stored with the following command: + +# sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Using the path of the directory containing the audit logs, check if the directory is owned by the "root" group by using the following command: + +# sudo stat -c "%n %G" /var/log/audit +/var/log/audit root + +If the audit log directory is owned by a group other than "root", this is a finding.SRG-OS-000063-GPOS-00032<GroupDescription></GroupDescription>UBTU-18-010311The Ubuntu operating system must be configured so that audit configuration files are not write-accessible by unauthorized users.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100695SV-109799CCI-000171Configure "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files to have a mode of 0640 by using the following command: + +# chmod -R 0640 /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/* + +Note: The "root" account must be used to edit any files in the /etc/audit and /etc/audit/rules.d/ directories.Verify that "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files have a mode of 0640 or less permissive by using the following command: + +# sudo ls -al /etc/audit/ /etc/audit/rules.d/ + +/etc/audit/: + +drwxr-x--- 3 root root 4096 Nov 25 11:02 . + +drwxr-xr-x 130 root root 12288 Dec 19 13:42 .. + +-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf + +-rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules + +-rw-r----- 1 root root 9373 Dec 27 09:56 audit.rules.prev + +-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules + +drwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d + +/etc/audit/rules.d/: + +drwxr-x--- 2 root root 4096 Dec 27 09:56 . + +drwxr-x--- 3 root root 4096 Nov 25 11:02 .. + +-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules + +If "/etc/audit/audit.rule","/etc/audit/rules.d/*" or "/etc/audit/auditd.conf" file have a mode more permissive than "0640", this is a finding.SRG-OS-000063-GPOS-00032<GroupDescription></GroupDescription>UBTU-18-010312The Ubuntu operating system must permit only authorized accounts to own the audit configuration files.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109801V-100697CCI-000171Configure "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files to be owned by root user by using the following command: + +# chown root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/* + +Note: The "root" account must be used to edit any files in the /etc/audit and /etc/audit/rules.d/ directories.Verify that "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files are owned by root account by using the following command: + +# sudo ls -al /etc/audit/ /etc/audit/rules.d/ + +/etc/audit/: + +drwxr-x--- 3 root root 4096 Nov 25 11:02 . + +drwxr-xr-x 130 root root 12288 Dec 19 13:42 .. + +-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf + +-rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules + +-rw-r----- 1 root root 9373 Dec 27 09:56 audit.rules.prev + +-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules + +drwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d + +/etc/audit/rules.d/: + +drwxr-x--- 2 root root 4096 Dec 27 09:56 . + +drwxr-x--- 3 root root 4096 Nov 25 11:02 .. + +-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules + +If "/etc/audit/audit.rules" or "/etc/audit/rules.d/*" or "/etc/audit/auditd.conf" file is owned by a user other than "root", this is a finding.SRG-OS-000063-GPOS-00032<GroupDescription></GroupDescription>UBTU-18-010313The Ubuntu operating system must permit only authorized groups to own the audit configuration files.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100699SV-109803CCI-000171Configure "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files to be owned by root group by using the following command: + +# chown :root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/* + +Note: The "root" account must be used to edit any files in the /etc/audit and /etc/audit/rules.d/ directories.Verify that "/etc/audit/audit.rules", "/etc/audit/rules.d/*" and "/etc/audit/auditd.conf" files are owned by root group by using the following command: + +# sudo ls -al /etc/audit/ /etc/audit/rules.d/ + +/etc/audit/: + +drwxr-x--- 3 root root 4096 Nov 25 11:02 . + +drwxr-xr-x 130 root root 12288 Dec 19 13:42 .. + +-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf + +-rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules + +-rw-r----- 1 root root 9373 Dec 27 09:56 audit.rules.prev + +-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules + +drwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d + +/etc/audit/rules.d/: + +drwxr-x--- 2 root root 4096 Dec 27 09:56 . + +drwxr-x--- 3 root root 4096 Nov 25 11:02 .. + +-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules + +If "/etc/audit/audit.rules" or "/etc/audit/rules.d/*" or "/etc/audit/auditd.conf" file is owned by a group other than "root", this is a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>UBTU-18-010314The Ubuntu operating system must allocate audit record storage capacity to store at least one weeks worth of audit records, when audit records are not immediately sent to a central audit record storage facility.<VulnDiscussion>In order to ensure Ubuntu operating systems have sufficient storage capacity in which to write the audit logs, Ubuntu operating system needs to be able to allocate audit record storage capacity. + +The task of allocating audit record storage capacity is usually performed during initial installation of the Ubuntu operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100701SV-109805CCI-001849Allocate enough storage capacity for at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. + +If audit records are stored on a partition made specifically for audit records, use the "parted" program to resize the partition with sufficient space to contain one week's worth of audit records. + +If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient amount of space will need be to be created. + +Set the auditd server to point to the mount point where the audit records must be located: + +# sudo sed -i -E 's@^(log_file\s*=\s*).*@\1 <log mountpoint>/audit.log@' /etc/audit/auditd.conf + +where <log mountpoint> is the aforementioned mount point.Verify the Ubuntu operating system allocates audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. + +Determine which partition the audit records are being written to with the following command: + +# sudo grep log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Check the size of the partition that audit records are written to (with the example being /var/log/audit/) with the following command: + +# df –h /var/log/audit/ +/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit + +If the audit records are not written to a partition made specifically for audit records (/var/log/audit is a separate partition), determine the amount of space being used by other files in the partition with the following command: + +#du –sh [audit_partition] +1.8G /var/log/audit + +Note: The partition size needed to capture a week's worth of audit records is based on the activity level of the system and the total storage capacity available. In normal circumstances, 10.0 GB of storage space for audit records will be sufficient. + +If the audit record partition is not allocated for sufficient storage capacity, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010315The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the su command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109807V-100703CCI-000172Configure the Ubuntu operating system to generate audit records when successful/unsuccessful attempts to use the "su" command occur. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify if the Ubuntu operating system generates audit records when successful/unsuccessful attempts to use the "su" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep '/bin/su' + +-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-priv_change + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010316The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chfn command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100705SV-109809CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "chfn" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chfn + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify if the Ubuntu operating system generates audit records when successful/unsuccessful attempts to use of the "chfn" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep '/usr/bin/chfn' + +-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chfn + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010317The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the mount command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100707SV-109811CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "mount" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/bin/mount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify if the Ubuntu operating system generates audit records when successful/unsuccessful attempts to use of the "mount" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep '/bin/mount' + +-a always,exit -F path=/bin/mount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-mount + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010318The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the umount command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109813V-100709CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "umount" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-umount + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify if the Ubuntu operating system generates audit records when successful/unsuccessful attempts to use of the "umount" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep '/bin/umount' + +-a always,exit -F path=/bin/umount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-umount + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010319The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the ssh-agent command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100711SV-109815CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ssh-agent" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "ssh-agent" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep '/usr/bin/ssh-agent' + +-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010320The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the ssh-keysign command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100713SV-109817CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ssh-keysign" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "ssh-keysign" command occur. + +Check the configured audit rules with the following commands: + +#sudo auditctl -l | grep ssh-keysign + +-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010321The Ubuntu operating system must generate audit records for any usage of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000462-GPOS-00206</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100715SV-109819CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +To reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record upon successful/unsuccessful attempts to use the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep xattr + +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod + +If the command does not return audit rules for the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" syscalls or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The "-k" allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010327The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100725SV-109829CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown", "fchown", "fchownat", and "lchown" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules": + +-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng +-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +To reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record upon successful/unsuccessful attempts to use the "chown", "fchown", "fchownat", and "lchown" system calls. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep chown + +-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng +-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return audit rules for the "chown", "fchown", "fchownat", and "lchown" syscalls or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The "-k" allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010331The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100733SV-109837CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod", "fchmod", and "fchmodat" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules": + +-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng +-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +To reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record upon successful/unsuccessful attempts to use the "chmod", "fchmod", and "fchmodat" system calls. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep chmod + +-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng +-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return audit rules for the "chmod", "fchmod", and "fchmodat" syscalls or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The "-k" allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010334The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100739SV-109843CCI-000172Configure the audit system to generate an audit event for any unsuccessful use of the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +To reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record upon unsuccessful attempts to use the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep 'open\|truncate\|creat' + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access + +If the command does not return audit rules for the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" syscalls or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The "-k" allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010340The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the sudo command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109855V-100751CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudo" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "sudo" command. + +Check the configured audit rules with the following command: + +# sudo auditctl -l | grep /usr/bin/sudo + +-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010341The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the sudoedit command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100753SV-109857CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudoedit" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules": + +-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "sudoedit" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep /usr/bin/sudoedit + +-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010342The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chsh command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109859V-100755CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chsh" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chsh" command. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep chsh + +-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Notes: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010343The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the newgrp command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100757SV-109861CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "newgrp" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "newgrp" command occur. + +Check the configured audit rules with the following commands: + +# sudo auditctl -l | grep newgrp + +-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010344The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chcon command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100759SV-109863CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chcon" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chcon" command occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep chcon + +-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010345The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the apparmor_parser command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100761SV-109865CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "apparmor_parser" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "apparmor_parser" command occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep apparmor_parser + +-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010346The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the setfacl command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109867V-100763CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "setfacl" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "setfacl" command occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep setfacl + +-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010347The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chacl command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100765SV-109869CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chacl" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chacl" command occur. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep chacl + +-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above. + +If the command does not return a line that matches the example or the line is commented out, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010348The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the passwd command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109871V-100767CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "passwd" command. + +Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --load +Verify that an audit event is generated for any successful/unsuccessful use of the "passwd" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w passwd + +-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-passwd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010349The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the unix_update command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100769SV-109873CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "unix_update" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-unix-update + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "unix_update" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w unix_update + +-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-unix-update + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010350The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the gpasswd command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109875V-100771CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the gpasswd command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "gpasswd" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w gpasswd + +-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-gpasswd + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010351The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the chage command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109877V-100773CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "chage" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "chage" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w chage + +-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chage + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010352The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the usermod command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109879V-100775CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "usermod" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "usermod" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w usermod + +-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-usermod + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010353The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the crontab command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100917SV-110021CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "crontab" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w crontab + +-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-crontab + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>UBTU-18-010354The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the pam_timestamp_check command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100777SV-109881CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "pam_timestamp_check" command. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify that an audit event is generated for any successful/unsuccessful use of the "pam_timestamp_check" command. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep -w pam_timestamp_check + +-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-pam_timestamp_check + +If the command does not return a line that matches the example or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000326-GPOS-00126<GroupDescription></GroupDescription>UBTU-18-010358The Ubuntu operating system must prevent all software from executing at higher privilege levels than users executing the software and the audit system must be configured to audit the execution of privileged functions.<VulnDiscussion>In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations. + +Some programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review. + +Satisfies: SRG-OS-000326-GPOS-00126, SRG-OS-000327-GPOS-00127</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109889V-100785CCI-002233CCI-002234Configure the Ubuntu operating system to audit the execution of all privileged functions. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv +-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv +-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv +-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system audits the execution of privilege functions by auditing the "execve" system call. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep execve + +-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv +-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv +-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv +-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000468-GPOS-00212<GroupDescription></GroupDescription>UBTU-18-010375The Ubuntu operating system must generate audit records upon successful/unsuccessful use of unlink, unlinkat, rename, renameat, and rmdir system calls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, however, by combining syscalls into one rule whenever possible.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100797SV-109901CCI-000172Configure the audit system to generate audit events upon successful/unsuccessful use of "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -Fauid>=1000 -F auid!=4294967295 -k delete +-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=4294967295 -k delete + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +To reload the rules file, issue the following command: + +# sudo augenrules --loadVerify the Ubuntu operating system generates audit records upon successful/unsuccessful use of "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls. + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep 'unlink\|rename\|rmdir' + +-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k delete +-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k delete + +If the command does not return audit rules for the "unlink", "unlinkat", "rename", "renameat", and "rmdir" syscalls or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The "-k" allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>UBTU-18-010387The Ubuntu operating system must generate records for successful/unsuccessful uses of init_module or finit_module syscalls.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109919V-100815CCI-000172Configure the audit system to generate an audit event for any use of the "init_module" or "finit_module" system calls. + +Add or update the following rules in the "/etc/audit/rules.d/stig.rules" file: + +-a always,exit -F arch=b32 -S init_module -S finit_module -F key=modules +-a always,exit -F arch=b64 -S init_module -S finit_module -F key=modules + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify if the Ubuntu operating system is configured to audit the "init_module" and "finit_module" syscalls, by running the following command: + +# sudo auditctl -l | grep -E 'init_module|finit_module' + +-a always,exit -F arch=b64 -S init_module -S finit_module -F key=modules +-a always,exit -F arch=b32 -S init_module -S finit_module -F key=modules + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>UBTU-18-010388The Ubuntu operating system must generate records for successful/unsuccessful uses of delete_module syscall and when unloading dynamic kernel modules.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). +Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000471-GPOS-00216</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100817SV-109921CCI-000172Configure the Ubuntu operating system to generate an audit event for any use of the delete_module system call. + +Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file. + +-a always,exit -F arch=b32 -S delete_module -F key=modules +-a always,exit -F arch=b64 -S delete_module -F key=modules + +Notes: For 32-bit architectures, only the 32-bit specific entries are required. +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify if the Ubuntu operating system is configured to audit the "delete_module" syscall, by running the following command: + +# sudo auditctl -l | egrep delete_module + +-a always,exit -F arch=b64 -S delete_module -F key=modules +-a always,exit -F arch=b32 -S delete_module -F key=modules + +If the command does not return lines that match the example or the lines are commented out, this is a finding. + +Notes: +For 32-bit architectures, only the 32-bit specific output lines from the commands are required. +The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>UBTU-18-010389The Ubuntu operating system must generate audit records when successful/unsuccessful attempts to use modprobe command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100819SV-109923CCI-000172Configure the Ubuntu operating system to audit the execution of the module management program "modprobe". + +Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file. + +-w /sbin/modprobe -p x -k modules + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify if the Ubuntu operating system is configured to audit the execution of the module management program "modprobe", by running the following command: + +sudo auditctl -l | grep "/sbin/modprobe" + +-w /sbin/modprobe -p x -k modules + +If the command does not return a line, or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>UBTU-18-010391The Ubuntu operating system must generate audit records when successful/unsuccessful attempts to use the kmod command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109925V-100821CCI-000172Configure the Ubuntu operating system to audit the execution of the module management program "kmod". + +Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file. + +-w /bin/kmod -p x -k modules + +Note: +The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify if the Ubuntu operating system is configured to audit the execution of the module management program "kmod". + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep kmod + +-w /bin/kmod -p x -k module + +If the command does not return a line, or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>UBTU-18-010392The Ubuntu operating system must generate audit records when successful/unsuccessful attempts to use the fdisk command.<VulnDiscussion>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100823SV-109927CCI-000172Configure the Ubuntu operating system to audit the execution of the partition management program "fdisk". + +Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file. + +-w /sbin/fdisk -p x -k fdisk + +Note: The root account must be used to view and/or edit any files in the /etc/audit/rules.d/ directory. + +In order to reload the rules file, issue the following command: + +# sudo augenrules --loadVerify if the Ubuntu operating system is configured to audit the execution of the partition management program "fdisk". + +Check the currently configured audit rules with the following command: + +# sudo auditctl -l | grep fdisk + +-w /sbin/fdisk -p x -k fdisk + +If the command does not return a line, or the line is commented out, this is a finding. + +Note: The '-k' allows for specifying an arbitrary identifier and the string after it does not need to match the example output above.SRG-OS-000027-GPOS-00008<GroupDescription></GroupDescription>UBTU-18-010400The Ubuntu operating system must limit the number of concurrent sessions to ten for all accounts and/or account types.<VulnDiscussion>Ubuntu operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks. + +This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100825SV-109929CCI-000054Configure the Ubuntu operating system to limit the number of concurrent sessions to ten for all accounts and/or account types. + +Add the following line to the top of the /etc/security/limits.conf: + +* hard maxlogins 10Verify that the Ubuntu operating system limits the number of concurrent sessions to ten for all accounts and/or account types by running the following command: +$ grep maxlogins /etc/security/limits.conf + +The result must contain the following line: +* hard maxlogins 10 + +If the "maxlogins" item is missing, or the value is not set to 10 or less, or is commented out, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>UBTU-18-010401The Ubuntu operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. + +The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, Ubuntu operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100827SV-109931CCI-000056Configure the Ubuntu operating system so that it allows a user to lock the current graphical user interface session. + +Note: If the Ubuntu operating system does not have a Graphical User Interface installed, this requirement is Not Applicable. + +Set the ""lock-enabled"" setting to allow graphical user interface session locks with the following command: + +# sudo gsettings set org.gnome.desktop.screensaver lock-enabled trueVerify the Ubuntu operation system has a graphical user interface session lock enabled. + +Note: If the Ubuntu operating system does not have a Graphical User Interface installed, this requirement is Not Applicable. + +Get the ""lock-enabled"" setting to verify if the graphical user interface session has the lock enabled with the following command: + +# sudo gsettings get org.gnome.desktop.screensaver lock-enabled + +true + +If "lock-enabled" is not set to "true", this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>UBTU-18-010402The Ubuntu operating system must initiate a session lock after a 15-minute period of inactivity for all connection types.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, the Ubuntu operating system need to be able to identify when a user's session has idled and take action to initiate the session lock. + +The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109933V-100829CCI-000057Configure the Ubuntu operating system to initiate a session logout after a 15-minute period of inactivity. + +Create a file to contain the system-wide session auto logout script (if it does not already exist) with the following command: + +# sudo touch /etc/profile.d/autologout.sh + +Add the following lines to the "/etc/profile.d/autologout.sh" script: + +TMOUT=900 +readonly TMOUT +export TMOUTVerify the Ubuntu operating system initiates a session logout after a 15-minute period of inactivity. + +Check that the proper auto logout script exists with the following command: + +# cat /etc/profile.d/autologout.sh +TMOUT=900 +readonly TMOUT +export TMOUT + +If the file "/etc/profile.d/autologout.sh" does not exist with the contents shown above, the value of "TMOUT" is greater than 900, or the timeout values are commented out, this is a finding.SRG-OS-000030-GPOS-00011<GroupDescription></GroupDescription>UBTU-18-010403The Ubuntu operating system must be configured for users to directly initiate a session lock for all connection types.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. + +The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, the Ubuntu operating system need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity. + +Satisfies: SRG-OS-000030-GPOS-00011, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100831SV-109935CCI-000058CCI-000060Install the "vlock" (if it is not already installed) package by running the following command: + +# sudo apt-get install vlockVerify the Ubuntu operating system has the 'vlock' package installed, by running the following command: + +# dpkg -l | grep vlock + +If "vlock" is not installed, this is a finding.SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>UBTU-18-010410The Ubuntu operating system must monitor remote access methods.<VulnDiscussion>Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best. + +Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Automated monitoring of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109939V-100835CCI-000067Configure the Ubuntu operating system to monitor all remote access methods by adding the following lines to the "/etc/rsyslog.d/50-default.conf" file: + +auth.*,authpriv.* /var/log/secure +daemon.* /var/log/messages + +In order for the changes to take effect the "rsyslog" service must be restarted with the following command: + +$ sudo systemctl restart rsyslog.serviceVerify that the Ubuntu operating system monitors all remote access methods. + +Check that remote access methods are being logged by running the following command: + +$ grep -E -r '^(auth,authpriv\.\*|daemon\.\*)' /etc/rsyslog.* +/etc/rsyslog.d/50-default.conf:auth,authpriv.* /var/log/auth.log +/etc/rsyslog.d/50-default.conf:daemon.* /var/log/messages + +If "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged in at least one of the config files, this is a finding.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>UBTU-18-010411The Ubuntu operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions.<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. + +Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. + +By specifying a cipher list with the order of ciphers being in a “strongest to weakest” orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109941V-100837CCI-000068Configure the Ubuntu operating system to allow the SSH daemon to only implement DoD-approved encryption. + +Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): + +Ciphers aes256-ctr,aes192-ctr,aes128-ctr + +In order for the changes to take effect, the SSH daemon must be restarted. + +# sudo systemctl restart sshd.serviceVerify the SSH daemon is configured to only implement DoD-approved encryption. + +Check the SSH daemon's current configured ciphers by running the following command: + +# grep -E '^Ciphers ' /etc/ssh/sshd_config + +Ciphers aes256-ctr,aes192-ctr, aes128-ctr + +If any ciphers other than "aes256-ctr", "aes192-ctr", or "aes128-ctr" are listed, the order differs from the example above, the "Ciphers" keyword is missing, or the returned line is commented out, this is a finding. +SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>UBTU-18-010412The Ubuntu operating system must enforce SSHv2 for network access to all accounts.<VulnDiscussion>A replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the authenticator and the operating system validating the user credentials must not be vulnerable to a replay attack. + +An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. + +A privileged account is any information system account with authorizations of a privileged user. + +Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100839SV-109943CCI-001941CCI-001942Configure the Ubuntu operating system to enforce SSHv2 for network access to all accounts. + +Add or update the following line in the "/etc/ssh/sshd_config" file: + +Protocol 2 + +Restart the ssh service. + +# systemctl restart sshd.serviceVerify that the Ubuntu operating system enforces SSH protocol 2 for network access. + +Check the protocol versions that SSH allows with the following command: + +# grep Protocol /etc/ssh/sshd_config + +Protocol 2 + +If the returned line allows for use of protocol "1", is commented out, or the line is missing, this is a finding.SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>UBTU-18-010414The Ubuntu operating system must use strong authenticators in establishing nonlocal maintenance and diagnostic sessions.<VulnDiscussion>Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100841SV-109945CCI-000877Configure the Ubuntu operating system to use strong authentication when establishing nonlocal maintenance and diagnostic sessions. + +Add or modify the following line to /etc/ssh/sshd_config + +UsePAM yesVerify the Ubuntu operating system is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance. + +Check that "UsePAM" is set to yes in /etc/ssh/sshd_config: + +# grep UsePAM /etc/ssh/sshd_config + +UsePAM yes + +If "UsePAM" is not set to "yes", this is a finding.SRG-OS-000126-GPOS-00066<GroupDescription></GroupDescription>UBTU-18-010415The Ubuntu operating system must immediately terminate all network connections associated with SSH traffic after a period of inactivity.<VulnDiscussion>Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. + +Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. + +Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. + +This capability is typically reserved for specific Ubuntu operating system functionality where the system owner, data owner, or organization requires additional assurance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100843SV-109947CCI-000879Configure the Ubuntu operating system to automatically terminate inactive SSH sessions after a period of inactivity. + +Modify or append the following line in the "/etc/ssh/sshd_config" file replacing "[Count]" with a value of 1: + +ClientAliveCountMax 1 + +In order for the changes to take effect, the SSH daemon must be restarted. + +# sudo systemctl restart sshd.serviceVerify that all network connections associated with SSH traffic automatically terminate after a period of inactivity. + +Check that "ClientAliveCountMax" variable is set in "/etc/ssh/sshd_config" file by performing the following command: + +# sudo grep -i clientalivecountmax /etc/ssh/sshd_config + +ClientAliveCountMax 1 + +If "ClientAliveCountMax" is not set, or not set to "1", or is commented out, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>UBTU-18-010416The Ubuntu operating system must automatically terminate all network connections associated with SSH traffic at the end of the session or after 10 minutes of inactivity.<VulnDiscussion>Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. + +Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. + +Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. + +Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. + +Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. + +Satisfies: SRG-OS-000279-GPOS-00109</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100845SV-109949CCI-001133CCI-002361Configure the Ubuntu operating system to automatically terminate all network connections associated with SSH traffic at the end of a session or after a 10 minute period of inactivity. + +Modify or append the following line in the "/etc/ssh/sshd_config" file replacing "[Interval]" with a value of "600" or less: + +ClientAliveInterval 600 + +In order for the changes to take effect, the SSH daemon must be restarted. + +# sudo systemctl restart sshd.serviceVerify that all network connections associated with SSH traffic are automatically terminated at the end of the session or after 10 minutes of inactivity. + +Check that the "ClientAliveInterval" variable is set to a value of "600" or less by performing the following command: + +# sudo grep -i clientalive /etc/ssh/sshd_config + +ClientAliveInterval 600 + +If "ClientAliveInterval" does not exist, is not set to a value of "600" or less in "/etc/ssh/sshd_config", or is commented out, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>UBTU-18-010417The Ubuntu operating system must configure the SSH daemon to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms to protect the integrity of nonlocal maintenance and diagnostic communications.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. + +Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. + +Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. + +Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100847SV-109951CCI-001453CCI-002890CCI-003123Configure the Ubuntu operating system to allow the SSH daemon to only use Message Authentication Codes (MACs) that employ FIPS 140-2 approved ciphers. + +Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): + +MACs hmac-sha2-512,hmac-sha2-256 + +In order for the changes to take effect, reload the SSH daemon. + +# sudo systemctl reload sshd.serviceVerify the Ubuntu operating system configures the SSH daemon to only use Message Authentication Codes (MACs) that employ FIPS 140-2 approved ciphers. + +Check that the SSH daemon is configured to only use MACs that employ FIPS 140-2 approved ciphers with the following command: + +# sudo grep -i macs /etc/ssh/sshd_config + +MACs hmac-sha2-512,hmac-sha2-256 + +If any ciphers other than "hmac-sha2-512" or "hmac-sha2-256" are listed, the order differs from the example above, or the returned line is commented out, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>UBTU-18-010420The Ubuntu operating system must use SSH to protect the confidentiality and integrity of transmitted information unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS).<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. + +This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. + +Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. + +Alternative physical protection measures include PDS. PDSs are used to transmit unencrypted classified National Security Information (NSI) through an area of lesser classification or control. Since the classified NSI is unencrypted, the PDS must provide adequate electrical, electromagnetic, and physical safeguards to deter exploitation. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109953V-100849CCI-002418CCI-002420CCI-002421CCI-002422Install the "ssh" meta-package on the system with the following command: + +# sudo apt install ssh + +Enable the "ssh" service to start automatically on reboot with the following command: + +# sudo systemctl enable sshd.service + +Ensure that the "ssh" service is running. + +# sudo systemctl start sshd.serviceCheck that the ssh package is installed with the following command: + +# sudo dpkg -l | grep openssh +ii openssh-client 1:7.6p1-4ubuntu0.1 amd64 secure shell (SSH) client, for secure access to remote machines +ii openssh-server 1:7.6p1-4ubuntu0.1 amd64 secure shell (SSH) server, for secure access from remote machines +ii openssh-sftp-server 1:7.6p1-4ubuntu0.1 amd64 secure shell (SSH) sftp server module, for SFTP access from remote machines + +If the "openssh" server package is not installed, this is a finding. + +Check that the "sshd.service" is loaded and active with the following command: + +# sudo systemctl status sshd.service | egrep -i "(active|loaded)" + Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) + Active: active (running) since Thu 2019-01-24 22:52:58 UTC; 1 weeks 3 days ago + +If "sshd.service" is not active or loaded, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>UBTU-18-010424The Ubuntu operating system must not allow unattended or automatic login via ssh.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts Ubuntu operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109955V-100851CCI-000366Configure the Ubuntu operating system to allow the SSH daemon to not allow unattended or automatic login to the system. + +Add or edit the following lines in the "/etc/ssh/sshd_config" file: + +PermitEmptyPasswords no +PermitUserEnvironment no + +In order for the changes to take effect, the SSH daemon must be restarted. + +# sudo systemctl restart sshd.serviceVerify that unattended or automatic login via ssh is disabled. + +Check that unattended or automatic login via ssh is disabled with the following command: + +# egrep '(Permit(.*?)(Passwords|Environment))' /etc/ssh/sshd_config + +PermitEmptyPasswords no +PermitUserEnvironment no + +If "PermitEmptyPasswords" or "PermitUserEnvironment" keywords are not set to "no", are missing completely, or they are commented out, this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>UBTU-18-010425The Ubuntu operating system, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.<VulnDiscussion>Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. + +A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. + +When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. + +This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000384-GPOS-00167</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100853SV-109957CCI-000185CCI-001991Configure the Ubuntu operating system, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor. + +Determine which pkcs11 module is being used via the use_pkcs11_module in /etc/pam_pkcs11/pam_pkcs11.conf and ensure "ca" is enabled in "cert_policy". + +Add or update the "cert_policy" to ensure "ca" is enabled: + +cert_policy = ca,signature,ocsp_on; + +If the system is missing an "/etc/pam_pkcs11/" directory and an "/etc/pam_pkcs11/pam_pkcs11.conf", find an example to copy into place and modify accordingly at "/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz".Verify the Ubuntu operating system, for PKI-based authentication, had valid certificates by constructing a certification path to an accepted trust anchor. + +Check which pkcs11 module is being used via the use_pkcs11_module in /etc/pam_pkcs11/pam_pkcs11.conf and then ensure "ca" is enabled in "cert_policy" with the following command: + +# sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ca + +cert_policy = ca,signature,ocsp_on; + +If "cert_policy" is not set to "ca", or the line is commented out, this is a finding.SRG-OS-000068-GPOS-00036<GroupDescription></GroupDescription>UBTU-18-010426The Ubuntu operating system must map the authenticated identity to the user or group account for PKI-based authentication.<VulnDiscussion>Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109959V-100855CCI-000187Install libpam-pkcs11 package on the system. + +Set use_mappers=pwent in /etc/pam_pkcs11/pam_pkcs11.conf + +If the system is missing an "/etc/pam_pkcs11/" directory and an "/etc/pam_pkcs11/pam_pkcs11.conf", find an example to copy into place and modify accordingly at "/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz".Verify the Ubuntu operating system has the "libpam-pkcs11" package installed, by running the following command: + + # dpkg -l | grep libpam-pkcs11 + +If "libpam-pkcs11" is not installed, this is a finding. + +Check if use_mappers is set to pwent in /etc/pam_pkcs11/pam_pkcs11.conf file + # grep use_mappers /etc/pam_pkcs11/pam_pkcs11.conf + use_mappers = pwent + +If "use_mappers" is not found, or is not set to "pwent", this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>UBTU-18-010427The Ubuntu operating system must implement smart card logins for multifactor authentication for access to accounts.<VulnDiscussion>Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. + +Multifactor authentication requires using two or more factors to achieve authentication. + +Factors include: +1) something a user knows (e.g., password/PIN); +2) something a user has (e.g., cryptographic identification device, token); and +3) something a user is (e.g., biometric). + +A privileged account is defined as an information system account with authorizations of a privileged user. + +Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). + +The DOD CAC with DOD-approved PKI is an example of multifactor authentication. + +Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100857SV-109961CCI-000765CCI-000766CCI-000767CCI-000768CCI-001954Configure the Ubuntu operating system to use multifactor authentication for local access to accounts. + +Add or update the following line in "/etc/pam.d/common-auth", placing it above any lines containing "pam_unix.so": + +auth [success=2 default=ignore] pam_pkcs11.soVerify the Ubuntu operating system uses multifactor authentication for local access to accounts. + +Check that the "pam_pkcs11.so" option is configured in the "/etc/pam.d/common-auth" file with the following command: + +# grep pam_pkcs11.so /etc/pam.d/common-auth +auth [success=2 default=ignore] pam_pkcs11.so + +If "pam_pkcs11.so" is not set in "/etc/pam.d/common-auth", this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>UBTU-18-010431The Ubuntu operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.<VulnDiscussion>Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. + +Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card. + +A privileged account is defined as an information system account with authorizations of a privileged user. + +Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). + +Requires further clarification from NIST.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100859SV-109963CCI-001948Configure the Ubuntu operating system to implement multifactor authentication by installing the required packages. + +Install the "libpam-pkcs11" package on the system with the following command: + +# sudo apt install libpam-pkcs11Verify the Ubuntu operating system has the packages required for multifactor authentication installed. + +Check for the presence of the packages required to support multifactor authentication with the following commands: + +# dpkg -l | grep libpam-pkcs11 + +ii libpam-pkcs11 0.6.8-4 amd64 Fully featured PAM module for using PKCS#11 smart cards + +If the "libpam-pkcs11" package is not installed, this is a finding.SRG-OS-000376-GPOS-00161<GroupDescription></GroupDescription>UBTU-18-010432The Ubuntu operating system must accept Personal Identity Verification (PIV) credentials.<VulnDiscussion>The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. + +DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100861SV-109965CCI-001953Configure the Ubuntu operating system to accept Personal Identity Verification (PIV) credentials. + +Install the "opensc-pkcs11" package using the following command: + +# sudo apt-get install opensc-pkcs11Verify the Ubuntu operating system accepts Personal Identity Verification (PIV) credentials. + +Check that the "opensc-pcks11" package is installed on the system with the following command: + +# dpkg -l | grep opensc-pkcs11 + +ii opensc-pkcs11:amd64 0.15.0-1Ubuntu1 amd64 Smart card utilities with support for PKCS#15 compatible cards + +If the "opensc-pcks11" package is not installed, this is a finding.SRG-OS-000377-GPOS-00162<GroupDescription></GroupDescription>UBTU-18-010434The Ubuntu operating system must implement certificate status checking for multifactor authentication.<VulnDiscussion>The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. + +DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109967V-100863CCI-001954Configure the Ubuntu operating system to certificate status checking for multifactor authentication. + +Modify all of the cert_policy lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include ocsp_on.Verify the Ubuntu operating system implements certificate status checking for multifactor authentication. + +Check that certificate status checking for multifactor authentication is implemented with the following command: + +# sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ocsp_on + +cert_policy = ca,signature,ocsp_on; + +If "cert_policy" is not set to "ocsp_on", or the line is commented out, this is a finding.SRG-OS-000403-GPOS-00182<GroupDescription></GroupDescription>UBTU-18-010436The Ubuntu operating system must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.<VulnDiscussion>Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DoD-approved CA, trust of this CA has not been established. + +The DoD will only accept PKI-certificates obtained from a DoD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100865SV-109969CCI-002470Add at least one DOD certificate authority to the '/usr/local/share/ca-certificates' directory, then run the 'update-ca-certificates' command.Verify the directory containing the root certificates for the Ubuntu operating system only contains certificate files for DoD PKI-established certificate authorities by iterating over all files in the '/etc/ssl/certs' directory and checking if, at least one, has the subject matching "DOD ROOT CA". + +If none is found, this is a finding.SRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>UBTU-18-010437Pam_Apparmor must be configured to allow system administrators to pass information to any other Ubuntu operating system administrator or user, change security attributes, and to confine all non-privileged users from executing functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.<VulnDiscussion>When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124, SRG-OS-000324-GPOS-0012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100867SV-109971CCI-002165CCI-002235Configure the Ubuntu operating system to allow system administrators to pass information to any other Ubuntu operating system administrator or user. + +Install "Pam_Apparmor" (if it is not installed) with the following command: + +# sudo apt-get install libpam-apparmor + +Enable/Activate "Apparmor" (if it is not already active) with the following command: + +# sudo systemctl enable apparmor.service + +Start "Apparmor" with the following command: + +# sudo systemctl start apparmor.service + +Note: Pam_Apparmor must have properly configured profiles. All configurations will be based on the actual system setup and organization. See the "Pam_Apparmor" documentation for more information on configuring profiles.Verify that the Ubuntu operating system is configured to allow system administrators to pass information to any other Ubuntu operating system administrator or user. + +Check that "Pam_Apparmor" is installed on the system with the following command: + +# dpkg -l | grep -i apparmor + +ii libpam-apparmor 2.10.95-0Ubuntu2.6 + +If the "Pam_Apparmor" package is not installed, this is a finding. + +Check that the "AppArmor" daemon is running with the following command: + +# systemctl status apparmor.service | grep -i active + +If something other than "Active: active" is returned, this is a finding. + +Note: Pam_Apparmor must have properly configured profiles. All configurations will be based on the actual system setup and organization. See the "Pam_Apparmor" documentation for more information on configuring profiles.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>UBTU-18-010441The Ubuntu operating system must be configured to use AppArmor.<VulnDiscussion>Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level. + +Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. + +Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109973V-100869CCI-001764Install "Apparmor" (if it is not installed) with the following command: + +# sudo apt-get install apparmor + +# sudo systemctl enable apparmor.service + +Start "Apparmor" with the following command: + +# sudo systemctl start apparmor.service + +Note: Apparmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. See the "Apparmor" documentation for more information on configuring profiles.Verify the operating system prevents program execution in accordance with local policies. + +Check that apparmor is installed and active by running the following command: + +# dpkg -l | grep apparmor + +If the "apparmor" package is not installed, this is a finding. + +#systemctl is-active apparmor.service + +active + +If "active" is not returned, this is a finding. + +#systemctl is-enabled apparmor.service + +enabled + +If "enabled" is not returned, then this is a finding.SRG-OS-000370-GPOS-00155<GroupDescription></GroupDescription>UBTU-18-010442The Apparmor module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders.<VulnDiscussion>Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level. + +Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. + +Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100871SV-109975CCI-001774Configure the Ubuntu operating system to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + +Install "Apparmor" (if it is not installed) with the following command: + +# sudo apt-get install apparmor + +Enable "Apparmor" (if it is not already active) with the following command: + +# sudo systemctl enable apparmor.service + +Start "Apparmor" with the following command: + +# sudo systemctl start apparmor.service + +Note: Apparmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. See the "Apparmor" documentation for more information on configuring profiles.Verify that the Ubuntu operating system is configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and access to user home directories. + +Check that "Apparmor" is configured to employ application whitelisting and home directory access control with the following command: + +# sudo apparmor_status + +apparmor module is loaded. +17 profiles are loaded. +17 profiles are in enforce mode. + /sbin/dhclient + /usr/bin/lxc-start + ... +0 processes are in complain mode. +0 processes are unconfined but have a profile defined. + +If the defined profiles do not match the organization's list of authorized software, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>UBTU-18-010444The Ubuntu operating system must uniquely identify interactive users.<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. + +Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: + +1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and + +2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. + +Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109977V-100873CCI-000764CCI-000804Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate User ID (UID) with a unique UID.Verify that the Ubuntu operating system contains no duplicate User IDs (UIDs) for interactive users. + +Check that the Ubuntu operating system contains no duplicate UIDs for interactive users with the following command: + +# awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd + +If output is produced, and the accounts listed are interactive user accounts, this is a finding.SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>UBTU-18-010445The Ubuntu operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.<VulnDiscussion>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. + +Ubuntu operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109979V-100875CCI-000795Configure the Ubuntu operating system to disable account identifiers after 35 days of inactivity since the password expiration. + +Run the following command to change the configuration for adduser: + +# sudo useradd -D -f 35 + +Note: DoD recommendation is 35 days, but a lower value is acceptable. The value "0" will disable the account immediately after the password expires.Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity with the following command: + +Check the account inactivity value by performing the following command: + +# sudo grep INACTIVE /etc/default/useradd + +INACTIVE=35 + +If "INACTIVE" is not set to a value 0<[VALUE]<=35, or is commented out, this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>UBTU-18-010447The Ubuntu operating system must automatically expire temporary accounts within 72 hours.<VulnDiscussion>Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors. + +Temporary accounts are different from emergency accounts. Emergency accounts, also known as "last resort" or "break glass" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements. + +The automatic expiration of temporary accounts may be extended as needed by the circumstances but it must not be extended indefinitely. A documented permanent account should be established for privileged users who need long-term maintenance accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109981V-100877CCI-001682Configure the operating system to expire temporary accounts after 72 hours with the following command: + + $ sudo chage -E $(date -d +3days +%Y-%m-%d) <temporary_account_name>Verify temporary accounts have been provisioned with an expiration date of 72 hours. + +For every existing temporary account, run the following command to obtain its account expiration information: + + $ sudo chage -l <temporary_account_name> | grep -i "account expires" + +Verify each of these accounts has an expiration date set within 72 hours. +If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>UBTU-18-010448The Ubuntu operating system default filesystem permissions must be defined in such a way that all authenticated users can only read and modify their own files.<VulnDiscussion>Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109983V-100879CCI-000366Configure the system to define the default permissions for all authenticated users in such a way that the user can only read and modify their own files. + +Edit the "UMASK" parameter in the "/etc/login.defs" file to match the example below: + +UMASK 077Verify the Ubuntu operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. + +Check that the Ubuntu operating system defines default permissions for all authenticated users with the following command: + +# grep -i "umask" /etc/login.defs + +UMASK 077 + +If the "UMASK" variable is set to "000", this is a finding with the severity raised to a CAT I. + +If the value of "UMASK" is not set to "077", "UMASK" is commented out or "UMASK" is missing completely, this is a finding.SRG-OS-000002-GPOS-00002<GroupDescription></GroupDescription>UBTU-18-010449The Ubuntu operating system must provision temporary user accounts with an expiration time of 72 hours or less.<VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. + +Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. + +If temporary accounts are used, the Ubuntu operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. + +To address access requirements, the Ubuntu operating system may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109985V-100881CCI-000016If a temporary account must be created configure the system to terminate the account after a 72 hour time period with the following command to set an expiration date on it. Substitute "system_account_name" with the account to be created. + +# sudo chage -E $(date -d "+3 days" +%F) system_account_nameVerify the Ubuntu operating system expires temporary user accounts within 72 hours or less. + +For every existing temporary account, run the following command to obtain its account expiration information. + +# sudo chage -l system_account_name | grep expires + +Password expires : Aug 07, 2019 +Account expires : Aug 07, 2019 + +Verify each of these accounts has an expiration date set within 72 hours of accounts' creation. +If any temporary account does not expire within 72 hours of that account's creation, this is a finding.SRG-OS-000142-GPOS-00071<GroupDescription></GroupDescription>UBTU-18-010500The Ubuntu operating system must be configured to use TCP syncookies.<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. + +Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109987V-100883CCI-001095Configure the Ubuntu operating system to use TCP syncookies, by running the following command: + +# sudo sysctl -w net.ipv4.tcp_syncookies=1 + +If "1" is not the system's default value then add or update the following line in "/etc/sysctl.conf": + +net.ipv4.tcp_syncookies = 1Verify the Ubuntu operating system is configured to use TCP syncookies. + +Check the value of TCP syncookies with the following command: + +# sysctl net.ipv4.tcp_syncookies +net.ipv4.tcp_syncookies = 1 + +If the value is not "1", this is a finding. + +Check the saved value of TCP syncookies with the following command: + +# sudo grep -i net.ipv4.tcp_syncookies /etc/sysctl.conf /etc/sysctl.d/* | grep -v '#' + +If no output is returned, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>UBTU-18-010501The Ubuntu operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).<VulnDiscussion>Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. + +Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. + +Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100885SV-109989CCI-001891If the system is not networked this requirement is Not Applicable. + +To configure the system clock to compare the system clock at least every 24 hours to the authoritative time source, edit the "/etc/chrony/chrony.conf" file. Add or correct the following lines, by replacing "[source]" in the following line with an authoritative DoD time source. + +server [source] iburst maxpoll = 16 + +If the "chrony" service was running and the value of "maxpoll" or "server" was updated then the service must be restarted using the following command: + +# sudo systemctl restart chrony.serviceIf the system is not networked this requirement is Not Applicable. + +The system clock must be configured to compare the system clock at least every 24 hours to the authoritative time source. + +Check the value of "maxpoll" in the "/etc/chrony/chrony.conf" file with the following command: + +# sudo grep maxpoll /etc/chrony/chrony.conf +server tick.usno.navy.mil iburst maxpoll 16 + +If the "maxpoll" option is set to a number greater than 16 or the line is commented out, this is a finding. + +Verify that the "chrony.conf" file is configured to an authoritative DoD time source by running the following command: + +# grep -i server /etc/chrony/chrony.conf +server tick.usno.navy.mil iburst maxpoll 16 +server tock.usno.navy.mil iburst maxpoll 16 +server ntp2.usno.navy.mil iburst maxpoll 16 + +If the parameter "server" is not set, is not set to an authoritative DoD time source, or is commented out, this is a finding.SRG-OS-000356-GPOS-00144<GroupDescription></GroupDescription>UBTU-18-010502The Ubuntu operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.<VulnDiscussion>Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. + +Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems). + +Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done in order to determine the time difference.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100887SV-109991CCI-002046Configure chrony to synchronize the internal system clocks to the authoritative source when the time difference is greater than one second by doing the following, + +Edit the /etc/chrony/chrony.conf file and add: + +makestep 1 -1 + +Restart the chrony service, + +# sudo systemctl restart chrony.serviceVerify the operating system synchronizes internal system clocks to the authoritative time source when the time difference is greater than one second. + +Check the value of "makestep" by running the following command: + +# sudo grep makestep /etc/chrony/chrony.conf + +makestep 1 -1 + +If the makestep option is commented out or is not set to "1 -1", this is a finding.SRG-OS-000359-GPOS-00146<GroupDescription></GroupDescription>UBTU-18-010503The Ubuntu operating system must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).<VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. + +Time stamps generated by the operating system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109993V-100889CCI-001890To configure the system time zone to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT), run the following command replacing [ZONE] with UTC or GMT. + +# sudo timedatectl set-timezone [ZONE]The time zone must be configured to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). To verify run the following command. + +# sudo timedatectl status | grep -i "time zone" +Timezone: UTC (UTC, +0000) + +If "Timezone" is not set to UTC or GMT, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>UBTU-18-010504The Ubuntu operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. + +The Ubuntu operating system is capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. + +To support the requirements and principles of least functionality, the Ubuntu operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100891SV-109995CCI-000382Add all ports, protocols, or services allowed by the PPSM CLSA by using the following command: +$ ufw allow <direction> <port/protocol/service> + +where the direction is 'in' or 'out' and the port is the one corresponding to the protocol or service allowed. + +To deny access to port, protocols or services, use: +$ ufw deny <direction> <port/protocol/service>Verify the Ubuntu operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments. + +Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services by running the following commands: +$ sudo ufw show before-rules +$ sudo ufw show user-rules +$ sudo ufw show after-rules + +Ask the system administrator for the site or program PPSM Component Local Services Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. + +If there are any additional ports, protocols, or services that are not included in the PPSM CLSA, this is a finding. + +If there are any ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding.SRG-OS-000184-GPOS-00078<GroupDescription></GroupDescription>UBTU-18-010505Kernel core dumps must be disabled unless needed.<VulnDiscussion>Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-109997V-100893CCI-001190If kernel core dumps are not required, disable the "kdump" service with the following command: + +# systemctl disable kdump.service + +If kernel core dumps are required, document the need with the Information System Security Officer (ISSO).Verify that kernel core dumps are disabled unless needed. + +Check if "kdump" service is active with the following command: + +# systemctl is-active kdump.service +inactive + +If the "kdump" service is active, ask the System Administrator if the use of the service is required and documented with the Information System Security Officer (ISSO). + +If the service is active and is not documented, this is a finding.SRG-OS-000278-GPOS-00108<GroupDescription></GroupDescription>UBTU-18-010506The Ubuntu operating system must use cryptographic mechanisms to protect the integrity of audit tools.<VulnDiscussion>Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. + +Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. + +It is not uncommon for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs. + +To address this risk, audit tools must be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100895SV-109999CCI-001496Add or update the following selection lines to "/etc/aide/aide.conf", in order to protect the integrity of the audit tools. + +# Audit Tools +/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/audispd p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured to use cryptographic mechanisms to protect the integrity of audit tools. + +Check the selection lines that aide is configured to add/check with the following command: + +# egrep '(\/sbin\/(audit|au))' /etc/aide/aide.conf + +/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/audispd p+i+n+u+g+s+b+acl+xattrs+sha512 +/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 + +If any of the seven audit tools does not have an appropriate selection line, this is a finding.SRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>UBTU-18-010507The Ubuntu operating system must enable and run the uncomplicated firewall(ufw).<VulnDiscussion>Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best. + +Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Ubuntu operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets). + +Satisfies: SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110001V-100897CCI-000366CCI-002314Enable the Uncomplicated Firewall by using the following command: + +# sudo systemctl enable ufw.service + +If the Uncomplicated Firewall is not currently running on the system, start it with the following command: + +# sudo systemctl start ufw.serviceVerify the Uncomplicated Firewall is enabled on the system by running the following command: + +# systemctl is-enabled ufw + +If the above command returns the status as "disabled", this is a finding. + +Verify the Uncomplicated Firewall is active on the system by running the following command: + +# sudo systemctl is-active ufw + +If the above command returns 'inactive' or any kind of error, this is a finding. + +If the Uncomplicated Firewall is not installed ask the System Administrator if another application firewall is installed. + +If no application firewall is installed this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>UBTU-18-010508The Ubuntu operating system must notify designated personnel if baseline configurations are changed in an unauthorized manner. The file integrity tool must notify the system administrator when changes to the baseline configuration or anomalies in the operation of any security functions are discovered.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the Ubuntu operating system. Changes to Ubuntu operating system configurations can have unintended side effects, some of which may be relevant to security. + +Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the Ubuntu operating system. The Ubuntu operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. + +Satisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000447-GPOS-00201</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110003V-100899CCI-001744CCI-002702Configure the Ubuntu operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. + +Modify the "SILENTREPORTS" parameter in the "/etc/default/aide" file with a value of "no" if it does not already exist.Verify that Advanced Intrusion Detection Environment (AIDE) notifies the system administrator when anomalies in the operation of any security functions are discovered. + +Check that AIDE notifies the system administrator when anomalies in the operation of any security functions are discovered with the following command: + +#sudo grep SILENTREPORTS /etc/default/aide + +SILENTREPORTS=no + +If SILENTREPORTS is uncommented and set to yes, this is a finding.SRG-OS-000378-GPOS-00163<GroupDescription></GroupDescription>UBTU-18-010509The Ubuntu operating system must disable automatic mounting of Universal Serial Bus (USB) mass storage driver.<VulnDiscussion>Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. + +Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110023V-100919CCI-001958Configure the Ubuntu operating system to disable using the USB storage kernel module. + +Create a file under "/etc/modprobe.d" to contain the following: +$ sudo su -c "echo install usb-storage /bin/false >> /etc/modprobe.d/DISASTIG.conf" + +Configure the operating system to disable the ability to use USB mass storage devices: +$ sudo su -c "echo blacklist usb-storage >> /etc/modprobe.d/DISASTIG.conf"Note: The "install" and "blacklist" methods are utilized together to fully disable automatic mounting of the USB mass storage driver. + +Verify the Ubuntu operating system disables the ability to load the USB storage kernel module: +$ grep usb-storage /etc/modprobe.d/* | grep "/bin/false" + +install usb-storage /bin/false + +If the command does not return any output, or the line is commented out, this is a finding. + +Verify the operating system disables the ability to use USB mass storage device: +$ grep usb-storage /etc/modprobe.d/* | grep -i "blacklist" + +blacklist usb-storage + +If the command does not return any output, or the line is commented out, this is a finding.SRG-OS-000420-GPOS-00186<GroupDescription></GroupDescription>UBTU-18-010512The Ubuntu operating system must configure the uncomplicated firewall to rate-limit impacted network interfaces.<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. + +This requirement addresses the configuration of the Ubuntu operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110005V-100901CCI-002385Configure the application firewall to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the Ubuntu operating system is implementing rate-limiting measures on impacted network interfaces. + +Run the following command replacing "[service]" with the service that needs to be rate limited. + +$ sudo ufw limit [service] + +Or rate-limiting can be done on an interface. An example of adding a rate-limit on the eth0 interface: + +$ sudo ufw limit in on eth0Verify an application firewall is configured to rate limit any connection to the system. + +Check that the Uncomplicated Firewall is configured to rate limit any connection to the system with the following command: + +$ sudo ufw show user-rules + +IPV4 (user): + +Chain ufw-user-input (1 references) + + pkts bytes target prot opt in out source destination + + 1 52 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 /* 'dapp_OpenSSH' */ + + 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 + + + +Chain ufw-user-forward (1 references) + + pkts bytes target prot opt in out source destination + + + +Chain ufw-user-output (1 references) + + pkts bytes target prot opt in out source destination + + + +Chain ufw-user-limit-accept (0 references) + + pkts bytes target prot opt in out source destination + + 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 + + + +Chain ufw-user-limit (0 references) + + pkts bytes target prot opt in out source destination + + 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 0 level 4 prefix "[UFW LIMIT BLOCK] " + + 0 0 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable + +If any service is not rate limited by the Uncomplicated Firewall, this is a finding.SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>UBTU-18-010513The Ubuntu operating system must implement non-executable data to protect its memory from unauthorized code execution.<VulnDiscussion>Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. + +Examples of attacks are buffer overflow attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110007V-100903CCI-002824Configure the Ubuntu operating system to enable NX. + +If "nx" is not showing up in /proc/cpuinfo and the system's BIOS setup configuration permits toggling the No Execution bit, then set it to "enable".Verify the NX (no-execution) bit flag is set on the system. + +Check that the no-execution bit flag is set with the following commands: + +# dmesg | grep -i "execute disable" +[ 0.000000] NX (Execute Disable) protection: active + +If "dmesg" does not show "NX (Execute Disable) protection: active", check the cpuinfo settings with the following command: + +# grep flags /proc/cpuinfo | grep -w nx | sort -u +flags : fpu vme de pse tsc ms nx rdtscp lm constant_tsc + +If "flags" does not contain the "nx" flag, this is a finding.SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>UBTU-18-010514The Ubuntu operating system must implement address space layout randomization to protect its memory from unauthorized code execution.<VulnDiscussion>Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. + +Examples of attacks are buffer overflow attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110009V-100905CCI-002824Set the "kernel.randomize_va_space" entry found in the "/etc/sysctl.conf" file to a value of "2". + +After the line has been modified the kernel settings from all system configuration files must be reloaded; before any of the changes will take effect. + +Run the following command to reload all of the kernel system configuration files: + +# sudo sysctl --system +Verify the Ubuntu operating system implements address space layout randomization (ASLR). + +Check that ASLR is configured on the system with the following command: + +# sudo sysctl kernel.randomize_va_space + +kernel.randomize_va_space = 2 + +Verify the kernel parameter "randomize_va_space" is set to 2 with the following command: + +# cat /proc/sys/kernel/randomize_va_space + +2 + +If "kernel.randomize_va_space" is not set to 2, this is a finding. + +Check the saved value of the kernel.randomize_va_space variable is not different from 2. + +# sudo egrep -R "^kernel.randomize_va_space=[^2]" /etc/sysctl.conf /etc/sysctl.d + +If this returns a result, this is a finding.SRG-OS-000445-GPOS-00199<GroupDescription></GroupDescription>UBTU-18-010515The Ubuntu operating system must use a file integrity tool to verify correct operation of all security functions.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. + +This requirement applies to the Ubuntu operating system performing security function verification/testing and/or systems and environments that require this functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100907SV-110011CCI-002696Install AIDE, initialize it, and perform a manual check. + +Install AIDE: + $ sudo apt install aide + +Initialize it (this may take a few minutes): + $ sudo aideinit + Running aide --init... + +Example output: + + Start timestamp: 2022-11-20 11:53:17 -0700 (AIDE 0.16) + AIDE initialized database at /var/lib/aide/aide.db.new + Verbose level: 6 + + Number of entries: 119543 + + --------------------------------------------------- + The attributes of the (uncompressed) database(s): + --------------------------------------------------- + + /var/lib/aide/aide.db.new + RMD160 : PiEP1DX91JMcHnRSPnpFqNfIFr4= + TIGER : /zM5yQBnOIoEH0jplJE5v6S0rUErbTXL + SHA256 : BE2iHtBN9lEX53l4R/p7t1al0dIlsgPc + Lg4YI08+/Jk= + SHA512 : JIdGeNVRgtBPPSwun9St+9cwUrgIIKUW + KVTksZXJ29Tt+luC/XNDcjIub7fbPVw/ + EcTDsvYtt9MBmBxw1wCYng== + CRC32 : jB2FVw== + HAVAL : Jhe+fqaDpkswpWSnOTN28TO05QFHsjdq + RcFZwCVUGTQ= + GOST : WFrarVyxpXbKdW9SAaOy1Te8rSodV3/q + nLsXuP7YujA= + + +End timestamp: 2022-11-20 11:58:19 -0700 (run time: 5m 2s) + +The new database will need to be renamed to be read by AIDE: + $ sudo cp -p /var/lib/aide/aide.db.new /var/lib/aide/aide.db + +Perform a manual check: + $ sudo aide.wrapper --check + +Example output: + Start timestamp: 2022-11-20 11:59:16 -0700 (AIDE 0.16) + AIDE found differences between database and filesystem!! + ... + +Done.Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions. + +Check that the AIDE package is installed with the following command: + $ sudo dpkg -l | grep aide + ii aide 0.16-3ubuntu0.1 amd64 Advanced Intrusion Detection Environment - static binary + +If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. + +If there is no application installed to perform integrity checks, this is a finding. + +If AIDE is installed, check if it has been initialized with the following command: + $ sudo aide.wrapper --check + +If the output is "Couldn't open file /var/lib/aide/aide.db for reading", this is a finding.SRG-OS-000446-GPOS-00200<GroupDescription></GroupDescription>UBTU-18-010516The Ubuntu operating system must be configured so that a file integrity tool verifies the correct operation of security functions every 30 days.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. + +Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights. + +This requirement applies to the Ubuntu operating system performing security function verification/testing and/or systems and environments that require this functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055SV-110013V-100909CCI-002699The cron file for AIDE is fairly complex as it creates the report. This file is installed with the aide-common package and the default can be restored by copying it from another location: + +# sudo cp /usr/share/aide/config/cron.daily/aide /etc/cron.daily/aideVerify that Advanced Intrusion Detection Environment (AIDE) performs a verification of the operation of security functions every 30 days. + +Note: A file integrity tool other than AIDE may be used, but the tool must be executed at least once per week. + +Check that AIDE is being executed every 30 days or less with the following command: + +# ls -al /etc/cron.daily/aide + +-rwxr-xr-x 1 root root 26049 Oct 24 2014 /etc/cron.daily/aide + +If the "/etc/cron.daily/aide" file does not exist or a cron job is not configured to run at least every 30 days, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010418The Ubuntu operating system must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements.<VulnDiscussion>The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator may have a stance in which they want to protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding, which can warrant a ''no'' setting. +X11 forwarding should be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker may then be able to perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled. +If X11 services are not required for the system's intended function, they should be disabled or restricted as appropriate to the system’s needs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): + +X11Forwarding no + +The SSH service must be restarted for changes to take effect: + +$ sudo systemctl restart sshdVerify that X11Forwarding is disabled with the following command: + +# grep -i x11forwarding /etc/ssh/sshd_config | grep -v "^#" + +X11Forwarding no + +If the "X11Forwarding" keyword is set to "yes" and is not documented with the Information System Security Officer (ISSO) as an operational requirement or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010419The Ubuntu operating system SSH daemon must prevent remote hosts from connecting to the proxy display.<VulnDiscussion>When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the SSHD proxy display is configured to listen on the wildcard address. By default, SSHD binds the forwarding server to the loopback address and sets the hostname part of the DIPSLAY environment variable to localhost. This prevents remote hosts from connecting to the proxy display.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Configure the SSH daemon to prevent remote hosts from connecting to the proxy display. + +Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11UseLocalhost" keyword and set its value to "yes" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): + +X11UseLocalhost yesVerify the SSH daemon prevents remote hosts from connecting to the proxy display. + +Check the SSH X11UseLocalhost setting with the following command: + +# sudo grep -i x11uselocalhost /etc/ssh/sshd_config +X11UseLocalhost yes + +If the "X11UseLocalhost" keyword is set to "no", is missing, or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010450All local interactive user home directories defined in the /etc/passwd file must exist.<VulnDiscussion>If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service (DoS) because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Create home directories to all local interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in "/etc/ passwd": + +Note: The example will be for the user smithj, who has a home directory of "/home/smithj", a User ID (UID) of "smithj", and a Group Identifier (GID) of "users assigned" in "/etc/passwd". + +$ sudo mkdir /home/smithj +$ sudo chown smithj /home/smithj +$ sudo chgrp users /home/smithj +$ sudo chmod 0750 /home/smithjVerify the assigned home directory of all local interactive users on the Ubuntu operating system exists. + +Check the home directory assignment for all local interactive non-privileged users with the following command: + +$ sudo awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6}' /etc/passwd + +smithj 1001 /home/smithj + +Note: This may miss interactive users that have been assigned a privileged User ID (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. + +Check that all referenced home directories exist with the following command: + +$ sudo pwck -r + +user 'smithj': directory '/home/smithj' does not exist + +If any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010451All local interactive user home directories must have mode 0750 or less permissive.<VulnDiscussion>Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Change the mode of interactive user’s home directories to "0750". To change the mode of a local interactive user’s home directory, use the following command: + +Note: The example will be for the user "smithj". + +$ sudo chmod 0750 /home/smithjVerify the assigned home directory of all local interactive users has a mode of "0750" or less permissive with the following command: + +Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. + +$ sudo ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) + +drwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj + +If home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010452All local interactive user home directories must be group-owned by the home directory owners primary group.<VulnDiscussion>If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Change the group owner of a local interactive user’s home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user’s home directory, use the following command: + +Note: The example will be for the user "smithj", who has a home directory of "/home/smithj", and has a primary group of users. + +$ sudo chgrp users /home/smithj +Verify the assigned home directory of all local interactive users is group-owned by that user’s primary Group Identifier (GID). + +Check the home directory assignment for all non-privileged users on the system with the following command: + +Note: This may miss local interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information. The returned directory "/home/smithj" is used as an example. + +$ sudo ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) + +drwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj + +Check the user's primary group with the following command: + +$ sudo grep admin /etc/group +admin:x:250:smithj,jonesj,jacksons + +If the user home directory referenced in "/etc/passwd" is not group-owned by that user’s primary GID, this is a finding. +SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010522The Ubuntu operating system must not have accounts configured with blank or null passwords.<VulnDiscussion>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Configure all accounts on the system to have a password or lock the account with the following commands: + +Perform a password reset: + +$ sudo passwd [username] + +Lock an account: + +$ sudo passwd -l [username]Check the "/etc/shadow" file for blank passwords with the following command: + +$ sudo awk -F: '!$2 {print $1}' /etc/shadow + +If the command returns any results, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-010523The Ubuntu operating system must not allow accounts configured with blank or null passwords.<VulnDiscussion>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating. + +Remove any instances of the "nullok" option in "/etc/pam.d/common-password" to prevent logons with empty passwords.To verify that null passwords cannot be used, run the following command: + +$ grep nullok /etc/pam.d/common-password + +If this produces any output, it may be possible to log on with accounts with empty passwords. + +If null passwords can be used, this is a finding.SRG-OS-000481-GPOS-00481<GroupDescription></GroupDescription>UBTU-18-010521The Ubuntu operating system must disable all wireless network adapters.<VulnDiscussion>Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the operating system. + +This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an operating system. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the AO. Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the operating system. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. + +Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055V-100913SV-110017CCI-002418Configure the system to disable all wireless network interfaces with the following command: + +# sudo ifdown [ADAPTER_NAME]Verify that there are no wireless interfaces configured on the system. + +Check that the system does not have active wireless interfaces with the following command: + +Note: This requirement is Not Applicable for systems that do not have physical wireless network radios. + +# ifconfig -a | more + +eth0 Link encap:Ethernet HWaddr ff:ff:ff:ff:ff:ff + inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 + ... + +eth1 IEEE 802.11b ESSID:"tacnet" + Mode:Managed Frequency:2.412 GHz Access Point: 00:40:E7:22:45:CD + ... + +lo Link encap:Local Loopback + inet addr:127.0.0.1 Mask:255.0.0.0 + inet6 addr: ::1/128 Scope:Host + ... + +If a wireless interface is configured and has not been documented and approved by the Information System Security Officer (ISSO), this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>UBTU-18-010421The Ubuntu operating system SSH server must be configured to use only FIPS-validated key exchange algorithms.<VulnDiscussion>Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection. + +The system will attempt to use the first algorithm presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest algorithm available to secure the SSH connection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000068Configure the SSH server to use only FIPS-validated key exchange algorithms by adding or modifying the following line in "/etc/ssh/sshd_config": + + KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 + +Restart the "sshd" service for changes to take effect: + + $ sudo systemctl restart sshdVerify that the SSH server is configured to use only FIPS-validated key exchange algorithms: + + $ sudo grep -i kexalgorithms /etc/ssh/sshd_config + KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 + +If "KexAlgorithms" is not configured, is commented out, or does not contain only the algorithms "ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256" in exact order, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>UBTU-18-010510The Ubuntu operating system must restrict access to the kernel message buffer.<VulnDiscussion>Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a nonprivileged user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-001090Configure the operating system to restrict access to the kernel message buffer. + +Set the system to the required kernel parameter by adding or modifying the following line in /etc/sysctl.conf or a config file in the /etc/sysctl.d/ directory: + + kernel.dmesg_restrict = 1 + +Remove any configurations that conflict with the above from the following locations: + /run/sysctl.d/ + /etc/sysctl.d/ + /usr/local/lib/sysctl.d/ + /usr/lib/sysctl.d/ + /lib/sysctl.d/ + /etc/sysctl.conf + +Reload settings from all system configuration files with the following command: + + $ sudo sysctl --systemVerify the operating system is configured to restrict access to the kernel message buffer with the following commands: + + $ sudo sysctl kernel.dmesg_restrict + kernel.dmesg_restrict = 1 + +If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding. + +Check that the configuration files are present to enable this kernel parameter: + + $ sudo grep -r kernel.dmesg_restrict /run/sysctl.d/* /etc/sysctl.d/* /usr/local/lib/sysctl.d/* /usr/lib/sysctl.d/* /lib/sysctl.d/* /etc/sysctl.conf 2> /dev/null + /etc/sysctl.conf:kernel.dmesg_restrict = 1 + /etc/sysctl.d/99-sysctl.conf:kernel.dmesg_restrict = 1 + +If "kernel.dmesg_restrict" is not set to "1", is missing or commented out, this is a finding. + +If conflicting results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>UBTU-18-999999The Ubuntu operating system must be a vendor supported release.<VulnDiscussion>An Ubuntu operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Canonical Ubuntu 18.04 LTSDISADPMS TargetCanonical Ubuntu 18.04 LTS4055CCI-000366Upgrade to a supported version of the Ubuntu operating system.Verify the version of the Ubuntu operating system is vendor supported. + +Check the version of the Ubuntu operating system with the following command: + +# cat /etc/lsb-release + +DISTRIB_RELEASE=18.04 +DISTRIB_CODENAME=bionic +DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" + +Validate that "Extended Security Maintenance" support has been purchased from the vendor. +If the operating system does not have a documented "Extended Security Maintenance" agreement in place, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_ForeScout_CounterACT_NDM_STIG_V1R2_Manual-xccdf.xml b/benchmarks/DISA/U_ForeScout_CounterACT_NDM_STIG_V1R2_Manual-xccdf.xml new file mode 100644 index 000000000..c94c1cbe8 --- /dev/null +++ b/benchmarks/DISA/U_ForeScout_CounterACT_NDM_STIG_V1R2_Manual-xccdf.xml @@ -0,0 +1,540 @@ +acceptedForeScout CounterACT NDM Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 2 Benchmark Date: 24 Jul 20243.51.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000033<GroupDescription></GroupDescription>DTOO208Office client polling of SharePoint servers published links must be disabled.<VulnDiscussion>Users of Office applications can see and use links to Microsoft Office SharePoint Server sites from those applications. Administrators configure published links to Office applications during initial deployment, and can add or change links as part of regular operations. These links appear on the My SharePoint Sites tab of the Open, Save, and Save As dialog boxes when opening and saving documents from these applications. Links can be targeted so that they only appear to users who are members of particular audiences. +If a malicious person gains access to the list of published links, they could modify the links to point to unapproved sites, which could make sensitive data vulnerable to exposure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52755V-17670CCI-000213Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Server Settings "Disable the Office client from polling the SharePoint Server for published links" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Server Settings "Disable the Office client from polling the SharePoint Server for published links" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\portal + +If the value 'LinkPublishingDisabled' is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO182The Help Improve Proofing Tools feature for Office must be configured.<VulnDiscussion>The "Help Improve Proofing Tools" feature collects data about use of the Proofing Tools, such as additions to the custom dictionary, and sends it to Microsoft. After about six months, the feature stops sending data to Microsoft and deletes the data collection file from the user's computer. Although this feature does not intentionally collect personal information, some of the content sent could include items that were marked as spelling or grammar errors, such as proper names and account numbers. However, any numbers such as account numbers, street addresses, and phone numbers are converted to zeroes when the data is collected. Microsoft uses this information solely to improve the effectiveness of the Office Proofing Tools, not to identify users. +By default, this feature is enabled, if users choose to participate in the Customer Experience Improvement Program (CEIP). If an organization has policies that govern the use of external resources such as the CEIP, allowing the use of the "Help Improve Proofing Tools" feature might cause them to violate these policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52719V-17627CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Tools \ Options \ Spelling -> Proofing Data Collection "Improve Proofing Tools" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools >> Options >> Spelling >> Proofing Data Collection "Improve Proofing Tools" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following. HKCU\Software\Policies\Microsoft\Office\15.0\common\ptwatson + +If the value 'PTWOptIn' is REG_DWORD = 0, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO196A mix of policy and user locations for Office Products must be disallowed.<VulnDiscussion>When Microsoft Office files are opened from trusted locations, all the content in the files is enabled and active. Users are not notified about any potential risks that might be contained in the files, such as unsigned macros, ActiveX controls, or links to content on the Internet. +By default, users can specify any location as a trusted location, and a computer can have a combination of user-created, OCT-created, and Group Policy–created trusted locations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52745V-17560CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings -> Trust Center "Allow mix of policy and user locations" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings >> Trust Center "Allow mix of policy and user locations" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security\trusted locations + +If the value 'Allow User Locations' is REG_DWORD = 0, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO197Smart Documents use of Manifests in Office must be disallowed.<VulnDiscussion>An XML expansion pack is the group of files that constitutes a Smart Document in Excel and Word. One or more components that provide the logic needed for a Smart Document are packaged by using an XML expansion pack. These components can include any type of file, including XML schemas, Extensible Stylesheet Language Transforms (XSLTs), dynamic-link libraries (DLLs), and image files, as well as additional XML files, HTML files, Word files, Excel files, and text files. +The key component to building an XML expansion pack is creating an XML expansion pack manifest file. By creating this file, the locations of all files that make up the XML expansion pack are specified, as well as information that instructs Office 2013 how to set up the files for the Smart Document. The XML expansion pack can also contain information about how to set up other files, such as how to install and register a COM object required by the XML expansion pack. +XML expansion packs can be used to initialize and load malicious code, which might affect the stability of a computer and lead to data loss. Office applications can load an XML expansion pack manifest file with a Smart Document.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52746V-17669CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Smart Documents (Word, Excel) "Disable Smart Document's use of manifests" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Smart Documents (Word, Excel) "Disable Smart Document's use of manifests" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\Common\Smart Tag + +If the value 'NeverLoadManifests' is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO203Legacy format signatures must be enabled.<VulnDiscussion>Office applications use the XML-based XMLDSIG format to attach digital signatures to documents, including Office 97-2003 binary documents. XMLDSIG signatures are not recognized by Office 2003 applications or previous versions. If an Office user opens an Excel, PowerPoint, or Word binary document with an XMLDSIG signature attached, the signature will be lost.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52751V-17749CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Signing "Legacy format signatures" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Signing "Legacy format signatures" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\signatures + +If the value 'EnableCreationOfWeakXPSignatures' is REG_DWORD = 1, this is not a finding. + +Fix Text: Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Signing "Legacy format signatures" to "Enabled".SRG-APP-000516<GroupDescription></GroupDescription>DTOO204External Signature Services Menu for Office must be suppressed.<VulnDiscussion>Users can select Add Signature Services (from the Signature Line drop-down menu on the Insert tab of the Ribbon in Excel 2013, PowerPoint 2013, and Word 2013) to see a list of signature service providers on the Microsoft Office website. If an organization has policies that govern the use of external resources such as signature providers or Office Marketplace, allowing users to access the Add Signature Services menu item might enable them to violate those policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52752V-17805CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Signing "Suppress external signature services menu item" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Signing "Suppress external signature services menu item" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\signatures + +Criteria: If the value 'SuppressExtSigningSvcs' is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO206Inclusion of document properties for PDF and XPS output must be disallowed.<VulnDiscussion>If the Microsoft Save as PDF or XPS Add-in for Microsoft Office Programs is installed, document properties are saved as metadata when users save or publish files using the PDF or XPS commands in Access 2013, Excel 2013, InfoPath 2013, PowerPoint 2013, and Word 2013 using the PDF or XPS or Publish. If this metadata contains sensitive information, saving it with the file could compromise security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52753V-17660CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Microsoft Save As PDF and XPS add-ins "Disable inclusion of document properties in PDF and XPS output" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Microsoft Save As PDF and XPS add-ins "Disable inclusion of document properties in PDF and XPS output" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\fixedformat + +If the value 'DisableFixedFormatDocProperties' is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO212Blogging entries created from inside Office products must be configured for SharePoint only.<VulnDiscussion>The blogging feature in Office products enables users to compose blog entries and post them to their blogs directly from Office, without using any additional software. +By default, users can post blog entries to any compatible blogging service provider, including Windows Live Spaces, Blogger, a SharePoint or Community Server site, and others. Leaving this capability enabled introduces the risk of users posting confidential and FOUO date to non-DoD sites.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52756V-17581CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Miscellaneous "Control Blogging" to "Enabled (Only SharePoint blogs allowed)".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Miscellaneous "Control Blogging" is set to "Enabled (Only SharePoint blogs allowed)". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\Common\Blog + +If the value 'DisableBlog' is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO402The Enable Updates and Disable Updates options in the UI must be hidden from users.<VulnDiscussion>This policy setting allows the user interface (UI) options to enable or disable Office automatic updates to be hidden from users. These options are found in the Product Information area of all Office applications installed via Click-to-Run. This policy setting has no effect on Office applications installed via Windows Installer. If this policy setting is enabled, the "Enable Updates" and "Disable Updates" options in the UI are hidden from users. If this policy setting is not configured, the "Enable Updates" and "Disable Updates" options are visible, and users can enable or disable Office automatic updates from the UI.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53191V-40859CCI-000366Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine)->Updates->"Hide option to enable or disable updates" is set to "Enabled".Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine)->Updates->"Hide option to enable or disable updates" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\software\policies\Microsoft\office\15.0\common\officeupdate + +Criteria: If the value HideEnableDisableUpdates is REG_DWORD = 1, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO410When using the Office Feedback tool, the ability to include a screenshot must be disabled.<VulnDiscussion>The "Office Feedback" tool, also called "Send-a-Smile", allows a user to click on an icon and send feedback to Microsoft. The "Office Feedback" Tool must be configured to be disabled. In the event that the Office Feedback Tool has not been configured correctly as disabled, this policy configures whether the uploading of screenshots via the tool is allowed and should also be disabled. Uploading screenshots to a commercial vendor from a DoD computer may unintentionally reveal configuration and/or FOUO content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53212V-40880CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Privacy -> Trust Center -> "Allow including screenshot with Office Feedback" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center >>"Allow including screenshot with Office Feedback" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\feedback + +If the value 'includescreenshot' is REG_DWORD = 0, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO412The ability to run unsecure Office apps must be disabled.<VulnDiscussion>Unsecure apps for Office, which are apps that have web page or catalog locations that are not SSL-secured (https://), and/or are not in users' Internet zones may allow data to be transmitted/accessed via clear text to outside sources. By configuring this policy to be disabled, users will be prevented from transmitting/accessing data in a nonsecure manner.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53214V-40882CCI-000366Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings >> Trust Center >> Trusted Catalogs "Allow Unsecure Apps and Catalogs" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings >> Trust Center >> Trusted Catalogs "Allow Unsecure Apps and Catalogs" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following hive: + +HKCU\Software\Policies\Microsoft\Office\15.0\wef\trustedcatalogs + +If the value 'requireserververification' is REG_DWORD = 1, this is not a finding. +SRG-APP-000516<GroupDescription></GroupDescription>DTOO416The Office Telemetry Agent must be configured to obfuscate the file name, file path, and title of Office documents before uploading telemetry data to the shared folder.<VulnDiscussion>This policy setting configures the Office Telemetry Agent to disguise, or obfuscate, certain file properties that are reported in telemetry data. If this policy setting is enabled, Office Telemetry Agent obfuscates the file name, file path, and title of Office documents before uploading telemetry data to the shared folder. If this policy setting is disabled or not configured, the Office Telemetry Agent uploads telemetry data that shows the full file name, file path, and title of all Office documents.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53218V-40886CCI-000366Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on privacy setting in Office Telemetry Agent" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on privacy setting in Office Telemetry Agent" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\osm + +If the value 'enablefileobfuscation' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO183The Opt-In Wizard must be disabled.<VulnDiscussion>The Opt-in Wizard displays the first time users run a 2013 Microsoft Office application, which allows them to opt into Internet-based services that will help improve their Office experience, such as Microsoft Update, the Customer Experience Improvement Program, Office Diagnostics, and Online Help. If an organization has policies that govern the use of such external resources, allowing users to opt in to these services might cause them to violate the policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52720V-17664CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Privacy -> Trust Center "Disable Opt-in Wizard on first run" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center "Disable Opt-in Wizard on first run" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\general + +If the value 'ShownFirstRunOptin' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO184The Customer Experience Improvement Program for Office must be disabled.<VulnDiscussion>When users choose to participate in the Customer Experience Improvement Program (CEIP), Office applications automatically send information to Microsoft about how the applications are used. This information is combined with other CEIP data to help Microsoft solve problems and to improve the products and features customers use most often. This feature does not collect users' names, addresses, or any other identifying information except the IP address that is used to send the data. +By default, users have the opportunity to opt into participation in the CEIP the first time they run an Office application. If an organization has policies that govern the use of external resources such as the CEIP, allowing users to opt in to the program might cause them to violate these policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52721V-17612CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Privacy -> Trust Center "Enable Customer Experience Improvement Program" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center "Enable Customer Experience Improvement Program" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common + +Criteria: If the value 'QMEnable' is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO185Automatic receiving of small updates to improve reliability must be disallowed.<VulnDiscussion>Having access to updates, add-ins, and patches on the Office Online website can help users ensure computers are up to date and equipped with the latest security patches. However, to ensure updates are tested and applied in a consistent manner, many organizations prefer to roll out updates using a centralized mechanism such as Microsoft Systems Center or Windows Server Update Services. +By default, users are allowed to download updates, add-ins, and patches from the Office Online Web site to keep their Office applications running smoothly and securely. If an organization has policies that govern the use of external resources such as Office Online, allowing users to download updates might cause them to violate these policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52722V-17740CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Privacy -> Trust Center "Automatically receive small updates to improve reliability" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center "Automatically receive small updates to improve reliability" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common + +If the value 'UpdateReliabilityData' is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO198The Internet Fax Feature must be disabled.<VulnDiscussion>Excel, PowerPoint, and Word users can use the Internet Fax feature to send documents to fax recipients through an Internet fax service provider. If your organization has policies that govern the time, place, or manner in which faxes are sent, this feature could help users evade those policies. +By default, Office users can use the Internet Fax feature. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52747V-17661CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Services -> Fax "Disable Internet Fax feature" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Services >> Fax "Disable Internet Fax feature" to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\services\fax + +If the value 'NoFax' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO345Online content options must be configured for offline content availability. +<VulnDiscussion>The Office 2013 Help system automatically searches MicrosoftOffice.com for content when a computer is connected to the Internet. Users can change this default by clearing the Search Microsoft Office.com for Help content when I'm connected to the Internet check box in the Privacy Options section of the Trust Center. If an organization has policies that govern the use of external resources such as Office.com, allowing the Help system to download content might cause users to violate these policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52758V-26630CCI-000381Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools >> Options >> General >> Service Options... >> Online Content "Online content options" to "Enabled: Do not allow Office to connect to the internet".Note: This check is Not Applicable when the use of Office 365 is against the specific DoD instance of O365. + +The use of Offline Content for Non-DoD instances of O365 is prohibited and it must not allow for personal account synchronization. + +All non-DoD instances are subject to this requirement. + +Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools >> Options >> General >> Service Options... >> Online Content "Online content options" is set to "Enabled: Do not allow Office to connect to the internet". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\internet + +If the value 'UseOnlineContent' is REG_DWORD = 0, this is not a finding. +SRG-APP-000141<GroupDescription></GroupDescription>DTOO403The video informing a user about signing into Office365 must be disabled.<VulnDiscussion>Office 365 is a subscription-based service which offers access to various Microsoft Office applications. Access to Office 365 will not be permitted; only locally installed and configured Office 2013 installations will be used. Since the ability to sign into Office 365 will be disabled, this policy, which determines whether a video about signing into Office365 is played when Office first runs, will also be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53192V-40860CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> First Run -> "Disable First Run Movie" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> First Run >> "Disable First Run Movie" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\firstrun + +Criteria: If the value 'disablemovie' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO404The first-run prompt to sign into Office365 must be disabled.<VulnDiscussion>Office 365 functionality allows users to provide credentials for accessing Office 365 using either their Microsoft Account, or the user ID assigned by the organization. Access to Office 365 will not be permitted; only locally installed and configured Office 2013 installations will be used. Since the ability to sign into Office 365 will be disabled, this policy, which determines whether the Office First Run comes up on first application boot if not previously viewed, will also be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53193V-40861CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> First Run -> "Disable Office First Run on application boot" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> First Run >> "Disable Office First Run on application boot" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\firstrun + +Criteria: If the value 'bootedrtm' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO405 The ability to sign into Office365 must be disabled.<VulnDiscussion>Office 2013 can be configured to prompt users for credentials to Office365 using either their Microsoft Account or the user ID assigned by an organization for accessing Office 365. Access to Office 365 will not be permitted and only locally installed and configured Office installations will be used.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53194V-40862CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Miscellaneous -> "Block signing into Office" to "Enabled: org ID only".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Miscellaneous >> "Block signing into Office" is set to "Enabled: org ID only". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\signin + +If the value 'signinoptions' is REG_DWORD = 2, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO406The ability to automatically hyperlink screenshots within Word, PowerPoint, Excel and Outlook must be disabled.<VulnDiscussion>The ability to automatically bind hyperlink to a screenshot inserted through the Insert Screenshot tool introduces the possibility of a malicious URL or website being imbedded in the Word, PowerPoint, Excel or Outlook document. Disabling the hyperlink in those screenshots will ensure users do not have the ability to directly open the hyperlinks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53195V-40863CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Miscellaneous -> "Do not automatically hyperlink screenshots" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Miscellaneous >> "Do not automatically hyperlink screenshots" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\gfx + +If the value 'disablescreenshotautohyperlink' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO407The prompt to save to OneDrive (formerly SkyDrive) must be disabled.<VulnDiscussion>OneDrive (formerly SkyDrive) is a cloud based storage feature that introduces the capability for users to save documents to locations outside of protected enclaves. This feature introduces the risk that FOUO and PII data, as well as other DoD protected data, may be inadvertently stored in a nonsecure location. This setting, which will prompt the user to sign in to OneDrive while performing a file save operation, must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53196V-40864CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Miscellaneous -> "Show OneDrive Sign In" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Miscellaneous .> "Show OneDrive Sign In" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\general + +If the value 'SkyDriveSignInOption' is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO408Office Presentation Service must be removed as an option for presenting PowerPoint and Word online.<VulnDiscussion>The Office Presentation Service is a free, public service that allows others to follow along in a web browser. Allowing this feature could result in presentations with DoD FOUO, PII and other protected data to be viewed in a nonsecure location. By disabling this policy, the user will not have the ability to deliver a presentation online.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53207V-40875CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Present Online -> "Remove Office Presentation Service from the list of online presentation services in PowerPoint and Word" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Present Online >> "Remove Office Presentation Service from the list of online presentation services in PowerPoint and Word" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\broadcast + +If the value 'disabledefaultservice' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO411The Office Feedback tool must be disabled.<VulnDiscussion>The "Office Feedback" tool, also called "Send-a-Smile", allows a user to click on an icon and send feedback to Microsoft. Applications used by DoD users should not be able to provide feedback to commercial vendors regarding their positive and negative experiences when using Office due to the potential of unintentionally revealing FOUO or other protected content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53213V-40881CCI-000381Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center >> "Send Office Feedback" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Privacy >> Trust Center >> "Send Office Feedback" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\feedback + +If the value 'enabled' is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO414Roaming settings must be stored locally and not synchronized to the Microsoft Office roaming settings web service.<VulnDiscussion>Microsoft Office includes the ability to roam settings for specific Office features amongst devices by storing this data in the cloud. This data includes user activity such as the list of most recently used documents as well as user preferences such as the Office theme. This policy setting controls whether this data is allowed to be stored in the cloud. If this policy setting is enabled, roaming settings are only stored locally and not synchronized to the Microsoft Office roaming settings web service. If this policy setting is disabled or not configured, roaming settings are synchronized with the Microsoft Office roaming settings web service and users can access their data from other devices. Existing data in the cloud is not affected by this policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53216V-40884CCI-000381Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Services >> "Disable Roaming Office User Settings" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Services >> "Disable Roaming Office User Settings" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\roaming + +If the value 'roamingsettingsdisabled' is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO415The ability of the Office Telemetry Agent to periodically upload telemetry data to a shared folder must be disabled.<VulnDiscussion>Office Telemetry is a new compatibility monitoring framework. When an Office document or solution is loaded, used, closed, or raises an error in certain Office 2013 applications, the Office Telemetry application adds a record about the event to a local data store. Each record includes a description of the problem and a link to more information. Inventory and usage data is also tracked. The actual logging capability will be enabled, but this policy allows that data to be uploaded to a remote location which, if enabled, could pass information about the internal network and configuration to that remote site.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53217V-40885CCI-000381Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on data uploading for Office Telemetry Agent" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on data uploading for Office Telemetry Agent" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\osm + +If the value 'enableupload' is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO417The Office Telemetry Agent and Office applications must be configured to collect telemetry data.<VulnDiscussion>Office Telemetry is a new compatibility monitoring framework. When an Office document or solution is loaded, used, closed, or raises an error in certain Office 2013 applications, the Office Telemetry application adds a record about the event to a local data store. Each record includes a description of the problem and a link to more information. Inventory and usage data is also tracked. This policy setting allows the data collection features in Office that are used by the Office Telemetry Dashboard and Office Telemetry Log to be turned on. If this policy setting is enabled, Office Telemetry Agent and Office applications will collect telemetry data, which includes Office application usage, most recently used Office documents (including file names) and solutions usage, compatibility issues, and critical errors that occur on the local computers. Office Telemetry Dashboard can be used to view this data remotely, and users can use Office Telemetry Log to view this data on their local computers. If this policy setting is disabled or not configured, the Office Telemetry Agent and Office applications do not generate or collect telemetry data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53219V-40887CCI-000381Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on telemetry data collection" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Telemetry Dashboard >> "Turn on telemetry data collection" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\osm + +If the value 'enablelogging' is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO179Documents must be configured to not open as Read Write when browsing.<VulnDiscussion>By default, when an Office 2013 document on a web server is opened using Internet Explorer, the appropriate application opens the file in read-only mode. However, if the default configuration is changed, the document is opened as read/write. Users could potentially make changes to documents and resave them in situations where the web server security is not configured to prevent such changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52714V-17759CCI-001170Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools | Options | General | Web Options... >> Files "Open Office documents as read/write while browsing" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools | Options | General | Web Options... >> Files "Open Office documents as read/write while browsing" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\internet + +If the value 'OpenDocumentsReadWriteWhileBrowsing' for REG_DWORD = 0, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO180Relying on Vector markup Language (VML) for displaying graphics in browsers must be disallowed.<VulnDiscussion>When saving documents as web pages, Excel, PowerPoint, and Word can save vector-based graphics in Vector Markup Language (VML), which enables Internet Explorer to display them smoothly at any resolution. By default, when saving VML graphics, Office applications also save copies of the graphics in a standard raster file format (GIF or PNG) for use by browsers that cannot display VML. If the "Rely on VML for displaying graphics in browsers" check box in the web Options dialog box is selected, applications will not save raster copies of VML graphics, which means those graphics will not display in non-Microsoft browsers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52715V-17773CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Tools \ Options \ General \ Web Options -> Browsers "Rely on VML for displaying graphics in browsers" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Tools >> Options >> General >> Web Options >> Browsers "Rely on VML for displaying graphics in browsers" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\internet. + +If the value 'RelyOnVML' is REG_DWORD = 0, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO193Automation Security to enforce macro level security in Office documents must be configured.<VulnDiscussion>When a separate program is used to launch Microsoft Office Excel, PowerPoint, or Word programmatically, any macros can run in the programmatically opened application without being blocked. This functionality could allow an attacker to use automation to run malicious code in Excel, PowerPoint, or Word.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52730V-17741CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Automation Security" to "Enabled (Use application macro security level)".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Automation Security" is set to "Enabled (Use application macro security level)". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\Common\Security + +If the value "AutomationSecurity" is REG_DWORD =2, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO409The ability to create an online presentation programmatically must be disabled.<VulnDiscussion>Allowing online presentations to be created programmatically allows for the capability of malicious content to become imbedded in those programmatically created presentations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53211V-40879CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Present Online -> "Restrict programmatic access for creating online presentations in PowerPoint and Word" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Present Online >> "Restrict programmatic access for creating online presentations in PowerPoint and Word" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\broadcast + +If the value 'disableprogrammaticaccess' is REG_DWORD = 1, this is not a finding.SRG-APP-000231<GroupDescription></GroupDescription>DTOO188Document metadata for password protected files must be protected.<VulnDiscussion>When an Office Open XML document is protected with a password and saved, any metadata associated with the document is encrypted along with the rest of the document's contents. If this configuration is changed, potentially sensitive information such as the document author and hyperlink references could be exposed to unauthorized people. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52725V-17768CCI-001199Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Protect document metadata for password protected files" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Protect document metadata for password protected files" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +If the value 'OpenXMLEncryptProperty' is REG_DWORD = 1, this is not a finding.SRG-APP-000231<GroupDescription></GroupDescription>DTOO189The encryption type for password protected Open XML files must be set.<VulnDiscussion>If unencrypted files are intercepted, sensitive information in the files can be compromised. To protect information confidentiality, Microsoft Office application files can be encrypted and password protected. Only users who know the correct password will be able to decrypt such files. Since some encryption types are less secure and easier to breach, Microsoft Enhanced RSA and AES Cryptographic Provider, AES-256, 256-bit should be used when encrypting documents.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52726V-17619CCI-001199Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Encryption type for password protected Office Open XML files" to "Enabled (Microsoft Enhanced RSA and AES Cryptographic Provider,AES 256,256)".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Encryption type for password protected Office Open XML files" is set to "Enabled (Microsoft Enhanced RSA and AES Cryptographic Provider, AES 256,256)". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +If the value 'OpenXMLEncryption' is REG_SZ = "Microsoft Enhanced RSA and AES Cryptographic Provider, AES 256,256", this is not a finding.SRG-APP-000231<GroupDescription></GroupDescription>DTOO190The encryption type for password protected Office 97 thru Office 2003 must be set.<VulnDiscussion>If unencrypted files are intercepted, sensitive information in the files can be compromised. To protect information confidentiality, Microsoft Office application files can be encrypted and password protected. Only users who know the correct password will be able to decrypt such files. Since some encryption types are less secure and easier to breach, Microsoft Enhanced RSA and AES Cryptographic Provider, AES-256, 256-bit should be used when encrypting documents.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52727V-17617CCI-001199Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Encryption type for password protected Office 97-2003 files" to "Enabled (Microsoft Enhanced RSA and AES Cryptographic Provider,AES 256,256)".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Encryption type for password protected Office 97-2003 files" is set to "Enabled (Microsoft Enhanced RSA and AES Cryptographic Provider, AES 256,256)". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +If the value 'DefaultEncryption12' is REG_SZ = "Microsoft Enhanced RSA and AES Cryptographic Provider, AES 256,256", this is not a finding.SRG-APP-000231<GroupDescription></GroupDescription>DTOO195Passwords for secured documents must be enforced.<VulnDiscussion>If 2013 Office users add passwords to documents, other users can be prevented from opening the documents. This capability can provide an extra level of protection to documents already protected by access control lists, or provide a means of securing documents not protected by file-level security. +By default, users can add passwords to Excel 2013 workbooks, PowerPoint 2013 presentations, and Word 2013 documents from the Save or Save As dialog box by clicking Tools, clicking General Options, and entering appropriate passwords to open or modify the documents. If this configuration is changed, the General Options dialog box for saving with a password will not be available for the user to password-protect their documents.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52744V-17665CCI-001199Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Disable password to open UI" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Disable password to open UI" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following key: +HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +If the value 'DisablePasswordUI' is REG_DWORD = 0, this is not a finding. + +Fix Text: Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Disable password to open UI" to "Disabled". SRG-APP-000209<GroupDescription></GroupDescription>DTOO186Trust Bar notifications for Security messages must be enforced.<VulnDiscussion>The Message Bar in Office applications is used to identify security issues, such as unsigned macros or potentially unsafe add-ins. When such issues are detected, the application disables the unsafe feature or content and displays the Message Bar at the top of the active window. The Message Bar informs the users about the nature of the security issue and, in some cases, provides the users with an option to enable the potentially unsafe feature or content, which could harm the user's computer. +By default, if an Office application detects a security issue, the Message Bar is displayed. However, this configuration can be modified by users in the Trust Center.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52723V-17590CCI-001662Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Disable all Trust Bar notifications for security issues" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Disable all Trust Bar notifications for security issues" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\trustcenter + +If the value 'TrustBar' is REG_DWORD = 0, this is not a finding.SRG-APP-000209<GroupDescription></GroupDescription>DTOO192Load controls in forms3 must be disabled from loading.<VulnDiscussion>ActiveX controls are Component Object Model (COM) objects and have unrestricted access to users' computers. ActiveX controls can access the local file system and change the registry settings of the operating system. If a malicious user repurposes an ActiveX control to take over a user's computer, the effect could be significant. +To help improve security, ActiveX developers can mark controls as Safe For Initialization (SFI), which means that the developer states that the controls are safe to open and run and not capable of causing harm to any computers. If a control is not marked SFI, the control could adversely affect a computer--or it could mean the developers did not test the control in all situations and are not sure whether their control might be compromised at some future date. +SFI controls run in safe mode, which limits their access to the computer. For example, a worksheet control can both read and write files when it is in unsafe mode, but perhaps only read from files when it is in safe mode. This functionality allows the control to be used in very powerful ways when safety is not important, but the control would still be safe for use in a Web page. +If a control is not marked as SFI, it is marked Unsafe For Initialization (UFI), which means that it is capable of affecting a user's computer. If UFI ActiveX controls are loaded, they are always loaded in unsafe mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52729V-17750CCI-001662Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Load Controls in Forms3" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Load Controls in Forms3" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\keycupoliciesmsvbasecurity + +If the value 'LoadControlsInForms' exists, this is a finding.SRG-APP-000131<GroupDescription></GroupDescription>DTOO413Users must be prevented from using or inserting apps that come from the Office Store.<VulnDiscussion>This policy setting allows users to be prevented from using or inserting apps that come from the Office Store. If this policy setting is enabled, apps from the Office Store are blocked. If this policy setting is disabled or not configured, apps from the Office Store are allowed, unless the "Block Apps for Office" policy setting is enabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-53215V-40883CCI-001749Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings >> Trust Center >> Trusted Catalogs "Block the Office Store" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings >> Trust Center >> Trusted Catalogs "Block the Office Store" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\wef\trustedcatalogs + +If the value 'disableomexcatalogs' is REG_DWORD = 1, this is not a finding.SRG-APP-000328<GroupDescription></GroupDescription>DTOO199Changing permissions on rights managed content for users must be enforced.<VulnDiscussion>This setting controls whether Office 2013 users can change permissions for content that is protected with Information Rights Management (IRM). The Information Rights Management feature of Office 2013 allows individuals and administrators to specify access permissions to Word documents, Excel workbooks, PowerPoint presentations, InfoPath templates and forms, and Outlook email messages. This functionality helps prevent sensitive information from being printed, forwarded, or copied by unauthorized people.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52748V-17765CCI-002165Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Manage Restricted Permissions "Prevent users from changing permissions on rights managed content" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Manage Restricted Permissions "Prevent users from changing permissions on rights managed content" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\drm + +Criteria: If the value 'DisableCreation' is REG_DWORD = 0, this is not a finding.SRG-APP-000328<GroupDescription></GroupDescription>DTOO200Office must be configured to not allow read with browsers.<VulnDiscussion>The Windows Rights Management Add-on for Internet Explorer provides a way for users who do not use the 2013 Office release to view, but not alter, files with restricted permissions. By default, IRM-enabled files are saved in a format that cannot be viewed by using the Windows Rights Management Add-on. If this setting is enabled, an embedded rights-managed HTML version of the content is saved with each IRM-enabled file, which can be viewed in Internet Explorer using the add-on, representing the risk of documents being read by those without the rights and not intended to have access to the document.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52749V-17583CCI-002165Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Manage Restricted Permissions "Allow users with earlier versions of Office to read with browsers" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Manage Restricted Permissions "Allow users with earlier versions of Office to read with browsers" is set to "Disabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\drm + +If the value 'IncludeHTML' is REG_DWORD = 0, this is not a finding.SRG-APP-000340<GroupDescription></GroupDescription>DTOO201Connection verification of permissions must be enforced.<VulnDiscussion>Users are not required to connect to the network to verify permissions. If users do not need their licenses confirmed when attempting to open Office documents, they might be able to access documents after their licenses have been revoked. Also, it is not possible to log the usage of files with restricted permissions if users' licenses are not confirmed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52750V-17731CCI-002235Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Manage Restricted Permissions "Always require users to connect to verify permission" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Manage Restricted Permissions "Always require users to connect to verify permission" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\drm + +Criteria: If the value 'RequireConnection' is REG_DWORD = 1, this is not a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO191ActiveX control initialization must be disabled.<VulnDiscussion>ActiveX controls can adversely affect a computer directly. In addition, malicious code can be used to compromise an ActiveX control and attack a computer. To indicate the safety of an ActiveX control, developers can denote them as Safe For Initialization (SFI). SFI indicates a control is safe to open and run, and it is not capable of causing a problem for any computer, regardless of whether it has persisted data values or not. +If a control is not marked SFI, it is possible the control could adversely affect a computer—or it could mean the developers did not test the control in all situations and are not sure whether it might be compromised in the future. +By default, if a control is marked SFI, the application loads the control in safe mode and uses persisted values (if any). If the control is not marked SFI, the application loads the control in unsafe mode with persisted values (if any), or uses the default (first-time initialization) settings. In both situations, the Message Bar informs users the controls have been disabled and prompts them to respond.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52728V-17547CCI-002460Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "ActiveX Control Initialization" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "ActiveX Control Initialization" is set to "Disabled". +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\Common\Security + +If the value 'UFIControls' exists, this is a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO194Hyperlink warnings for Office must be configured for use.<VulnDiscussion>Unsafe hyperlinks are links that might pose a security risk if users click them. Clicking an unsafe link could compromise the security of sensitive information or harm the computer. +Links that Office considers unsafe include links to executable files, TIFF files, and Microsoft Document Imaging (MDI) files. Other unsafe links are those using protocols considered to be unsafe, including msn, nntp, mms, outlook, and stssync.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52731V-17659CCI-002460Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Suppress hyperlink warnings" to "Disabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Suppress hyperlink warnings" is set to "Disabled". +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +Criteria: If the value 'DisableHyperLinkWarning' is REG_DWORD = 0, this is not a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO207Document Information panel Beaconing must show UI.<VulnDiscussion>This policy setting controls whether users see a security warning when they open custom Document Information Panels that contain a web beaconing threat. Web beacons can be used to contact an external server when users open forms. Information could be gathered by the form, or information entered by users could be sent to an external server, exposing the internal users and systems to additional attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52754V-17605CCI-002460Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Document Information Panel "Document Information Panel Beaconing UI" to "Enabled (Always show UI)".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Document Information Panel "Document Information Panel Beaconing UI" is set to "Enabled (Always show UI)". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\documentinformationpanel + +If the value 'Beaconing' is REG_DWORD = 1, this is not a finding.SRG-APP-000429<GroupDescription></GroupDescription>DTOO187Rights managed Office Open XML files must be protected.<VulnDiscussion>When Information Rights Management (IRM) is used to restrict access to an Office Open XML document, any metadata associated with the document is not encrypted. This configuration could allow potentially sensitive information such as the document author and hyperlink references to be exposed to unauthorized individuals.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52724V-17769CCI-002476Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Protect document metadata for rights managed Office Open XML Files" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Protect document metadata for rights managed Office Open XML Files" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +If the value 'DRMEncryptProperty' is REG_DWORD = 1, this is not a finding.SRG-APP-000429<GroupDescription></GroupDescription>DTOO321Encrypt document properties must be configured for OLE documents. +<VulnDiscussion>This policy setting allows a document's properties to be encrypted. This applies to OLE documents (Office 97-2003 compatible) if the application is configured for CAPI RC4. Disabling this setting will prevent the encryption of document properties, which may expose sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227SV-52757V-26704CCI-002476Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Security Settings "Encrypt document properties" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2013 >> Security Settings "Encrypt document properties" is set to "Enabled". + +Use the Windows Registry Editor to navigate to the following HKCU\Software\Policies\Microsoft\Office\15.0\common\security + +Criteria: If the value 'EncryptDocProps' is REG_DWORD = 1, this is not a finding.SRG-APP-000456<GroupDescription></GroupDescription>DTOO401The version of Microsoft Office running on the system must be a supported version.<VulnDiscussion>Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. + +Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). + +This requirement will apply to software patch management solutions used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. + +The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Office System 2013DISADPMS TargetMicrosoft Office System 20134227V-40858SV-53190CCI-002605Upgrade to a supported version.Microsoft Office 2013 is no longer supported by the vendor. If the system is running Microsoft Office 2013, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_MS_PowerPoint_2010_STIG_V1R11_Manual-xccdf.xml b/benchmarks/DISA/U_MS_PowerPoint_2010_STIG_V1R11_Manual-xccdf.xml new file mode 100644 index 000000000..6677701ac --- /dev/null +++ b/benchmarks/DISA/U_MS_PowerPoint_2010_STIG_V1R11_Manual-xccdf.xml @@ -0,0 +1,269 @@ +acceptedMicrosoft PowerPoint 2010 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 11 Benchmark Date: 24 Jul 20243.51.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000210<GroupDescription></GroupDescription>DTOO104Disabling of user name and password syntax from being used in URLs must be enforced in PowerPoint.<VulnDiscussion>The Uniform Resource Locator (URL) standard allows user authentication to be included in URL strings in the form http://username:password@example.com. A malicious user might use this URL syntax to create a hyperlink that appears to open a legitimate website but actually opens a deceptive (spoofed) website. For example, the URL http://www.wingtiptoys.com@example.com appears to open http://www.wingtiptoys.com but actually opens http://example.com. To protect users from such attacks, Internet Explorer usually blocks any URLs using this syntax. + +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If user names and passwords in URLs are allowed, users could be diverted to dangerous web pages, which could pose a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17173SV-53464CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" to "Enabled" and place a check in the 'powerpnt.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" is set to "Enabled" and a check in the 'powerpnt.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO110Blocking as default file block opening behavior must be enforced.<VulnDiscussion>Users can open, view, or edit a large number of file types in PowerPoint 2013. Some file types are safer than others, as some could allow malicious code to become active on user computers or the network. For this reason, disabling or not configuring this setting could allow malicious code to become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26612SV-53468CCI-001662Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> File Block Settings "Set default file block behavior" to "Enabled: Blocked files are not opened".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> File Block Settings "Set default file block behavior" is set to "Enabled: Blocked files are not opened". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\fileblock + +Criteria: If the value OpenInProtectedView is REG_DWORD = 0, this is not a findingSRG-APP-000112<GroupDescription></GroupDescription>DTOO111The Internet Explorer Bind to Object functionality must be enabled in PowerPoint.<VulnDiscussion>Internet Explorer performs a number of safety checks before initializing an ActiveX control. It will not initialize a control if the kill bit for the control is set in the registry, or if the security settings for the zone in which the control is located do not allow it to be initialized. +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). A security risk could occur if potentially dangerous controls are allowed to load.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17174SV-53537CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" to "Enabled" and place a check in the 'powerpnt.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" is set to "Enabled" and a check in the 'powerpnt.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SAFE_BINDTOOBJECT + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO117The Saved from URL mark must be selected to enforce Internet zone processing in PowerPoint.<VulnDiscussion>Typically, when Internet Explorer loads a web page from a Universal Naming Convention (UNC) share that contains a Mark of the Web (MOTW) comment, indicating the page was saved from a site on the Internet; Internet Explorer runs the page in the Internet security zone instead of the less restrictive Local Intranet security zone. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer does not evaluate the page for a MOTW, potentially dangerous code could be allowed to run.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17175SV-53470CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" to "Enabled" and place a check in the 'powerpnt.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" is set to "Enabled" and a check in the 'powerpnt.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_UNC_SAVEDFILECHECK + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO119Configuration for file validation must be enforced.<VulnDiscussion>Office File Validation helps detect and prevent a kind of exploit known as a file format attack or file fuzzing attack. File format attacks exploit the integrity of a file. They occur when someone modifies the structure of a file with the intent of adding malicious code. Usually the malicious code is run remotely and is used to elevate the privilege of restricted accounts on the computer. As a result, an attacker could gain access to a computer that they did not previously have access to. This could enable an attacker to read sensitive information from the computer's hard disk drive or install malware, such as a worm or a key logging program. The Office File Validation feature helps prevent file format attacks by scanning and validating files before they are opened. To validate files, Office File Validation compares a file's structure to a predefined file schema, which is a set of rules that determine what a readable file looks like. If Office File Validation detects that a file's structure does not follow all rules that are described in the schema, the file does not pass validation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26592SV-53471CCI-001695Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Turn off file validation" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Turn off file validation" set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\filevalidation + +Criteria: If the value EnableOnLoad is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO121Files from the Internet zone must be opened in Protected View.<VulnDiscussion>This policy setting allows for determining if files downloaded from the Internet zone open in Protected View. If enabling this policy setting, files downloaded from the Internet zone do not open in Protected View. If disabling or not configuring this policy setting, files downloaded from the Internet zone open in Protected View.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26614SV-53473CCI-001662Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Do not open files from the Internet zone in Protected View to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Do not open files from the Internet zone in Protected View" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\protectedview + +Criteria: If the value DisableInternetFilesInPV is REG_DWORD = 0, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO123Navigation to URLs embedded in Office products must be blocked in PowerPoint.<VulnDiscussion>To protect users from attacks, Internet Explorer usually does not attempt to load malformed URLs. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer attempts to load a malformed URL, a security risk could occur.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17183SV-53475CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" to "Enabled" and place a check in the 'powerpnt.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" must be "Enabled" and a check in the 'powerpnt.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_VALIDATE_NAVIGATE_URL + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO124Scripted Window Security must be enforced in PowerPoint.<VulnDiscussion>Malicious websites often try to confuse or trick users into giving a site permission to perform an action allowing the site to take control of the users' computers in some manner. Disabling or not configuring this setting allows unknown websites to: +-Create browser windows appearing to be from the local operating system. +-Draw active windows displaying outside of the viewable areas of the screen capturing keyboard input. +-Overlay parent windows with their own browser windows to hide important system information, choices or prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26588SV-53477CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" to "Enabled" and 'powerpnt.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" is set to "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO126Add-on Management functionality must be allowed in PowerPoint.<VulnDiscussion>Internet Explorer add-ons are pieces of code, run in Internet Explorer, to provide additional functionality. Rogue add-ons may contain viruses or other malicious code. Disabling or not configuring this setting could allow malicious code or users to become active on user computers or the network. For example, a malicious user can monitor and then use keystrokes users type into Internet Explorer. Even legitimate add-ons may demand resources, compromising the performance of Internet Explorer, and the operating systems for user computers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26584SV-53479CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" to "Enabled" and 'powerpnt.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" is set to "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following keys: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ADDON_MANAGEMENT + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000131<GroupDescription></GroupDescription>DTOO127Add-ins to Office applications must be signed by a Trusted Publisher.<VulnDiscussion>Office 2013 applications do not check the digital signature on application add-ins before opening them. Disabling or not configuring this setting may allow an application to load a dangerous add-in. As a result, malicious code could become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26589SV-53481CCI-001749Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value RequireAddinSig is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO129Links that invoke instances of Internet Explorer from within an Office product must be blocked in PowerPoint.<VulnDiscussion>The Pop-up Blocker feature in Internet Explorer can be used to block most unwanted pop-up and pop-under windows from appearing. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If the Pop-up Blocker is disabled, disruptive and potentially dangerous pop-up windows could load and present a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17184SV-53484CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" to "Enabled" and select 'powerpnt.exe'.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" must be "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000131<GroupDescription></GroupDescription>DTOO131Trust Bar Notifications for unsigned application add-ins must be blocked.<VulnDiscussion>If an application is configured to require all add-ins to be signed by a trusted publisher, any unsigned add-ins the application loads will be disabled and the application will display the Trust Bar at the top of the active window. The Trust Bar contains a message informing users about the unsigned add-in. If a user is allowed to make the determination to allow an unsigned add-in, it increases the risk of malicious code being introduced onto the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17187SV-53486CCI-001749Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins and block them" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins and block them" must be "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\software\policies\Microsoft\office\15.0\powerpoint\security + +Criteria: If the value notbpromptunsignedaddin is REG_DWORD = 1, this is not a finding.SRG-APP-000209<GroupDescription></GroupDescription>DTOO132File Downloads must be configured for proper restrictions in PowerPoint.<VulnDiscussion>Disabling this setting allows websites to present file download prompts via code without the user specifically initiating the download. User preferences may also allow the download to occur without prompting or interaction with the user. Even if Internet Explorer prompts the user to accept the download, some websites abuse this functionality. Malicious websites may continually prompt users to download a file or present confusing dialog boxes to trick users into downloading or running a file. If the download occurs and it contains malicious code, the code could become active on the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26587SV-53491CCI-001169Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" to "Enabled" and 'powerpnt.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" is set to "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_FILEDOWNLOAD + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO133All automatic loading from Trusted Locations must be disabled.<VulnDiscussion>Trusted locations specified in the Trust Center are used to define file locations assumed to be safe. Content, code, and add-ins are allowed to load from trusted locations with a minimal amount of security, without prompting the users for permission. If a dangerous file is opened from a trusted location, it will not be subject to standard security measures and could harm users' computers or data. By default, files located in trusted locations (those specified in the Trust Center) are assumed to be safe.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17471SV-53492CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Trusted Locations "Disable all trusted locations" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Trusted Locations "Disable all trusted locations" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\trusted locations + +Criteria: If the value AllLocationsDisabled is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO134Disallowance of Trusted Locations on the network must be enforced.<VulnDiscussion>Files located in Trusted Locations and specified in the Trust Center are assumed to be safe. Content, code, and add-ins are allowed to load from Trusted Locations with minimal security and without prompting the user for permission. By default, users can specify Trusted Locations on network shares, or in other remote locations not under their direct control, by selecting the "Allow Trusted Locations on my network" (not recommended) check box in the Trusted Locations section of the Trust Center. If a dangerous file is opened from a trusted location, it will not be subject to typical security measures and could affect users' computers or data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17520SV-53494CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Trusted Locations "Allow Trusted Locations on the network" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Trusted Locations "Allow Trusted Locations on the network" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\trusted locations + +Criteria: If the value AllowNetworkLocations is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO139The Save commands default file format must be configured.<VulnDiscussion>When users create new PowerPoint files, PowerPoint 2013 saves them in the new *.pptx format. Ensure this setting is enabled to specify that all new files are created in PowerPoint 2013. If a new file is created in an earlier format, some users may not be able to open or use the file, or they may choose a format this is less secure than the PowerPoint 2013 format. Users can still select a specific format when they save files, but they cannot change default of this setting from the PowerPoint Options dialog box. This enforced user behavior ensures any change to the file format requires additional deliberate user interaction.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17521SV-53496CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Save "default file format" to "Enabled PowerPoint Presentation (*.pptx)".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Save "default file format" is set to "Enabled PowerPoint Presentation (*.pptx)". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\options + +Criteria: If the value DefaultFormat is REG_DWORD = 1b (hex) 27 (dec), this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO142Enforce encrypted macros to be scanned in open XML documents must be determined and configured.<VulnDiscussion>When an Office Open XML document (Word, Excel, and PowerPoint) is rights-managed, or password-protected, any macros embedded in the document are encrypted along with the rest of the contents. By default, these encrypted macros will be disabled unless they are scanned by antivirus software immediately before being loaded. If this default configuration is modified, Office products will not require encrypted macros to be scanned before loading. They will be handled as specified by the Office System macro security settings, which can cause macro viruses to load undetected and lead to data loss or reduced application functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17473SV-53498CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Scan encrypted macros in PowerPoint Open XML presentations" to "Enabled (Scan encrypted macros (default)".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Scan encrypted macros in PowerPoint Open XML presentations" must be "Enabled (Scan encrypted macros (default)". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value PowerPointBypassEncryptedMacroScan is REG_DWORD = 0, this not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO146Trust access for VBA must be disallowed.<VulnDiscussion>VSTO projects require access to the Visual Basic for Applications project system in Excel, PowerPoint, and Word, even though the projects do not use Visual Basic for Applications. Design-time support of controls in both Visual Basic and C# projects depends on the Visual Basic for Applications project system in Word and Excel. By default, Excel, Word, and PowerPoint do not allow automation clients to have programmatic access to VBA projects. Users can enable this by selecting the Trust access to the VBA project object model in the Macro Settings section of the Trust Center. However, doing so allows macros in any documents the user opens to access the core Visual Basic objects, methods, and properties, which represents a potential security hazard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17522SV-53505CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Trust access to Visual Basic Project" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "Trust access to Visual Basic Project" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value AccessVBOM is REG_DWORD=0, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO209Protection from zone elevation must be enforced in PowerPoint.<VulnDiscussion>Internet Explorer places restrictions on each web page users can use the browser to open. Web pages on a user's local computer have the fewest security restrictions and reside in the Local Machine zone, making this security zone a prime target for malicious users and code. Disabling or not configuring this setting could allow pages in the Internet zone to navigate to pages in the Local Machine zone to then run code to elevate privileges. This could allow malicious code or users to become active on the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26585SV-53509CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" to "Enabled" and 'powerpnt.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" is set to "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ZONE_ELEVATION + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000384<GroupDescription></GroupDescription>DTOO210The opening of pre-release versions of file formats new to PowerPoint 2013 through the Compatibility Pack for Office 2013 and PowerPoint 2013 Converter must be blocked.<VulnDiscussion>Versions of file formats from pre-release versions of Office applications may introduce bugs found in those pre-release versions of the applications which have been subsequently fixed in the final release version.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17322SV-53513CCI-001764Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Office 2013 Converters -> "Block opening of pre-release versions of file formats new to PowerPoint 2013 through the Compatibility Pack for Office 2013 and PowerPoint 2013 Converter" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Office 2013 Converters -> "Block opening of pre-release versions of file formats new to PowerPoint 2013 through the Compatibility Pack for Office 2013 and PowerPoint 2013 Converter" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\software\policies\Microsoft\office\15.0\PowerPoint\security\fileblock + +Criteria: If the value powerpoint12betafilesfromconverters is REG_DWORD = 1, this is not a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO211ActiveX Installs must be configured for proper restriction in PowerPoint.<VulnDiscussion>Microsoft ActiveX controls allow unmanaged, unprotected code to run on the user computers. ActiveX controls do not run within a protected container in the browser like the other types of HTML or Microsoft Silverlight-based controls. Disabling or not configuring this setting does not block prompts for ActiveX control installations and these prompts display to users. This could allow malicious code to become active on the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26586SV-53515CCI-002460Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" to "Enabled" and 'powerpnt.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" is set to "Enabled" and 'powerpnt.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ACTIVEXINSTALL + +Criteria: If the value powerpnt.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO288Files in unsafe locations must be opened in Protected View. +<VulnDiscussion>This policy setting determines if files located in unsafe locations will open in Protected View. If unsafe locations have not been specified, only the "Downloaded Program Files" and "Temporary Internet Files" folders are considered unsafe locations. If enabling this policy setting, files located in unsafe locations do not open in Protected View. If disabling or not configuring this policy setting, files located in unsafe locations open in Protected View.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26615SV-53517CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Do not open files in unsafe locations in Protected View" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Do not open files in unsafe locations in Protected View" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\protectedview + +Criteria: If the value DisableUnsafeLocationsInPV is REG_DWORD = 0, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO289The ability to run programs from a PowerPoint presentation must be disallowed.<VulnDiscussion>Action buttons can be used to launch external programs from PowerPoint presentations. If a malicious person adds an action button to a presentation that launches a dangerous program, it could significantly affect the security of a user's computer and data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17788SV-53519CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Run Programs" to "Enabled (disable - (don't run any programs))".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Run Programs" must be "Enabled (disable - (don't run any programs))". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value RunPrograms is REG_DWORD = 0, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO290Hidden markup options must be visible.<VulnDiscussion>PowerPoint presentations that are saved in standard or HTML format can contain a flag indicating whether markup (comments or ink annotations) in the presentation should be visible when the presentation is open. PowerPoint ignores this flag when opening a file, and always displays any markup present in the file. In addition, when saving a file, PowerPoint sets the flag to display markup when the presentation is next opened. +If this default configuration is changed, PowerPoint sets the flag according to the state of the Show Markup option on the Review tab of the Ribbon when it saves presentations in standard or HTML format. In addition, PowerPoint enables or disables the Show Markup option according to the way the flag is set when it opens files, which means that a presentation saved with hidden markup is opened with the markup still hidden. +If a file is saved with hidden markup, users might inadvertently distribute sensitive comments or information to others via the presentation file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17752SV-53522CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Make hidden markup visible" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Make hidden markup visible" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\options + +Criteria: If the value MarkupOpenSave is REG_DWORD = 1, this is not a finding. +SRG-APP-000209<GroupDescription></GroupDescription>DTOO291Automatic download of linked images must be disallowed.<VulnDiscussion>When users insert images into PowerPoint presentations, they can select Link to File instead of Insert. If they do so, the image is represented by a link to a file on disk instead of being embedded in the presentation file itself. By default, when PowerPoint opens a presentation it does not display any linked images saved on a different computer unless the presentation itself is saved in a trusted location (as configured in the Trust Center). If this configuration is changed, PowerPoint will load any images that were saved in remote locations, which presents a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17809SV-55919CCI-001169Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Unblock automatic download of linked images" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security "Unblock automatic download of linked images" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value DownloadImages is REG_DWORD = 0, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO292Document behavior if file validation fails must be set.<VulnDiscussion>This policy key controls the behavior of how Office documents should be handled when failing file validation. By requiring such documents to be opened in Protected View, any potentially malicious code would be disabled, allowing the user to edit the document and resave correctly.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26616SV-53524CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Set document behavior if file validation fails" to "Enabled: Open in Protected View" and Unchecked for "Do not allow edit".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Set document behavior if file validation fails" must be "Enabled: Open in Protected View" and Unchecked for "Do not allow edit". + +Procedure: Use the Windows Registry Editor to navigate to the following keys: + + +If both +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\filevalidation\OpenInProtectedView is set to REG_DWORD = 1 and HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\filevalidation\DisableEditFromPV is set to REG_DWORD = 1, this is not a finding. + +If either, or both keys are not set to REG_DWORD = 1, this is an open finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO293Attachments opened from Outlook must be in Protected View.<VulnDiscussion>This policy setting allows for determining if PowerPoint files in Outlook attachments open in Protected View. If enabling this policy setting, Outlook attachments do not open in Protected View. If disabling or not configuring this policy setting, Outlook attachments open in Protected View.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26617SV-53526CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Turn off Protected View for attachments opened from Outlook" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center -> Protected View "Turn off Protected View for attachments opened from Outlook" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security\protectedview + +Criteria: If the value DisableAttachmentsInPV is REG_DWORD = 0, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO304Warning Bar settings for VBA macros must be configured.<VulnDiscussion>When users open files containing VBA macros, applications open the files with the macros disabled and displays the Trust Bar with a warning that macros are present and have been disabled. Users may then enable these macros by clicking Options on the Trust Bar and selecting the option to enable them. Disabling or not configuring this setting may allow dangerous macros to become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-17545SV-53528CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "VBA Macro Notification Settings" to "Enabled (Disable all with notification)".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> PowerPoint Options -> Security -> Trust Center "VBA Macro Notification Settings" is set to "Enabled (Disable all with notification)". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value VBAWarnings is REG_DWORD = 2, this is not a finding.SRG-APP-000516<GroupDescription></GroupDescription>DTOO319The configuration for Slide Update with counterparts must be disallowed.<VulnDiscussion>This setting controls whether users can link slides in a presentation with their counterparts in a PowerPoint Slide Library. If this policy setting is enabled, PowerPoint cannot check the status of a slide in a Slide Library when a presentation with Slide Update data is opened. If this policy setting is disabled or not configured, each time users open a presentation that contains a shared slide, PowerPoint notifies them if the slide has been updated and provides them with the opportunity to ignore the update, append a new slide to the outdated slide, or replace the outdated slide with the updated one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-26639SV-53533CCI-000366Set the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> Miscellaneous "Disable Slide Update" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft PowerPoint 2013 -> Miscellaneous "Disable Slide Update" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\slide libraries + +Criteria: If the value DisableSlideUpdate is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO501Disabling of user name and password syntax from being used in URLs must be enforced in PowerPoint Viewer.<VulnDiscussion>The Uniform Resource Locator (URL) standard allows user authentication to be included in URL strings in the form http://username:password@example.com. A malicious user might use this URL syntax to create a hyperlink that appears to open a legitimate website but actually opens a deceptive (spoofed) website. For example, the URL http://www.wingtiptoys.com@example.com appears to open http://www.wingtiptoys.com but actually opens http://example.com. To protect users from such attacks, Internet Explorer usually blocks any URLs using this syntax. + +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If user names and passwords in URLs are allowed, users could be diverted to dangerous web pages, which could pose a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42327SV-54944CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" to "Enabled" and place a check in the 'pptview.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" is set to "Enabled" and a check in the 'pptview.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO502The Internet Explorer Bind to Object functionality must be enabled in PowerPoint Viewer.<VulnDiscussion>Internet Explorer performs a number of safety checks before initializing an ActiveX control. It will not initialize a control if the kill bit for the control is set in the registry, or if the security settings for the zone in which the control is located do not allow it to be initialized. +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). A security risk could occur if potentially dangerous controls are allowed to load.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42332SV-54951CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" to "Enabled" and place a check in the 'pptview.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" is set to "Enabled" and a check in the 'pptview.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SAFE_BINDTOOBJECT + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO503The Saved from URL mark must be selected to enforce Internet zone processing in PowerPoint Viewer.<VulnDiscussion>Typically, when Internet Explorer loads a web page from a Universal Naming Convention (UNC) share that contains a Mark of the Web (MOTW) comment, indicating the page was saved from a site on the Internet; Internet Explorer runs the page in the Internet security zone instead of the less restrictive Local Intranet security zone. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer does not evaluate the page for a MOTW, potentially dangerous code could be allowed to run.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42333SV-54952CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" to "Enabled" and place a check in the 'pptview.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" is set to "Enabled" and a check in the 'pptview.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_UNC_SAVEDFILECHECK + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO504Navigation to URLs embedded in Office products must be blocked in PowerPoint Viewer.<VulnDiscussion>To protect users from attacks, Internet Explorer usually does not attempt to load malformed URLs. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer attempts to load a malformed URL, a security risk could occur.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42334SV-54953CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" to "Enabled" and place a check in the 'pptview.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" must be "Enabled" and a check in the 'pptview.exe' check box is selected. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_VALIDATE_NAVIGATE_URL + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO505Scripted Window Security must be enforced in PowerPoint Viewer.<VulnDiscussion>Malicious websites often try to confuse or trick users into giving a site permission to perform an action allowing the site to take control of the users' computers in some manner. Disabling or not configuring this setting allows unknown websites to: +-Create browser windows appearing to be from the local operating system. +-Draw active windows displaying outside of the viewable areas of the screen capturing keyboard input. +-Overlay parent windows with their own browser windows to hide important system information, choices or prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42335SV-54954CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" to "Enabled" and 'pptview.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" is set to "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO506Add-on Management functionality must be allowed in PowerPoint Viewer.<VulnDiscussion>Internet Explorer add-ons are pieces of code, run in Internet Explorer, to provide additional functionality. Rogue add-ons may contain viruses or other malicious code. Disabling or not configuring this setting could allow malicious code or users to become active on user computers or the network. For example, a malicious user can monitor and then use keystrokes users type into Internet Explorer. Even legitimate add-ons may demand resources, compromising the performance of Internet Explorer, and the operating systems for user computers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42336SV-54955CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" to "Enabled" and 'pptview.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" is set to "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following keys: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ADDON_MANAGEMENT + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO507File Links that invoke instances of Internet Explorer from within an Office product must be blocked in PowerPoint Viewer.<VulnDiscussion>The Pop-up Blocker feature in Internet Explorer can be used to block most unwanted pop-up and pop-under windows from appearing. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If the Pop-up Blocker is disabled, disruptive and potentially dangerous pop-up windows could load and present a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42330SV-54949CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" to "Enabled" and select 'pptview.exe'.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" must be "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000209<GroupDescription></GroupDescription>DTOO508File Downloads must be configured for proper restrictions in PowerPoint Viewer.<VulnDiscussion>Disabling this setting allows websites to present file download prompts via code without the user specifically initiating the download. User preferences may also allow the download to occur without prompting or interaction with the user. Even if Internet Explorer prompts the user to accept the download, some websites abuse this functionality. Malicious websites may continually prompt users to download a file or present confusing dialog boxes to trick users into downloading or running a file. If the download occurs and it contains malicious code, the code could become active on the user's computer or the network. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42331SV-54950CCI-001169Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" to "Enabled" and 'pptview.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" is set to "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_FILEDOWNLOAD + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO509Protection from zone elevation must be enforced in PowerPoint Viewer.<VulnDiscussion>Internet Explorer places restrictions on each web page users can use the browser to open. Web pages on a user's local computer have the fewest security restrictions and reside in the Local Machine zone, making this security zone a prime target for malicious users and code. Disabling or not configuring this setting could allow pages in the Internet zone to navigate to pages in the Local Machine zone to then run code to elevate privileges. This could allow malicious code or users to become active on the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42329SV-54948CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" to "Enabled" and 'pptview.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" is set to "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ZONE_ELEVATION + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO510ActiveX Installs must be configured for proper restriction in PowerPoint Viewer.<VulnDiscussion>Microsoft ActiveX controls allow unmanaged, unprotected code to run on the user computers. ActiveX controls do not run within a protected container in the browser like the other types of HTML or Microsoft Silverlight-based controls. Disabling or not configuring this setting does not block prompts for ActiveX control installations and these prompts display to users. This could allow malicious code to become active on the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-42328SV-54946CCI-002460Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" to "Enabled" and 'pptview.exe' is checked.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" is set to "Enabled" and 'pptview.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ACTIVEXINSTALL + +Criteria: If the value pptview.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO600Macros must be blocked from running in Office 2013 files from the Internet. <VulnDiscussion>This policy setting allows you to block macros from running in Office files that come from the Internet. If you enable this policy setting, macros are blocked from running, even if "Enable all macros" is selected in the Macro Settings section of the Trust Center. Also, instead of having the choice to "Enable Content", users will receive a notification that macros are blocked from running. If the Office file is saved to a trusted location or was previously trusted by the user, macros will be allowed to run. If you disable or don't configure this policy setting, the settings configured in the Macro Settings section of the Trust Center determine whether macros run in Office files that come from the Internet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386V-72839SV-87491CCI-001170Set the policy value for User Configuration >> Administrative Templates >> Microsoft PowerPoint 2013 >> PowerPoint Options >> Security >> Trust Center "Block macros from running in Office files from the Internet" to "Enabled".Verify the policy value for User Configuration >> Administrative Templates >> Microsoft PowerPoint 2013 >> PowerPoint Options >> Security >> Trust Center "Block macros from running in Office files from the Internet" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\PowerPoint\security + +Criteria: If the value blockcontentexecutionfrominternet is REG_DWORD = 1, this is not a finding. +SRG-APP-000456<GroupDescription></GroupDescription>DTOO999-PP13The version of PowerPoint running on the system must be a supported version.<VulnDiscussion>Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. + +Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). + +This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. + +The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft PowerPoint 2013DISADPMS TargetMicrosoft PowerPoint 20135386CCI-002605Upgrade to a supported version.PowerPoint 2013 is no longer supported by the vendor. If the system is running PowerPoint 2013, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_MS_Project_2010_STIG_V1R10_Manual-xccdf.xml b/benchmarks/DISA/U_MS_Project_2010_STIG_V1R10_Manual-xccdf.xml new file mode 100644 index 000000000..332a5008f --- /dev/null +++ b/benchmarks/DISA/U_MS_Project_2010_STIG_V1R10_Manual-xccdf.xml @@ -0,0 +1,89 @@ +acceptedMicrosoft Project 2010 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 10 Benchmark Date: 24 Jul 20243.51.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000210<GroupDescription></GroupDescription>DTOO104Disabling of user name and password syntax from being used in URLs must be enforced.<VulnDiscussion>The Uniform Resource Locator (URL) standard allows user authentication to be included in URL strings in the form http://username:password@example.com. A malicious user might use this URL syntax to create a hyperlink that appears to open a legitimate website but actually opens a deceptive (spoofed) website. For example, the URL http://www.wingtiptoys.com@example.com appears to open http://www.wingtiptoys.com but actually opens http://example.com. To protect users from such attacks, Internet Explorer usually blocks any URLs using this syntax. + +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If user names and passwords in URLs are allowed, users could be diverted to dangerous web pages, which would pose a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-17173SV-53220CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Disable user name and password" is "Enabled" and a check in the 'winproj.exe' check box is present. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO111The Internet Explorer Bind to Object functionality must be enabled.<VulnDiscussion>Internet Explorer performs a number of safety checks before initializing an ActiveX control. It will not initialize a control if the kill bit for the control is set in the registry, or if the security settings for the zone in which the control is located do not allow it to be initialized. +This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). A security risk could occur if potentially dangerous controls are allowed to load.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-17174SV-53221CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Bind to Object" is "Enabled" and a check in the 'winproj.exe' check box is present. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SAFE_BINDTOOBJECT + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO117The Saved from URL mark must be selected to enforce Internet zone processing.<VulnDiscussion>Typically, when Internet Explorer loads a web page from a Universal Naming Convention (UNC) share that contains a Mark of the Web (MOTW) comment, indicating the page was saved from a site on the Internet, Internet Explorer runs the page in the Internet security zone instead of the less restrictive Local Intranet security zone. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer does not evaluate the page for a MOTW, potentially dangerous code could be allowed to run.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-17175SV-53222CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Saved from URL" is "Enabled" and a check in the 'winproj.exe' check box is present. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_UNC_SAVEDFILECHECK + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO123Navigation to URLs embedded in Office products must be blocked.<VulnDiscussion>To protect users from attacks, Internet Explorer usually does not attempt to load malformed URLs. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer attempts to load a malformed URL, a security risk could occur.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-17183SV-53223CCI-001170Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Navigate URL" is "Enabled" and a check in the 'winproj.exe' check box is present. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_VALIDATE_NAVIGATE_URL + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO124Scripted Window Security must be enforced.<VulnDiscussion>Malicious websites often try to confuse or trick users into giving a site permission to perform an action allowing the site to take control of the users' computers in some manner. Disabling or not configuring this setting allows unknown websites to: +-Create browser windows appearing to be from the local operating system. +-Draw active windows displaying outside of the viewable areas of the screen capturing keyboard input. +-Overlay parent windows with their own browser windows to hide important system information, choices, or prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-26588SV-53224CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" is set to "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO126Add-on Management functionality must be allowed.<VulnDiscussion>Internet Explorer add-ons are pieces of code, run in Internet Explorer, to provide additional functionality. Rogue add-ons may contain viruses or other malicious code. Disabling or not configuring this setting could allow malicious code or users to become active on user computers or the network. For example, a malicious user can monitor and then use keystrokes users type into Internet Explorer. Even legitimate add-ons may demand resources, compromising the performance of Internet Explorer, and the operating systems for user computers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-26584SV-53225CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Add-on Management" is set to "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ADDON_MANAGEMENT + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000131<GroupDescription></GroupDescription>DTOO127Add-ins to Office applications must be signed by a Trusted Publisher.<VulnDiscussion>Office 2013 applications do not check the digital signature on application add-ins before opening them. Disabling or not configuring this setting may allow an application to load a dangerous add-in. As a result, malicious code could become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-40888SV-53226CCI-001749Set the policy User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "Require that application add-ins are signed by Trusted Publisher" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "Require that application add-ins are signed by Trusted Publisher" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\software\policies\Microsoft\office\15.0\ms project\security + +Criteria: If the value requireaddinsig is REG_DWORD = 1, this is not a finding.SRG-APP-000207<GroupDescription></GroupDescription>DTOO129Links that invoke instances of Internet Explorer from within an Office product must be blocked.<VulnDiscussion>The Pop-up Blocker feature in Internet Explorer can be used to block most unwanted pop-up and pop-under windows from appearing. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If the Pop-up Blocker is disabled, disruptive and potentially dangerous pop-up windows could load and present a security risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-17184SV-53227CCI-001662Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Block popups" is "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000131<GroupDescription></GroupDescription>DTOO131Trust Bar Notifications for unsigned application add-ins must be blocked.<VulnDiscussion>If an application is configured to require all add-ins to be signed by a trusted publisher, any unsigned add-ins the application loads will be disabled and the application will display the Trust Bar at the top of the active window. The Trust Bar contains a message informing users about the unsigned add-in. If a user is allowed to make the determination to allow an unsigned add-in, it increases the risk of malicious code being introduced onto the user's computer or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-40889SV-53228CCI-001749Set the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "Disable Trust Bar Notification for unsigned application add-ins and block them" to "Enabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "Disable Trust Bar Notification for unsigned application add-ins and block them" is set to "Enabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\software\policies\Microsoft\office\15.0\ms project\security + +Criteria: If the value notbpromptunsignedaddin is REG_DWORD = 1, this is not a finding.SRG-APP-000209<GroupDescription></GroupDescription>DTOO132File Downloads must be configured for proper restrictions.<VulnDiscussion>Disabling this setting allows websites to present file download prompts via code without the user specifically initiating the download. User preferences may also allow the download to occur without prompting or interaction with the user. Even if Internet Explorer prompts the user to accept the download, some websites abuse this functionality. Malicious websites may continually prompt users to download a file or present confusing dialog boxes to trick users into downloading or running a file. If the download occurs and it contains malicious code, the code could become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-26587SV-53229CCI-001169Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict File Download" is set to "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_FILEDOWNLOAD + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000112<GroupDescription></GroupDescription>DTOO209Protection from zone elevation must be enforced. +<VulnDiscussion>Internet Explorer places restrictions on each web page users can use the browser to open. Web pages on a user's local computer have the fewest security restrictions and reside in the Local Machine zone, making this security zone a prime target for malicious users and code. Disabling or not configuring this setting could allow pages in the Internet zone to navigate to pages in the Local Machine zone to then run code to elevate privileges. This could allow malicious code or users to become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-26585SV-53230CCI-001695Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" is set to "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ZONE_ELEVATION + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000488<GroupDescription></GroupDescription>DTOO211ActiveX Installs must be configured for proper restriction.<VulnDiscussion>Microsoft ActiveX controls allow unmanaged, unprotected code to run on the user computers. ActiveX controls do not run within a protected container in the browser like the other types of HTML or Microsoft Silverlight-based controls. Disabling or not configuring this setting does not block prompts for ActiveX control installations and these prompts display to users. This could allow malicious code to become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-26586SV-53231CCI-002460Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" to "Enabled" and place a check in the 'winproj.exe' check box.Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2013 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" is set to "Enabled" and 'winproj.exe' is checked. + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ACTIVEXINSTALL + +Criteria: If the value winproj.exe is REG_DWORD = 1, this is not a finding.SRG-APP-000141<GroupDescription></GroupDescription>DTOO304Warning Bar settings for VBA macros must be configured.<VulnDiscussion>When users open files containing VBA macros, applications open the files with the macros disabled and displays the Trust Bar with a warning that macros are present and have been disabled. Users may then enable these macros by clicking Options on the Trust Bar and selecting the option to enable them. Disabling or not configuring this setting may allow dangerous macros to become active on user computers or the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-40890SV-53232CCI-000381Set the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "VBA Macro Notification Settings" must be set to "Enabled: Disable all with notification".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security -> Trust Center -> "VBA Macro Notification Settings" is set to "Enabled: Disable all with notification". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\software\policies\Microsoft\office\15.0\ms project\security + +Criteria: If the value vbawarnings is REG_DWORD = 2, this is not a finding.SRG-APP-000210<GroupDescription></GroupDescription>DTOO346Untrusted intranet zone access to Project servers must not be allowed.<VulnDiscussion>Enabling this setting allows users to access Project server websites and workspaces outside of the trusted Internet zone. As a result, malicious code could become active on user computers or the network to gain access to sensitive data. In this situation, the site could attempt to capture personal information, such as passwords and user names.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387V-40892SV-53234CCI-001170Set the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security "Enable untrusted intranet zone access to Project server" to "Disabled".Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Project 2013 -> Project Options -> Security "Enable untrusted intranet zone access to Project server" is set to "Disabled". + +Procedure: Use the Windows Registry Editor to navigate to the following key: + +HKCU\Software\Policies\Microsoft\Office\15.0\ms project\security + +Criteria: If the value TrustWSS is REG_DWORD = 0, this is not a finding.SRG-APP-000456<GroupDescription></GroupDescription>DTOO999-Project13The version of Microsoft Project running on the system must be a supported version.<VulnDiscussion>Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. + +Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). + +This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. + +The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Microsoft Project 2013DISADPMS TargetMicrosoft Project 20135387CCI-002605Upgrade to a supported version.Microsoft Project 2013 is no longer supported by the vendor. If the system is running Microsoft Project 2013, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_MS_Publisher_2010_STIG_V1R12_Manual-xccdf.xml b/benchmarks/DISA/U_MS_Publisher_2010_STIG_V1R12_Manual-xccdf.xml new file mode 100644 index 000000000..f2ad589ec --- /dev/null +++ b/benchmarks/DISA/U_MS_Publisher_2010_STIG_V1R12_Manual-xccdf.xml @@ -0,0 +1,110 @@ +acceptedMicrosoft Publisher 2010 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 12 Benchmark Date: 24 Jul 20243.51.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000033-DB-000084<GroupDescription></GroupDescription>SQL4-00-002000SQL Server must enforce approved authorizations for logical access to information and database-level system resources in accordance with applicable access control policies.<VulnDiscussion>Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access the database and all its contents. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems, including SQL Server databases, must be properly configured to implement access control policies. + +Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. + +Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. + +This requirement is applicable to access control enforcement applications, a category that includes SQL Server. If SQL Server is not configured to follow applicable policy when approving access, it may be in conflict with networks or other applications in the information system. This may result in users either gaining or being denied access inappropriately and in conflict with applicable policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81847V-67357CCI-000213Use GRANT, REVOKE, DENY, ALTER ROLE … ADD MEMBER … and/or ALTER ROLE …. DROP MEMBER statements to add and remove permissions on database-level securables, bringing them into line with the documented requirements.Review the system documentation to determine the required levels of protection for securables in the database, by type of user. + +Review the permissions actually in place in the database. + +The database permission functions and views provided in the supplemental file Permissions.sql can help with this. + +If the actual permissions do not match the documented requirements, this is a finding.SRG-APP-000089-DB-000064<GroupDescription></GroupDescription>SQL4-00-011200SQL Server must generate Trace or Audit records for organization-defined auditable events.<VulnDiscussion>Audit records can be generated from various components within the information system (e.g., network interface, hard disk, modem, etc.). From an application perspective, certain specific application functionalities may be audited as well. + +The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. Examples are auditable events, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. + +Organizations define which application components shall provide auditable events. + +The DBMS must provide auditing for the list of events defined by the organization or risk negatively impacting forensic investigations into malicious behavior in the information system. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81849V-67359CCI-000169Design and deploy a SQL Server Audit or Trace that captures all auditable events. + +The script provided in the supplemental file Trace.sql can be used to create a trace; edit it as necessary to capture any additional, locally-defined events. + +The script provided in the supplemental file Audit.sql can be used to create an audit; edit it as necessary to capture any additional, locally-defined events.If there are no locally-defined security tables or procedures, this is not applicable. + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should all be among those listed; if not, this is a finding. + +Any additional events locally defined should also be in the list; if not, this is a finding. + +14 -- Audit Login +15 -- Audit Logout +16 -- Attention +17 -- ExistingConnection +18 -- Audit Server Starts and Stops +20 -- Audit Login Failed +42 -- SP:Starting +43 -- SP:Completed +46 -- Object:Created +47 -- Object:Deleted +90 -- User-defined Event +102 -- Audit Database Scope GDR Event +103 -- Audit Object GDR Event +104 -- Audit AddLogin Event +105 -- Audit Login GDR Event +106 -- Audit Login Change Property Event +107 -- Audit Login Change Password Event +108 -- Audit Add Login to Server Role Event +109 -- Audit Add DB User Event +110 -- Audit Add Member to DB Role Event +111 -- Audit Add Role Event +112 -- Audit App Role Change Password Event +113 -- Audit Statement Permission Event +115 -- Audit Backup/Restore Event +116 -- Audit DBCC Event +117 -- Audit Change Audit Event +118 -- Audit Object Derived Permission Event +128 -- Audit Database Management Event +129 -- Audit Database Object Management Event +130 -- Audit Database Principal Management Event +131 -- Audit Schema Object Management Event +132 -- Audit Server Principal Impersonation Event +133 -- Audit Database Principal Impersonation Event +134 -- Audit Server Object Take Ownership Event +135 -- Audit Database Object Take Ownership Event +152 -- Audit Change Database Owner +153 -- Audit Schema Object Take Ownership Event +162 -- User error message +164 -- Object:Altered +170 -- Audit Server Scope GDR Event +171 -- Audit Server Object GDR Event +172 -- Audit Database Object GDR Event +173 -- Audit Server Operation Event +175 -- Audit Server Alter Trace Event +176 -- Audit Server Object Management Event +177 -- Audit Server Principal Management Event +178 -- Audit Database Operation Event +180 -- Audit Database Object Access Event + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses broad, server-level audit action groups for this purpose. SQL Server Audit's flexibility makes other techniques possible. + +If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following code to verify that all configuration-related actions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>'); +GO + +Examine the list produced by the query. + +If the audited_result column is not "SUCCESS AND FAILURE" on every row, this is a finding. + +If any of the following audit action groups is not included in the list, this is a finding. + +APPLICATION_ROLE_CHANGE_PASSWORD_GROUP +AUDIT_CHANGE_GROUP +BACKUP_RESTORE_GROUP +DATABASE_CHANGE_GROUP +DATABASE_OBJECT_ACCESS_GROUP +DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP +DATABASE_OBJECT_PERMISSION_CHANGE_GROUP +DATABASE_OPERATION_GROUP +DATABASE_OWNERSHIP_CHANGE_GROUP +DATABASE_PERMISSION_CHANGE_GROUP +DATABASE_PRINCIPAL_CHANGE_GROUP +DATABASE_PRINCIPAL_IMPERSONATION_GROUP +DATABASE_ROLE_MEMBER_CHANGE_GROUP +DBCC_GROUP +FAILED_LOGIN_GROUP +LOGIN_CHANGE_PASSWORD_GROUP +LOGOUT_GROUP +SCHEMA_OBJECT_ACCESS_GROUP +SCHEMA_OBJECT_CHANGE_GROUP +SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP +SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP +SERVER_OBJECT_CHANGE_GROUP +SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP +SERVER_OBJECT_PERMISSION_CHANGE_GROUP +SERVER_OPERATION_GROUP +SERVER_PERMISSION_CHANGE_GROUP +SERVER_PRINCIPAL_CHANGE_GROUP +SERVER_PRINCIPAL_IMPERSONATION_GROUP +SERVER_ROLE_MEMBER_CHANGE_GROUP +SERVER_STATE_CHANGE_GROUP +SUCCESSFUL_LOGIN_GROUP +TRACE_CHANGE_GROUPSRG-APP-000090-DB-000065<GroupDescription></GroupDescription>SQL4-00-011320Where SQL Server Audit is in use at the database level, SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited at the database level.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. + +Suppression of auditing could permit an adversary to evade detection. + +Misconfigured audits can degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +This version of the requirement deals with SQL Server Audit-based audit trails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81851V-67361CCI-000171Create a database role specifically for audit maintainers, and give it permission to maintain audits, without granting it unnecessary permissions: +USE <database name>; +GO +CREATE ROLE DATABASE_AUDIT_MAINTAINERS; +GO +GRANT ALTER ANY DATABASE AUDIT TO DATABASE_AUDIT_MAINTAINERS; +GO +(The role name used here is an example; other names may be used.) + +Use REVOKE and/or DENY and/or ALTER ROLE ... DROP MEMBER ... statements to remove the ALTER ANY DATABASE AUDIT permission from all users. + +Then, for each authorized database user, run the statement: +ALTER ROLE DATABASE_AUDIT_MAINTAINERS ADD MEMBER <user name> ; +GO + +Use REVOKE and/or DENY and/or ALTER SERVER ROLE ... DROP MEMBER ... statements to remove CONTROL DATABASE permission from logins that do not need it.If SQL Server Audit is not in use at the database level, this is not applicable (NA). + +Obtain the list of approved audit maintainers from the system documentation. + +Review the database roles and individual users that have the following permissions, both of which enable the ability to maintain audit definitions: +ALTER ANY DATABASE AUDIT +CONTROL ON DATABASE + +The functions and views provided in the supplemental file Permissions.sql can assist in this review. In the following, "STIG" stands for the schema where you have deployed these views and functions. To see which logins and server roles have been granted these permissions: + SELECT + * + FROM + STIG.database_permissions P + WHERE + (P.[Permission] = 'ALTER ANY DATABASE AUDIT') + OR + (P.[Permission] = 'CONTROL' AND P.[Securable Type or Class] = 'DATABASE') + ; + +To see what users and database roles inherit these permissions from the database roles reported by the previous query, repeat the following for each one: + SELECT * FROM STIG.members_of_database_role(<database role name>); + +To see all the permissions in effect for a database principal (server role or login): + SELECT * FROM STIG.server_effective_permissions(<principal name>); + +If designated personnel are not able to configure auditable events, this is a finding. + +If unapproved personnel are able to configure auditable events, this is a finding.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL4-00-014900SQL Server must be monitored to discover unauthorized changes to functions.<VulnDiscussion>When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of SQL Server and/or application can potentially have significant effects on the overall security of the system. + +If SQL Server were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement is contingent upon the language in which the application is programmed, as many application architectures in use today incorporate their software libraries into, and make them inseparable from, their compiled distributions, rendering them static and version-dependent. However, this requirement does apply to applications with software libraries accessible and configurable, as in the case of interpreted languages. + +Accordingly, only qualified and authorized individuals shall be allowed to obtain access to SQL Server components for purposes of initiating changes, including upgrades and modifications. + +Unmanaged changes that occur to the SQL Server software libraries or configuration, such as Functions, can lead to unauthorized or compromised installations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81855V-67365CCI-001499Configure a SQL Server timed job that automatically checks all system and user-defined Functions for being modified. + +(The supplemental file Track.sql, provided with this STIG, can be used to establish a monitoring job. This should be supplemented with a process for informing the appropriate personnel. Other techniques for achieving the same ends, such as the use of DDL triggers, are acceptable.)Check the SQL Server configuration for a timed job that automatically checks all system and user-defined Functions for being modified by running the following SQL Server query: +EXEC msdb.dbo.sp_help_job @job_name = '<enter . . . job name>'; + +(Alternatively, in SQL Server Management Studio, navigate to SQL Server Agent and examine the job from there.) + +If a timed job or some other method is not implemented to check for Functions being modified, this is a finding.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL4-00-015100SQL Server must be monitored to discover unauthorized changes to triggers.<VulnDiscussion>When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of SQL Server and/or application can potentially have significant effects on the overall security of the system. + +If SQL Server were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement is contingent upon the language in which the application is programmed, as many application architectures in use today incorporate their software libraries into, and make them inseparable from, their compiled distributions, rendering them static and version-dependent. However, this requirement does apply to applications with software libraries accessible and configurable, as in the case of interpreted languages. + +Accordingly, only qualified and authorized individuals shall be allowed to obtain access to SQL Server components for purposes of initiating changes, including upgrades and modifications. + +Unmanaged changes that occur to the SQL Server software libraries or configuration, such as Triggers, can lead to unauthorized or compromised installations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81857V-67367CCI-001499Configure a SQL Server timed job that automatically checks all system and user-defined Triggers for modification. + +(The supplemental file Track.sql, provided with this STIG, can be used to establish a monitoring job. This should be supplemented with a process for informing the appropriate personnel. Other techniques for achieving the same ends, such as the use of DDL triggers, are acceptable.)Check the SQL Server configuration for the timed job that automatically checks all system and user-defined Triggers for being modified by running the following SQL Server query: +EXEC msdb.dbo.sp_help_job @job_name = '<enter . . . job name>'; + +(Alternatively, in SQL Server Management Studio, navigate to SQL Server Agent and examine the job from there.) + +If such a job, or an alternative method of monitoring triggers for modification, does not exist, this is a findingSRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL4-00-015200SQL Server must be monitored to discover unauthorized changes to stored procedures.<VulnDiscussion>When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of SQL Server and/or application can potentially have significant effects on the overall security of the system. + +If SQL Server were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement is contingent upon the language in which the application is programmed, as many application architectures in use today incorporate their software libraries into, and make them inseparable from, their compiled distributions, rendering them static and version-dependent. However, this requirement does apply to applications with software libraries accessible and configurable, as in the case of interpreted languages. + +Accordingly, only qualified and authorized individuals shall be allowed to obtain access to SQL Server components for purposes of initiating changes, including upgrades and modifications. + +Unmanaged changes that occur to the SQL Server software libraries or configuration, such as Stored Procedures, can lead to unauthorized or compromised installations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81859V-67369CCI-001499Configure a SQL Server timed job that automatically checks all system and user-defined Stored Procedures for modification. + +(The supplemental file Track.sql, provided with this STIG, can be used to establish a monitoring job. This should be supplemented with a process for informing the appropriate personnel. Other techniques for achieving the same ends, such as the use of DDL triggers, are acceptable.)Check for the existence of a job to monitor for changes to stored procedures: +EXEC msdb.dbo.sp_help_job @job_name = '<enter . . . job name>'; + +(Alternatively, in SQL Server Management Studio, navigate to SQL Server Agent and examine the job from there.) + +If such a job, or an alternative method of monitoring stored procedures for modification, does not exist, this is a finding.SRG-APP-000133-DB-000200<GroupDescription></GroupDescription>SQL4-00-015600Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to SQL Server, etc.) must be owned by database/DBMS principals authorized for ownership.<VulnDiscussion>Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. + +Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81861V-67371CCI-001499Add and/or update system documentation to include any accounts authorized for object ownership and remove any account not authorized. + +To change the schema owning a database object in SQL Server, use this code: +USE <database name>; +GO +ALTER SCHEMA <name of new schema> TRANSFER <name of old schema>.<object name>; +GO + +Caution: this can break code. This Fix should be implemented in conjunction with corrections to such code. Test before deploying in production. Deploy during a scheduled maintenance window.Review system documentation to identify SQL Server accounts authorized to own database objects. + +If the SQL Server database ownership list does not exist or needs to be updated, this is a finding. + +The view STIG.database_permissions, included in the supplemental file, Permissions.sql, can be of use in making this determination: +USE <database name>; +GO +SELECT DISTINCT + S.[Schema/Owner] AS [Owner], + O.[Schema/Owner] AS [Schema], + O.[Securable] +FROM + STIG.database_permissions O + INNER JOIN STIG.database_permissions S + ON S.[Securable] = O.[Schema/Owner] + AND O.[Securable Type or Class] = 'OBJECT_OR_COLUMN' + AND S.[Securable Type or Class] = 'SCHEMA' +WHERE + S.[Schema/Owner] NOT IN ('dbo', 'sys', 'INFORMATION_SCHEMA' ... ) + -- Complete the "NOT IN" list with the names of user accounts authorized for ownership. +; +If any of the listed owners is not authorized, this is a finding.SRG-APP-000133-DB-000200<GroupDescription></GroupDescription>SQL4-00-015610In a database owned by [sa], or by any other login having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF.<VulnDiscussion>SQL Server's fixed (built-in) server roles, especially [sysadmin], have powerful capabilities that could cause great harm if misused, so their use must be tightly controlled. + +The SQL Server instance uses each database's TRUSTWORTHY property to guard against tampering that could enable unwarranted privilege escalation. When TRUSTWORTHY is 0/False/Off, SQL Server prevents the database from accessing resources in other databases. When TRUSTWORTHY is 1/True/On, SQL Server permits access to other databases (subject to other protections). SQL Server sets TRUSTWORTHY OFF when it creates a new database. SQL Server forces TRUSTWORTHY OFF, irrespective of its prior value, when an existing database is attached to it, to address the possibility that an adversary may have tampered with the database, introducing malicious code. To set TRUSTWORTHY ON, an account with the [sysadmin] role must issue an ALTER DATABASE command. + +Although SQL Server itself treats this property conservatively, application installer programs may set TRUSTWORTHY ON and leave it on. This provides an opportunity for misuse. + +When TRUSTWORTHY is ON, users of the database can take advantage of the database owner's privileges, by impersonating the owner. This can have particularly serious consequences if the database owner is the [sa] login (which may have been renamed in accordance with SQL4-00-010200, and disabled in accordance with SQL4-00-017100, but nonetheless can be invoked in an EXECUTE AS USER = 'dbo' statement, or CREATE PROCEDURE ... WITH EXECUTE AS OWNER ...). The [sa] login cannot be removed from the [sysadmin] role. The user impersonating [sa] - or another [sysadmin] account - is then able to perform administrative actions across all databases under the instance, including making any himself or any other login a member of [sysadmin]. + +Most of the other fixed server roles could be similarly abused. + +Therefore, TRUSTWORTHY must not be used on databases owned by logins that are members of the fixed server roles. Further, if TRUSTWORTHY is to be used for any other database, the need must be documented and approved. + +The system database [msdb] is an exception: it is required to be TRUSTWORTHY.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81865V-67375CCI-001499Set the TRUSTWORTHY property OFF; or remove the database owner from the fixed server role(s); or change the database owner. + +To set the TRUSTWORTHY property OFF: +USE [master]; +GO +ALTER DATABASE <name> SET TRUSTWORTHY OFF; +GO +Verify that this produced the intended result by re-running the query specified in the Check. + +To determine the path or paths by which the database owner is assigned the fixed server role or roles, run this query: + +USE <database name>; +GO +WITH C AS +( +SELECT + P.name AS [Parent Server Role], + CAST('Fixed' AS varchar(8)) + AS [Server Role Type], + M.name AS [Member], + M.type_desc AS [Member Type], + P.name AS [Root], + 1 AS [Level] +FROM + [sys].[server_role_members] X + INNER JOIN [sys].[server_principals] P ON P.principal_id = X.role_principal_id + INNER JOIN [sys].[server_principals] M ON M.principal_id = X.member_principal_id +WHERE + P.is_fixed_role = 1 +UNION ALL +SELECT + P.name AS [Parent Server Role], + CASE WHEN M.is_fixed_role = 1 THEN CAST('Fixed' AS varchar(8)) ELSE CAST('Custom' AS varchar(8)) END + AS [Server Role Type], + M.name AS [Member], + M.type_desc AS [Member Type], + C.[Root] AS [Root], + C.[Level] + 1 AS [Level] +FROM + [sys].[server_role_members] X + INNER JOIN [sys].[server_principals] P ON P.principal_id = X.role_principal_id + INNER JOIN [sys].[server_principals] M ON M.principal_id = X.member_principal_id + INNER JOIN C ON P.name = C.Member +) +, +B AS +( +SELECT + C.[Member] AS [Leaf], + C.[Root], + C.[Parent Server Role], + C.[Server Role Type], + C.[Member], + C.[Member Type], + C.[Level] +FROM C +WHERE + C.[Member Type] NOT LIKE '%ROLE%' +UNION ALL +SELECT + B.[Leaf], + C.[Root], + C.[Parent Server Role], + C.[Server Role Type], + C.[Member], + C.[Member Type], + C.[Level] +FROM C +INNER JOIN B + ON C.[Member] = B.[Parent Server Role] + AND C.[Level] = B.[Level] - 1 + AND C.[Root] = B.[Root] +) +SELECT + DB_NAME() AS [Database], + B.[Leaf] AS [Owner Login], + B.[Root] AS[Top-Level Server Role], + B.[Parent Server Role], + B.[Server Role Type], + B.[Member], + B.[Member Type], + B.[Level] +FROM B +WHERE B.[Leaf] = (SELECT SUSER_SNAME(D.owner_sid) FROM sys.databases D WHERE D.Name = DB_NAME()) +ORDER BY B.[Root], B.[Level], B.[Parent Server Role], B.[Member] +; +GO + +To remove the database owner from a fixed server role or a custom server role: +USE [master]; +GO +ALTER SERVER ROLE <fixed/custom server role name> + DROP MEMBER <database owner name>; +GO +Verify that this produced the intended result by re-running the Check query. + +To change the database owner: +USE [master]; +GO +ALTER AUTHORIZATION ON DATABASE::<DB name> TO <new owner name>; +GO +Verify that this produced the intended result by re-running the Check query.Run the SQL statements: +USE <database name>; +GO +WITH FixedServerRoles(RoleName) AS +( + SELECT 'sysadmin' + UNION SELECT 'securityadmin' + UNION SELECT 'serveradmin' + UNION SELECT 'setupadmin' + UNION SELECT 'processadmin' + UNION SELECT 'diskadmin' + UNION SELECT 'dbcreator' + UNION SELECT 'bulkadmin' +) +SELECT + DB_NAME() AS [Database], + SUSER_SNAME(D.owner_sid) AS [Database Owner], + F.RoleName AS [Fixed Server Role], + CASE WHEN D.is_trustworthy_on = 1 THEN 'ON' ELSE 'off' END + AS [Trustworthy] +FROM + FixedServerRoles F + INNER JOIN sys.databases D ON D.Name = DB_NAME() +WHERE + IS_SRVROLEMEMBER(F.RoleName, SUSER_SNAME(D.owner_sid)) = 1 +AND DB_NAME() <> 'msdb' +AND D.is_trustworthy_on = 1; +GO + +If the query returns any rows, this is a finding.SRG-APP-000133-DB-000200<GroupDescription></GroupDescription>SQL4-00-015620In a database owned by a login not having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF unless required and authorized.<VulnDiscussion>SQL Server's fixed (built-in) server roles, especially [sysadmin], have powerful capabilities that could cause great harm if misused, so their use must be tightly controlled. + +The SQL Server instance uses each database's TRUSTWORTHY property to guard against tampering that could enable unwarranted privilege escalation. When TRUSTWORTHY is 0/False/Off, SQL Server prevents the database from accessing resources in other databases. When TRUSTWORTHY is 1/True/On, SQL Server permits access to other databases (subject to other protections). SQL Server sets TRUSTWORTHY OFF when it creates a new database. SQL Server forces TRUSTWORTHY OFF, irrespective of its prior value, when an existing database is attached to it, to address the possibility that an adversary may have tampered with the database, introducing malicious code. To set TRUSTWORTHY ON, an account with the [sysadmin] role must issue an ALTER DATABASE command. + +Although SQL Server itself treats this property conservatively, application installer programs may set TRUSTWORTHY ON and leave it on. This provides an opportunity for misuse. + +When TRUSTWORTHY is ON, users of the database can take advantage of the database owner's privileges, by impersonating the owner. This can have particularly serious consequences if the database owner is the [sa] login (which may have been renamed in accordance with SQL4-00-010200, and disabled in accordance with SQL4-00-017100, but nonetheless can be invoked in an EXECUTE AS USER = 'dbo' statement, or CREATE PROCEDURE ... WITH EXECUTE AS OWNER ...). The [sa] login cannot be removed from the [sysadmin] role. The user impersonating [sa] - or another [sysadmin] account - is then able to perform administrative actions across all databases under the instance, including making any himself or any other login a member of [sysadmin]. + +Most of the other fixed server roles could be similarly abused. + +Therefore, TRUSTWORTHY must not be used on databases owned by logins that are members of the fixed server roles. Further, if TRUSTWORTHY is to be used for any other database, the need must be documented and approved. + +The system database [msdb] is an exception: it is required to be TRUSTWORTHY.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81863V-67373CCI-001499Run the SQL statements: +USE [master]; +GO +ALTER DATABASE <name> SET TRUSTWORTHY OFF; +GOIf the database is owned by an account that is directly or indirectly a member of a fixed (built-in) server role, this is not applicable (NA). + +Run the query: +USE <database name>; +GO +SELECT +DB_NAME() AS [Database], +SUSER_SNAME(D.owner_sid) AS [Database Owner], +CASE WHEN D.is_trustworthy_on = 1 THEN 'ON' ELSE 'off' END +AS [Trustworthy] +FROM +sys.databases D +WHERE +D.[name] = DB_NAME() +AND DB_NAME() <> 'msdb' +AND D.is_trustworthy_on = 1; +GO +If the query returns a row indicating that the TRUSTWORTHY setting is OFF, or returns no rows, this is not a finding. + +Review the system security plan to determine whether the need for TRUSTWORTHY is documented and approved. If not, this is a finding.SRG-APP-000226-DB-000147<GroupDescription></GroupDescription>SQL4-00-021210In the event of a system failure, SQL Server must preserve any information necessary to return to operations with least disruption to mission processes.<VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. The existence and reliability of database backups is an essential aspect of the ability to fail to a known state. It helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. + +Backups must be performed according to an appropriate schedule, and must be tested periodically to provide assurance that they can be used for restoring the database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81867V-67377CCI-001665Modify the system security plan, to include whether the database is static, the correct recovery model to be used, the backup schedule, and the plan for testing database restoration. + +In SQL Server Management Studio, Object Explorer, right-click on the name of the database; select Properties. Select the Options page. Set the Recovery Model field, near the top of the page, to the correct value. + +In Object Explorer, expand <server name> >> SQL Server Agent >> Jobs. Create, modify and delete jobs to implement the backup schedule. (Alternatively, this may done using T-SQL code.) + +Correct any issues that have been causing backups to fail. + +Test the restoration of the database at least once a year; correct any issues that cause it to fail. Maintain a record of these tests.Review the system security plan (SSP) to determine whether the database is static, the recovery model to be used, the backup schedule, and the plan for testing database restoration. If the SSP does not state that the database is static, assume that it is not static. If any of the other information is absent, this is a finding. + +If the database is not static, but the documented recovery model is Simple, this is a finding. + +If the database is not static, and the documented recovery model is Bulk Logged, but the justification and authorization for this are not documented, this is a finding. + +In SQL Server Management Studio, Object Explorer, right-click on the name of the database; select Properties. Select the Options page. + +Observe the Recovery Model field, near the top of the page. If this does not match the documented recovery model, this is a finding. + +In Object Explorer, expand <server name> >> SQL Server Agent >> Jobs. + +Review the jobs set up to implement the backup plan. If they are absent, this is a finding. + +Right-click on each backup job; select View History. If the history indicates a pattern of job failures, this is a finding. + +Review evidence that database recovery is tested annually or more often, and that the most recent test was successful. If not, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL4-00-021300SQL Server must protect data at rest and ensure confidentiality and integrity of data.<VulnDiscussion>This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. + +User-generated data, as well as, application-specific configuration data, needs to be protected. Configurations and/or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content are examples of system information likely requiring protection. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. + +If the confidentiality and integrity of SQL Server data is not protected, the data will be open to compromise and unauthorized modification. + +Protective measures include encryption, physical security of the facility where the storage devices reside, operating system file permissions, and organizational controls. Each of these should be applied as necessary and appropriate.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-82367V-67877CCI-001199Apply appropriate controls to protect the confidentiality and integrity of data on a secondary device. + +Where encryption is required, this can be done by full-disk encryption or by database encryption. To enable database encryption, create a master key, create a database encryption key, and protect it by using mechanisms tied to the master key, and then set encryption on. + +Implement physical security measures, operating system access control lists and organizational controls appropriate to the sensitivity level of the data in the database(s).If the application owner and Authorizing Official have determined that encryption of data at rest is NOT required, this is not a finding. + +If the application owner and Authorizing Official have determined that encryption of data at rest is required, ensure the data on secondary devices is encrypted. + +If full-disk encryption is being used, this is not a finding. + +If DBMS data encryption is required, ensure the data is encrypted before being put on the secondary device by executing: + +SELECT + d.name AS [Database Name], + CASE e.encryption_state + WHEN 0 THEN 'No database encryption key present, no encryption' + WHEN 1 THEN 'Unencrypted' + WHEN 2 THEN 'Encryption in progress' + WHEN 3 THEN 'Encrypted' + WHEN 4 THEN 'Key change in progress' + WHEN 5 THEN 'Decryption in progress' + WHEN 6 THEN 'Protection change in progress' + END AS [Encryption State] +FROM sys.dm_database_encryption_keys e +RIGHT JOIN sys.databases d ON DB_NAME(e.database_id) = d.name +WHERE d.name NOT IN ('master','model','msdb') +ORDER BY 1 +; + +For each user database where encryption is required, verify that encryption is in effect. If not, this is a finding. + +Verify that there are physical security measures, operating system access control lists and organizational controls appropriate to the sensitivity level of the data in the database(s). If not, this is a finding.SRG-APP-000243-DB-000128<GroupDescription></GroupDescription>SQL4-00-021800Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.<VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse. + +Data used for the development and testing of applications often involves copying data from production. It is important that specific procedures exist for this process, so copies of sensitive data are not misplaced or left in a temporary location without the proper controls.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81879V-67389CCI-001090Create and document a process for moving data from production to development/test systems and follow the process. + +Modify any code used for moving data from production to development/test systems to ensure copies of production data are not left in unsecured locations.Verify there are proper procedures in place for the transfer of development/test data from production. Review any scripts or code that exists for the movement of production data to development/test and verify copies of production data are not left in unprotected locations. + +If there is no documented procedure for data movement from production to development/test, this is a finding. + +If data movement code that copies from production to development/test does exist and leaves any copies of production data in unprotected locations, this is a finding.SRG-APP-000251-DB-000160<GroupDescription></GroupDescription>SQL4-00-022500SQL Server must check the validity of all data inputs except those specifically identified by the organization.<VulnDiscussion>Invalid user input occurs when a user inserts data or characters into an application’s data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior potentially leading to an application or information system compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. + +SQL Server needs to validate the data user’s attempt to input to the application for processing. Rules for checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, acceptable values) are in place to verify inputs match specified definitions for format and content. Inputs passed to interpreters are prescreened to prevent the content from being unintentionally interpreted as commands. + +A poorly designed database system can have many problems. A common issue with these types of systems is the missed opportunity to use constraints. + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81881V-67391CCI-001310Use triggers, constraints, foreign keys, etc. to validate data input. + +Modify SQL Server to properly use the correct column data types as required in the database.Review DBMS code (stored procedures, functions, triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input. + +If code exists that allows invalid data to be acted upon or input into the database, this is a finding. + +If column/field definitions are not reflective of the data, this is a finding. + +If columns/fields do not contain constraints and validity checking where required, this is a finding. + +Where a column/field is noted in the system documentation as necessarily free-form, even though its name and context suggest that it should be strongly typed and constrained, the absence of these protections is not a finding. + +Where a column/field is clearly identified by name, caption or context as Notes, Comments, Description, Text, etc., the absence of these protections is not a finding.SRG-APP-000266-DB-000162<GroupDescription></GroupDescription>SQL4-00-022800The DBMS and associated applications must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.<VulnDiscussion>Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organization and development team. + +Databases can inadvertently provide a wealth of information to an attacker through improperly handled error messages. In addition to sensitive business or personal information, database errors can provide host names, IP addresses, user names, and other system information not required for end-user troubleshooting but very useful to someone targeting the system. + +Carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. + +It is important that detailed error messages be visible only to those who are authorized to view them; that general users receive only generalized acknowledgment that errors have occurred; and that these generalized messages appear only when relevant to the user's task. For example, a message along the lines of, "An error has occurred. Unable to save your changes. If this problem persists, please contact your help desk" would be relevant. A message such as "Warning: your transaction generated a large number of page splits" would likely not be relevant. "ABGQ is not a valid widget code" would be appropriate; but "The INSERT statement conflicted with the FOREIGN KEY constraint "WidgetTransactionFK". The conflict occurred in database "DB7", table "dbo.WidgetMaster", column 'WidgetCode'" would not, as it reveals too much about the database structure. + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81887V-67397CCI-001312Configure DBMS settings, custom database code, and associated application code not to divulge sensitive information or information useful for system identification in error messages that are displayed to general users.Review application behavior and custom database code (stored procedures; triggers), to determine whether error messages contain information beyond what is needed for explaining the issue to general users. + +If database error messages contain PII data, sensitive business data, or information useful for identifying the host system or database structure, this is a finding.SRG-APP-000267-DB-000163<GroupDescription></GroupDescription>SQL4-00-022900SQL Server must reveal detailed error messages only to the ISSO, ISSM (or their designees), SA and DBA.<VulnDiscussion>If the DBMS provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. + +Some default DBMS error messages can contain information that could aid an attacker in, among others things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. + +It is important that detailed error messages be visible only to those who are authorized to view them; that general users receive only generalized acknowledgment that errors have occurred; and that these generalized messages appear only when relevant to the user's task. For example, a message along the lines of, "An error has occurred. Unable to save your changes. If this problem persists, please contact your help desk" would be relevant. A message such as "Warning: your transaction generated a large number of page splits" would likely not be relevant. "ABGQ is not a valid widget code" would be appropriate; but "The INSERT statement conflicted with the FOREIGN KEY constraint "WidgetTransactionFK". The conflict occurred in database "DB7", table "dbo.WidgetMaster", column 'WidgetCode'" would not, as it reveals too much about the database structure. + +Administrative users authorized to review detailed error messages typically are the ISSO, ISSM, SA and DBA. Other individuals or roles may be specified according to organization-specific needs, with appropriate approval. + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81889V-67399CCI-001314Configure audit logging, tracing and/or custom code in the database or application to record detailed error messages generated by SQL Server, for review by authorized personnel.Review application behavior, custom database code (stored procedures; triggers) and DBMS audit and trace settings, to determine whether detailed error messages are logged or stored for review by authorized personnel. + +If detailed error messages are not available to individuals authorized to view them, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL4-00-024100The Database Master Key must be encrypted by the Service Master Key, where a Database Master Key is required and another encryption method has not been specified.<VulnDiscussion>When not encrypted by the Service Master Key, system administrators or application administrators may access and use the Database Master Key to view sensitive data that they are not authorized to view. Where alternate encryption means are not feasible, encryption by the Service Master Key may be necessary. To help protect sensitive data from unauthorized access by DBAs, mitigations may be in order. Mitigations may include automatic alerts or other audit events when the Database Master Key is accessed outside of the application or by a DBA account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81871V-67381CCI-001199Where possible, encrypt the Database Master Key with a password known only to the application administrator. Where not possible, configure additional audit events or alerts to detect unauthorized access to the Database Master Key by users not authorized to view sensitive data.If no databases require encryption, this is not a finding. + +From the query prompt: +SELECT name +FROM [master].sys.databases +WHERE is_master_key_encrypted_by_server = 1 +AND owner_sid <> 1 +AND state = 0; +(Note that this query assumes that the [sa] account is not used as the owner of application databases, in keeping with other STIG guidance. If this is not the case, modify the query accordingly.) + +If no databases are returned by the query, this is not a finding. + +For any databases returned, verify in the System Security Plan that encryption of the Database Master Key using the Service Master Key is acceptable and approved by the Information Owner, and the encrypted data does not require additional protections to deter or detect DBA access. If not approved, this is a finding. + +If approved and additional protections are required, then verify the additional requirements are in place in accordance with the System Security Plan. These may include additional auditing on access of the Database Master Key with alerts or other automated monitoring. + +If the additional requirements are not in place, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL4-00-024200Database Master Key passwords must not be stored in credentials within the database.<VulnDiscussion>Storage of the Database Master Key password in a database credential allows decryption of sensitive data by privileged users who may not have a need-to-know requirement to access the data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81873V-67383CCI-001199Use the stored procedure sp_control_dbmasterkey_password to remove any credentials that +store Database Master Key passwords. +From the query prompt: +EXEC SP_CONTROL_DBMASTERKEY_PASSWORD @db_name = '<database name>', @action += N'drop'From the query prompt: +SELECT COUNT(credential_id) +FROM [master].sys.master_key_passwords + +If count is not 0, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL4-00-024300Symmetric keys (other than the database master key) must use a DoD certificate to encrypt the key.<VulnDiscussion>Data within the database is protected by use of encryption. The symmetric keys are critical for this process. If the symmetric keys were to be compromised the data could be disclosed to unauthorized personnel. + +The database master key is exempt, as a password must be supplied when creating it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81875V-67385CCI-001199Configure or alter symmetric keys to encrypt keys with certificates or authorized asymmetric keys. +In a query tool: + ALTER SYMMETRIC KEY <key name> ADD ENCRYPTION BY CERTIFICATE <certificate name>; + ALTER SYMMETRIC KEY <key name> DROP ENCRYPTION BY <password, symmetric key or asymmetric key>; + +The symmetric key must specify a certificate or asymmetric key for encryption.In a query tool: +USE <database name>; +GO +SELECT s.name, k.crypt_type_desc +FROM sys.symmetric_keys s, sys.key_encryptions k +WHERE s.symmetric_key_id = k.key_id +AND s.name <> '##MS_DatabaseMasterKey##' +AND k.crypt_type IN ('ESKP', 'ESKS') +ORDER BY s.name, k.crypt_type_desc; +GO + +Review any symmetric keys that have been defined against the System Security Plan. + +If any keys are defined that are not documented in the System Security Plan, this is a finding. + +Review the System Security Plan to review the encryption mechanism specified for each symmetric key. If the method does not indicate use of certificates, this is a finding. + +If the certificate specified is not a DoD PKI certificate, this is a finding.SRG-APP-000251-DB-000391<GroupDescription></GroupDescription>SQL4-00-031500The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.<VulnDiscussion>With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. + +The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81883V-67393CCI-001310Where dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, modify the code to do so.Review source code in the database (stored procedures, functions, triggers) and application source code, to identify cases of dynamic code execution. + +If dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, this is a finding.SRG-APP-000251-DB-000392<GroupDescription></GroupDescription>SQL4-00-031600The DBMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.<VulnDiscussion>With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. + +The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). + +When dynamic execution is necessary, ways to mitigate the risk include the following, which should be implemented both in the on-screen application and at the database level, in the stored procedures: +-- Allow strings as input only when necessary. +-- Rely on data typing to validate numbers, dates, etc. Do not accept invalid values. If substituting other values for them, think carefully about whether this could be subverted. +-- Limit the size of input strings to what is truly necessary. +-- If single quotes/apostrophes, double quotes, semicolons, equals signs, angle brackets, or square brackets will never be valid as input, reject them. +-- If comment markers will never be valid as input, reject them. In SQL, these are -- or /* */ +-- If HTML and XML tags, entities, comments, etc., will never be valid, reject them. +-- If wildcards are present, reject them unless truly necessary. In SQL these are the underscore and the percentage sign, and the word ESCAPE is also a clue that wildcards are in use. +-- If SQL key words, such as SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, ESCAPE, UNION, GRANT, REVOKE, DENY, MODIFY will never be valid, reject them. Use case-insensitive comparisons when searching for these. Bear in mind that some of these words, particularly Grant (as a person's name), could also be valid input. +-- If there are range limits on the values that may be entered, enforce those limits. +-- Institute procedures for inspection of programs for correct use of dynamic coding, by a party other than the developer. +-- Conduct rigorous testing of program modules that use dynamic coding, searching for ways to subvert the intended use. +-- Record the inspection and testing in the system documentation. +-- Bear in mind that all this applies not only to screen input, but also to the values in an incoming message to a web service or to a stored procedure called by a software component that has not itself been hardened in these ways. Not only can the caller be subject to such vulnerabilities; it may itself be the attacker. + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81885V-67395CCI-001310Where dynamic code execution is used, modify the code to implement protections against code injection.Review source code in the database (stored procedures, functions, triggers) and application source code to identify cases of dynamic code execution. + +If dynamic code execution is employed without protective measures against code injection, this is a finding.SRG-APP-000311-DB-000308<GroupDescription></GroupDescription>SQL4-00-031900When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in storage.<VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. + +Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. + +These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. + +One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. + + +SQL Server does not include security labeling as a standard or licensable feature. Earlier releases of this STIG suggested using the SQL Server Label Security Toolkit, from codeplex.com. However, codeplex.com has been shut down, and it is unclear whether the Toolkit is still supported. If the organization does have access to the Toolkit, it may still be used, provided the organization accepts responsibility for its support. Other implementations may also exist. Custom application code is also a viable way to implement a solution.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81891V-67401CCI-002262Develop SQL or application code or acquire a third party tool to perform data labeling.If security labeling is not required, this is not a finding. + +If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.SRG-APP-000313-DB-000309<GroupDescription></GroupDescription>SQL4-00-032000When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in process.<VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. + +Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. + +These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. + +One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. + +SQL Server does not include security labeling as a standard or licensable feature. Earlier releases of this STIG suggested using the SQL Server Label Security Toolkit, from codeplex.com. However, codeplex.com has been shut down, and it is unclear whether the Toolkit is still supported. If the organization does have access to the Toolkit, it may still be used, provided the organization accepts responsibility for its support. Other implementations may also exist. Custom application code is also a viable way to implement a solution.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81893V-67403CCI-002263Develop SQL or application code or acquire a third party tool to perform data labeling.If security labeling is not required, this is not a finding. + +If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in process, this is a finding.SRG-APP-000314-DB-000310<GroupDescription></GroupDescription>SQL4-00-032100When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission.<VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. + +Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. + +These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. + +One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. + +SQL Server does not include security labeling as a standard or licensable feature. Earlier releases of this STIG suggested using the SQL Server Label Security Toolkit, from codeplex.com. However, codeplex.com has been shut down, and it is unclear whether the Toolkit is still supported. If the organization does have access to the Toolkit, it may still be used, provided the organization accepts responsibility for its support. Other implementations may also exist. Custom application code is also a viable way to implement a solution.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81895V-67405CCI-002264Develop SQL or application code or acquire a third party tool to perform data labeling.If security labeling is not required, this is not a finding. + +If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in transmission, this is a finding.SRG-APP-000375-DB-000323<GroupDescription></GroupDescription>SQL4-00-033700Time stamps in database tables, intended for auditing or activity-tracking purposes, must include both date and time of day, with a minimum granularity of one second.<VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis, in audit files, trace files/tables, and application data tables. + +Time stamps generated by SQL Server must include date and time, to a granularity of one second or finer. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the precision available in time stamp values. Granularity coarser than one second is not sufficient for audit trail purposes, and granularity finer than one second is recommended. Time stamp values are typically presented with three or more decimal places of seconds; however, the actual granularity may be coarser than the apparent precision. For example, SQL Server's GETDATE()/CURRENT_TMESTAMP values are presented to three decimal places, but the granularity is not one millisecond: it is about 1/300 of a second. + +The data types that can be used for this purpose in SQL Server are: +DATETIME2 - precision variable from a whole second down to a ten-millionth (subject to the actual precision of the hardware and operating system) +DATETIMEOFFSET - as datetime2, together with local offset from UTC +DATE, together with TIME (same precision considerations as for datetime2) +DATETIME - precision 1/300 of a second +Character-string data types allowing for at least 20 characters are also permissible, but not recommended. + +SQL Server built-in functions for retrieving current timestamps are: (high precision) sysdatetime(), sysdatetimeoffset(), sysutcdatetime(); (lower precision) CURRENT_TIMESTAMP or getdate(), getutcdate(). + +Ensure that values recorded for tracking purposes in data tables are correctly defined and maintained. (Design decisions about which tables require audit-trail or activity-tracking columns are outside the scope of this STIG. This requirement applies only to the data type and maintenance of such columns if they do exist.) + +The SMALLDATETIME data type is not precise enough for this purpose. Although it gives the impression of including a seconds component, the seconds value is always "00". + +SQL Server offers a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP. To avoid confusion, Microsoft recommends using the newer name for this data type, ROWVERSION, instead.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81897V-67407CCI-001889Modify applications and/or column/field definitions so that the time stamps in audit-trail and activity-tracking columns/fields in application data include date and time of day, to a granularity of one second or finer, and are recorded accurately.Review the column definitions and contents of audit-trail and activity-tracking timestamps in database tables. + +If these are not defined and maintained to include date and time of day, accurate to a granularity of one second or finer, this is a finding.SRG-APP-000428-DB-000386<GroupDescription></GroupDescription>SQL4-00-034700SQL Server must implement and/or support cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.<VulnDiscussion>Databases holding data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81899V-67409CCI-002475Where full-disk encryption is required, configure Windows and/or the storage system to provide this. + +Where transparent data encryption (TDE) is required, deploy the necessary stack of certificates and keys, and set the Encryption Enabled to True. For guidance from the Microsoft Developer Network on how to do this, perform a web search for "SQL Server 2014 TDE". + +Where column encryption is required, deploy the necessary stack of certificates and keys, and enable encryption on the columns in question. For guidance from the Microsoft Developer Network on how to do this, perform a web search for "SQL Server 2014 Encrypt a Column of Data".Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information. + +If no information is identified as requiring such protection, this is not a finding. + +Review the configuration of SQL Server, Windows, and additional software as relevant. + +If full-disk encryption is required, and Windows or the storage system is not configured for this, this is a finding. + +If database transparent data encryption (TDE) is called for, check whether it is enabled: +In SQL Server Management Studio, Object Explorer, expand the instance and right-click on the database name; select properties. Select the Options page, State section, Encryption Enabled parameter. + +If the value displayed is False, this is a finding. + +If column encryption, done via SQL Server features, is required, review the definitions and contents of the relevant tables and columns. + +If any of the information defined as requiring cryptographic protection is not encrypted in a manner that provides the required level of protection, this is a finding.SRG-APP-000447-DB-000393<GroupDescription></GroupDescription>SQL4-00-035200When invalid inputs are received, SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives.<VulnDiscussion>A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. + +The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input. + +This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81901V-67411CCI-002754Revise and deploy the source code for database program objects (stored procedures, functions, triggers) and application source code, to implement the documented behavior.Review system documentation to determine how input errors are to be handled in general and if any special handling is defined for specific circumstances. + +Review the source code for database program objects (stored procedures, functions, triggers) and application source code to identify how the system responds to invalid input. + +If it does not implement the documented behavior, this is a finding.SRG-APP-000494-DB-000344<GroupDescription></GroupDescription>SQL4-00-035800Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is accessed.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. Note also that Trace does not support auditing of SELECT statements, whereas Audit does. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide this tracking at the application level, if Trace is used for audit purposes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81903V-67413CCI-000172Where SQL Server Trace is in use, implement tracking of SELECTs on categorized data at the application level, using the system stored procedure sp_trace_generateevent to write the tracking records to the Trace used for audit purposes. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the application(s) using the database to verify that all SELECT actions on categorized data are being audited, and that the tracking records are written to the SQL Server Trace. If not, this is a finding. + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. + +If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000494-DB-000345<GroupDescription></GroupDescription>SQL4-00-035900Trace or Audit records must be generated when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. Note also that Trace does not support auditing of SELECT statements, whereas Audit does. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide this tracking at the application level, if Trace is used for audit purposes. + +Use of SQL Server Audit's SCHEMA_OBJECT_ACCESS_GROUP causes capture of all accesses, successful and otherwise, to all schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False. For example, SELECT 1/0 FROM SYS.ALL_OBJECTS will appear in the audit trail as successful, if the user has permission to perform that action, even though it contains an invalid expression. Some other actions that one would consider failures (such as selecting from a table that does not exist) may not appear at all.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81905V-67415CCI-000172Where SQL Server Trace is in use, implement tracking of SELECTs on categorized data at the application level, using the system stored procedure sp_trace_generateevent to write the tracking records to the Trace used for audit purposes. Include failed attempts in the tracking. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the application(s) using the database to verify that all SELECT actions on categorized data, including unsuccessful attempts, are being audited; and that the tracking records are written to the SQL Server Trace used for audit purposes. If not, this is a finding. + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. + +If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000495-DB-000328<GroupDescription></GroupDescription>SQL4-00-036200SQL Server must generate Trace or Audit records when privileges/permissions are modified via locally-defined security objects.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. + +In SQL Server, there is no distinction between modification of permissions and granting or dropping them. However, native SQL Server security functionality may be supplemented with application-specific tables and logic, in which case the following actions on these tables and procedures/triggers/functions are also relevant: +UPDATE +EXECUTE + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81907V-67417CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Add blocks of code to Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. + +Create triggers to raise a custom event on each locally-defined security table that requires tracking of Insert-Update-Delete operations. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Execute Trace.sql. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOObtain the list of locally-defined security tables, procedures and functions that require tracking. + +If there are none, this is not a finding. + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the locally-defined security tables for the existence of triggers to raise a custom event on each Update operation. If such triggers are not present, this is a finding. + +Verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +42 -- SP:Starting +43 -- SP:Completed +82-91 -- User-defined Event +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +Verify that all EXECUTE actions on locally-defined permissions-related procedures are being audited. If not, this is a finding. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all UPDATE and EXECUTE actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000495-DB-000329<GroupDescription></GroupDescription>SQL4-00-036300SQL Server must generate Trace or Audit records when unsuccessful attempts to modify privileges/permissions via locally-defined security objects occur.<VulnDiscussion>Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected. + +In SQL Server, there is no distinction between modification of permissions and granting or dropping them. However, native SQL Server security functionality may be supplemented with application-specific tables and logic, in which case the following actions on these tables and procedures/triggers/functions are also relevant: +UPDATE +EXECUTE + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Use of SQL Server Audit's SCHEMA_OBJECT_ACCESS_GROUP causes capture of all accesses, successful and otherwise, to the system views (and all other schema-scoped objects). The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False. For example, SELECT 1/0 FROM SYS.ALL_OBJECTS will appear in the audit trail as successful, if the user has permission to perform that action, even though it contains an invalid expression. Some other actions that one would consider failures (such as selecting from a table that does not exist) may not appear at all.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81909V-67419CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Add blocks of code to Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. + +Create triggers to raise a custom event on each locally-defined security table that requires tracking of Insert-Update-Delete operations. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Execute Trace.sql. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOObtain the list of locally-defined security tables, procedures and functions that require tracking. If there are none, this is not a finding. + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the locally-defined security tables for the existence of triggers to raise a custom event on each Update operation. If such triggers are not present, this is a finding. + +Verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +42 -- SP:Starting +43 -- SP:Completed +82-91 -- User-defined Event +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +Verify that all EXECUTE actions on locally-defined permissions-related procedures are being audited. If not, this is a finding. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all UPDATE and EXECUTE actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000496-DB-000334<GroupDescription></GroupDescription>SQL4-00-036400SQL Server must generate Trace or Audit records when locally-defined security objects are modified.<VulnDiscussion>SQL Server protects its built-in security objects (tables, views, functions, procedures, etc.) from alteration by database users and administrators. However, applications sometimes have additional, security-related objects defined in the database. ALTER operations on these objects must be monitored. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81911V-67421CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_CHANGE_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf there are no locally-defined security tables or procedures, this is not a finding. + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should all be among those listed; if not, this is a finding: + +46 -- Object:Created +47 -- Object:Deleted +162 -- User error message +164 -- Object:Altered + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_CHANGE_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all CREATE, ALTER, and DROP actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000496-DB-000335<GroupDescription></GroupDescription>SQL4-00-036500SQL Server must generate Trace or Audit records when unsuccessful attempts to modify locally-defined security objects occur.<VulnDiscussion>SQL Server protects its built-in security objects (tables, views, functions, procedures, etc.) from alteration by database users and administrators. However, applications sometimes have additional, security-related objects defined in the database. ALTER operations on these objects must be monitored. + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Use of SQL Server Audit's SCHEMA_OBJECT_CHANGE_GROUP causes capture of all attempts, successful and otherwise, to CREATE, ALTER, or DROP any schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81925V-67435CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_CHANGE_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf there are no locally-defined security tables or procedures, this is not a finding. + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should all be among those listed; if not, this is a finding: + +46 -- Object:Created +47 -- Object:Deleted +162 -- User error message +164 -- Object:Altered + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_CHANGE_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all CREATE, ALTER, and DROP actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000498-DB-000346<GroupDescription></GroupDescription>SQL4-00-036600Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is created.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit INSERT actions at the application level. However, to capture all INSERTs, whether they come from the application or bypass it, the Trace must be configured to cover them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81927V-67437CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for INSERTs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the Trace settings, and the triggers on the tables holding categorized information, to determine whether all INSERT actions on these tables are traced, including failed attempts. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000498-DB-000346<GroupDescription></GroupDescription>SQL4-00-036650Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is modified.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit UPDATE actions at the application level. However, to capture all UPDATEs, whether they come from the application or bypass it, the Trace must be configured to cover them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81931V-67441CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for UPDATEs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the triggers on all tables holding categorized information, to determine whether trace events are generated for all UPDATE actions on these tables. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000498-DB-000347<GroupDescription></GroupDescription>SQL4-00-036800Trace or Audit records must be generated when unsuccessful attempts to create categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit INSERT actions at the application level. However, to capture all INSERTs, whether they come from the application or bypass it, the Trace must be configured to cover them. + +Use of SQL Server Audit's SCHEMA_OBJECT_ACCESS_GROUP causes capture of all accesses, successful and otherwise, to all schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False; and some other actions that one would consider failures (such as selecting from a table that does not exist) may not appear at all.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81929V-67439CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for INSERTs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the Trace settings, and the triggers on the tables holding categorized information, to determine whether all INSERT actions on these tables are traced, including failed attempts. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000498-DB-000347<GroupDescription></GroupDescription>SQL4-00-036850Trace or Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit UPDATE actions at the application level. However, to capture all UPDATEs, whether they come from the application or bypass it, the Trace must be configured to cover them. + +Use of SQL Server Audit's SCHEMA_OBJECT_ACCESS_GROUP causes capture of all accesses, successful and otherwise, to all schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False. For example, SELECT 1/0 FROM SYS.ALL_OBJECTS will appear in the audit trail as successful, if the user has permission to perform that action, even though it contains an invalid expression. Some other actions that one would consider failures (such as selecting from a table that does not exist) may not appear at all.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81933V-67443CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for UPDATEs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the Trace settings, and the triggers on the tables holding categorized information, to determine whether all UPDATE actions on these tables are traced, including failed attempts. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000501-DB-000336<GroupDescription></GroupDescription>SQL4-00-037100SQL Server must generate Trace or Audit records when locally-defined security objects are dropped.<VulnDiscussion>SQL Server protects its built-in security objects (tables, views, functions, procedures, etc.) from alteration by database users and administrators. However, applications sometimes have additional, security-related objects defined in the database. DROP operations on these objects must be monitored. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81923V-67433CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Add blocks of code to Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. + +Create triggers to raise a custom event on each locally-defined security table that requires tracking of Insert-Update-Delete operations. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Execute Trace.sql. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_CHANGE_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If there are no locally-defined security tables or procedures, this is not a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; +All currently defined traces for the SQL server instance will be listed. + +If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should all be among those listed; if not, this is a finding: + +46 -- Object:Created +47 -- Object:Deleted +162 -- User error message +164 -- Object:Altered + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_CHANGE_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all CREATE, ALTER, and DROP actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000501-DB-000337<GroupDescription></GroupDescription>SQL4-00-037200SQL Server must generate Trace or Audit records when unsuccessful attempts to drop locally-defined security objects occur.<VulnDiscussion>SQL Server protects its built-in security objects (tables, views, functions, procedures, etc.) from alteration by database users and administrators. However, applications sometimes have additional, security-related objects defined in the database. DROP operations on these objects must be monitored. + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Use of SQL Server Audit's SCHEMA_OBJECT_CHANGE_GROUP causes capture of all attempts, successful and otherwise, to CREATE, ALTER, or DROP any schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81921V-67431CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +Add blocks of code to Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. + +Create triggers to raise a custom event on each locally-defined security table that requires tracking of Insert-Update-Delete operations. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Execute Trace.sql. + +Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_CHANGE_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If there are no locally-defined security tables or procedures, this is not a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should all be among those listed; if not, this is a finding: + +46 -- Object:Created +47 -- Object:Deleted +162 -- User error message +164 -- Object:Altered + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_CHANGE_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all CREATE, ALTER, and DROP actions on any locally-defined permissions tables, procedures and functions are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000502-DB-000348<GroupDescription></GroupDescription>SQL4-00-037300Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit DELETE actions at the application level. However, to capture all DELETEs, whether they come from the application or bypass it, the Trace must be configured to cover them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81919V-67429CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for DELETEs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the triggers on all tables holding categorized information, to determine whether trace events are generated for all DELETE actions on these tables. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. + +In the following, replace # with a trace ID being used for the auditing requirements. + +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000502-DB-000349<GroupDescription></GroupDescription>SQL4-00-037400Trace or Audit records must be generated when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Since Trace does not provide for tracking SELECT statements, it is necessary to provide that part of the tracking at the application level. Because of this, it may also be appropriate to audit DELETE actions at the application level. However, to capture all DELETEs, whether they come from the application or bypass it, the Trace must be configured to cover them. + +Use of SQL Server Audit's SCHEMA_OBJECT_ACCESS_GROUP causes capture of all accesses, successful and otherwise, to all schema-scoped objects. The [Succeeded] column in the audit output indicates the success or failure of the attempted action. Be aware, however, that it may report True in some cases where one would intuitively expect False. For example, SELECT 1/0 FROM SYS.ALL_OBJECTS will appear in the audit trail as successful, if the user has permission to perform that action, even though it contains an invalid expression. Some other actions that one would consider failures (such as selecting from a table that does not exist) may not appear at all.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81917V-67427CCI-000172Where SQL Server Trace is in use, create triggers to raise a custom event for DELETEs on each table holding categorized information. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOReview the system documentation to determine whether it is required to track categories of information, such as classification or sensitivity level. If it is not, this is not applicable (NA). + +If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +If SQL Server Trace is in use for audit purposes, review the Trace settings, and the triggers on the tables holding categorized information, to determine whether all DELETE actions on these tables are traced, including failed attempts. If not, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +82-91 -- User-defined Event (at least one of these, matching the triggers; 90 is used in the supplied script) +162 -- User error message + + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the broad, server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all SELECT, INSERT, UPDATE, and DELETE actions on tables and views are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000507-DB-000356<GroupDescription></GroupDescription>SQL4-00-038100SQL Server must generate Trace or Audit records when successful accesses to designated objects occur.<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. + +Types of access include, but are not necessarily limited to: +SELECT +INSERT +UPDATE +DELETE +EXECUTE + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016. + +Trace does not offer tracking of SELECT operations, so where this is required it must be implemented at the application level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81915V-67425CCI-000172Where SQL Server Trace is in use, implement tracking of SELECTs on designated tables at the application level, using the system stored procedure sp_trace_generateevent to write the tracking records to the Trace used for audit purposes. + +Create triggers to raise a custom event on each table that requires tracking of Insert-Update-Delete operations. The examples provided in the supplemental file CustomTraceEvents.sql can serve as the basis for these. + +Add a block of code to the supplemental file Trace.sql for each custom event class (integers in the range 82-91; the same event class may be used for all such triggers) used in these triggers. + +Ensure that Trace.sql includes blocks of code for event classes 42, 43, and 162. + +Execute Trace.sql. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +Obtain the list of objects (tables and stored procedures) where tracking of SELECT, INSERT, UPDATE, DELETE, or EXECUTE actions is required. If there are none, this is not a finding. + +If SQL Server Trace is in use for audit purposes, review the application(s) using the database to verify that all SELECT actions on categorized data are being audited, and that the tracking records are written to the SQL Server Trace used for audit purposes. If not, this is a finding. + +Review the designated tables for the existence of triggers to raise a custom event on each Insert-Update-Delete operation. + +If such triggers are not present, this is a finding. + +Check to see that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event IDs should be among those listed; if not, this is a finding: + +42 -- SP:Starting +43 -- SP:Completed +82-91 -- User-defined Event (at least one of these; 90 is used in the supplied script) +162 -- User error message + +If SQL Server Audit is in use, verify that execution of all SELECT, INSERT, UPDATE, DELETE, or EXECUTE actions on the designated objects, is audited,. + +If any such actions are not audited, this is a finding. + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all logons and connections are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; +GO + +If no row is returned, this is a finding. + +If the audited_result column is not "SUCCESS" or "SUCCESS AND FAILURE", this is a finding.SRG-APP-000507-DB-000357<GroupDescription></GroupDescription>SQL4-00-038200SQL Server must generate Trace or Audit records when unsuccessful accesses to designated objects occur.<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Types of access include, but are not necessarily limited to: +SELECT +INSERT +UPDATE +DELETE +EXECUTE + +To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. + +Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990SV-81913V-67423CCI-000172Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this. + +If SQL Server Audit is in use, design and deploy an Audit that captures all auditable events and data items. The script provided in the supplemental file Audit.sql can be used as the basis for this. Supplement the standard audit data as necessary, using Extended Events and/or triggers. + +Alternatively, to add the necessary data capture to an existing server audit specification, run the script: +USE [master]; +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (SCHEMA_OBJECT_ACCESS_GROUP); +GO +ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON); +GOIf neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding. + +Obtain the list of objects (tables and stored procedures) where tracking of SELECT, INSERT, UPDATE, DELETE, or EXECUTE actions is required. If there are none, this is not a finding. + +If SQL Server Trace is in use for audit purposes, verify that all required event classes are being audited. From the query prompt: +SELECT * FROM sys.traces; + +All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding. + +Determine the trace(s) being used for the auditing requirement. +In the following, replace # with a trace ID being used for the auditing requirements. +From the query prompt: +SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#); + +The following required event ID should be among those listed; if not, this is a finding: + +162 -- User error message + +If SQL Server Audit is in use, proceed as follows. + +The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the server-level audit action group SCHEMA_OBJECT_ACCESS_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding. + +Determine the name(s) of the server audit specification(s) in use. + +To look at audits and audit specifications, in Management Studio's object explorer, expand +<server name> >> Security >> Audits +and +<server name> >> Security >> Server Audit Specifications. +Also, +<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications. + +Alternatively, review the contents of the system views with "audit" in their names. + +Run the following to verify that all logons and connections are being audited: +USE [master]; +GO +SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id = +(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>') +AND audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP'; +GO + +If no row is returned, this is a finding. + +If the audited_result column is not "FAILURE" or "SUCCESS AND FAILURE", this is a finding.SQL4-00-038300<GroupDescription></GroupDescription>SQL4-00-038300Microsoft SQL Server products must be a version supported by the vendor.<VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities. + +Systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation. + +When maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2014 DatabaseDISADPMS TargetMS SQL Server 2014 Database3990CCI-003376Upgrade unsupported DBMS or unsupported components to a supported version of the product.Review the version and release information. + +Verify the SQL Server version via one of the following methods: +Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server. + +Or, from SQL Server Management Studio: + +SELECT @@VERSION; + +More information for finding the version is available at the following link: +https://learn.microsoft.com/en-us/troubleshoot/sql/releases/find-my-sql-version + +SQL Server 2014 is no longer supported by the vendor. If the system is running SQL Server 2014 or earlier, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_MS_SQL_Server_2014_Instance_STIG_V2R4_Manual-xccdf.xml b/benchmarks/DISA/U_MS_SQL_Server_2014_Instance_STIG_V2R4_Manual-xccdf.xml new file mode 100644 index 000000000..8b3494df2 --- /dev/null +++ b/benchmarks/DISA/U_MS_SQL_Server_2014_Instance_STIG_V2R4_Manual-xccdf.xml @@ -0,0 +1,3245 @@ +acceptedMS SQL Server 2014 Instance Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 4 Benchmark Date: 24 Jul 20243.51.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-010000The SUSE operating system must be a vendor-supported release.<VulnDiscussion>A SUSE operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001230Upgrade the SUSE operating system to a version supported by the vendor. If the system is not registered with the SUSE Customer Center, register the system against the correct subscription. + +If the system requires Long-Term Service Pack Support (LTSS), obtain the correct LTSS subscription for the system.Verify the SUSE operating system is a vendor-supported release. + +Use the following command to verify the SUSE operating system is a vendor-supported release: + +> cat /etc/os-release + +NAME="SLES" +VERSION="15" + +Or any SUSE Linux Enterprise 15 Service Pack follow up release. + +NAME="SLES" +VERSION="15-SPx" + +Current End of Life for SLES 15 General Support is 31 Jul 2028 and Long-term Support is until 31 Jul 2031. + +If the release is not supported by the vendor, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-010010Vendor-packaged SUSE operating system security patches and updates must be installed and up to date.<VulnDiscussion>Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep SUSE operating system and application software patched is a common mistake made by IT professionals. New patches are released frequently, and it is often difficult for even experienced System Administrators (SAs) to keep abreast of all the new patches. When new weaknesses in a SUSE operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001227Install the applicable SUSE operating system patches available from SUSE by running the following command: + +> sudo zypper patchVerify the SUSE operating system security patches and updates are installed and up to date. + +Note: Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). + +Check for required SUSE operating system patches and updates with the following command: + +> sudo zypper patch-check + +0 patches needed (0 security patches) + +If the patch repository data is corrupt, check that the available package security updates have been installed on the system with the following command: + +> cut -d "|" -f 1-4 -s --output-delimiter " | " /var/log/zypp/history | grep -v " radd " + +2016-12-14 11:59:36 | install | libapparmor1-32bit | 2.8.0-2.4.1 +2016-12-14 11:59:36 | install | pam_apparmor | 2.8.0-2.4.1 +2016-12-14 11:59:36 | install | pam_apparmor-32bit | 2.8.0-2.4.1 + +If the SUSE operating system has not been patched within the site or PMO frequency, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>SLES-15-010020The SUSE operating system must display the Standard Mandatory DOD Notice and Consent Banner before granting access via local console.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. + +The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DOD will not be in compliance with system use notifications required by law. + +System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. + +The banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for SUSE operating system: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000048Configure the SUSE operating system to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via local console by performing the following tasks: + +Edit the "motd" file and replace the default text inside with the Standard Mandatory DOD banner text: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."Verify the SUSE operating system displays the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via local console. + +Check the "motd" (message of the day) file to verify that it contains the DOD required banner text: + +> more /etc/issue + +The output must display the following DOD-required banner text: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +If the output does not display the correct banner text, this is a finding.SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>SLES-15-010030The SUSE operating system must not have the vsftpd package installed if not required for operational support.<VulnDiscussion>It is detrimental for SUSE operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked, and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. + +SUSE operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions and functions). + +Examples of nonessential capabilities include but are not limited to games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission but which cannot be disabled. + +Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000197CCI-000381Document the "vsftpd" package with the ISSO as an operational requirement or remove it from the system with the following command: + +> sudo zypper remove vsftpdVerify the vsftpd package is not installed on the SUSE operating system. + +Check that the vsftpd package is not installed on the SUSE operating system by running the following command: + +> zypper info vsftpd | grep Installed + +If "vsftpd" is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>SLES-15-010040The SUSE operating system must display the Standard Mandatory DOD Notice and Consent Banner before granting access via SSH.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. + +System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. + +The banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for SUSE operating systems that can accommodate banners of 1300 characters: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure the SUSE operating system to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system by running the following commands: + +Edit the "sshd_config" file and edit the Banner flag to be the following: + +Banner /etc/issue/ + +Restart the sshd daemon: + +> sudo systemctl restart sshd.service + +To configure the system logon banner, edit the "/etc/issue" file. Replace the default text inside with the Standard Mandatory DOD banner text: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."Verify the SUSE operating system displays the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via SSH. + +Check the issue file to verify it contains one of the DOD required banners. If it does not, this is a finding. + +> more /etc/issue + +The output must display the following DOD-required banner text: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +If the output does not display the banner text, this is a finding. + +Check the banner setting for sshd_config: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*banner' + +Banner /etc/issue + +If "Banner" is not set to "/etc/issue", this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>SLES-15-010050The SUSE operating system must display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access to the local graphical user interface (GUI).<VulnDiscussion>The SUSE operating system must display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access to the local graphical user interface (GUI). + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000048CCI-000050Configure the SUSE operating system to display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access. + +Note: If a graphical user interface is not installed, this requirement is Not Applicable. + +Edit the file "/etc/gdm/Xsession". + +Add the following content to the file "/etc/gdm/Xsession" below the line #!/bin/sh: + +if ! zenity --text-info \ +--title "Consent" \ +--filename=/etc/gdm/banner \ +--no-markup \ +--checkbox="Accept." 10 10; then +sleep 1; +exit 1; +fi + +Save the file "/etc/gdm/Xsession".Verify the SUSE operating system displays the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on via the local GUI. + +Note: If a graphical user interface is not installed, this requirement is Not Applicable. + +Check the configuration by running the following command: + +> more /etc/gdm/Xsession + +The beginning of the file must contain the following text immediately after (#!/bin/sh): + +if ! zenity --text-info \ +--title "Consent" \ +--filename=/etc/gdm/banner \ +--no-markup \ +--checkbox="Accept." 10 10; then +sleep 1; +exit 1; +fi + +If the beginning of the file does not contain the above text immediately after the line (#!/bin/sh), this is a finding.SRG-OS-000024-GPOS-00007<GroupDescription></GroupDescription>SLES-15-010060The SUSE operating system file /etc/gdm/banner must contain the Standard Mandatory DoD Notice and Consent banner text.<VulnDiscussion>The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. + +To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000050Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Configure the SUSE operating system file "/etc/gdm/banner" to contain the Standard Mandatory DoD Notice and Consent Banner by running the following commands: + +> sudo vi /etc/gdm/banner + +Add the following information to the file: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Verify the SUSE operating system file "/etc/gdm/banner" contains the Standard Mandatory DoD Notice and Consent Banner text by running the following command: + +> more /etc/gdm/banner + +If the file does not contain the following text, this is a finding. + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."SRG-OS-000228-GPOS-00088<GroupDescription></GroupDescription>SLES-15-010080The SUSE operating system must display a banner before granting local or remote access to the system via a graphical user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. + +The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. + +System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. + +The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for SUSE operating system: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Configure the SUSE operating system to display a banner before local or remote access to the system via a graphical user logon. + +Create a database that will contain the system-wide graphical user logon settings (if it does not already exist) with the following command: + +> sudo mkdir -p /etc/dconf/db/gdm.d +> sudo touch /etc/dconf/db/gdm.d/01-banner-message + +Add the following content into /etc/dconf/profile/gdm: + +user-db:user +system-db:gdm +file-db:/usr/share/gdm/greeter-dconf-defaults + +Add the following line to the "[org/gnome/login-screen]" section of the "/etc/dconf/db/gdm.d/01-banner-message" file: + +[org/gnome/login-screen] +banner-message-enable=true + +Update the system databases: + +> sudo dconf update + +Users must log out and back in again before the system-wide settings take effect.Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Verify the SUSE operating system displays a banner before local or remote access to the system via a graphical user logon. + +Check that the SUSE operating system displays a banner at the logon screen by performing the following command: + +> grep banner-message-enable /etc/dconf/db/gdm.d/* +banner-message-enable=true + +> cat /etc/dconf/profile/gdm +user-db:user +system-db:gdm +file-db:/usr/share/gdm/greeter-dconf-defaults + +If "banner-message-enable" is set to "false" or is missing completely, this is a finding.SRG-OS-000228-GPOS-00088<GroupDescription></GroupDescription>SLES-15-010090The SUSE operating system must display the approved Standard Mandatory DoD Notice before granting local or remote access to the system via a graphical user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. + +The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. + +System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. + +The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for SUSE operating system: + +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +-At any time, the USG may inspect and seize data stored on this IS. + +-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. + +-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Configure the SUSE operating system to display the approved Standard Mandatory DoD Notice before granting local or remote access to the system via a graphical user logon. + +Create a database to contain the system wide graphical user logon settings (if it does not already exist) by performing the following command: + +> sudo touch /etc/dconf/db/gdm.d/01-banner-message + +Add the following lines to the "[org/gnome/login-screen]" section of the "dconf/db/gdm.d/01-banner-message" file: + +[org/gnome/login-screen] +banner-message-text="You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n-At any time, the USG may inspect and seize data stored on this IS.\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +Note: The "\n" characters are for formatting only. They will not be displayed on the GUI. + +Run the following command to update the database: +> sudo dconf updateNote: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Verify the SUSE operating system displays the approved Standard Mandatory DoD Notice before granting local or remote access to the system via a graphical user logon. + +Check that the SUSE operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text by performing the following command: + +> grep banner-message-text /etc/dconf/db/gdm.d/* +banner-message-text= +"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n-At any time, the USG may inspect and seize data stored on this IS.\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." + +Note: The "\n" characters are for formatting only. They will not be displayed on the GUI. + +If the banner text does not exactly match the approved Standard Mandatory DoD Notice and Consent Banner, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>SLES-15-010100The SUSE operating system must be able to lock the graphical user interface (GUI).<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. + +The session lock is implemented at the point where session activity can be determined. + +Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. + +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000056CCI-000057CCI-000060Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. This command must be run from an X11 session; otherwise, the command will not work correctly. + +Configure the SUSE operating system to allow the user to lock the GUI. + +Run the following command to configure the SUSE operating system to allow the user to lock the GUI: + +> sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen falseVerify the SUSE operating system allows the user to lock the GUI. + +Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +Run the following command: + +> sudo gsettings get org.gnome.desktop.lockdown disable-lock-screen + +If the result is "true", this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>SLES-15-010110The SUSE operating system must utilize vlock to allow for session locking.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. + +The session lock is implemented at the point where session activity can be determined. + +Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. + +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000056CCI-000057CCI-000060Allow users to lock the console by installing the "kbd" package using zypper: + +> sudo zypper install kbdCheck that the SUSE operating system has the "vlock" package installed by running the following command: + +> zypper search --installed-only --match-exact --provides vlock + +If the command outputs "no matching items found", this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>SLES-15-010120The SUSE operating system must initiate a session lock after a 15-minute period of inactivity for the graphical user interface (GUI).<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. + +Rather than relying on the users to manually lock their SUSE operating system session prior to vacating the vicinity, the SUSE operating system needs to be able to identify when a user's session has idled and take action to initiate the session lock. + +The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000057Configure the SUSE operating system to initiate a session lock after a 15-minute period of inactivity of the GUI by running the following command: + +Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. This command must be run from an X11 session, otherwise the command will not work correctly. + +> sudo gsettings set org.gnome.desktop.session idle-delay 900Verify the SUSE operating system initiates a session lock after a 15-minute period of inactivity via the GUI by running the following command: + +Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. + +> sudo gsettings get org.gnome.desktop.session idle-delay + +uint32 900 + +If the command does not return a value less than or equal to "900", this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>SLES-15-010130The SUSE operating system must initiate a session lock after a 15-minute period of inactivity.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. + +Rather than relying on the users to manually lock their SUSE operating system session prior to vacating the vicinity, the SUSE operating system needs to be able to identify when a user's session has idled and take action to initiate the session lock. + +The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000057Configure the SUSE operating system to initiate a session lock after a 15-minute period of inactivity by modifying or creating (if it does not already exist) the "/etc/profile.d/autologout.sh" file and add the following lines to it: + +TMOUT=900 +readonly TMOUT +export TMOUT + +Set the proper permissions for the "/etc/profile.d/autologout.sh" file with the following command: + +> sudo chmod +x /etc/profile.d/autologout.shVerify the SUSE operating system must initiate a session logout after a 15-minute period of inactivity for all connection types. + +Check the proper script exists to kill an idle session after a 15-minute period of inactivity with the following command: + +> cat /etc/profile.d/autologout.sh +TMOUT=900 +readonly TMOUT +export TMOUT + +If the file "/etc/profile.d/autologout.sh" does not exist or the output from the function call is not the same, this is a finding.SRG-OS-000031-GPOS-00012<GroupDescription></GroupDescription>SLES-15-010140The SUSE operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image in the graphical user interface (GUI).<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. + +The session lock is implemented at the point where session activity can be determined. The SUSE operating system session lock event must include an obfuscation of the display screen to prevent other users from reading what was previously displayed. + +Publicly viewable images can include static or dynamic images, such as patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images conveys sensitive information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000060Note: If the system does not have X Windows installed, this requirement is Not Applicable. + +Configure the SUSE operating system to use a publically viewable image by finding the Settings menu and then navigate to the Background selection section: + +- Click "Activities" on the top left. +- Click "Show Applications" at the bottom of the Activities menu. +- Click the "Settings" icon. +- Click "Background" from left hand menu. +- Select image and set the Lock Screen image to the user's choice. +- Exit Settings Dialog.Verify the SUSE operating system conceals via the session lock information previously visible on the display with a publicly viewable image in the GUI. + +Note: If the system does not have X Windows installed, this requirement is Not Applicable. + +Check that the lock screen is set to a publicly viewable image by running the following command: + +> sudo gsettings get org.gnome.desktop.screensaver picture-uri +'file:///usr/share/wallpapers/SLE-default-static.xml' + +If nothing is returned or "org.gnome.desktop.screensaver" is not set, this is a finding.SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>SLES-15-010150The SUSE operating system must log SSH connection attempts and failures to the server.<VulnDiscussion>Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best. + +Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Automated monitoring of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000067Configure SSH to verbosely log connection attempts and failed logon attempts to the SUSE operating system. + +Add or update the following line in the "/etc/ssh/sshd_config" file: + +LogLevel VERBOSE + +The SSH service will need to be restarted in order for the changes to take effect.Verify SSH is configured to verbosely log connection attempts and failed logon attempts to the SUSE operating system. + +Check that the SSH daemon configuration verbosely logs connection attempts and failed logon attempts to the server with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*loglevel' + +The output message must contain the following text: + +LogLevel VERBOSE + +If the output message does not contain "VERBOSE", the LogLevel keyword is missing, or the line is commented out, this is a finding.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>SLES-15-010160The SUSE operating system must implement DOD-approved encryption to protect the confidentiality of SSH remote connections.<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. + +Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. + +The system will attempt to use the first cipher presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest cipher available to secure the SSH connection. + +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000068Edit the SSH daemon configuration (/etc/ssh/sshd_config) and remove any ciphers not starting with "aes" and remove any ciphers ending with "cbc". If necessary, add a "Ciphers" line: + +Ciphers aes256-ctr,aes192-ctr,aes128-ctr + +Restart the SSH daemon: + +> sudo systemctl restart sshd.serviceVerify the SUSE operating system implements DOD-approved encryption to protect the confidentiality of SSH remote connections. + +Check the SSH daemon configuration for allowed ciphers with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*ciphers' + +Ciphers aes256-ctr,aes192-ctr,aes128-ctr + +If any ciphers other than "aes256-ctr", "aes192-ctr", or "aes128-ctr" are listed, the order differs from the example above, or the "Ciphers" keyword is missing, this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>SLES-15-010170The SUSE operating system, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.<VulnDiscussion>Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. + +A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. + +When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. + +This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000384-GPOS-00167</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000185CCI-004068Configure the SUSE operating system for PKI-based authentication to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. + +Modify all of the cert_policy lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "ca": + +cert_policy = ca,signature,oscp_on; + +Note: Additional certificate validation polices are permitted. + +Additional information on the configuration of multifactor authentication on the SUSE operating system can be found at https://www.suse.com/communities/blog/configuring-smart-card-authentication-suse-linux-enterprise/.Verify the SUSE operating system for PKI-based authentication had valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor. + +Check that the certification path to an accepted trust anchor for multifactor authentication is implemented with the following command: + +> grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf + +cert_policy = ca,oscp_on,signature,crl_auto; + +If "cert_policy" is not set to include "ca", this is a finding.SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>SLES-15-010180The SUSE operating system must not have the telnet-server package installed.<VulnDiscussion>It is detrimental for SUSE operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked, and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. + +SUSE operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions and functions). + +Examples of nonessential capabilities include but are not limited to games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission but which cannot be disabled. + +Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000197CCI-000381Remove the telnet-server package from the SUSE operating system by running the following command: + +> sudo zypper remove telnet-serverVerify the telnet-server package is not installed on the SUSE operating system. + +Check that the telnet-server package is not installed on the SUSE operating system by running the following command: + +> zypper info telnet-server | grep Installed + +If the telnet-server package is installed, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>SLES-15-010190SUSE operating systems with a basic input/output system (BIOS) must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. + +Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000213Note: If the system does not use a BIOS this requirement is Not Applicable. + +Configure the SUSE operating system to encrypt the boot password. + +Generate an encrypted (GRUB2) password for root with the following command: + +> grub2-mkpasswd-pbkdf2 +Enter Password: +Reenter Password: +PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG + +Using the hash from the output, modify the "/etc/grub.d/40_custom" file and add the following two lines to add a boot password for the root entry: + +set superusers="root" +password_pbkdf2 root grub.pbkdf2.sha512.VeryLongString + +Generate an updated "grub.conf" file with the new password using the following commands: + +> sudo grub2-mkconfig --output=/tmp/grub2.cfg +> sudo mv /tmp/grub2.cfg /boot/grub2/grub.cfgVerify that the SUSE operating system has set an encrypted root password. + +Note: If the system does not use a BIOS this requirement is Not Applicable. + +Check that the encrypted password is set for root with the following command: + +> sudo cat /boot/grub2/grub.cfg | grep -i password + +password_pbkdf2 root grub.pbkdf2.sha512.10000.VeryLongString + +If the root password entry does not begin with "password_pbkdf2", this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>SLES-15-010200SUSE operating systems with Unified Extensible Firmware Interface (UEFI) implemented must require authentication upon booting into single-user mode and maintenance.<VulnDiscussion>If the system allows a user to boot into single-user or maintenance mode without authentication, any user that invokes single-user or maintenance mode is granted privileged access to all system information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000213Note: If the system does not use UEFI, this requirement is Not Applicable. + +Configure the SUSE operating system to encrypt the boot password. + +Generate an encrypted (GRUB2) password for root with the following command: + +> grub2-mkpasswd-pbkdf2 +Enter Password: +Reenter Password: +PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG + +Using the hash from the output, modify the "/etc/grub.d/40_custom" file and add the following two lines to add a boot password for the root entry: + +set superusers="root" +password_pbkdf2 root grub.pbkdf2.sha512.VeryLongString + +Generate an updated "grub.conf" file with the new password using the following commands: + +> sudo grub2-mkconfig --output=/tmp/grub2.cfg +> sudo mv /tmp/grub2.cfg /boot/efi/EFI/sles/grub.cfgVerify that the SUSE operating system has set an encrypted root password. + +Note: If the system does not use UEFI, this requirement is Not Applicable. + +Check that the encrypted password is set for root with the following command: + +> sudo cat /boot/efi/EFI/sles/grub.cfg | grep -i password + +password_pbkdf2 root grub.pbkdf2.sha512.10000.VeryLongString + +If the root password entry does not begin with "password_pbkdf2", this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>SLES-15-010220The SUSE operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments.<VulnDiscussion>To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. + +SUSE operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. + +To support the requirements and principles of least functionality, the SUSE operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or address authorized quality-of-life issues. + +Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115, SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000382CCI-002314Configure the SUSE operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the PPSM CAL and vulnerability assessments. + +Add/modify /etc/firewalld configuration files to comply with the PPSM CAL. + +Enable the "firewalld.service" by running the following command: + +> sudo systemctl enable firewalld.service + +Start the "firewalld.service" by running the following command: + +> sudo systemctl start firewalld.serviceVerify the SUSE operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the PPSM CAL and vulnerability assessments. + +Check that the "firewalld.service" is enabled and running by running the following command: + +> systemctl status firewalld.service + firewalld.service - firewalld - dynamic firewall daemon + Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) + Active: active (running) since Wed 2019-11-06 10:58:11 CET; 24h ago + Docs: man:firewalld(1) + Main PID: 1105 (firewalld) + Tasks: 2 (limit: 4915) + CGroup: /system.slice/firewalld.service + ??1105 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid + +If the service is not enabled, this is a finding. + +If the service is not active, this is a finding. + +Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services by running the following command: + +> sudo firewall-cmd --list-all + +Ask the System Administrator for the site or program PPSM Component Local Services Assessment (Component Local Services Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. + +If there are any additional ports, protocols, or services that are not included in the PPSM CLSA, this is a finding. + +If there are any ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>SLES-15-010230The SUSE operating system must not have duplicate User IDs (UIDs) for interactive users.<VulnDiscussion>To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. + +Interactive users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Interactive users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: + +1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and + +2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. + +Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000764CCI-000804Configure the SUSE operating system to contain no duplicate UIDs for interactive users. + +Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate UID with a unique UID.Verify the SUSE operating system contains no duplicate UIDs for interactive users. + +Check that the SUSE operating system contains no duplicate UIDs for interactive users by running the following command: + +> awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd + +If output is produced, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>SLES-15-010240The SUSE operating system must disable the file system automounter unless required.<VulnDiscussion>Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity. + +Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000778CCI-001958Configure the SUSE operating system to disable the ability to automount devices. + +Turn off the automount service with the following command: + +> systemctl stop autofs +> systemctl disable autofs + +If "autofs" is required for Network File System (NFS), it must be documented with the ISSO.Verify the SUSE operating system disables the ability to automount devices. + +Check to see if automounter service is active with the following command: + +> systemctl status autofs +autofs.service - Automounts filesystems on demand +Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled) +Active: inactive (dead) + +If the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>SLES-15-010260The SUSE operating system must employ FIPS 140-2 approved cryptographic hashing algorithm for system authentication (login.defs).<VulnDiscussion>Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confidentiality or integrity, and DoD data may be compromised. + +SUSE operating systems using encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. + +FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules use authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general-purpose computing system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000803Configure the SUSE operating system to require "ENCRYPT_METHOD" of "SHA512". + +Edit the "/etc/login.defs" file with the following line: + +ENCRYPT_METHOD SHA512Verify the SUSE operating system requires that the "ENCRYPT_METHOD" value in "/etc/login.defs" is set to "SHA512". + +Check the value of "ENCRYPT_METHOD" value in "/etc/login.defs" with the following command: + +> grep "^ENCRYPT_METHOD " /etc/login.defs + +ENCRYPT_METHOD SHA512 + +If "ENCRYPT_METHOD" is not set to "SHA512", if any values other that "SHA512" are configured, or if no output is produced, this is a finding.SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>SLES-15-010270The SUSE operating system SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. + +Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. + +The system will attempt to use the first hash presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest hash available to secure the SSH connection. + +Satisfies: SRG-OS-000125-GPOS-00065, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000877CCI-001453CCI-003123Configure the SUSE operating system SSH daemon to only use MACs that employ FIPS 140-2 approved hashes. + +Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "MACs" keyword and set its value to "hmac-sha2-512" and/or "hmac-sha2-256" (The file might be named differently or be in a different location): + +MACs hmac-sha2-512,hmac-sha2-256Verify the SUSE operating system SSH daemon is configured to only use MACs that employ FIPS 140-2 approved hashes. + +Check that the SSH daemon is configured to only use MACs that employ FIPS 140-2 approved hashes with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*macs' + +MACs hmac-sha2-512,hmac-sha2-256 + +If any ciphers other than "hmac-sha2-512" or "hmac-sha2-256" are listed, the order differs from the example above, they are missing, or the returned line is commented out, this is a finding.SRG-OS-000126-GPOS-00066<GroupDescription></GroupDescription>SLES-15-010280The SUSE operating system SSH daemon must be configured with a timeout interval.<VulnDiscussion>Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. + +Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the SUSE operating system-level, and deallocating networking assignments at the application level if multiple application sessions are using a single SUSE operating system-level network connection. This does not mean that the SUSE operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. + +Satisfies: SRG-OS-000126-GPOS-00066, SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001133CCI-002361Configure the SUSE operating system SSH daemon to timeout idle sessions. + +Add or modify (to match exactly) the following line in the "/etc/ssh/sshd_config" file: + +ClientAliveInterval 600 + +The SSH daemon must be restarted for any changes to take effect.Verify the SUSE operating system SSH daemon is configured to timeout idle sessions. + +Check that the "ClientAliveInterval" parameter is set to a value of "600" with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*clientaliveinterval' + +ClientAliveInterval 600 + +If "ClientAliveInterval" is not set to "600" in "/etc/ssh/sshd_config", this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>SLES-15-010300The sticky bit must be set on all SUSE operating system world-writable directories.<VulnDiscussion>Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, and hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. + +This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies. + +There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001090Configure the SUSE operating system shared system resources to prevent any unauthorized and unintended information transfer by setting the sticky bit for all world-writable directories. + +An example of a world-writable directory is "/tmp" directory. Set the sticky bit on all of the world-writable directories (using the "/tmp" directory as an example) with the following command: + +> sudo chmod 1777 /tmp + +For every world-writable directory, replace "/tmp" in the command above with the world-writable directory that does not have the sticky bit set.Verify the SUSE operating system prevents unauthorized and unintended information transfer via the shared system resources. + +Check that world-writable directories have the sticky bit set with the following command: + +> sudo find / \( -path /.snapshots -o -path /sys -o -path /proc \) -prune -o -perm -002 -type d -exec ls -lLd {} \; + +256 0 drwxrwxrwt 1 root root 4096 Jun 14 06:45 /tmp + +If any of the returned directories do not have the sticky bit set, or are not documented as having the write permission for the other class, this is a finding.SRG-OS-000142-GPOS-00071<GroupDescription></GroupDescription>SLES-15-010310The SUSE operating system must be configured to use TCP syncookies.<VulnDiscussion>Denial of Service (DoS) is a condition in which a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. + +Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001095Configure the SUSE operating system to use IPv4 TCP syncookies by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.tcp_syncookies=1 + +If "1" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.tcp_syncookies=1" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system is configured to use IPv4 TCP syncookies. + +Check to see if syncookies are used with the following command: + +> sudo sysctl net.ipv4.tcp_syncookies +net.ipv4.tcp_syncookies = 1 + +If the network parameter "ipv4.tcp_syncookies" is not equal to "1" or nothing is returned, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>SLES-15-010320The SUSE operating system for all network connections associated with SSH traffic must immediately terminate at the end of the session or after 10 minutes of inactivity.<VulnDiscussion>Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. + +Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. + +Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. + +This capability is typically reserved for specific SUSE operating system functionality where the system owner, data owner, or organization requires additional assurance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001133CCI-002361Configure the SUSE operating system to automatically terminate all network connections associated with SSH traffic at the end of a session or after a 10-minute period of inactivity. + +Modify or append the following lines in the "/etc/ssh/sshd_config" file: + +ClientAliveCountMax 0 + +In order for the changes to take effect, the SSH daemon must be restarted. + +> sudo systemctl restart sshd.serviceVerify that all network connections associated with SSH traffic are automatically terminated at the end of the session or after 10 minutes of inactivity. + +Check that the "ClientAliveCountMax" variable is set to a value of "0" or less by performing the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*clientalivecountmax' + +ClientAliveCountMax 0 + +If "ClientAliveCountMax" does not exist or "ClientAliveCountMax" is not set to a value of "0" or less in "/etc/ssh/sshd_config", or the line is commented out, this is a finding.SRG-OS-000185-GPOS-00079<GroupDescription></GroupDescription>SLES-15-010330All SUSE operating system persistent disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection.<VulnDiscussion>SUSE operating systems handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001199CCI-002475Configure the SUSE operating system to prevent unauthorized modification of all information at rest by using disk encryption. + +Encrypting a partition in an already-installed system is more difficult because of the need to resize and change existing partitions. To encrypt an entire partition, dedicate a partition for encryption in the partition layout. The standard partitioning proposal as suggested by YaST (installation and configuration tool for Linux) does not include an encrypted partition by default. Add it manually in the partitioning dialog. + +Refer to the document "SUSE Linux Enterprise Server 15 SP1 - Security Guide", Section 12.1.2, for a detailed disk encryption guide: + +https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-security-cryptofs.html#sec-security-cryptofs-y2-part-runVerify the SUSE operating system prevents unauthorized disclosure or modification of all information requiring at rest protection by using disk encryption. + +Determine the partition layout for the system with the following command: + +> sudo fdisk -l + +Device Boot Start End Sectors Size Id Type +/dev/sda1 2048 4208639 4206592 2G 82 Linux swap +/dev/sda2 * 4208640 53479423 49270784 23.5G 83 Linux +/dev/sda3 53479424 125829119 72349696 34.5G 83 Linux + +Verify the system partitions are all encrypted with the following command: + +> sudo more /etc/crypttab + +cr_root UUID=26d4a101-7f48-4394-b730-56dc00e65f64 +cr_home UUID=f5b8a790-14cb-4b82-882d-707d52f27765 +cr_swap UUID=f2d86128-f975-478d-a5b0-25806c900eac + + +Every persistent disk partition present on the system must have an entry in the file. + +If any partitions other than pseudo file systems (such as /proc or /sys) are not listed or "/etc/crypttab" does not exist, this is a finding.SRG-OS-000205-GPOS-00083<GroupDescription></GroupDescription>SLES-15-010340The SUSE operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.<VulnDiscussion>Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. + +Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. + +The /var/log/btmp, /var/log/wtmp, and /var/log/lastlog files have group write and global read permissions to allow for the lastlog function to perform. Limiting the permissions beyond this configuration will result in the failure of functions that rely on the lastlog database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001312Configure the SUSE operating system to set permissions of all log files under /var/log directory to "640" or more restricted, by using the following command: + +Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. + +> sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec chmod 640 '{}' \;Verify the SUSE operating system has all system log files under the /var/log directory with a permission set to "640", by using the following command: + +Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. + +> sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec stat -c "%n %a" {} \; + +If command displays any output, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>SLES-15-010350The SUSE operating system must prevent unauthorized users from accessing system error messages.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the SUSE operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. + +The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001314Configure the SUSE operating system to prevent unauthorized users from accessing system error messages. + +Add or update the following rules in "/etc/permissions.local": + +/var/log/messages root:root 640 + +Set the correct permissions with the following command: + +> sudo chkstat --set --systemVerify the SUSE operating system prevents unauthorized users from accessing system error messages. + +Check the "/var/log/messages" file permissions with the following command: + +> sudo stat -c "%n %U:%G %a" /var/log/messages + +/var/log/messages root:root 640 + +Check that "permissions.local" file contains the correct permissions rules with the following command: + +> grep -i messages /etc/permissions.local + +/var/log/messages root:root 640 + +If the effective permissions do not match the "permissions.local" file, the command does not return any output, or is commented out, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010351The SUSE operating system library files must have mode 0755 or less permissive.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the library files to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec chmod 755 '{}' \;Verify the system-wide shared library files contained in the directories "/lib", "/lib64", "/usr/lib", and "/usr/lib64" have mode "0755" or less permissive. + +Check that the system-wide shared library files have mode "0755" or less permissive with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec stat -c "%n %a" '{}' \; + +If any files are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010352The SUSE operating system library directories must have mode 0755 or less permissive.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the shared library directories to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type d -exec chmod 755 '{}' \;Verify the system-wide shared library directories "/lib", "/lib64", "/usr/lib" and "/usr/lib64" have mode "0755" or less permissive. + +Check that the system-wide shared library directories have mode "0755" or less permissive with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type d -exec stat -c "%n %a" '{}' \; + +If any of the aforementioned directories are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010353The SUSE operating system library files must be owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system library files to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type f -exec chown root '{}' \;Verify the system-wide shared library files contained in the directories "/lib", "/lib64", "/usr/lib" and "/usr/lib64" are owned by root. + +Check that the system-wide shared library files are owned by root with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type f -exec stat -c "%n %U" '{}' \; + +If any system wide library file is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010354The SUSE operating system library directories must be owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the library files and their respective parent directories to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec chown root '{}' \;Verify the system-wide shared library directories "/lib", "/lib64", "/usr/lib/" and "/usr/lib64" are owned by root. + +Check that the system-wide shared library directories are owned by root with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; + +If any system wide library directory is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010355The SUSE operating system library files must be group-owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system library files to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type f -exec chgrp root '{}' \;Verify the system-wide library files contained in the directories "/lib", "/lib64", "/usr/lib" and "/usr/lib64" are group-owned by root. + +Check that the system-wide library files are group-owned by root with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type f -exec stat -c "%n %G" '{}' \; + +If any system wide shared library file is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010356The SUSE operating system library directories must be group-owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system library directories to be protected from unauthorized access. Run the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec chgrp root '{}' \;Verify the system-wide library directories "/lib", "/lib64", "/usr/lib" and "/usr/lib64" are group-owned by root. + +Check that the system-wide library directories are group-owned by root with the following command: + +> sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; + +If any system wide shared library directory is returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010357The SUSE operating system must have system commands set to a mode of 0755 or less permissive.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands to be protected from unauthorized access. Run the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec chmod 755 '{}' \;Verify the system commands contained in the following directories have mode "0755" or less permissive: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Check that the system command files have mode "0755" or less permissive with the following command: + +> find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec stat -c "%n %a" '{}' \; + +If any files are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010358The SUSE operating system must have directories that contain system commands set to a mode of 0755 or less permissive.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec chmod -R 755 '{}' \;Verify the system commands directories have mode "0755" or less permissive: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Check that the system command directories have mode "0755" or less permissive with the following command: + +> find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec stat -c "%n %a" '{}' \; + +If any directories are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010359The SUSE operating system must have system commands owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands - and their respective parent directories - to be protected from unauthorized access. Run the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec chown root '{}' \;Verify the system commands contained in the following directories are owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Use the following command for the check: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec stat -c "%n %U" '{}' \; + +If any system commands are returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010360The SUSE operating system must have directories that contain system commands owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec chown root '{}' \;Verify the system commands directories are owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Use the following command for the check: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec stat -c "%n %U" '{}' \; + +If any system commands directories are returned, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010361The SUSE operating system must have system commands group-owned by root or a system account.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any system command file not group-owned by "root" or a required system account. + +> sudo chgrp root [FILE]Verify the system commands contained in the following directories are group-owned by root or a system account: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Run the check with the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type f -exec stat -c "%n %G" '{}' \; + +If any system commands are returned that are not Set Group ID upon execution (SGID) files and group-owned by a required system account, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>SLES-15-010362The SUSE operating system must have directories that contain system commands group-owned by root.<VulnDiscussion>If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. + +This requirement applies to SUSE operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001499Configure the system commands directories to be protected from unauthorized access. Run the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec chgrp root '{}' \;Verify the system commands directories are group-owned by root: + +/bin +/sbin +/usr/bin +/usr/sbin +/usr/local/bin +/usr/local/sbin + +Run the check with the following command: + +> sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec stat -c "%n %G" '{}' \; + +If any system commands directories are returned that are not Set Group ID up on execution (SGID) files and owned by a privileged account, this is a finding.SRG-OS-000298-GPOS-00116<GroupDescription></GroupDescription>SLES-15-010370The SUSE operating system must have a firewall system installed to immediately disconnect or disable remote access to the whole operating system.<VulnDiscussion>Operating system remote access functionality must have the capability to immediately disconnect current users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of mission functions and the need to eliminate immediate or future remote access to organizational information systems. + +SUSE operating systems are capable to immediately stop remote connections and services by a local system administrator. + +To immediately disconnect or disable remote access, the firewall needs to be set into panic mode. + +> sudo firewall-cmd --panic-on + +To enable remote connection again, panic mode needs to be disabled. + +> sudo firewall-cmd --panic-off</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002322Configure the SUSE operating system to enable the firewall service. This is needed to be able to immediately disconnect or disable remote access to the whole system. + +Enable the "firewalld.service" by running the following command: + +> sudo systemctl enable firewalld.service + +Start the "firewalld.service" by running the following command: + +> sudo systemctl start firewalld.service + +To immediately disconnect or disable remote access the firewall needs to be set into panic mode. + +> sudo firewall-cmd --panic-on + +To enable remote connection again, panic mode needs to be disabled. + +> sudo firewall-cmd --panic-offVerify "firewalld" is configured to protect the SUSE operating system. + +Run the following command: + +> systemctl status firewalld.service + firewalld.service - firewalld - dynamic firewall daemon + Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) + Active: active (running) since Wed 2019-11-06 10:58:11 CET; 24h ago + Docs: man:firewalld(1) + Main PID: 1105 (firewalld) + Tasks: 2 (limit: 4915) + CGroup: /system.slice/firewalld.service + ??1105 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid + +If the service is not enabled, this is a finding. + +If the service is not active, this is a finding.SRG-OS-000299-GPOS-00117<GroupDescription></GroupDescription>SLES-15-010380The SUSE operating system wireless network adapters must be disabled unless approved and documented.<VulnDiscussion>Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the SUSE operating system. + +This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with a SUSE operating system. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the AO. Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the SUSE operating system. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. + +Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required. + +Satisfies: SRG-OS-000299-GPOS-00117, SRG-OS-000300-GPOS-00118, SRG-OS-000481-GPOS-000481</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001443CCI-001444CCI-002418Configure the SUSE operating system to disable all wireless network interfaces with the following command: + +For each interface of type wireless, bring the interface into "down" state: + +> sudo wicked ifdown wlan0 + +For each interface of type wireless with a configuration type of "compat:suse:", remove the associated file: + +> sudo rm /etc/sysconfig/network/ifcfg-wlan0 + +For each interface of type wireless, for each configuration of type "wicked:xml:", remove the associated file or remove the interface configuration from the file. + +> sudo rm /etc/wicked/ifconfig/wlan0.xmlVerify that the SUSE operating system has no wireless network adapters enabled. + +Check that there are no wireless interfaces configured on the system with the following command: + +> sudo wicked show all + +lo up +link: #1, state up +type: loopback +config: compat:suse:/etc/sysconfig/network/ifcfg-lo +leases: ipv4 static granted +leases: ipv6 static granted +addr: ipv4 127.0.0.1/8 [static] +addr: ipv6 ::1/128 [static] + +eth0 up +link: #2, state up, mtu 1500 +type: ethernet, hwaddr 06:00:00:00:00:01 +config: compat:suse:/etc/sysconfig/network/ifcfg-eth0 +leases: ipv4 dhcp granted +leases: ipv6 dhcp granted, ipv6 auto granted +addr: ipv4 10.0.0.100/16 [dhcp] +route: ipv4 default via 10.0.0.1 proto dhcp + +wlan0 up +link: #3, state up, mtu 1500 +type: wireless, hwaddr 06:00:00:00:00:02 +config: wicked:xml:/etc/wicked/ifconfig/wlan0.xml +leases: ipv4 dhcp granted +addr: ipv4 10.0.0.101/16 [dhcp] +route: ipv4 default via 10.0.0.1 proto dhcp + +If a wireless interface is configured, it must be documented and approved by the local AO. + +If a wireless interface is configured and has not been documented and approved, this is a finding.SRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>SLES-15-010390SUSE operating system AppArmor tool must be configured to control whitelisted applications and user home directory access control.<VulnDiscussion>Using a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. + +The organization must identify authorized software programs and permit execution of authorized software by adding each authorized program to the "pam_apparmor" exception policy. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. + +Verification of whitelisted software occurs prior to execution or at system startup. + +Users' home directories/folders may contain information of a sensitive nature. Nonprivileged users should coordinate any sharing of information with a System Administrator (SA) through shared resources. + +AppArmor can confine users to their home directory, not allowing them to make any changes outside of their own home directories. Confining users to their home directory will minimize the risk of sharing information. + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124, SRG-OS-000324-GPOS-00125, SRG-OS-000326-GPOS-00126, SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000480-GPOS-00230</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001764CCI-001774CCI-002165CCI-002233CCI-002235Configure the SUSE operating system to blacklist all applications by default and permit by whitelist. + +Install "pam_apparmor" (if it is not installed) with the following command: + +> sudo zypper in pam_apparmor + +Enable/activate "Apparmor" (if it is not already active) with the following command: + +> sudo systemctl enable apparmor.service + +Start "Apparmor" with the following command: + +> sudo systemctl start apparmor.service + +Note: "pam_apparmor" must have properly configured profiles. All configurations will be based on the actual system setup and organization. See the "pam_apparmor" documentation for more information on configuring profiles.Verify that the SUSE operating system AppArmor tool is configured to control whitelisted applications and user home directory access control. + +Check that "pam_apparmor" is installed on the system with the following command: + +> zypper info pam_apparmor | grep "Installed" + +If the package "pam_apparmor" is not installed on the system, this is a finding. + +Check that the "apparmor" daemon is running with the following command: + +> systemctl status apparmor.service | grep -i active + +Active: active (exited) since Fri 2017-01-13 01:01:01 GMT; 1day 1h ago + +If something other than "Active: active" is returned, this is a finding. + +Note: "pam_apparmor" must have properly configured profiles. All configurations will be based on the actual system setup and organization. See the "pam_apparmor" documentation for more information on configuring profiles.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>SLES-15-010400The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DOD time source at least every 24 hours.<VulnDiscussion>Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. + +Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. + +Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). + +Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000356-GPOS-00144</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004923CCI-004926The SUSE operating system clock must be configured to synchronize to an authoritative DOD time source when the time difference is greater than one second. + +To configure the system clock to synchronize to an authoritative DOD time source at least every 24 hours, edit the file "/etc/chrony.conf". Add or correct the following lines by replacing "[time_source]" with an authoritative DOD time source: + +server [time_source] maxpoll 16The SUSE operating system clock must be configured to synchronize to an authoritative DOD time source when the time difference is greater than one second. + +Check that the SUSE operating system clock must be configured to synchronize to an authoritative DOD time source when the time difference is greater than one second with the following command: + +> sudo grep maxpoll /etc/chrony.conf + +server 0.us.pool.ntp.mil maxpoll 16 + +If nothing is returned, "maxpoll" is greater than "16", or is commented out, this is a finding. + +Verify the "chrony.conf" file is configured to an authoritative DOD time source by running the following command: + +> sudo grep -i server /etc/chrony.conf +server 0.us.pool.ntp.mil + +If the parameter "server" is not set, is not set to an authoritative DOD time source, or is commented out, this is a finding.SRG-OS-000359-GPOS-00146<GroupDescription></GroupDescription>SLES-15-010410The SUSE operating system must be configured to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).<VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. + +Time stamps generated by the SUSE operating system include date and time. Time is commonly expressed in UTC, a modern continuation of GMT, or local time with an offset from UTC.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001890Configure the SUSE operating system is configured to use UTC or GMT. + +To configure the system time zone to use UTC or GMT, run the following command, replacing [ZONE] with "UTC" or "GMT". + +> sudo timedatectl set-timezone [ZONE]Verify the SUSE operating system is configured to use UTC or GMT. + +Check that the SUSE operating system is configured to use UTC or GMT with the following command: + +> timedatectl status | grep -i "time zone" +Time zone: UTC (UTC, +0000) + +If "Time zone" is not set to "UTC" or "GMT", this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>SLES-15-010420Advanced Intrusion Detection Environment (AIDE) must verify the baseline SUSE operating system configuration at least weekly.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the SUSE operating system. Changes to SUSE operating system configurations can have unintended side effects, some of which may be relevant to security. + +Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the SUSE operating system. The SUSE operating system's Information System Security Manager (ISSM)/Information System Security Officer (ISSO) and System Administrator (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. + +Satisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000445-GPOS-00199, SRG-OS-000446-GPOS-00200</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001744CCI-002696CCI-002699Configure the SUSE operating system to check the baseline configuration for unauthorized changes at least once weekly. + +If the "aide" package is not installed, install it with the following command: + + > sudo zypper in aide + +Configure the file integrity tool to automatically run on the system at least weekly. The following example output is generic. It will set cron to run AIDE weekly, but other file integrity tools may be used: + + > cat /etc/cron.weekly/aide + 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil + +Note: Per requirement SLES-15-010418, the "mailx" package must be installed on the system to enable email functionality.Verify the SUSE operating system checks the baseline configuration for unauthorized changes at least once weekly. + +Note: A file integrity tool other than AIDE may be used, but the tool must be executed at least once per week. + +Check for the presence of a cron job running daily or weekly on the system that executes AIDE to scan for changes to the system baseline. The command used in the following example looks at the daily cron job: + +Check the "/etc/cron" subdirectories for a "crontab" file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command: + + > sudo grep -R aide /etc/crontab /etc/cron.* + /etc/crontab: 30 04 * * * /etc/aide + +If the file integrity application does not exist, or a "crontab" file does not exist in "/etc/crontab", the "/etc/cron.daily" subdirectory, or "/etc/cron.weekly" subdirectory, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>SLES-15-010430The SUSE operating system tool zypper must have gpgcheck enabled.<VulnDiscussion>Changes to any software components can have significant effects on the overall security of the SUSE operating system. This requirement ensures the software has not been tampered with and has been provided by a trusted vendor. + +Accordingly, patches, service packs, device drivers, or SUSE operating system components must be signed with a certificate recognized and approved by the organization. + +Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The SUSE operating system should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved Certification Authority (CA).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-003992Configure that the SUSE operating system tool zypper to enable gpgcheck by editing or adding the following line to "/etc/zypp/zypp.conf": + +gpgcheck = 1Verify that the SUSE operating system tool zypper has gpgcheck enabled. + +Check that zypper has gpgcheck enabled with the following command: + +> grep -i '^gpgcheck' /etc/zypp/zypp.conf + +gpgcheck = 1 + +If "gpgcheck" is set to "0", "off", "no", or "false", this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>SLES-15-010450The SUSE operating system must reauthenticate users when changing authenticators, roles, or escalating privileges.<VulnDiscussion>Without reauthentication, users may access resources or perform tasks for which they do not have authorization. + +When the SUSE operating system provides the capability to change user authenticators, change security roles, or escalate a functional capability, it is critical the user reauthenticate. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004895Configure the SUSE operating system to remove any occurrence of "NOPASSWD" or "!authenticate" found in the "/etc/sudoers" file. If the system does not use passwords for authentication, the "NOPASSWD" tag may exist in the file.Verify that the SUSE operating system requires reauthentication when changing authenticators, roles, or escalating privileges. + +Check that "/etc/sudoers" has no occurrences of "NOPASSWD" or "!authenticate" with the following command: + +> sudo egrep -i '(nopasswd|!authenticate)' /etc/sudoers + +If any uncommented lines containing "!authenticate", or "NOPASSWD" are returned and active accounts on the system have valid passwords, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>SLES-15-010460The SUSE operating system must have the packages required for multifactor authentication to be installed.<VulnDiscussion>Using an authentication device, such as a Common Access Card (CAC) or token separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. + +Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification (PIV) card and the DOD CAC. + +A privileged account is defined as an information system account with authorizations of a privileged user. + +Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). + +Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000376-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004046CCI-001953CCI-001954Configure the SUSE operating system to implement multifactor authentication by installing the required packages. + +Install the packages required to support multifactor authentication with the following commands: + +> zypper install pam_pkcs11 + +> zypper install mozilla-nss + +> zypper install mozilla-nss-tools + +> zypper install pcsc-ccid + +> zypper install pcsc-lite + +> zypper install pcsc-tools + +> zypper install opensc + +> zypper install coolkey + +Additional information on the configuration of multifactor authentication on the SUSE operating system can be found at https://www.suse.com/communities/blog/configuring-smart-card-authentication-suse-linux-enterprise/.Verify the SUSE operating system has the packages required for multifactor authentication installed. + +Check for the presence of the packages required to support multifactor authentication with the following commands: + +> zypper info pam_pkcs11 | grep -i installed + +> zypper info mozilla-nss | grep -i installed + +> zypper info mozilla-nss-tools | grep -i installed + +> zypper info pcsc-ccid | grep -i installed + +> zypper info pcsc-lite | grep -i installed + +> zypper info pcsc-tools | grep -i installed + +> zypper info opensc | grep -i installed + +> zypper info coolkey | grep -i installed + +If any of the packages required for multifactor authentication are not installed, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>SLES-15-010470The SUSE operating system must implement certificate status checking for multifactor authentication.<VulnDiscussion>Using an authentication device, such as a Common Access Card (CAC) or token separate from the information system, ensures credentials stored on the authentication device will not be affected if the information system is compromised. + +Multifactor solutions that require devices separate from information systems to gain access include hardware tokens providing time-based or challenge-response authenticators, and smart cards such as the U.S. Government Personal Identity Verification (PIV) card and the DOD CAC. + +A privileged account is defined as an information system account with authorizations of a privileged user. + +Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +This requirement only applies to components with device-specific functions, or for organizational users (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). + +Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000376-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004046CCI-001953CCI-001954Configure the SUSE operating system to certificate status checking for PKI authentication. + +Modify all of the cert_policy lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "ocsp_on". + +Note: OCSP allows sending request for certificate status information. Additional certificate validation polices are permitted. + +Additional information on the configuration of multifactor authentication on the SUSE operating system can be found at https://www.suse.com/communities/blog/configuring-smart-card-authentication-suse-linux-enterprise/.Verify the SUSE operating system implements certificate status checking for multifactor authentication. + +Check that certificate status checking for multifactor authentication is implemented with the following command: + +> grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module coolkey {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy + +cert_policy = ca,ocsp_on,signature,crl_auto; + +If "cert_policy" is not set to include "ocsp", this is a finding.SRG-OS-000378-GPOS-00163<GroupDescription></GroupDescription>SLES-15-010480The SUSE operating system must disable the USB mass storage kernel module.<VulnDiscussion>Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. + +Peripherals include but are not limited to such devices as flash drives, external storage, and printers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001958Configure the SUSE operating system to prevent USB mass storage devices from automounting when connected to the host. + +Add or update the following line to the "/etc/modprobe.d/50-blacklist.conf" file: + +blacklist usb-storageVerify the SUSE operating system does not automount USB mass storage devices when connected to the host. + +Check that "usb-storage" is blacklisted in the "/etc/modprobe.d/50-blacklist.conf" file with the following command: + +> grep usb-storage /etc/modprobe.d/50-blacklist.conf +blacklist usb-storage + +If nothing is output from the command, this is a finding.SRG-OS-000383-GPOS-00166<GroupDescription></GroupDescription>SLES-15-010490If Network Security Services (NSS) is being used by the SUSE operating system it must prohibit the use of cached authentications after one day.<VulnDiscussion>If cached authentication information is out of date, the validity of the authentication information may be questionable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002007Configure NSS, if used by the SUSE operating system, to prohibit the use of cached authentications after one day. + +Add or change the following line in "/etc/sssd/sssd.conf" just below the line "[nss]": + +memcache_timeout = 86400If NSS is not used on the operating system, this is Not Applicable. + +If NSS is used by the SUSE operating system, verify it prohibits the use of cached authentications after one day. + +Check that cached authentications cannot be used after one day with the following command: + +> sudo grep -i "memcache_timeout" /etc/sssd/sssd.conf + +memcache_timeout = 86400 + +If "memcache_timeout" has a value greater than "86400", or is missing, this is a finding.SRG-OS-000383-GPOS-00166<GroupDescription></GroupDescription>SLES-15-010500The SUSE operating system must configure the Linux Pluggable Authentication Modules (PAM) to prohibit the use of cached offline authentications after one day.<VulnDiscussion>If cached authentication information is out of date, the validity of the authentication information may be questionable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002007Configure the SUSE operating system PAM to prohibit the use of cached authentications after one day. + +Add or change the following line in "/etc/sssd/sssd.conf" just below the line "[pam]": + +offline_credentials_expiration = 1If SSSD is not being used on the operating system, this is Not Applicable. + +Verify that the SUSE operating system PAM prohibits the use of cached off line authentications after one day. + +Check that cached off line authentications cannot be used after one day with the following command: + +> sudo grep "offline_credentials_expiration" /etc/sssd/sssd.conf + +offline_credentials_expiration = 1 + +If "offline_credentials_expiration" is not set to a value of "1", this is a finding.SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>SLES-15-010510FIPS 140-2 mode must be enabled on the SUSE operating system.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The SUSE operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. + +Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000478-GPOS-00223</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002450To configure the SUSE operating system to run in FIPS mode, add "fips=1" to the kernel parameter during the SUSE operating system install. + +Enabling FIPS mode on a preexisting system involves a number of modifications to the SUSE operating system. Refer to section 9.1, "Crypto Officer Guidance", of the following document for installation guidance: + +http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp2435.pdfVerify the SUSE operating system is running in FIPS mode by running the following command. + +> cat /proc/sys/crypto/fips_enabled + +1 + +If nothing is returned, the file does not exist, or the value returned is "0", this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>SLES-15-010530All networked SUSE operating systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. + +This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. + +Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, logical means (cryptography) do not have to be employed, and vice versa. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002418CCI-002420CCI-002421CCI-002422Note: If the system is not networked, this requirement is Not Applicable. + +Configure the SUSE operating system to implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission. + +Install the OpenSSH package on the SUSE operating system with the following command: + +> sudo zypper in openssh + +Enable the OpenSSH service to start automatically on reboot with the following command: + +> sudo systemctl enable sshd.service + +For the changes to take effect immediately, start the service with the following command: + +> sudo systemctl restart sshd.serviceNote: If the system is not networked, this requirement is Not Applicable. + +Verify that the SUSE operating system implements SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission. + +Check that the OpenSSH package is installed on the SUSE operating system with the following command: + +> zypper info openssh | grep -i installed + +If the OpenSSH package is not installed, this is a finding. + +Check that the OpenSSH service active on the SUSE operating system with the following command: + +> systemctl status sshd.service | grep -i "active:" + +Active: active (running) since Thu 2017-01-12 15:03:38 UTC; 1 months 4 days ago + +If OpenSSH service is not active, this is a finding.SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>SLES-15-010540The SUSE operating system must implement kptr-restrict to prevent the leaking of internal kernel addresses.<VulnDiscussion>Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced, with hardware providing the greater strength of mechanism. + +Examples of attacks are buffer overflow attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002824Configure the SUSE operating system to prevent leaking of internal kernel addresses by running the following command: + +> sudo sysctl -w kernel.kptr_restrict=1 + +If "1" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "kernel.kptr_restrict=1" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system prevents leaking of internal kernel addresses. + +Check that the SUSE operating system prevents leaking of internal kernel addresses by running the following command: + +> sudo sysctl kernel.kptr_restrict +kernel.kptr_restrict = 1 + +If the kernel parameter "kptr_restrict" is not equal to "1" or nothing is returned, this is a finding.SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>SLES-15-010550Address space layout randomization (ASLR) must be implemented by the SUSE operating system to protect memory from unauthorized code execution.<VulnDiscussion>Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced, with hardware providing the greater strength of mechanism. + +Examples of attacks are buffer overflow attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002824Configure the SUSE operating system to implement ASLR by running the following command as an administrator: + +> sudo sysctl -w kernel.randomize_va_space=2 + +If "2" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "kernel.randomize_va_space=2" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system implements ASLR. + +Check that the SUSE operating system implements ASLR by running the following command: + +> sudo sysctl kernel.randomize_va_space +Kernel.randomize_va_space = 2 + +If the kernel parameter "randomize_va_space" is not equal to "2" or nothing is returned, this is a finding.SRG-OS-000437-GPOS-00194<GroupDescription></GroupDescription>SLES-15-010560The SUSE operating system must remove all outdated software components after updated versions have been installed.<VulnDiscussion>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002617Configure the SUSE operating system to remove all outdated software components after an update by editing the following line in "/etc/zypp/zypp.conf" to match the one provided below: + +solver.upgradeRemoveDroppedPackages = trueVerify the SUSE operating system removes all outdated software components after updated version have been installed by running the following command: + +> grep -i upgraderemovedroppedpackages /etc/zypp/zypp.conf + +solver.upgradeRemoveDroppedPackages = true + +If "solver.upgradeRemoveDroppedPackages" is commented out, is set to "false", or is missing completely, this is a finding.SRG-OS-000447-GPOS-00201<GroupDescription></GroupDescription>SLES-15-010570The SUSE operating system must notify the System Administrator (SA) when Advanced Intrusion Detection Environment (AIDE) discovers anomalies in the operation of any security functions.<VulnDiscussion>If anomalies are not acted on, security functions may fail to secure the system. + +Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. + +Notifications provided by information systems include messages to local computer consoles and/or hardware indications, such as lights. + +This capability must take into account operational requirements for availability for selecting an appropriate response. The organization may choose to shut down or restart the information system upon security function anomaly detection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002702Configure the SUSE operating system to notify the SA when AIDE discovers anomalies in the operation of any security functions. + +Create the aide crontab file in "/etc/cron.daily" and add following command replacing the "[E-MAIL]" parameter with a proper email address for the SA: + + 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil + +Note: Per requirement SLES-15-010418, the "mailx" package must be installed on the system to enable email functionality.Verify the SUSE operating system notifies the SA when AIDE discovers anomalies in the operation of any security functions. + +Check to see if the aide cron job sends an email when executed with the following command: + + > grep -i "aide" /etc/cron.*/aide + 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil + +If the "aide" file does not exist under the "/etc/cron" directory structure or the cron job is not configured to execute a binary to send an email (such as "/bin/mail"), this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>SLES-15-010580The SUSE operating system must off-load rsyslog messages for networked systems in real time and off-load standalone systems at least weekly.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Configure the SUSE operating system to off-load rsyslog messages for networked systems in real time. + +For stand-alone systems establish a procedure to off-load log messages at least once a week. + +For networked systems add a "@[Log_Server_IP_Address]" option to every active message label in "/etc/rsyslog.conf" that does not have one. Some examples are listed below: + +*.*;mail.none;news.none -/var/log/messages +*.*;mail.none;news.none @192.168.1.101:514 + +An additional option is to capture all of the log messages and send them to a remote log host: + +*.* @@loghost:514Verify that the SUSE operating system must off-load rsyslog messages for networked systems in real time and off-load standalone systems at least weekly. + +For stand-alone hosts, verify with the System Administrator that the log files are off-loaded at least weekly. + +For networked systems, check that rsyslog is sending log messages to a remote server with the following command: + +> sudo grep "\*.\*" /etc/rsyslog.conf | grep "@" | grep -v "^#" + +*.*;mail.none;news.none @192.168.1.101:514 + +If any active message labels in the file do not have a line to send log messages to a remote server, this is a finding.SRG-OS-000002-GPOS-00002<GroupDescription></GroupDescription>SLES-15-020000The SUSE operating system must provision temporary accounts with an expiration date for 72 hours.<VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. + +Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. + +If temporary accounts are used, the SUSE operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000016In the event temporary accounts are required, configure the SUSE operating system to terminate them after "72" hours. + +For every temporary account, run the following command to set an expiration date on it, substituting "system_account_name" with the appropriate value: + +> sudo chage -E `date -d "+3 days" +%Y-%m-%d` system_account_name + +`date -d "+3 days" +%Y-%m-%d` sets the 72-hour expiration date for the account at the time the command is run.Verify that the SUSE operating system provisions temporary accounts with an expiration date for "72" hours. + +Ask the System Administrator if any temporary accounts have been added to the system. For every existing temporary account, run the following command to obtain its account expiration information: + +> sudo chage -l system_account_name + +Verify each of these accounts has an expiration date that is within "72" hours of its creation. + +If any temporary accounts have no expiration date set or do not expire within "72" hours of their creation, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>SLES-15-020010The SUSE operating system must lock an account after three consecutive invalid access attempts.<VulnDiscussion>By limiting the number of failed access attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. + +The pam_tally2.so module maintains a count of attempted accesses. This includes user name entry into a logon field as well as password entry. With counting access attempts, it is possible to lock an account without presenting a password into the password field. This should be taken into consideration as it poses as an avenue for denial of service. + +Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000044CCI-002238Configure the operating system to lock an account when three unsuccessful access attempts occur. + +Modify the first line of the auth section "/etc/pam.d/common-auth" file to match the following lines: + +auth required pam_tally2.so onerr=fail silent audit deny=3 + +Add or modify the following line in the /etc/pam.d/common-account file: +account required pam_tally2.so + +Note: Manual changes to the listed files may be overwritten by the "pam-config" program. The "pam-config" program should not be used to update the configurations listed in this requirement.Verify the SUSE operating system locks a user account after three consecutive failed access attempts until the locked account is released by an administrator. + +Check that the system locks a user account after three consecutive failed login attempts using the following command: + +> grep pam_tally2.so /etc/pam.d/common-auth +auth required pam_tally2.so onerr=fail deny=3 + +If no line is returned or the line is commented out, this is a finding. +If the line is missing "onerr=fail", this is a finding. +If the line has "deny" set to a value other than 1, 2, or 3, this is a finding. + +Check that the system resets the failed login attempts counter after a successful login using the following command: + +> grep pam_tally2.so /etc/pam.d/common-account +account required pam_tally2.so + +If the account option is missing, or commented out, this is a finding.SRG-OS-000027-GPOS-00008<GroupDescription></GroupDescription>SLES-15-020020The SUSE operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.<VulnDiscussion>SUSE operating system management includes the ability to control the number of users and user sessions that utilize a SUSE operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to Denial-of-Service (DoS) attacks. + +This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000054Configure the SUSE operating system to limit the number of concurrent sessions to "10" or less for all accounts and/or account types. + +Add the following line to the file "/etc/security/limits.conf": + +* hard maxlogins 10Verify the SUSE operating system limits the number of concurrent sessions to 10 for all accounts and/or account types by running the following command: + +> grep "maxlogins" /etc/security/limits.conf + +The result must contain the following line: + +* hard maxlogins 10 + +If the "maxlogins" item is missing, the line does not begin with a star symbol, or the value is not set to "10" or less, this is a finding.SRG-OS-000068-GPOS-00036<GroupDescription></GroupDescription>SLES-15-020030The SUSE operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM).<VulnDiscussion>Using an authentication device, such as a Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. + +Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification (PIV) card and the DOD CAC. + +A privileged account is defined as an information system account with authorizations of a privileged user. + +Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. + +This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). + +Satisfies: SRG-OS-000068-GPOS-00036, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160, SRG-OS-000376-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000187CCI-000765CCI-000766CCI-004046CCI-001953CCI-001954CCI-004047Configure the SUSE operating system to implement multifactor authentication for remote access to privileged accounts via PAM. + +Add or update "pam_pkcs11.so" in "/etc/pam.d/common-auth" to match the following line: + +auth sufficient pam_pkcs11.soVerify the SUSE operating system implements multifactor authentication for remote access to privileged accounts via PAM. + +Check that the "pam_pkcs11.so" option is configured in the "/etc/pam.d/common-auth" file with the following command: + +> grep pam_pkcs11.so /etc/pam.d/common-auth + +auth sufficient pam_pkcs11.so + +If "pam_pkcs11.so" is not set in "/etc/pam.d/common-auth", this is a finding.SRG-OS-000109-GPOS-00056<GroupDescription></GroupDescription>SLES-15-020040The SUSE operating system must deny direct logons to the root account using remote access via SSH.<VulnDiscussion>To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated. + +A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account. + +For example, the UNIX and Windows SUSE operating systems offer a "switch user" capability, allowing users to authenticate with their individual credentials and, when needed, "switch" to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. + +Users (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the SUSE operating system without identification or authentication. + +Requiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004045Configure the SUSE operating system to deny direct logons to the root account using remote access via SSH. + +Edit the appropriate "/etc/ssh/sshd_config" file, add or uncomment the line for "PermitRootLogin" and set its value to "no" (this file may be named differently or be in a different location): + +PermitRootLogin noVerify the SUSE operating system denies direct logons to the root account using remote access via SSH. + +Check that SSH denies any user trying to log on directly as root with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*permitrootlogin' + +PermitRootLogin no + +If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>SLES-15-020050The SUSE operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity after password expiration.<VulnDiscussion>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. + +The SUSE operating system needs to track periods of inactivity and disable application identifiers after 35 days of inactivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-003627CCI-003628Configure the SUSE operating system to disable account identifiers after 35 days of inactivity since the password expiration. + +Run the following command to change the configuration for "useradd" to disable the account identifier after 35 days: + +> sudo useradd -D -f 35 + +DOD recommendation is 35 days, but a lower value greater than "0" is acceptable.Verify the SUSE operating system disables account identifiers after 35 days of inactivity since the password expiration. + +Check the account inactivity value by performing the following command: + +> sudo grep -i '^inactive' /etc/default/useradd + +INACTIVE=35 + +If no output is produced, or if "INACTIVE" is not set to a value greater than "0" and less than or equal to "35", this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>SLES-15-020060The SUSE operating system must never automatically remove or disable emergency administrator accounts.<VulnDiscussion>Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. + +Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. + +To address access requirements the SUSE operating system can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001682Configure the SUSE operating system to never automatically remove or disable emergency administrator accounts. + +Replace "[Emergency_Administrator]" in the following command with the correct emergency administrator account. Run the following command as an administrator: + +> sudo chage -I -1 -M 99999 [Emergency_Administrator]Verify the SUSE operating system is configured such that emergency administrator accounts are never automatically removed or disabled. + +Note: Root is typically the "account of last resort" on a system and is also used as the example emergency administrator account. If another account is being used as the emergency administrator account, the command should be used against that account. + +Check to see if the root account password or account expires with the following command: + +> sudo chage -l [Emergency_Administrator] + +Password expires:never + +If "Password expires" or "Account expires" is set to anything other than "never", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020080The SUSE operating system must display the date and time of the last successful account logon upon logon.<VulnDiscussion>Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000052Configure the SUSE operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/login". + +Add the following line to the top of "/etc/pam.d/login": + +session required pam_lastlog.so showfailedVerify the SUSE operating system users are provided with feedback on when account accesses last occurred. + +Check that "pam_lastlog" is used and not silent with the following command: + +> grep pam_lastlog /etc/pam.d/login + +session required pam_lastlog.so showfailed + +If "pam_lastlog" is missing from "/etc/pam.d/login" file, the "silent" option is present, or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020090The SUSE operating system must not have unnecessary accounts.<VulnDiscussion>Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system so all accounts on the system are assigned to an active system, application, or user account. + +Remove accounts that do not support approved system activities or that allow for a normal user to perform administrative-level actions. + +Document all authorized accounts on the system.Verify all SUSE operating system accounts are assigned to an active system, application, or user account. + +Obtain the list of authorized system accounts from the Information System Security Officer (ISSO). + +Check the system accounts on the system with the following command: + +> more /etc/passwd +root:x:0:0:root:/root:/bin/bash +... +games:x:12:100:Games account:/var/games:/bin/bash + +Accounts such as "games" and "gopher" are not authorized accounts as they do not support authorized system functions. + +If the accounts on the system do not match the provided documentation, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020091The SUSE operating system must not have unnecessary account capabilities.<VulnDiscussion>Accounts providing no operational purpose provide additional opportunities for system compromise. Therefore all necessary non interactive accounts should not have an interactive shell assigned to them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system so that all non-interactive accounts on the system have no interactive shell assigned to them. + +Run the following command to disable the interactive shell for a specific non-interactive user account: + +> sudo usermod --shell /sbin/nologin nobodyVerify all non-interactive SUSE operating system accounts do not have an interactive shell assigned to them. + +Obtain the list of authorized system accounts from the Information System Security Officer (ISSO). + +Check the system accounts on the system with the following command: + +> awk -F: '($7 !~ "/sbin/nologin" && $7 !~ "/bin/false"){print $1 ":" $3 ":" $7}' /etc/passwd +root:0:/bin/bash +nobody:65534:/bin/bash + +If a non-interactive accounts such as "games" or "nobody" is listed with an interactive shell, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020100The SUSE operating system root account must be the only account with unrestricted access to the system.<VulnDiscussion>If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire SUSE operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Change the UID of any account on the SUSE operating system, other than the root account, that has a UID of "0". + +If the account is associated with system commands or applications, the UID should be changed to one greater than "0" but less than "1000". Otherwise, assign a UID of greater than "1000" that has not already been assigned.Verify that the SUSE operating system root account is the only account with unrestricted access to the system. + +Check the system for duplicate UID "0" assignments with the following command: + +> awk -F: '$3 == 0 {print $1}' /etc/passwd + +root + +If any accounts other than root have a UID of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020101The SUSE operating system must restrict privilege elevation to authorized personnel.<VulnDiscussion>The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your request to execute a command by checking a file, called sudoers. If the "sudoers" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Remove the following entries from the sudoers file: +ALL ALL=(ALL) ALL +ALL ALL=(ALL:ALL) ALLVerify the "sudoers" file restricts sudo access to authorized personnel. +> sudo grep -iw 'ALL' /etc/sudoers /etc/sudoers.d/* + +If the either of the following entries are returned, this is a finding: +ALL ALL=(ALL) ALL +ALL ALL=(ALL:ALL) ALLSRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>SLES-15-020102The SUSE operating system must require reauthentication when using the "sudo" command.<VulnDiscussion>Without reauthentication, users may access resources or perform tasks for which they do not have authorization. + +When operating systems provide the capability to escalate a functional capability, it is critical the organization requires the user to re-authenticate when using the "sudo" command. + +If the value is set to an integer less than 0, the user's time stamp will not expire and the user will not have to reauthenticate for privileged actions until the user's session is terminated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004895Configure the "sudo" command to require reauthentication. +Edit the /etc/sudoers file: + +> sudo visudo + +Add or modify the following line: + +Defaults timestamp_timeout=[value] + +Note: The "[value]" must be a number that is greater than or equal to "0".Verify the operating system requires re-authentication when using the "sudo" command to elevate privileges. + +> sudo grep -ir 'timestamp_timeout' /etc/sudoers /etc/sudoers.d +/etc/sudoers:Defaults timestamp_timeout=0 + +If conflicting results are returned, this is a finding. + +If "timestamp_timeout" is set to a negative number, is commented out, or no results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020103The SUSE operating system must use the invoking user's password for privilege escalation when using "sudo".<VulnDiscussion>The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates the invoking user's credentials. If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" user password. +For more information on each of the listed configurations, reference the sudoers(5) manual page.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Define the following in the Defaults section of the /etc/sudoers file or a configuration file in the /etc/sudoers.d/ directory: + +Defaults !targetpw +Defaults !rootpw +Defaults !runaspwVerify that the sudoers security policy is configured to use the invoking user's password for privilege escalation. + +> sudo egrep -ir '(rootpw|targetpw|runaspw)' /etc/sudoers /etc/sudoers.d* | grep -v '#' + +/etc/sudoers:Defaults !targetpw +/etc/sudoers:Defaults !rootpw +/etc/sudoers:Defaults !runaspw + +If conflicting results are returned, this is a finding. +If "Defaults !targetpw" is not defined, this is a finding. +If "Defaults !rootpw" is not defined, this is a finding. +If "Defaults !runaspw" is not defined, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020110All SUSE operating system local interactive user accounts, upon creation, must be assigned a home directory.<VulnDiscussion>If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to assign home directories to all new local interactive users by setting the "CREATE_HOME" parameter in "/etc/login.defs" to "yes" as follows. + +CREATE_HOME yesVerify all SUSE operating system local interactive users on the system are assigned a home directory upon creation. + +Check to see if the system is configured to create home directories for local interactive users with the following command: + +> grep -i create_home /etc/login.defs +CREATE_HOME yes + +If the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020120The SUSE operating system must display the date and time of the last successful account logon upon an SSH logon.<VulnDiscussion>Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000052Configure the SUSE operating system to provide users with feedback on when account accesses last occurred. + +Add or edit the following lines in the "/etc/ssh/sshd_config" file: + +PrintLastLog yesVerify all remote connections via SSH to the SUSE operating system display feedback on when account accesses last occurred. + +Check that "PrintLastLog" keyword in the sshd daemon configuration file is used and set to "yes" with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*printlastlog' + +PrintLastLog yes + +If the "PrintLastLog" keyword is set to "no", is missing, or is commented out, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>SLES-15-020130The SUSE operating system must enforce passwords that contain at least one uppercase character.<VulnDiscussion>Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce password complexity by requiring at least one uppercase character. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "ucredit=-1" after the third column.Verify the SUSE operating system enforces password complexity by requiring at least one uppercase character. + +Check that the operating system enforces password complexity by requiring that at least one uppercase character be used by using the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so ucredit=-1 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "ucredit=-1", this is a finding.SRG-OS-000070-GPOS-00038<GroupDescription></GroupDescription>SLES-15-020140The SUSE operating system must enforce passwords that contain at least one lowercase character.<VulnDiscussion>Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce password complexity by requiring at least one lowercase character. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "lcredit=-1" after the third column.Verify the SUSE operating system enforces password complexity by requiring that at least one lowercase character. + +Check that the operating system enforces password complexity by requiring that at least one lowercase character be used by using the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so lcredit=-1 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "lcredit=-1", this is a finding.SRG-OS-000071-GPOS-00039<GroupDescription></GroupDescription>SLES-15-020150The SUSE operating system must enforce passwords that contain at least one numeric character.<VulnDiscussion>Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce password complexity by requiring at least one numeric character. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "dcredit=-1" after the third column.Verify the SUSE operating system enforces password complexity by requiring that at least one numeric character. + +Check that the operating system enforces password complexity by requiring that at least one numeric character be used by using the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so dcredit=-1 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "dcredit=-1", this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>SLES-15-020160The SUSE operating system must require the change of at least eight of the total number of characters when passwords are changed.<VulnDiscussion>If the SUSE operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to require at least eight characters be changed between the old and new passwords during a password change with the following command: + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "difok=8" after the third column.Verify the SUSE operating system requires at least eight characters be changed between the old and new passwords during a password change. + +Check that the operating system requires at least eight characters be changed between the old and new passwords during a password change by running the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so difok=8 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "difok", or the value is less than "8", this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>SLES-15-020170The SUSE operating system must configure the Linux Pluggable Authentication Modules (PAM) to only store encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004062Configure the SUSE operating system Linux PAM to only store encrypted representations of passwords. All account passwords must be hashed with SHA512 encryption strength. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_unix.so" to contain the SHA512 keyword after third column. Remove the "nullok" option.Verify the SUSE operating system configures the Linux PAM to only store encrypted representations of passwords. All account passwords must be hashed with SHA512 encryption strength. + +Check that PAM is configured to create SHA512 hashed passwords by running the following command: + +> grep pam_unix.so /etc/pam.d/common-password +password required pam_unix.so sha512 + +If the command does not return anything or the returned line is commented out, has a second column value different from "required", or does not contain "sha512", this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>SLES-15-020180The SUSE operating system must employ FIPS 140-2-approved cryptographic hashing algorithms for all stored passwords.<VulnDiscussion>The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy. + +Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. + +Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004062CCI-000803Configure the SUSE operating system to encrypt all stored passwords with a strong cryptographic hash. + +Edit/modify the following line in the "/etc/login.defs" file and set "ENCRYPT_METHOD" to have a value of "SHA512". + +ENCRYPT_METHOD SHA512 + +Lock all interactive user accounts not using SHA512 hashing until the passwords can be regenerated.Verify the SUSE operating system requires the shadow password suite configuration be set to encrypt interactive user passwords using a strong cryptographic hash. + +Check that the interactive user account passwords are using a strong password hash with the following command: + +> sudo cut -d: -f2 /etc/shadow + +$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/ + +Password hashes "!" or "*" indicate inactive accounts not available for logon and are not evaluated. + +If any interactive user password hash does not begin with "$6", this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>SLES-15-020190The SUSE operating system must employ FIPS 140-2-approved cryptographic hashing algorithms for all stored passwords.<VulnDiscussion>The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy. + +Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. + +Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004062CCI-000803Configure the SUSE operating system to encrypt all stored passwords with a strong cryptographic hash. + +Edit/modify the following line in the "/etc/login.defs" file and set "SHA_CRYPT_MIN_ROUNDS" to a value no lower than "5000": + +SHA_CRYPT_MIN_ROUNDS 5000Verify the SUSE operating system configures the shadow password suite configuration to encrypt passwords using a strong cryptographic hash. + +Check that a minimum number of hash rounds is configured by running the following command: + +> egrep "^SHA_CRYPT_" /etc/login.defs + +If only one of "SHA_CRYPT_MIN_ROUNDS" or "SHA_CRYPT_MAX_ROUNDS" is set, and this value is below "5000", this is a finding. + +If both "SHA_CRYPT_MIN_ROUNDS" and "SHA_CRYPT_MAX_ROUNDS" are set, and the highest value for either is below "5000", this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>SLES-15-020200The SUSE operating system must be configured to create or update passwords with a minimum lifetime of 24 hours (one day).<VulnDiscussion>Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce 24 hours/one day or greater as the minimum password age. + +Edit the file "/etc/login.defs" and add or correct the following line. Replace [DAYS] with the appropriate amount of days: + +PASS_MIN_DAYS [DAYS] + +The DOD requirement is "1" but a greater value is acceptable.Verify the SUSE operating system creates or updates passwords with minimum password age of one day or greater. + +To check that the SUSE operating system enforces 24 hours/one day as the minimum password age, run the following command: + +> grep '^PASS_MIN_DAYS' /etc/login.defs + +PASS_MIN_DAYS 1 + +If no output is produced, or if "PASS_MIN_DAYS" does not have a value of "1" or greater, this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>SLES-15-020210The SUSE operating system must employ user passwords with a minimum lifetime of 24 hours (one day).<VulnDiscussion>Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce 24 hours/one day or greater as the minimum password age for user accounts. + +Change the minimum time period between password changes for each [USER] account to "1" day with the command, replacing [USER] with the user account that must be changed: + +> sudo passwd -n 1 [USER]Verify the SUSE operating system enforces a minimum time period between password changes for each user account of one day or greater. + +Check the minimum time period between password changes for each user account with the following command: + +> sudo awk -F: '$4 < 1 {print $1 ":" $4}' /etc/shadow + +smithj:1 + +If any results are returned that are not associated with a system account, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>SLES-15-020220The SUSE operating system must be configured to create or update passwords with a maximum lifetime of 60 days.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the SUSE operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the SUSE operating system passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce a maximum password age of 60 days or less. + +Edit the file "/etc/login.defs" and add or correct the following line. Replace [DAYS] with the appropriate amount of days: + +PASS_MAX_DAYS [DAYS] + +The DOD requirement is 60 days or less (greater than zero, as zero days will lock the account immediately).Verify that the SUSE operating system is configured to create or update passwords with a maximum password age of 60 days or less. + +Check that the SUSE operating system enforces 60 days or less as the maximum password age with the following command: + +> grep '^PASS_MAX_DAYS' /etc/login.defs + +The DOD requirement is "60" days or less (greater than zero, as zero days will lock the account immediately). + +If no output is produced, or if "PASS_MAX_DAYS" is not set to "60" days or less, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>SLES-15-020230The SUSE operating system must employ user passwords with a maximum lifetime of 60 days.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the SUSE operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the SUSE operating system passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce a maximum password age of each [USER] account to 60 days. The command in the check text will give a list of users that need to be updated to be in compliance: + +> sudo passwd -x 60 [USER] + +The DOD requirement is 60 days.Verify that the SUSE operating system enforces a maximum user password age of 60 days or less. + +Check that the SUSE operating system enforces 60 days or less as the maximum user password age with the following command: + +> sudo awk -F: '$5 > 60 || $5 == "" {print $1 ":" $5}' /etc/shadow + +If any results are returned that are not associated with a system account, this is a finding.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>SLES-15-020260The SUSE operating system must employ passwords with a minimum of 15 characters.<VulnDiscussion>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. + +Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps determine strength and how long it takes to crack a password. Use of more characters in a password helps exponentially increase the time and/or resources required to compromise the password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce a minimum 15-character password length. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "minlen=15" after the third column. + +The DOD standard requires a minimum 15-character password length.Verify the SUSE operating system enforces a minimum 15-character password length. + +Check that the operating system enforces a minimum 15-character password length with the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so minlen=15 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "minlen" value, or the value is less than "15", this is a finding.SRG-OS-000266-GPOS-00101<GroupDescription></GroupDescription>SLES-15-020270The SUSE operating system must enforce passwords that contain at least one special character.<VulnDiscussion>Use of a complex password helps increase the time and resources required to compromise the password. Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. + +Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. + +Special characters are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004066Configure the SUSE operating system to enforce password complexity by requiring at least one special character. + +Edit "/etc/pam.d/common-password" and edit the line containing "pam_cracklib.so" to contain the option "ocredit=-1" after the third column.Verify the SUSE operating system enforces password complexity by requiring at least one special character. + +Check that the operating system enforces password complexity by requiring at least one special character using the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so ocredit=-1 + +If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain "ocredit=-1", this is a finding.SRG-OS-000480-GPOS-00225<GroupDescription></GroupDescription>SLES-15-020290The SUSE operating system must prevent the use of dictionary words for passwords.<VulnDiscussion>If the SUSE operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to prevent the use of dictionary words for passwords. + +Edit "/etc/pam.d/common-password" and add the following line: + +password requisite pam_cracklib.soVerify the SUSE operating system prevents the use of dictionary words for passwords. + +Check that the SUSE operating system prevents the use of dictionary words for passwords with the following command: + +> grep pam_cracklib.so /etc/pam.d/common-password +password requisite pam_cracklib.so + +If the command does not return anything, or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020300The SUSE operating system must not be configured to allow blank or null passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not allow blank or null passwords. + +Remove any instances of the "nullok" option in "/etc/pam.d/common-auth" and "/etc/pam.d/common-password" to prevent logons with empty passwords.Verify the SUSE operating system is not configured to allow blank or null passwords. + +Check that blank or null passwords cannot be used by running the following command: + +> grep pam_unix.so /etc/pam.d/* | grep nullok + +If this produces any output, it may be possible to log on with accounts with empty passwords. + +If null passwords can be used, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>SLES-15-030000The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation mitigates this risk. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000274-GPOS-00104, SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000303-GPOS-00120, SRG-OS-000463-GPOS-00207, SRG-OS-000304-GPOS-00121, SRG-OS-000470-GPOS-00214, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000015CCI-000018CCI-000172CCI-001403CCI-002130Configure the SUSE operating system to generate an audit record when all modifications to the "/etc/passwd" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /etc/passwd -p wa -k account_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when all modifications occur to the "/etc/passwd" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/passwd' + +-w /etc/passwd -p wa -k account_mod + +If the command does not return a line, this is a finding. + +Note: The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>SLES-15-030010The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation mitigates this risk. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000018CCI-000172CCI-001403CCI-002130CCI-000015Configure the SUSE operating system to generate an audit record when all modifications to the "/etc/group" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /etc/group -p wa -k account_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when modifications occur to the "/etc/group" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/group' + +-w /etc/group -p wa -k account_mod + +If the command does not return a line, this is a finding. + +Note: The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>SLES-15-030020The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation mitigates this risk. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000018CCI-000172CCI-001403CCI-002130CCI-000015Configure the SUSE operating system to generate an audit record when all modifications to the "/etc/shadow" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /etc/shadow -p wa -k account_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when modifications occur to the "/etc/shadow" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/shadow' + +-w /etc/shadow -p wa -k account_mod + +If the command does not return a line, this is a finding. + +Note: The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>SLES-15-030030The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation mitigates this risk. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000018CCI-000172CCI-001403CCI-002130CCI-000015Configure the SUSE operating system to generate an audit record when all modifications to the "/etc/security/opasswd" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /etc/security/opasswd -p wa -k account_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when modifications occur to the "/etc/security/opasswd" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/security/opasswd' + +-w /etc/security/opasswd -p wa -k account_mod + +If the command does not return a line, this is a finding. + +Note: The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>SLES-15-030040The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation mitigates this risk. + +To address access requirements, many SUSE operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000018CCI-000172CCI-001403CCI-002130Configure the SUSE operating system to generate an audit record when all modifications to the "/etc/gshadow" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /etc/gshadow -p wa -k account_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when all modifications occur to the "/etc/gshadow" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/gshadow' + +-w /etc/gshadow -p wa -k account_mod + +If the command does not return a line, this is a finding. + +Notes: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030050SUSE operating system audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.<VulnDiscussion>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. + +Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. + +Associating event types with detected events in the SUSE operating system audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured SUSE operating system. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000131CCI-000132CCI-000133CCI-000134CCI-000135CCI-000154CCI-000158CCI-001464CCI-001487CCI-001876CCI-002884Enable the SUSE operating system auditd service by performing the following commands: + +> sudo systemctl enable auditd.service +> sudo systemctl start auditd.serviceVerify the SUSE operating system produces audit records. + +Check that the SUSE operating system produces audit records by running the following command to determine the current status of the auditd service: + +> systemctl is-active auditd.service +active + +> systemctl is-enabled auditd.service +enabled + +If the service is not active or not enabled, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030060The SUSE operating system must generate audit records for all uses of the ssh-keysign command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "ssh-keysign" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh-keysign + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "ssh-keysign" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/lib/ssh/ssh-keysign' + +-a always,exit -S all -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh-keysign + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030070The SUSE operating system must generate audit records for all uses of the passwd command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "passwd" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "passwd" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/passwd' + +-a always,exit -S all -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-passwd + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030080The SUSE operating system must generate audit records for all uses of the gpasswd command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "gpasswd" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "gpasswd" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/gpasswd' + +-a always,exit -S all -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-gpasswd + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030090The SUSE operating system must generate audit records for all uses of the newgrp command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "newgrp" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-newgrp + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "newgrp" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/newgrp' + +-a always,exit -S all -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-newgrp + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030100The SUSE operating system must generate audit records for a uses of the chsh command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chsh" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chsh + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chsh" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chsh' + +-a always,exit -S all -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chsh + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030110The SUSE operating system must generate audit records for all uses of the unix_chkpwd or unix2_chkpwd commands.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "unix_chkpwd" and "unix2_chkpwd" commands. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-unix-chkpwd +-a always,exit -F path=/sbin/unix2_chkpwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-unix2-chkpwd + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "unix_chkpwd" or "unix2_chkpwd" commands. + +Check that the commands are being audited by performing the following command: + +> sudo auditctl -l | egrep -w "(unix_chkpwd|unix2_chkpwd)" + +-a always,exit -S all -F path=/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-unix-chkpwd +-a always,exit -S all -F path=/sbin/unix2_chkpwd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-unix2-chkpwd + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030120The SUSE operating system must generate audit records for all uses of the chage command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chage" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "chage" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chage' + +-a always,exit -S all -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chage + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030130The SUSE operating system must generate audit records for all uses of the crontab command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "crontab" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "crontab" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/crontab' + +-a always,exit -S all -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-crontab + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030140The SUSE operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate audit records when successful/unsuccessful attempts to access the "/etc/sudoers" file and files in the "/etc/sudoers.d/" directory. + +Add or update the following rule in "/etc/audit/rules.d/audit.rules": + +-w /etc/sudoers -p wa -k privileged-actions + +-w /etc/sudoers.d -p wa -k privileged-actions + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the operating system generates audit records when successful/unsuccessful attempts to access the "/etc/sudoers" file and files in the "/etc/sudoers.d/" directory. + +Check that the file and directory is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/etc/sudoers' + +-w /etc/sudoers -p wa -k privileged-actions +-w /etc/sudoers.d -p wa -k privileged-actions + +If the commands do not return output that match the examples, this is a finding. + +Notes: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030150The SUSE operating system must generate audit records for all uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000461-GPOS-00205, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep 'open\|truncate\|creat' + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access + +-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access +-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access + +If both the "b32" and "b64" audit rules are not defined for the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" syscalls, this is a finding. + +If the output does not produce rules containing "-F exit=-EPERM", this is a finding. + +If the output does not produce rules containing "-F exit=-EACCES", this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030190The SUSE operating system must generate audit records for all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "setxattr", "fsetxattr", "lsetxattr","removexattr", "fremovexattr", and "lremovexattr" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep xattr + +-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod + +If both the "b32" and "b64" audit rules are not defined for the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" syscalls, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030250The SUSE operating system must generate audit records for all uses of the chown, fchown, fchownat, and lchown system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chown", "fchown", "fchownat", and "lchown" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chown", "fchown", "fchownat", and "lchown" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep chown + +-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_mod + +If both the "b32" and "b64" audit rules are not defined for the "chown", "fchown", "fchownat", and "lchown" syscalls, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030290The SUSE operating system must generate audit records for all uses of the chmod, fchmod, and fchmodat system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chmod", "fchmod", and "fchmodat" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chmod", "fchmod" a,nd "fchmodat" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep chmod + +-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_mod + +If both the "b32" and "b64" audit rules are not defined for the "chmod", "fchmod", and "fchmodat" syscalls, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030330The SUSE operating system must generate audit records for all uses of the sudoedit command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "sudoedit" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-sudoedit + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify an audit record is generated for all uses of the "sudoedit" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/sudoedit' + +-a always,exit -S all -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-sudoedit + +If the command does not return any output or the returned line is commented out, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030340The SUSE operating system must generate audit records for all uses of the chfn command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chfn" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chfn + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chfn" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chfn' + +-a always,exit -S all -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chfn + +If the command does not return any output or the returned line is commented out, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030350The SUSE operating system must generate audit records for all uses of the mount system call.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "mount" system call. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount +-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "mount" system call. + +Check that the system call is being audited by performing the following command: + +> sudo auditctl -l | grep -w 'mount' + +-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -k privileged-mount +-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=-1 -k privileged-mount + +If both the "b32" and "b64" audit rules are not defined for the "mount" syscall, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030360The SUSE operating system must generate audit records for all uses of the umount system call.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "umount" and "umount2" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=4294967295 -k privileged-umount +-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=4294967295 -k privileged-umount +-a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=4294967295 -k privileged-umount + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "umount" and "umount2" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep 'umount' + +-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=-1 -k privileged-umount +-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=-1 -k privileged-umount +-a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=-1 -k privileged-umount + +If both the "b32" and "b64" audit rules are not defined for the "umount" syscall, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030370The SUSE operating system must generate audit records for all uses of the ssh-agent command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "ssh-agent" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh-agent + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "ssh-agent" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/ssh-agent' + +-a always,exit -S all -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh-agent + +If the command does not return any output or the returned line is commented out, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030380The SUSE operating system must generate audit records for all uses of the insmod command.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. + +DoD has defined the following list of events for which the SUSE operating system will provide an audit record generation capability: + +1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); + +2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; + +3) All account creations, modifications, disabling, and terminations; and + +4) All kernel module load, unload, and restart actions. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to audit the execution of the module management program "insmod" by adding the following line to "/etc/audit/rules.d/audit.rules": + +-w /sbin/insmod -p x -k modules + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system is generates an audit record for all uses of the "insmod" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/sbin/insmod' + +-w /sbin/insmod -p x -k modules + +If the system is configured to audit the execution of the module management program "insmod", the command will return a line. + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030390The SUSE operating system must generate audit records for all uses of the rmmod command.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. + +DoD has defined the following list of events for which the SUSE operating system will provide an audit record generation capability: + +1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); + +2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; + +3) All account creations, modifications, disabling, and terminations; and + +4) All kernel module load, unload, and restart actions. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to audit the execution of the module management program "rmmod" by adding the following line to "/etc/audit/rules.d/audit.rules": + +-w /sbin/rmmod -p x -k modules + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "rmmod" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/sbin/rmmod' + +-w /sbin/rmmod -p x -k modules + +If the system is configured to audit the execution of the module management program "rmmod", the command will return a line. + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030400The SUSE operating system must generate audit records for all uses of the modprobe command.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. + +DoD has defined the following list of events for which the SUSE operating system will provide an audit record generation capability: + +1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); + +2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; + +3) All account creations, modifications, disabling, and terminations; and + +4) All kernel module load, unload, and restart actions. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to audit the execution of the module management program "modprobe" by adding the following line to "/etc/audit/rules.d/audit.rules": + +-w /sbin/modprobe -p x -k modules + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "modprobe" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/sbin/modprobe' + +-w /sbin/modprobe -p x -k modules + +If the system is configured to audit the execution of the module management program "modprobe", the command will return a line. + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030410The SUSE operating system must generate audit records for all uses of the kmod command.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. + +DoD has defined the following list of events for which the SUSE operating system will provide an audit record generation capability: + +1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); + +2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; + +3) All account creations, modifications, disabling, and terminations; and + +4) All kernel module load, unload, and restart actions. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to audit the execution of the module management program "kmod" by adding the following line to "/etc/audit/rules.d/audit.rules": + +-w /usr/bin/kmod -p x -k modules + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "kmod" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/kmod' + +-w /usr/bin/kmod -p x -k modules + +If the system is configured to audit the execution of the module management program "kmod", the command will return a line. + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030420The SUSE operating system must generate audit records for all uses of the chmod command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chmod" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chmod -F perm=x -F auid>=1000 -F auid!=4294967295 -k prim_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chmod" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chmod' + +-a always,exit -S all -F path=/usr/bin/chmod -F perm=x -F auid>=1000 -F auid!=-1 -k prim_mod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030430The SUSE operating system must generate audit records for all uses of the setfacl command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "setfacl" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k prim_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "setfacl" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/setfacl' + +-a always,exit -S all -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -k prim_mod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030440The SUSE operating system must generate audit records for all uses of the chacl command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chacl" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k prim_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chacl" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chacl' + +-a always,exit -S all -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -k prim_mod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030450The SUSE operating system must generate audit records for all uses of the chcon command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "chcon" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -k prim_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "chcon" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/chcon' + +-a always,exit -S all -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -k prim_mod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030460The SUSE operating system must generate audit records for all uses of the rm command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "rm" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/rm -F perm=x -F auid>=1000 -F auid!=4294967295 -k prim_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "rm" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/rm' + +-a always,exit -S all -F path=/usr/bin/rm -F perm=x -F auid>=1000 -F auid!=-1 -k prim_mod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030470The SUSE operating system must generate audit records for all modifications to the tallylog file must generate an audit record.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for any all modifications to the "tallylog" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /var/log/tallylog -p wa -k logins + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when all modifications to the "tallylog" file occur. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/var/log/tallylog' + +-w /var/log/tallylog -p wa -k logins + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030480The SUSE operating system must generate audit records for all modifications to the lastlog file.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for any all modifications to the "lastlog" file occur. + +Add or update the following rule to "/etc/audit/rules.d/audit.rules": + +-w /var/log/lastlog -p wa -k logins + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record when all modifications to the "lastlog" file occur. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/var/log/lastlog' + +-w /var/log/lastlog -p wa -k logins + +If the command does not return a line, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030490The SUSE operating system must generate audit records for all uses of the passmass command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "passmass" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/passmass -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passmass + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "passmass" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/passmass' + +-a always,exit -S all -F path=/usr/bin/passmass -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-passmass + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030500The SUSE operating system must generate audit records for all uses of the usermod command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "usermod" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "usermod" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/sbin/usermod' + +-a always,exit -S all -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-usermod + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030510The SUSE operating system must generate audit records for all uses of the pam_timestamp_check command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "pam_timestamp_check" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "pam_timestamp_check" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/sbin/pam_timestamp_check' + +-a always,exit -S all -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-pam_timestamp_check + +If the command does not return any output, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030520The SUSE operating system must generate audit records for all uses of the delete_module system call.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "delete_module" system call. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=4294967295 -k unload_module +-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=4294967295 -k unload_module + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "delete_module" system call. + +Check that the system call is being audited by performing the following command: + +> sudo auditctl -l | grep -w 'delete_module' + +-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=-1 -k unload_module +-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -k unload_module + +If both the "b32" and "b64" audit rules are not defined for the "unload_module" syscall, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030530The SUSE operating system must generate audit records for all uses of the init_module and finit_module system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "init_module" and "finit_module" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=4294967295 -k moduleload +-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=4294967295 -k moduleload + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "init_module" and "finit_module" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep init_module + +-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k moduleload +-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k moduleload + +If both the "b32" and "b64" audit rules are not defined for the init_module" and "finit_module" syscalls, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030550The SUSE operating system must generate audit records for all uses of the su command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000042-GPOS-00020</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "su" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "su" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/su' + +-a always,exit -S all -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-priv_change + +If the command does not return any output or the returned line is commented out, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>SLES-15-030560The SUSE operating system must generate audit records for all uses of the sudo command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. + +At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. + +Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000042-GPOS-00020</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000130CCI-000169CCI-000172CCI-002884Configure the SUSE operating system to generate an audit record for all uses of the "sudo" command. + +Add or update the following rules in the "/etc/audit/rules.d/audit.rules" file: + +-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-sudo + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any use of the "sudo" command. + +Check that the command is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/usr/bin/sudo' + +-a always,exit -S all -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-sudo + +If the command does not return any output, or the returned line is commented out, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>SLES-15-030570The Information System Security Officer (ISSO) and System Administrator (SA), at a minimum, must be alerted of a SUSE operating system audit processing failure event.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. + +Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. + +This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000139Configure the auditd service to notify the administrators in the event of a SUSE operating system audit processing failure. + +Edit the following line in "/etc/audit/auditd.conf" to ensure that administrators are notified via email for those situations: + +action_mail_acct = rootVerify the administrators are notified in the event of a SUSE operating system audit processing failure by inspecting "/etc/audit/auditd.conf". + +Check if the system is configured to send email to an account when it needs to notify an administrator with the following command: + +> sudo grep action_mail /etc/audit/auditd.conf + +action_mail_acct = root + +If the value of the "action_mail_acct" keyword is not set to "root" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the returned line is commented out, this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>SLES-15-030580The Information System Security Officer (ISSO) and System Administrator (SA), at a minimum, must have mail aliases to be notified of a SUSE operating system audit processing failure.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. + +Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. + +This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000139Configure the auditd service to notify the administrators in the event of a SUSE operating system audit processing failure. + +Configure an alias value for the postmaster with the following command: + +> sudo sh -c 'echo "postmaster: root" >> /etc/aliases' + +Configure an alias for root that forwards to a monitored email address with the following command: + +> sudo sh -c 'echo "root: box@server.mil" >> /etc/aliases' + +The following command must be run to implement changes to the /etc/aliases file: + +> sudo newaliasesVerify the administrators are notified in the event of a SUSE operating system audit processing failure by checking that "/etc/aliases" has a defined value for root. + +> grep -i "^postmaster:" /etc/aliases + +postmaster: root + +If the above command does not return a value of "root", or the output is commented out, this is a finding + +Verify the alias for root forwards to a monitored e-mail account: + +> grep -i "^root:" /etc/aliases +root: person@server.mil + +If the alias for root does not forward to a monitored e-mail account, or the output is commented out, this is a finding.SRG-OS-000047-GPOS-00023<GroupDescription></GroupDescription>SLES-15-030590The SUSE operating system audit system must take appropriate action when the audit storage volume is full.<VulnDiscussion>It is critical that when the SUSE operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Responses to audit failure depend on the nature of the failure mode. + +When availability is an overriding concern, other approved actions in response to an audit failure are as follows: + +1) If the failure was caused by the lack of audit record storage capacity, the SUSE operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. + +2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the SUSE operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000140Configure the SUSE operating system to shut down by default upon audit failure (unless availability is an overriding concern). + +Add or update the following line (depending on configuration "disk_full_action" can be set to "SYSLOG", "SINGLE", or "HALT" depending on configuration) in "/etc/audit/auditd.conf" file: + +disk_full_action = HALTVerify the SUSE operating system takes the appropriate action when the audit storage volume is full. + +Check that the SUSE operating system takes the appropriate action when the audit storage volume is full with the following command: + +> sudo grep disk_full_action /etc/audit/auditd.conf + +disk_full_action = SYSLOG + +If the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>SLES-15-030600The SUSE operating system must protect audit rules from unauthorized modification.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000162CCI-000163CCI-000164Configure the SUSE operating system to protect audit rules from unauthorized modification. + +Add or update the following rules in "/etc/permissions.local": + +/var/log/audit root:root 600 +/var/log/audit/audit.log root:root 600 +/etc/audit/audit.rules root:root 640 +/etc/audit/rules.d/audit.rules root:root 640 + +Set the correct permissions with the following command: + +> sudo chkstat --set /etc/permissions.localVerify that the SUSE operating system protects audit rules from unauthorized modification. + +Check that "permissions.local" file contains the correct permissions rules with the following command: + +> grep -i audit /etc/permissions.local + +/var/log/audit root:root 600 +/var/log/audit/audit.log root:root 600 +/etc/audit/audit.rules root:root 640 +/etc/audit/rules.d/audit.rules root:root 640 + +If the command does not return any output, this is a finding. + +Check that all of the audit information files and folders have the correct permissions with the following command: + +> sudo chkstat /etc/permissions.local + +If the command returns any output, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>SLES-15-030620The SUSE operating system audit tools must have the proper permissions configured to protect against unauthorized access.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +SUSE operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the access to audit tools. + +Audit tools include but are not limited to vendor-provided and open-source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. + +Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001493CCI-001494CCI-001495Configure the SUSE operating system audit tools to have proper permissions set in the permissions profile to protect from unauthorized access. + +Edit the file "/etc/permissions.local" and insert the following text: + +/usr/sbin/audispd root:root 0750 +/usr/sbin/auditctl root:root 0750 +/usr/sbin/auditd root:root 0750 +/usr/sbin/ausearch root:root 0755 +/usr/sbin/aureport root:root 0755 +/usr/sbin/autrace root:root 0750 +/usr/sbin/augenrules root:root 0750 + +Set the correct permissions with the following command: + +> sudo chkstat --set /etc/permissions.localVerify that the SUSE operating system audit tools have the proper permissions configured in the permissions profile to protect from unauthorized access. + +Check that "permissions.local" file contains the correct permissions rules with the following command: + +> grep "^/usr/sbin/au" /etc/permissions.local + +/usr/sbin/audispd root:root 0750 +/usr/sbin/auditctl root:root 0750 +/usr/sbin/auditd root:root 0750 +/usr/sbin/ausearch root:root 0755 +/usr/sbin/aureport root:root 0755 +/usr/sbin/autrace root:root 0750 +/usr/sbin/augenrules root:root 0750 + +If the command does not return any output, this is a finding. + +Check that all of the audit information files and folders have the correct permissions with the following command: + +> sudo chkstat /etc/permissions.local + +If the command returns any output, this is a finding.SRG-OS-000278-GPOS-00108<GroupDescription></GroupDescription>SLES-15-030630The SUSE operating system file integrity tool must be configured to protect the integrity of the audit tools.<VulnDiscussion>Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. + +Audit tools include but are not limited to vendor-provided and open-source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. + +It is not uncommon for attackers to replace the audit tools or inject code into the existing tools to provide the capability to hide or erase system activity from the audit logs. + +To address this risk, audit tools must be cryptographically signed to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001496Configure the SUSE operating system file integrity tool to protect the integrity of the audit tools. + +Add or update the following lines to "/etc/aide.conf" to protect the integrity of the audit tools: + +# audit tools +/usr/sbin/auditctl p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/auditd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/ausearch p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/aureport p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/autrace p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/audispd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/augenrules p+i+n+u+g+s+b+acl+selinux+xattrs+sha512Verify that the SUSE operating system file integrity tool is configured to protect the integrity of the audit tools. + +Check that AIDE is properly configured to protect the integrity of the audit tools by running the following command: + +> sudo grep /usr/sbin/au /etc/aide.conf + +/usr/sbin/auditctl p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/auditd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/ausearch p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/aureport p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/autrace p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/audispd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 +/usr/sbin/augenrules p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 + +If AIDE is properly configured to protect the integrity of the audit tools, all lines listed above will be returned from the command. + +If one or more lines are missing, or is commented out, this is a finding.SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>SLES-15-030640The SUSE operating system must generate audit records for all uses of the privileged functions.<VulnDiscussion>Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000358-GPOS-00145, SRG-OS-000359-GPOS-00146, SRG-OS-000365-GPOS-00152</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-003938CCI-001875CCI-001877CCI-001878CCI-001879CCI-001880CCI-001881CCI-001882CCI-001889CCI-001914CCI-002234Configure the SUSE operating system to generate an audit record for any privileged use of the "execve" system call. + +Add or update the following rules in "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid +-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid +-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid +-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for any privileged use of the "execve" system call. + +> sudo auditctl -l | grep -w 'execve' + +-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid +-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid +-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid +-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid + +If both the "b32" and "b64" audit rules for "SUID" files are not defined, this is a finding. + +If both the "b32" and "b64" audit rules for "SGID" files are not defined, this is a finding. + +Note: The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000337-GPOS-00129<GroupDescription></GroupDescription>SLES-15-030650The SUSE operating system must have the auditing package installed.<VulnDiscussion>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. + +Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. + +Associating event types with detected events in the SUSE operating system audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured SUSE operating system. + +Satisfies: SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000358-GPOS-00145, SRG-OS-000359-GPOS-00146, SRG-OS-000365-GPOS-00152, SRG-OS-000474-GPOS-00219, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000172CCI-003938CCI-001875CCI-001877CCI-001878CCI-001879CCI-001880CCI-001881CCI-001882CCI-001889CCI-001914The SUSE operating system auditd package must be installed on the system. If it is not installed, use the following command to install it: + +> sudo zypper in auditVerify the SUSE operating system auditing package is installed. + +Check that the "audit" package is installed by performing the following command: + +> zypper info audit | grep Installed + +i | audit | User Space Tools for 2.6 Kernel Auditing + +If the package "audit" is not installed on the system, then this is a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>SLES-15-030660The SUSE operating system must allocate audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.<VulnDiscussion>To ensure SUSE operating systems have a sufficient storage capacity in which to write the audit logs, SUSE operating systems need to be able to allocate audit record storage capacity. + +The task of allocating audit record storage capacity is usually performed during initial installation of the SUSE operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001849Allocate enough storage capacity for at least one week of SUSE operating system audit records when audit records are not immediately sent to a central audit record storage facility. + +If audit records are stored on a partition made specifically for audit records, use the "YaST2 - Partitioner" program (installation and configuration tool for Linux) to resize the partition with sufficient space to contain one week of audit records. + +If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient amount of space will need be to be created. The new partition can be created using the "YaST2 - Partitioner" program on the system.Verify the SUSE operating system allocates audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. + +Determine to which partition the audit records are being written with the following command: + +> sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Check the size of the partition that audit records are written to (with the example being /var/log/audit/) with the following command: + +> df -h /var/log/audit/ +/dev/sda2 24G 10.4G 13.6G 43% /var + +If the audit records are not written to a partition made specifically for audit records (/var/log/audit is a separate partition), determine the amount of space being used by other files in the partition with the following command: + +> sudo du -sh [audit_partition] +1.8G /var/log/audit + +The partition size needed to capture a week of audit records is based on the activity level of the system and the total storage capacity available. In normal circumstances, 10.0 GB of storage space for audit records will be sufficient. + +If the audit record partition is not allocated sufficient storage capacity, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>SLES-15-030670The audit-audispd-plugins must be installed on the SUSE operating system.<VulnDiscussion>The audit-audispd-plugins must be installed on the SUSE operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Install the "audit-audispd-plugins" package on the SUSE operating system by running the following command: + +> sudo zypper install audit-audispd-plugins + +In "/etc/audisp/plugins.d/au-remote.conf", change the value of "active" to "yes", or add "active = yes" if no such setting exists in the file.Verify that the "audit-audispd-plugins" package is installed on the SUSE operating system. + +Check that the "audit-audispd-plugins" package is installed on the SUSE operating system with the following command: + +> zypper info audit-audispd-plugins | grep Installed + +If the "audit-audispd-plugins" package is not installed, this is a finding. + +Verify the "au-remote" plugin is enabled with the following command: + +> sudo grep -i active /etc/audisp/plugins.d/au-remote.conf +active = yes + +If "active" is missing, commented out, or is not set to "yes", this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>SLES-15-030680The SUSE operating system audit event multiplexor must be configured to use Kerberos.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Allowing devices and users to connect to or from the system without first authenticating them allows untrusted access and can lead to a compromise or attack. Audit events that may include sensitive data must be encrypted prior to transmission. Kerberos provides a mechanism to provide both authentication and encryption for audit event records.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Configure the SUSE operating system audit event multiplexor to use Kerberos by editing the "/etc/audisp/audisp-remote.conf" file. + +Edit or add the following line to match the text below: + +enable_krb5 = yesDetermine if the SUSE operating system audit event multiplexor is configured to use Kerberos by running the following command: + +> sudo grep enable_krb5 /etc/audisp/audisp-remote.conf +enable_krb5 = yes + +If "enable_krb5" is not set to "yes", or is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>SLES-15-030690Audispd must off-load audit records onto a different system or media from the SUSE operating system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Configure the SUSE operating system "/etc/audisp/audisp-remote.conf" file to off-load audit records onto a different system or media by adding or editing the following line with the correct IP address: + +remote_server = [IP ADDRESS]Verify "audispd" off-loads audit records onto a different system or media from the SUSE operating system being audited. + +Check if "audispd" is configured to off-load audit records onto a different system or media from the SUSE operating system by running the following command: + +> sudo grep remote_server /etc/audisp/audisp-remote.conf +remote_server = 192.168.1.101 + +If "remote_server" is not set to an external server or media, or is commented out, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>SLES-15-030700The SUSE operating system auditd service must notify the System Administrator (SA) and Information System Security Officer (ISSO) immediately when audit storage capacity is 75 percent full.<VulnDiscussion>If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001855Check the system configuration to determine the partition to which the audit records are written: + +> sudo grep -iw log_file /etc/audit/auditd.conf + +Determine the size of the partition to which audit records are written (e.g., "/var/log/audit/"): + +> df -h /var/log/audit/ + +Set the value of the "space_left" keyword in "/etc/audit/auditd.conf" to 25 percent of the partition size.Determine if the SUSE operating system auditd is configured to notify the SA and ISSO when the audit record storage volume reaches 75 percent of the storage capacity. + +Check the system configuration to determine the partition to which audit records are written using the following command: + +> sudo grep -iw log_file /etc/audit/auditd.conf +log_file = /var/log/audit/audit.log + +Check the size of the partition to which audit records are written (e.g., "/var/log/audit/"): + +> df -h /var/log/audit/ +/dev/sda2 24G 10.4G 13.6G 43% /var + +If the audit records are not being written to a partition specifically created for audit records (in this example "/var/log/audit" is a separate partition), use the following command to determine the amount of space other files in the partition currently occupy: + +> sudo du -sh <partition> +1.8G /var/log/audit + +Determine the threshold for the system to take action when 75 percent of the repository maximum audit record storage capacity is reached: + +> sudo grep -iw space_left /etc/audit/auditd.conf +space_left = 225 + +If the value of the "space_left" keyword is not set to 25 percent of the total partition size, this is a finding.SRG-OS-000468-GPOS-00212<GroupDescription></GroupDescription>SLES-15-030740The SUSE operating system must generate audit records for all uses of the unlink, unlinkat, rename, renameat, and rmdir system calls.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter). The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary, since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000172Configure the SUSE operating system to generate an audit record for all uses of the "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=4294967295 -k perm_mod +-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=4294967295 -k perm_mod + +To reload the rules file, restart the audit daemon: + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for all uses of the "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls. + +Check that the system calls are being audited by performing the following command: + +> sudo auditctl -l | grep 'unlink\|rename\|rmdir' + +-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k perm_mod +-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k perm_mod + +If both the "b32" and "b64" audit rules are not defined for the "unlink", "unlinkat", "rename", "renameat", and "rmdir" syscalls, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>SLES-15-030760The SUSE operating system must generate audit records for the /run/utmp file.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000172Configure the SUSE operating system to generate an audit record for the "/run/utmp" file. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-w /run/utmp -p wa -k login_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for the "/run/utmp" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/run/utmp' + +-w /run/utmp -p wa -k login_mod + +If the command does not return a line that match the example, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>SLES-15-030770The SUSE operating system must generate audit records for the /var/log/wtmp file.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000172Configure the SUSE operating system to generate an audit record for the "/var/log/wtmp" file. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-w /var/log/wtmp -p wa -k login_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for the "/var/log/wtmp" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/var/log/wtmp' + +-w /var/log/wtmp -p wa -k login_mod + +If the command does not return a line that matches the example, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>SLES-15-030780The SUSE operating system must generate audit records for the /var/log/btmp file.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. + +Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000172Configure the SUSE operating system to generate an audit record for the "/var/log/btmp" file. + +Add or update the following rules to "/etc/audit/rules.d/audit.rules": + +-w /var/log/btmp -p wa -k login_mod + +To reload the rules file, restart the audit daemon + +> sudo systemctl restart auditd.service + +or issue the following command: + +> sudo augenrules --loadVerify the SUSE operating system generates an audit record for the "/var/log/btmp" file. + +Check that the file is being audited by performing the following command: + +> sudo auditctl -l | grep -w '/var/log/btmp' + +-w /var/log/btmp -p wa -k login_mod + +If the command does not return a line that matches the example, this is a finding. + +Note: +The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>SLES-15-030790The SUSE operating system must off-load audit records onto a different system or media from the system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Configure the SUSE operating system to take the appropriate action if it cannot off-load audit records to a different system or storage media from the system being audited due to a network failure. + +Uncomment the "network_failure_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt". See the example below: + +network_failure_action = syslogVerify what action the audit system takes if it cannot off-load audit records to a different system or storage media from the SUSE operating system being audited. + +Check the action that the audit system takes in the event of a network failure with the following command: + +> sudo grep -i "network_failure_action" /etc/audisp/audisp-remote.conf + +network_failure_action = syslog + +If the "network_failure_action" option is not set to "syslog", "single", or "halt" or the line is commented out, this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>SLES-15-030800Audispd must take appropriate action when the SUSE operating system audit storage is full.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. + +Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001851Configure the SUSE operating system to take the appropriate action if the audit storage is full. + +Add, edit, or uncomment the "disk_full_action" option in "/etc/audisp/audisp-remote.conf". Set it to "syslog", "single" or "halt" as in the example below: + +disk_full_action = syslogVerify the audit system off-loads audit records if the SUSE operating system storage volume becomes full. + +Check that the records are properly off-loaded to a remote server with the following command: + +> sudo grep -i "disk_full_action" /etc/audisp/audisp-remote.conf +disk_full_action = syslog + +If "disk_full_action" is not set to "syslog", "single", or "halt" or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-030810The SUSE operating system must use a separate file system for the system audit data path.<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Migrate the SUSE operating system audit data path onto a separate file system.Verify that the SUSE operating system has a separate file system/partition for the system audit data path. + +Check that a file system/partition has been created for the system audit data path with the following command: + +Note: "/var/log/audit" is used as the example as it is a common location. + +> grep /var/log/audit /etc/fstab +UUID=3645951a /var/log/audit ext4 defaults 1 2 + +If a separate entry for the system audit data path (in this example the "/var/log/audit" path) does not exist, ask the System Administrator if the system audit logs are being written to a different file system/partition on the system and then grep for that file system/partition. + +If a separate file system/partition does not exist for the system audit data path, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-030820The SUSE operating system must not disable syscall auditing.<VulnDiscussion>By default, the SUSE operating system includes the "-a task,never" audit rule as a default. This rule suppresses syscall auditing for all tasks started with this rule in effect. Because the audit daemon processes the "audit.rules" file from the top down, this rule supersedes all other defined syscall rules; therefore no syscall auditing can take place on the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Remove the "-a task,never" rule from the /etc/audit/rules.d/audit.rules file. + +The audit daemon must be restarted for the changes to take effect. + +> sudo systemctl restart auditd.serviceVerify syscall auditing has not been disabled: + +> auditctl -l | grep -i "a task,never" + +If any results are returned, this is a finding. + +Verify the default rule "-a task,never" is not statically defined : + +> grep -rv "^#" /etc/audit/rules.d/ | grep -i "a task,never" + +If any results are returned, this is a finding.SRG-OS-000480-GPOS-00226<GroupDescription></GroupDescription>SLES-15-040000The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.<VulnDiscussion>Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to enforce a delay of at least four seconds between logon prompts following a failed logon attempt. + +Add or update the following variable in "/etc/login.defs" to match the line below ("FAIL_DELAY" must have a value of "4" or higher): + +FAIL_DELAY 4Verify the SUSE operating system enforces a delay of at least four seconds between logon prompts following a failed logon attempt. + +Check that the SUSE operating system enforces a delay of at least four seconds between logon prompts following a failed logon attempt with the following command: + +> grep FAIL_DELAY /etc/login.defs +FAIL_DELAY 4 + +If the value of "FAIL_DELAY" is not set to "4", "FAIL_DELAY" is commented out, or "FAIL_DELAY" is missing, then this is a finding.SRG-OS-000480-GPOS-00226<GroupDescription></GroupDescription>SLES-15-040010The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.<VulnDiscussion>The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to enforce a delay of at least four seconds between logon prompts following a failed logon attempt. + +Edit the file "/etc/pam.d/common-auth". + +Add a parameter "pam_faildelay" and set it to: + +> delay is in micro seconds +auth required pam_faildelay.so delay=4000000Verify the SUSE operating system enforces a delay of at least four seconds between logon prompts following a failed logon attempt. + +> grep pam_faildelay /etc/pam.d/common-auth +auth required pam_faildelay.so delay=4000000 + +If the value of "delay" is not set to "4000000", "delay" is commented out, "delay" is missing, or the "pam_faildelay" line is missing completely, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040020There must be no .shosts files on the SUSE operating system.<VulnDiscussion>The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Remove any ".shosts" files found on the SUSE operating system. + +> sudo rm /[path]/[to]/[file]/.shostsText: Verify there are no ".shosts" files on the SUSE operating system. + +Check the system for the existence of these files with the following command: + +> sudo find / \( -path /.snapshots -o -path /sys -o -path /proc \) -prune -o -name '.shosts' -print + +If any ".shosts" files are found on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040030There must be no shosts.equiv files on the SUSE operating system.<VulnDiscussion>The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Remove any "shosts.equiv" files found on the SUSE operating system. + +> sudo rm /[path]/[to]/[file]/shosts.equivVerify there are no "shosts.equiv" files on the SUSE operating system. + +Check the system for the existence of these files with the following command: + +> sudo find /etc -name shosts.equiv + +If any "shosts.equiv" files are found on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040040The SUSE operating system file integrity tool must be configured to verify Access Control Lists (ACLs).<VulnDiscussion>ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system file integrity tool to check file and directory ACLs. + +If AIDE is installed, ensure the "acl" rule is present on all file and directory selection lists.Verify that the SUSE operating system file integrity tool is configured to verify extended attributes. + +If there is no application installed to perform integrity checks, this is a finding. + +Check the "/etc/aide.conf" file to determine if the "xattrs" rule has been added to the rule list being applied to the files and directories selection lists. + +An example rule that includes the "acl" rule follows: + + All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux + /bin All > apply the custom rule to the files in bin + /sbin All > apply the same custom rule to the files in sbin + +If the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040050The SUSE operating system file integrity tool must be configured to verify extended attributes.<VulnDiscussion>Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system file integrity tool to check file and directory extended attributes. + +If AIDE is installed, ensure the "xattrs" rule is present on all file and directory selection lists.Verify that the SUSE operating system file integrity tool is configured to verify extended attributes. + +If there is no application installed to perform integrity checks, this is a finding. + +Check the "/etc/aide.conf" file to determine if the "xattrs" rule has been added to the rule list being applied to the files and directories selection lists. + +An example rule that includes the "xattrs" rule follows: + + All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux + /bin All > apply the custom rule to the files in bin + /sbin All > apply the same custom rule to the files in sbin + +If the "xattrs" rule is not being used on all selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040060The SUSE operating system must disable the x86 Ctrl-Alt-Delete key sequence.<VulnDiscussion>A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the graphical user interface environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commands: + +> sudo systemctl disable ctrl-alt-del.target + +> sudo systemctl mask ctrl-alt-del.target + +And reload the daemon to take effect + +> sudo systemctl daemon-reloadVerify the SUSE operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed. + +Check that the ctrl-alt-del.target is masked with the following command: + +> systemctl status ctrl-alt-del.target +ctrl-alt-del.target +Loaded: masked (/dev/null; maksed) +Active: inactive (dead) + +If the ctrl-alt-del.target is not masked, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040061The SUSE operating system must disable the x86 Ctrl-Alt-Delete key sequence for Graphical User Interfaces.<VulnDiscussion>A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the graphical user interface environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the system to disable the Ctrl-Alt-Delete sequence for the +graphical user interface. + +Create a database to contain the system-wide setting (if it does not +already exist) with the following steps: + +1. Create a user profile and with the listed content: + +/etc/dconf/profile/user +user-db:user +system-db:local + +2. Create the following directories: + +> sudo mkdir -p /etc/dconf/db/local.d/ +> sudo mkdir -p /etc/dconf/db/local.d/locks/ + +3. Add the following files with the listed content: + +/etc/dconf/db/local.d/01-fips-settings +[org/gnome/settings-daemon/plugins/media-keys] +logout=[''] + +/etc/dconf/db/local.d/locks/01-fips-locks +/org/gnome/settings-daemon/plugins/media-keys/logout + +4. Update the dconf database: + +> sudo dconf updateNote: If a graphical user interface is not installed, this requirement is Not Applicable. + +Verify the SUSE operating system is not configured to reboot the system +when Ctrl-Alt-Delete is pressed in the graphical user interface. + +Check that the dconf setting was disabled to allow the Ctrl-Alt-Delete +sequence in the graphical user interface with the following command: + +Check the default logout key sequence: + +> sudo gsettings get org.gnome.settings-daemon.plugins.media-keys logout +[''] + +Check that the value is not writable and cannot be changed by the user: + +> sudo gsettings writable org.gnome.settings-daemon.plugins.media-keys logout +false + +If the logout value is not [''] and the writable status is not false, this +is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040062The SUSE operating system must disable the systemd Ctrl-Alt-Delete burst key sequence.<VulnDiscussion>A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the graphical user interface environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the system to disable the CtrlAltDelBurstAction by added or modifying the following line in the "/etc/systemd/system.conf" configuration file: + +CtrlAltDelBurstAction=none + +Reload the daemon for this change to take effect + +> sudo systemctl daemon-reloadVerify the SUSE operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed seven times within two seconds with the following command: + +> sudo grep -i ctrl /etc/systemd/system.conf + +CtrlAltDelBurstAction=none + +If the "CtrlAltDelBurstAction" is not set to "none", commented out, or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040070All SUSE operating system local interactive users must have a home directory assigned in the /etc/passwd file.<VulnDiscussion>If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Assign home directories to all SUSE operating system local interactive users that currently do not have a home directory assigned. + +Assign a home directory to users via the usermod command: + +> sudo usermod -d /home/smithj smithjVerify SUSE operating system local interactive users on the system have a home directory assigned. + +Check for missing local interactive user home directories with the following command: + +> sudo pwck -r +user 'smithj': directory '/home/smithj' does not exist + +Ask the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command: + +> awk -F: '($3>=1000)&&($1!="nobody"){print $1 ":" $3}' /etc/passwd + +If any interactive users do not have a home directory assigned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040080All SUSE operating system local interactive user home directories defined in the /etc/passwd file must exist.<VulnDiscussion>If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Create home directories to all SUSE operating system local interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in "/etc/ passwd": + +Note: The example will be for the user smithj, who has a home directory of "/home/smithj", a UID of "smithj", and a Group Identifier (GID) of "users assigned" in "/etc/passwd". + +> sudo mkdir /home/smithj +> sudo chown smithj /home/smithj +> sudo chgrp users /home/smithj +> sudo chmod 0750 /home/smithjVerify the assigned home directory of all SUSE operating system local interactive users on the system exists. + +Check the home directory assignment for all local interactive non-privileged users on the system with the following command: + +> awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $6}' /etc/passwd + +smithj /home/smithj + +Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. + +Check that all referenced home directories exist with the following command: + +> sudo pwck -r + +user 'smithj': directory '/home/smithj' does not exist + +If any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040090All SUSE operating system local interactive user home directories must have mode 0750 or less permissive.<VulnDiscussion>Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Change the mode of SUSE operating system local interactive user's home directories to "0750". To change the mode of a local interactive user's home directory, use the following command: + +Note: The example will be for the user "smithj". + +> sudo chmod 0750 /home/smithjVerify the assigned home directory of all SUSE operating system local interactive users has a mode of "0750" or less permissive. + +Check the home directory assignment for all non-privileged users on the system with the following command: + +Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. + +> ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) +-rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj + +If home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040100All SUSE operating system local interactive user home directories must be group-owned by the home directory owner's primary group.<VulnDiscussion>If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Change the group owner of a SUSE operating system local interactive user's home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user's home directory, use the following command: + +Note: The example will be for the user "smithj", who has a home directory of "/home/smithj", and has a primary group of users. + +> sudo chgrp users /home/smithjVerify the assigned home directory of all SUSE operating system local interactive users is group-owned by that user's primary GID. + +Check the home directory assignment for all non-privileged users on the system with the following command: + +Note: This may miss local interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. The returned directory "/home/smithj" is used as an example. + +> awk -F: '($3>=1000)&&($7 !~ /nologin/){print $4, $6}' /etc/passwd) +250:/home/smithj + +Check the user's primary group with the following command: + +> grep users /etc/group +users:x:250:smithj,jonesj,jacksons + +If the user home directory referenced in "/etc/passwd" is not group-owned by that user's primary GID, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040110All SUSE operating system local initialization files must have mode 0740 or less permissive.<VulnDiscussion>Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Set the mode of SUSE operating system local initialization files to "0740" with the following command: + +Note: The example will be for the smithj user, who has a home directory of "/home/smithj". + +> sudo chmod 0740 /home/smithj/.<INIT_FILE>Verify that all SUSE operating system local initialization files have a mode of "0740" or less permissive. + +Check the mode on all SUSE operating system local initialization files with the following command: + +Note: The example will be for the user "smithj", who has a home directory of "/home/smithj". + +> sudo ls -al /home/smithj/.* | more +-rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile +-rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login +-rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something + +If any local initialization files have a mode more permissive than "0740", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040120All SUSE operating system local interactive user initialization files executable search paths must contain only paths that resolve to the users home directory.<VulnDiscussion>The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory (other than the user's home directory), executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Edit the SUSE operating system local interactive user initialization files to change any PATH variable statements for executables that reference directories other than their home directory. If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the ISSO.Verify that all SUSE operating system local interactive user initialization files executable search path statements do not contain statements that will reference a working directory other than the user's home directory. + +Check the executable search path statement for all operating system local interactive user initialization files in the user's home directory with the following commands: + +Note: The example will be for the user "smithj", who has a home directory of "/home/smithj". + +> sudo grep -i path= /home/smithj/.* +/home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin + +If any local interactive user initialization files have executable search path statements that include directories outside of their home directory, and the additional path statements are not documented with the ISSO as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040130All SUSE operating system local initialization files must not execute world-writable programs.<VulnDiscussion>If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Remove the references to these files in the local initialization scripts or remove the world-writable permission of files referenced by SUSE operating system local initialization scripts with the following command: + +> sudo chmod 0755 <file>Verify that SUSE operating system local initialization files do not execute world-writable programs. + +Verify that SUSE operating system local initialization files do not +execute world-writable programs. + +Check the system for world-writable files with the following command: + +> sudo find / -xdev -perm -002 -type f -exec ls -ld {} \; + +For all files listed, check for their presence in the local +initialization files with the following command: + +Note: The example will be for a system that is configured to create +users' home directories in the "/home" directory. + +> sudo find /home/* -maxdepth 1 -type f -name \.\* -exec grep -H <file> {} \; + +If any local initialization files are found to reference world-writable +files, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040140SUSE operating system file systems that contain user home directories must be mounted to prevent files with the setuid and setgid bit set from being executed.<VulnDiscussion>The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system "/etc/fstab" file to use the "nosuid" option on file systems that contain user home directories for interactive users. + +Re-mount the filesystems. + +> sudo mount -o remount /homeVerify that SUSE operating system file systems that contain user home directories are mounted with the "nosuid" option. + +Print the currently active file system mount options of the file system(s) that contain the user home directories with the following command: + +> for X in `awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd`; do findmnt -nkT $X; done | sort -r +/home /dev/mapper/system-home ext4 rw,nosuid,relatime,data=ordered + +If a file system containing user home directories is not mounted with the FSTYPE OPTION nosuid, this is a finding. + +Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is not a finding as the "nosuid" option cannot be used on the "/" system.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040150SUSE operating system file systems that are used with removable media must be mounted to prevent files with the setuid and setgid bit set from being executed.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system "/etc/fstab" file to use the "nosuid" option on file systems that are associated with removable media.Verify SUSE operating system file systems used for removable media are mounted with the "nosuid" option. + +Check the file systems that are mounted at boot time with the following command: + +> more /etc/fstab + +UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid 0 0 + +If a file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040160SUSE operating system file systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setgid bit set from being executed.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system "/etc/fstab" file to use the "nosuid" option on file systems that are being exported via NFS.Verify SUSE operating system file systems that are being NFS exported are mounted with the "nosuid" option. + +Find the file system(s) that contain the directories being exported with the following command: + +> grep nfs /etc/fstab + +UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0 + +If a file system found in "/etc/fstab" refers to NFS and it does not have the "nosuid" option set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040170SUSE operating system file systems that are being imported via Network File System (NFS) must be mounted to prevent binary files from being executed.<VulnDiscussion>The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system "/etc/fstab" file to use the "noexec" option on file systems that are being exported via NFS.Verify the SUSE operating system file systems that are being NFS exported are mounted with the "noexec" option. + +Find the file system(s) that contain the directories being exported with the following command: + +> grep nfs /etc/fstab + +UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0 + +If a file system found in "/etc/fstab" refers to NFS and it does not have the "noexec" option set, and use of NFS exported binaries is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040180All SUSE operating system world-writable directories must be group-owned by root, sys, bin, or an application group.<VulnDiscussion>If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others. + +The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Change the group of the SUSE operating system world-writable directories to root with the following command: + +> sudo chgrp root <directory>Verify all SUSE operating system world-writable directories are group-owned by root, sys, bin, or an application group. + +Check the system for world-writable directories with the following command: + +> sudo find / -perm -002 -type d -exec ls -lLd {} \; +drwxrwxrwt. 2 root root 40 Aug 26 13:07 /dev/mqueue +drwxrwxrwt. 2 root root 220 Aug 26 13:23 /dev/shm +drwxrwxrwt. 14 root root 4096 Aug 26 13:29 /tmp + +If any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040190SUSE operating system kernel core dumps must be disabled unless needed.<VulnDiscussion>Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366If SUSE operating system kernel core dumps are not required, disable the "kdump" service with the following command: + +> sudo systemctl disable kdump.service + +If kernel core dumps are required, document the need with the ISSO.Verify that SUSE operating system kernel core dumps are disabled unless needed. + +Check the status of the "kdump" service with the following command: + +> systemctl status kdump.service +Loaded: not-found (Reason: No such file or directory) +Active: inactive (dead) + +If the "kdump" service is active, ask the System Administrator if the use of the service is required and documented with the Information System Security Officer (ISSO). + +If the service is active and is not documented, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040200A separate file system must be used for SUSE operating system user home directories (such as /home or an equivalent).<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Create a separate file system/partition for SUSE operating system non-privileged local interactive user home directories. + +Migrate the non-privileged local interactive user home directories onto the separate file system/partition.Verify that a separate file system/partition has been created for SUSE operating system non-privileged local interactive user home directories. + +Check the home directory assignment for all non-privileged users (those with a UID greater than 1000) on the system with the following command: + +> awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6, $7}' /etc/passwd + +adamsj 1002 /home/adamsj /bin/bash +jacksonm 1003 /home/jacksonm /bin/bash +smithj 1001 /home/smithj /bin/bash + +The output of the command will give the directory/partition that contains the home directories for the non-privileged users on the system (in this example, /home) and user's shell. All accounts with a valid shell (such as /bin/bash) are considered interactive users. + +Check that a file system/partition has been created for the non-privileged interactive users with the following command: + +Note: The partition of /home is used in the example. + +> grep /home /etc/fstab +UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1 2 + +If a separate entry for the file system/partition that contains the non-privileged interactive users' home directories does not exist, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040210The SUSE operating system must use a separate file system for /var.<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Create a separate file system/partition on the SUSE operating system for "/var". + +Migrate "/var" onto the separate file system/partition.Verify that the SUSE operating system has a separate file system/partition for "/var". + +Check that a file system/partition has been created for "/var" with the following command: + +> grep /var /etc/fstab +UUID=c274f65f /var ext4 noatime,nobarrier 1 2 + +If a separate entry for "/var" is not in use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040220The SUSE operating system must be configured to not overwrite Pluggable Authentication Modules (PAM) configuration on package changes.<VulnDiscussion>The "pam-config" command line utility automatically generates a system PAM configuration as packages are installed, updated, or removed from the system. "pam-config" removes configurations for PAM modules and parameters that it does not know about. It may render ineffective PAM configuration by the system administrator and thus impact system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Copy the PAM configuration files to their static locations and remove the SUSE operating system soft links for the PAM configuration files with the following command: + +> sudo sh -c 'for X in /etc/pam.d/common-*-pc; do cp -ivp --remove-destination $X ${X:0:-3}; done' + +Additional information on the configuration of multifactor authentication on the SUSE operating system can be found at https://www.suse.com/communities/blog/configuring-smart-card-authentication-suse-linux-enterprise/.Verify the SUSE operating system is configured to not overwrite PAM configuration on package changes. + +Check that soft links between PAM configuration files are removed with the following command: + +> find /etc/pam.d/ -type l -iname "common-*" + +If any results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040230The SUSE operating system SSH daemon must be configured to not allow authentication using known hosts authentication.<VulnDiscussion>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system SSH daemon to not allow authentication using "known hosts" authentication. + +Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": + +IgnoreUserKnownHosts yesVerify the SUSE operating system SSH daemon is configured to not allow authentication using "known hosts" authentication. + +To determine how the SSH daemon's "IgnoreUserKnownHosts" option is set, run the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*ignoreuserknownhosts' + +IgnoreUserKnownHosts yes + +If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040240The SUSE operating system SSH daemon public host key files must have mode 0644 or less permissive.<VulnDiscussion>If a public host key file is modified by an unauthorized user, the SSH service may be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system SSH daemon public host key files have mode "0644" or less permissive. + +Note: SSH public key files may be found in other directories on the system depending on the installation. + +Change the mode of public host key files under "/etc/ssh" to "0644" with the following command: + +> sudo chmod 0644 /etc/ssh/ssh_host*key.pubVerify the SUSE operating system SSH daemon public host key files have mode "0644" or less permissive. + +Note: SSH public key files may be found in other directories on the system depending on the installation. + +The following command will find all SSH public key files on the system: + +> find /etc/ssh -name 'ssh_host*key.pub' -exec stat -c "%a %n" {} \; + +644 /etc/ssh/ssh_host_rsa_key.pub +644 /etc/ssh/ssh_host_dsa_key.pub +644 /etc/ssh/ssh_host_ecdsa_key.pub +644 /etc/ssh/ssh_host_ed25519_key.pub + +If any file has a mode more permissive than "0644", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040250The SUSE operating system SSH daemon private host key files must have mode 0640 or less permissive.<VulnDiscussion>If an unauthorized user obtains the private SSH host key file, the host could be impersonated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the mode of the SUSE operating system SSH daemon private host key files under "/etc/ssh" to "0640" with the following command: + + > sudo chmod 0640 /etc/ssh/ssh_host*keyVerify the SUSE operating system SSH daemon private host key files have mode "0640" or less permissive. + +The following command will find all SSH private key files on the system: + + > sudo find / -name '*ssh_host*key' -exec ls -lL {} \; + +Check the mode of the private host key files under "/etc/ssh" file with the following command: + + > find /etc/ssh -name 'ssh_host*key' -exec stat -c "%a %n" {} \; + + 640 /etc/ssh/ssh_host_rsa_key + 640 /etc/ssh/ssh_host_dsa_key + 640 /etc/ssh/ssh_host_ecdsa_key + 640 /etc/ssh/ssh_host_ed25519_key + +If any file has a mode more permissive than "0640", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040260The SUSE operating system SSH daemon must perform strict mode checking of home directory configuration files.<VulnDiscussion>If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system SSH daemon performs strict mode checking of home directory configuration files. + +Uncomment the "StrictModes" keyword in "/etc/ssh/sshd_config" and set the value to "yes": + +StrictModes yesVerify the SUSE operating system SSH daemon performs strict mode checking of home directory configuration files. + +Check that the SSH daemon performs strict mode checking of home directory configuration files with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*strictmodes' + +StrictModes yes + +If "StrictModes" is set to "no", is missing, or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040290The SUSE operating system SSH daemon must disable forwarded remote X connections for interactive users, unless to fulfill documented and validated mission requirements.<VulnDiscussion>The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator may have a stance in which they want to protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding, which can warrant a ''no'' setting. +X11 forwarding should be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker may then be able to perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled. +If X11 services are not required for the system's intended function, they should be disabled or restricted as appropriate to the system’s needs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system SSH daemon to disable forwarded X connections for interactive users. + +Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): + +X11Forwarding noDetermine if X11Forwarding is disabled. + +Verify the SUSE operating system SSH daemon remote X forwarded connections for interactive users are disabled. + +Check that SSH remote X forwarded connections are disabled with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*x11forwarding' + +X11Forwarding no + +If the "X11Forwarding" keyword is set to "yes" and is not documented with the information system security officer (ISSO) as an operational requirement, is missing, or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040300The SUSE operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4/IPv6 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to disable IPv4 source routing by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.all.accept_source_route=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.all.accept_source_route=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv4 source-routed packets. + +Check the value of the IPv4 accept source route variable with the following command: + +> sudo sysctl net.ipv4.conf.all.accept_source_route +net.ipv4.conf.all.accept_source_route = 0 + +If the network parameter "ipv4.conf.all.accept_source_route" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040310The SUSE operating system must not forward Internet Protocol version 6 (IPv6) source-routed packets.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to disable IPv6 source routing by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.all.accept_source_route=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.all.accept_source_route=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv6 source-routed packets. + +Check the value of the IPv6 accept source route variable with the following command: + +> sudo sysctl net.ipv6.conf.all.accept_source_route +net.ipv6.conf.all.accept_source_route = 0 + +If the network parameter "ipv6.conf.all.accept_source_route" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040320The SUSE operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to disable IPv4 default source routing by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.default.accept_source_route=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.default.accept_source_route=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv4 source-routed packets by default. + +Check the value of the default IPv4 accept source route variable with the following command: + +> sudo sysctl net.ipv4.conf.default.accept_source_route +net.ipv4.conf.default.accept_source_route = 0 + +If the network parameter "ipv4.conf.default.accept_source_route" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040321The SUSE operating system must not forward Internet Protocol version 6 (IPv6) source-routed packets by default.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to disable IPv6 default source routing by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.default.accept_source_route=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.default.accept_source_route=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv6 source-routed packets by default. + +Check the value of the default IPv6 accept source route variable with the following command: + +> sudo sysctl net.ipv6.conf.default.accept_source_route +net.ipv6.conf.default.accept_source_route = 0 + +If the network parameter "ipv6.conf.default.accept_source_route" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040330The SUSE operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not accept IPv4 ICMP redirect messages by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.all.accept_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.all.accept_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv4 ICMP redirect messages. + +Check the value of the IPv4 accept_redirects variable with the following command: + +> sudo sysctl net.ipv4.conf.all.accept_redirects +net.ipv4.conf.all.accept_redirects =0 + +If the network parameter "ipv4.conf.all.accept_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040340The SUSE operating system must not allow interfaces to accept Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages by default.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not accept IPv4 ICMP redirect messages by default by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.default.accept_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.default.accept_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv4 ICMP redirect messages by default. + +Check the value of the default IPv4 accept_redirects variable with the following command: + +> sudo sysctl net.ipv4.conf.default.accept_redirects +net.ipv4.conf.default.accept_redirects = 0 + +If the network parameter "ipv4.conf.default.accept_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040341The SUSE operating system must prevent Internet Protocol version 6 (IPv6) Internet Control Message Protocol (ICMP) redirect messages from being accepted.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not accept IPv6 ICMP redirect messages by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.all.accept_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.all.accept_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not accept IPv6 ICMP redirect messages. + +Check the value of the IPv6 accept_redirects variable with the following command: + +> sudo sysctl net.ipv6.conf.all.accept_redirects +net.ipv6.conf.all.accept_redirects =0 + +If the network parameter "ipv6.conf.all.accept_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040350The SUSE operating system must not allow interfaces to accept Internet Protocol version 6 (IPv6) Internet Control Message Protocol (ICMP) redirect messages by default.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not accept IPv6 ICMP redirect messages by default by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.default.accept_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.default.accept_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not allow IPv6 ICMP redirect messages by default. + +Check the value of the default IPv6 accept_redirects variable with the following command: + +> sudo sysctl net.ipv6.conf.default.accept_redirects +net.ipv6.conf.default.accept_redirects = 0 + +If the network parameter "ipv6.conf.default.accept_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040360The SUSE operating system must not allow interfaces to send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages by default.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not allow interfaces to perform IPv4 ICMP redirects by default by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.default.send_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.default.send_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not allow interfaces to perform IPv4 ICMP redirects by default. + +Check the value of the default IPv4 send_redirects variable with the following command: + +> sudo sysctl net.ipv4.conf.default.send_redirects +net.ipv4.conf.default.send_redirects = 0 + +If the network parameter "ipv4.conf.default.send_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040370The SUSE operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not allow interfaces to perform IPv4 ICMP redirects by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.conf.all.send_redirects=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.conf.all.send_redirects=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system does not allow interfaces to perform IPv4 ICMP redirects. + +Check the value of the IPv4 send_redirects variable with the following command: + +> sudo sysctl net.ipv4.conf.all.send_redirects +net.ipv4.conf.all.send_redirects = 0 + +If the network parameter "ipv4.conf.all.send_redirects" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040380The SUSE operating system must not be performing Internet Protocol version 4 (IPv4) packet forwarding unless the system is a router.<VulnDiscussion>Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not performing IPv4 packet forwarding by running the following command as an administrator: + +> sudo sysctl -w net.ipv4.ip_forward=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv4.ip_forward=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system is not performing IPv4 packet forwarding, unless the system is a router. + +Check to see if IPv4 forwarding is disabled using the following command: + +> sudo sysctl net.ipv4.ip_forward +net.ipv4.ip_forward = 0 + +If the network parameter "ipv4.ip_forward" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040381The SUSE operating system must not be performing Internet Protocol version 6 (IPv6) packet forwarding unless the system is a router.<VulnDiscussion>Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not performing IPv6 packet forwarding by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.all.forwarding=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.all.forwarding=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system is not performing IPv6 packet forwarding, unless the system is a router. + +Check to see if IPv6 forwarding is enabled using the following command: + +> sudo sysctl net.ipv6.conf.all.forwarding +net.ipv6.conf.all.forwarding = 0 + +If the network parameter "ipv6.conf.all.forwarding" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040382The SUSE operating system must not be performing Internet Protocol version 6 (IPv6) packet forwarding by default unless the system is a router.<VulnDiscussion>Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to not performing IPv6 packet forwarding by default by running the following command as an administrator: + +> sudo sysctl -w net.ipv6.conf.default.forwarding=0 + +If "0" is not the system's default value, add or update the following line in "/etc/sysctl.d/99-stig.conf": + +> sudo sh -c 'echo "net.ipv6.conf.default.forwarding=0" >> /etc/sysctl.d/99-stig.conf' + +> sudo sysctl --systemVerify the SUSE operating system is not performing IPv6 packet forwarding by default, unless the system is a router. + +Check to see if IPv6 forwarding is disabled by default using the following command: + +> sudo sysctl net.ipv6.conf.default.forwarding +net.ipv6.conf.default.forwarding = 0 + +If the network parameter "ipv6.conf.default.forwarding" is not equal to "0" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040390The SUSE operating system must not have network interfaces in promiscuous mode unless approved and documented.<VulnDiscussion>Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access these applications, it may allow then to collect information such as logon IDs, passwords, and key exchanges between systems. + +If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information System Security Officer (ISSO) and restricted to only authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system network interfaces to turn off promiscuous mode unless approved by the ISSO and documented. + +Set the promiscuous mode of an interface to off with the following command: + +> sudo ip link set dev <devicename> promisc offVerify the SUSE operating system network interfaces are not in promiscuous mode unless approved by the ISSO and documented. + +Check for the status with the following command: + +> ip link | grep -i promisc + +If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSO and documented, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040400All SUSE operating system files and directories must have a valid owner.<VulnDiscussion>Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier (UID) as the UID of the unowned files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001230Either remove all files and directories from the SUSE operating system that do not have a valid user, or assign a valid user to all unowned files and directories on the system with the "chown" command: + +> sudo chown <user> <file>Verify that all SUSE operating system files and directories on the system have a valid owner. + +Check the owner of all files and directories with the following command: + +Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example. + +> sudo find / -fstype xfs -nouser + +If any files on the system do not have an assigned owner, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-040410All SUSE operating system files and directories must have a valid group owner.<VulnDiscussion>Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001230Either remove all files and directories from the SUSE operating system that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command: + +> sudo chgrp <group> <file>Verify all SUSE operating system files and directories on the system have a valid group. + +Check the owner of all files and directories with the following command: + +Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example. + +> sudo find / -fstype xfs -nogroup + +If any files on the system do not have an assigned group, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>SLES-15-040420The SUSE operating system default permissions must be defined in such a way that all authenticated users can only read and modify their own files.<VulnDiscussion>Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system to define the default permissions for all authenticated users in such a way that the users can only read and modify their own files. + +Add or edit the "UMASK" parameter in the "/etc/login.defs" file to match the example below: + +UMASK 077Verify the SUSE operating system defines default permissions for all authenticated users in such a way that the users can only read and modify their own files. + +Check the system default permissions with the following command: + +> grep -i "^umask" /etc/login.defs + +UMASK 077 + +If the "UMASK" variable is set to "000", the severity is raised to a CAT I, and this is a finding. + +If the value of "UMASK" is not set to "077", or "UMASK" is missing, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>SLES-15-040430The SUSE operating system must not allow unattended or automatic logon via the graphical user interface (GUI).<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts SUSE operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Note: If a graphical user interface is not installed, this requirement is Not Applicable. + +Configure the SUSE operating system GUI to not allow unattended or automatic logon to the system. + +Add or edit the following lines in the "/etc/sysconfig/displaymanager" +configuration file: + +DISPLAYMANAGER_AUTOLOGIN="" +DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no"Note: If a graphical user interface is not installed, this requirement is Not Applicable. + +Verify the SUSE operating system does not allow unattended or automatic logon via the GUI. + +Check that unattended or automatic login is disabled with the following commands: + +> grep -i ^DISPLAYMANAGER_AUTOLOGIN /etc/sysconfig/displaymanager + +DISPLAYMANAGER_AUTOLOGIN="" + +> grep -i ^DISPLAYMANAGER_PASSWORD_LESS_LOGIN /etc/sysconfig/displaymanager + +DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" + +If the "DISPLAYMANAGER_AUTOLOGIN" parameter includes a username or the +"DISPLAYMANAGER_PASSWORD_LESS_LOGIN" +If parameter is not set to "no", this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>SLES-15-040440The SUSE operating system must not allow unattended or automatic logon via SSH.<VulnDiscussion>Failure to restrict system access via SSH to authenticated users negatively impacts SUSE operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the SUSE operating system disables unattended or automatic logon via SSH. + +Add or edit the following lines in the "/etc/ssh/sshd_config" file: + +PermitEmptyPasswords no +PermitUserEnvironment noVerify the SUSE operating system disables unattended or automatic logon via SSH. + +Check that unattended or automatic logon via SSH is disabled with the following command: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iEH '^\s*(permit(.*?)(passwords|environment))' + +PermitEmptyPasswords no +PermitUserEnvironment no + +If "PermitEmptyPasswords" or "PermitUserEnvironment" keywords are not set to "no", are missing completely, or are commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020099The SUSE operating system must specify the default "include" directory for the /etc/sudoers file.<VulnDiscussion>The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used to configure authorized "sudo" users as well as the programs they are allowed to run. Some configuration options in the "/etc/sudoers" file allow configured users to run programs without re-authenticating. Use of these configuration options makes it easier for one compromised account to be used to compromise other accounts. + +It is possible to include other sudoers files from within the sudoers file currently being parsed using the @include and @includedir directives. For compatibility with sudo versions prior to 1.9.1, #include and #includedir are also accepted. When sudo reaches this line it will suspend processing of the current file (/etc/sudoers) and switch to the specified file/directory. Once the end of the included file(s) is reached, the rest of /etc/sudoers will be processed. Files that are included may themselves include other files. A hard limit of 128 nested include files is enforced to prevent include file loops.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure the /etc/sudoers file to only include the /etc/sudoers.d directory. + +Edit the /etc/sudoers file with the following command: + +> sudo visudo + +Add or modify the following line: +@includedir /etc/sudoers.dNote: If the "include" and "includedir" directives are not present in the /etc/sudoers file, this requirement is not applicable. + +Verify the operating system specifies only the default "include" directory for the /etc/sudoers file with the following command: + +> sudo grep include /etc/sudoers + +@includedir /etc/sudoers.d + +If the results are not "/etc/sudoers.d" or additional files or directories are specified, this is a finding. + +Verify the operating system does not have nested "include" files or directories within the /etc/sudoers.d directory with the following command: + +> sudo grep -r include /etc/sudoers.d + +If results are returned, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>SLES-15-020104The SUSE operating system must not be configured to bypass password requirements for privilege escalation.<VulnDiscussion>Without re-authentication, users may access resources or perform tasks for which they do not have authorization. + +When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. + +Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-004895Configure the operating system to require users to supply a password for privilege escalation. + +Check the configuration of the "/etc/ pam.d/sudo" file with the following command: + +$ sudo vi /etc/pam.d/sudo + +Remove any occurrences of "pam_succeed_if" in the file.Verify the operating system is not be configured to bypass password requirements for privilege escalation. + +Check the configuration of the "/etc/pam.d/sudo" file with the following command: + +$ sudo grep pam_succeed_if /etc/pam.d/sudo + +If any occurrences of "pam_succeed_if" are returned from the command, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>SLES-15-020181The SUSE operating system must not have accounts configured with blank or null passwords.<VulnDiscussion>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-000366Configure all accounts on the system to have a password or lock the account with the following commands: + +Perform a password reset: +$ sudo passwd [username] +Lock an account: +$ sudo passwd -l [username]Check the "/etc/shadow" file for blank passwords with the following command: + +$ sudo awk -F: '!$2 {print $1}' /etc/shadow + +If the command returns any results, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>SLES-15-040450The SUSE operating system SSH server must be configured to use only FIPS-validated key exchange algorithms.<VulnDiscussion>Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection. + +The system will attempt to use the first algorithm presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest algorithm available to secure the SSH connection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001453Configure the SSH server to use only FIPS-validated key exchange algorithms by adding or modifying the following line in "/etc/ssh/sshd_config": + + KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 + +Restart the "sshd" service for changes to take effect: + + $ sudo systemctl restart sshdVerify the SSH server is configured to use only FIPS-validated key exchange algorithms: + +> sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*kexalgorithms' + +KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 + +If "KexAlgorithms" is not configured, is commented out, or does not contain only the algorithms "ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256" in exact order, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>SLES-15-010375The SUSE operating system must restrict access to the kernel message buffer.<VulnDiscussion>Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a nonprivileged user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001090Configure the operating system to restrict access to the kernel message buffer. + +Set the system to the required kernel parameter by adding or modifying the following line in /etc/sysctl.conf or a config file in the /etc/sysctl.d/ directory: + + kernel.dmesg_restrict = 1 + +Remove any configurations that conflict with the above from the following locations: + /run/sysctl.d/ + /etc/sysctl.d/ + /usr/local/lib/sysctl.d/ + /usr/lib/sysctl.d/ + /lib/sysctl.d/ + /etc/sysctl.conf + +Reload settings from all system configuration files with the following command: + + $ sudo sysctl --systemVerify the operating system is configured to restrict access to the kernel message buffer with the following commands: + + $ sudo sysctl kernel.dmesg_restrict + kernel.dmesg_restrict = 1 + +If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding. + +Check that the configuration files are present to enable this kernel parameter: + + $ sudo grep -r kernel.dmesg_restrict /run/sysctl.d/* /etc/sysctl.d/* /usr/local/lib/sysctl.d/* /usr/lib/sysctl.d/* /lib/sysctl.d/* /etc/sysctl.conf 2> /dev/null + /etc/sysctl.conf:kernel.dmesg_restrict = 1 + /etc/sysctl.d/99-sysctl.conf:kernel.dmesg_restrict = 1 + +If "kernel.dmesg_restrict" is not set to "1", is missing or commented out, this is a finding. + +If conflicting results are returned, this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>SLES-15-010419The SUSE operating system must use a file integrity tool to verify correct operation of all security functions.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. + +This requirement applies to the SUSE operating system performing security function verification/testing and/or systems and environments that require this functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-002696Install AIDE, initialize it, and perform a manual check. + +Install AIDE: + $ sudo zipper in aide + +Initialize it (this may take a few minutes): + $ sudo aide -i + +The new database will need to be renamed to be read by AIDE: + $ sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db + +Perform a manual check: + $ sudo aide --check + +Example output: + Summary: + Total number of files: 140621 + Added files: 1 + Removed files: 1 + Changed files: 0 + +Done.Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions. + +Check that the AIDE package is installed with the following command: + $ sudo zypper if aide | grep "Installed" + Installed: Yes + +If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. + +If there is no application installed to perform integrity checks, this is a finding. + +If AIDE is installed, check if it has been initialized with the following command: + $ sudo aide --check + +If the output is "Couldn't open file /var/lib/aide/aide.db for reading", this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>SLES-15-020061The SUSE operating system must automatically expire temporary accounts within 72 hours.<VulnDiscussion>Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors. + +Temporary accounts are different from emergency accounts. Emergency accounts, also known as "last resort" or "break glass" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements. + +The automatic expiration of temporary accounts may be extended as needed by the circumstances but it must not be extended indefinitely. A documented permanent account should be established for privileged users who need long-term maintenance accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001682Configure the operating system to expire temporary accounts after 72 hours with the following command: + + > sudo chage -E $(date -d +3days +%Y-%m-%d) <temporary_account_name>Verify temporary accounts have been provisioned with an expiration date of 72 hours. + +For every existing temporary account, run the following command to obtain its account expiration information: + + > sudo chage -l <temporary_account_name> | grep -i "account expires" + +Verify each of these accounts has an expiration date set within 72 hours. +If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>SLES-15-010418The SUSE operating system must be configured to allow sending email notifications of unauthorized configuration changes to designated personnel.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security. + +Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target SUSE Linux Enterprise Server 15DISADPMS TargetSUSE Linux Enterprise Server 155274CCI-001744Install the "mailx" package on the system: + + > sudo zypper install mailxVerify that the operating system is configured to allow sending email notifications. + +Note: The "mailx" package provides the "mail" command that is used to send email messages. + +Verify that the "mailx" package is installed on the system: + + > sudo zypper se mailx + + i | mailx | A MIME-Capable Implementation of the mailx Command | package + +If "mailx" package is not installed, this is a finding. \ No newline at end of file diff --git a/benchmarks/DISA/U_VPN_SRG_V3R1_Manual-xccdf.xml b/benchmarks/DISA/U_VPN_SRG_V3R1_Manual-xccdf.xml new file mode 100644 index 000000000..09848b9bb --- /dev/null +++ b/benchmarks/DISA/U_VPN_SRG_V3R1_Manual-xccdf.xml @@ -0,0 +1,579 @@ +acceptedVirtual Private Network (VPN) Security Requirements GuideThis Security Requirements Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 24 Jul 20243.51.10.03I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>