| Finding ID |
Severity |
Title |
Description |
|
V-268176
|
High |
NixOS must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
Some maintenance and... |
|
V-268172
|
High |
NixOS must not allow an unattended or automatic login to the system via the console. |
Failure to restrict system access via the console to authenticated users negatively impacts operating system security. |
|
V-268168
|
High |
NixOS must implement NIST FIPS-validated cryptography 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. |
Use of weak or untested encryption algorithms undermines the purposes of using 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 |
|
V-268159
|
High |
NixOS must protect the confidentiality and integrity of transmitted information. |
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... |
|
V-268157
|
High |
NixOS must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either... |
|
V-268154
|
High |
NixOS must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
Changes to any software components can have significant effects on the overall security of the 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 operating system components must be signed... |
|
V-268146
|
High |
NixOS must protect wireless access to and from the system using encryption. |
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. Since wireless communications can be intercepted, it is necessary to use encryption to protect the confidentiality of information in transit.
Wireless technologies include, for... |
|
V-268144
|
High |
NixOS must protect the confidentiality and integrity of all information at rest. |
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 operating system-specific configuration data. Organizations may choose to... |
|
V-268131
|
High |
NixOS must not have the telnet package installed. |
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. |
|
V-268130
|
High |
NixOS must store only encrypted representations of passwords. |
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. |
|
V-268089
|
High |
NixOS must implement DOD-approved encryption to protect the confidentiality of remote access sessions. |
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.... |
|
V-268181
|
Medium |
NixOS must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. |
|
V-268180
|
Medium |
NixOS must run a supported release of the operating system. |
Security flaws with operating systems 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... |
|
V-268179
|
Medium |
For PKI-based authentication, NixOS must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. |
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). |
|
V-268178
|
Medium |
NixOS must prohibit the use of cached authenticators after one day. |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable. |
|
V-268177
|
Medium |
NixOS 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. |
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... |
|
V-268175
|
Medium |
NixOS must employ approved cryptographic hashing algorithms for all stored passwords. |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DOD data may be compromised.
Operating systems using encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-3 is the... |
|
V-268174
|
Medium |
NixOS must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. |
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.
Operating systems need to track periods of inactivity and... |
|
V-268173
|
Medium |
NixOS must be configured to use AppArmor. |
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.
Satisfies: SRG-OS-000480-GPOS-00230, SRG-OS-000368-GPOS-00154 |
|
V-268171
|
Medium |
NixOS must enforce a delay of at least four seconds between login prompts following a failed login attempt. |
Limiting the number of login attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account. |
|
V-268170
|
Medium |
NixOS must enable the use of pwquality. |
If the 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. |
|
V-268169
|
Medium |
NixOS must prevent the use of dictionary words for passwords. |
If the 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. |
|
V-268167
|
Medium |
NixOS must generate audit records for all account creations, modifications, disabling, and termination events. |
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.,... |
|
V-268166
|
Medium |
NixOS must generate audit records when concurrent logins to the same account occur from different sources. |
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.,... |
|
V-268165
|
Medium |
NixOS must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
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.,... |
|
V-268164
|
Medium |
NixOS must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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.,... |
|
V-268163
|
Medium |
NixOS must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
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.,... |
|
V-268162
|
Medium |
NixOS must remove all software components after updated versions have been installed. |
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. |
|
V-268161
|
Medium |
NixOS must implement address space layout randomization to protect its memory from unauthorized code execution. |
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... |
|
V-268160
|
Medium |
NixOS must implement nonexecutable data to protect its memory from unauthorized code execution. |
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... |
|
V-268158
|
Medium |
NixOS must protect against or limit the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces. |
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... |
|
V-268156
|
Medium |
NixOS must require users to reauthenticate when changing roles. |
Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to change security roles, it is critical the user reauthenticate. |
|
V-268155
|
Medium |
NixOS must require users to reauthenticate for privilege escalation. |
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 user reauthenticate. |
|
V-268153
|
Medium |
NixOS must notify designated personnel if baseline configurations are changed in an unauthorized manner. |
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... |
|
V-268152
|
Medium |
NixOS must prohibit user installation of system software without explicit privileged status. |
Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceeds the rights of a regular user.
Operating system functionality... |
|
V-268151
|
Medium |
NixOS must have time synchronization enabled. |
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... |
|
V-268150
|
Medium |
NixOS must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. |
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... |
|
V-268149
|
Medium |
NixOS 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). |
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... |
|
V-268148
|
Medium |
NixOS must prevent all software from executing at higher privilege levels than users executing the software. |
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.... |
|
V-268147
|
Medium |
NixOS must protect wireless access to the system using authentication of users and/or devices. |
Allowing devices and users to connect to the system without first authenticating them allows untrusted access and can lead to a compromise or attack.
Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual... |
|
V-268145
|
Medium |
NixOS must enforce password complexity by requiring that at least one special character be used. |
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... |
|
V-268143
|
Medium |
NixOS must terminate all SSH connections after becoming unresponsive. |
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... |
|
V-268142
|
Medium |
NixOS must terminate all SSH connections after 10 minutes of becoming unresponsive. |
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... |
|
V-268141
|
Medium |
NixOS must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial-of-service (DoS) attacks. |
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... |
|
V-268140
|
Medium |
A sticky bit must be set on all NixOS public directories to prevent unauthorized and unintended information transferred via shared system resources. |
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.,... |
|
V-268139
|
Medium |
NixOS must enable USBguard. |
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.
Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000690-GPOS-00140 |
|
V-268138
|
Medium |
NixOS must not allow direct login to the root account. |
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... |
|
V-268137
|
Medium |
NixOS must not allow direct login to the root account via SSH. |
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... |
|
V-268136
|
Medium |
NixOS must use multifactor authentication for network access to privileged accounts. |
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... |
|
V-268135
|
Medium |
NixOS must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users). |
To ensure 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)... |
|
V-268134
|
Medium |
NixOS must enforce a minimum 15-character password length. |
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... |
|
V-268133
|
Medium |
NixOS must enforce a 60-day maximum password lifetime restriction. |
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. |
|
V-268132
|
Medium |
NixOS must enforce 24 hours/one day as the minimum password lifetime. |
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... |
|
V-268129
|
Medium |
NixOS must require the change of at least 50 percent of the total number of characters when passwords are changed. |
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. |
|
V-268128
|
Medium |
NixOS must enforce password complexity by requiring that at least one numeric character be used. |
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. |
|
V-268127
|
Medium |
NixOS must enforce password complexity by requiring that at least one lowercase character be used. |
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. |
|
V-268126
|
Medium |
NixOS must enforce password complexity by requiring that at least one uppercase character be used. |
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. |
|
V-268125
|
Medium |
NixOS must enforce authorized access to the corresponding private key for PKI-based authentication. |
If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure.
The cornerstone of the PKI is the private key used to encrypt or digitally sign information.
If the private key is stolen, this will lead... |
|
V-268124
|
Medium |
NixOS, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. |
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... |
|
V-268123
|
Medium |
NixOS system configuration files and directories must be group-owned by root. |
Without the capability to restrict the roles and individuals that 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,... |
|
V-268122
|
Medium |
NixOS system configuration files and directories must be owned by root. |
Without the capability to restrict the roles and individuals that 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,... |
|
V-268121
|
Medium |
NixOS system configuration file directories must have a mode of "0755" or less permissive. |
Without the capability to restrict the roles and individuals that 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,... |
|
V-268120
|
Medium |
NixOS system configuration files must have a mode of "0644" or less permissive. |
Without the capability to restrict the roles and individuals that 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,... |
|
V-268119
|
Medium |
NixOS audit system must protect login UIDs from unauthorized change. |
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.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit system activity.
In immutable mode, unauthorized users cannot execute... |
|
V-268118
|
Medium |
NixOS syslog logs must have a mode of 0640 or less permissive. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268117
|
Medium |
NixOS syslog log directory must have a mode of 0750 or less permissive. |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit NixOS system activity. |
|
V-268116
|
Medium |
NixOS syslog directory and logs must be group-owned by root to prevent unauthorized read access. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268115
|
Medium |
NixOS syslog directory and logs must be owned by root to prevent unauthorized read access. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268114
|
Medium |
NixOS audit logs must have a mode of 0600 or less permissive. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268113
|
Medium |
NixOS audit log directory must have a mode of 0700 or less permissive. |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit NixOS system activity. |
|
V-268112
|
Medium |
NixOS audit directory and logs must be group-owned by root to prevent unauthorized read access. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268111
|
Medium |
NixOS audit directory and logs must be owned by root to prevent unauthorized read access. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268110
|
Medium |
NixOS audit daemon must generate logs that are group-owned by root. |
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 NixOS system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-268109
|
Medium |
NixOS must authenticate the remote logging server for off-loading audit logs. |
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.
NixOS supports "syslog-ng". "syslog-ng" is a common system utility providing support for message logging. Support for both internet and Unix domain sockets enables... |
|
V-268108
|
Medium |
The NixOS audit records must be off-loaded onto a different system or storage media from the system being audited. |
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.
NixOS supports "syslog-ng". "syslog-ng" is a common system utility providing support for message logging. Support for both internet and Unix domain sockets enables... |
|
V-268107
|
Medium |
NixOS must have the packages required for offloading audit logs installed and running. |
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.
NixOS supports "syslog-ng". "syslog-ng" is a common system utility providing support for message logging. Support for both internet and Unix domain sockets enables... |
|
V-268106
|
Medium |
The NixOS audit system must take appropriate action when an audit processing failure occurs. |
It is critical that when NixOS 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... |
|
V-268105
|
Medium |
The NixOS audit system must take appropriate action when the audit storage volume is full. |
It is critical that when NixOS 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... |
|
V-268104
|
Medium |
NixOS must take action when allocated audit record storage volume reaches 90 percent of the repository maximum audit record storage capacity. |
If security personnel are not notified immediately when storage volume reaches 90 percent utilization, they are unable to plan for audit record storage capacity expansion. |
|
V-268103
|
Medium |
NixOS must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. |
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. |
|
V-268102
|
Medium |
NixOS must notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 90 percent utilization. |
If security personnel are not notified immediately when storage volume reaches 90 percent utilization, they are unable to plan for audit record storage capacity expansion. |
|
V-268101
|
Medium |
NixOS must notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75 percent utilization. |
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.
Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000343-GPOS-00134 |
|
V-268100
|
Medium |
Successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls in NixOS must generate an audit record. |
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.,... |
|
V-268099
|
Medium |
Successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls in NixOS must generate an audit record. |
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.,... |
|
V-268098
|
Medium |
NixOS must generate an audit record for successful/unsuccessful uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls. |
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.,... |
|
V-268097
|
Medium |
NixOS must generate an audit record for successful/unsuccessful modifications to the cron configuration. |
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.,... |
|
V-268096
|
Medium |
Successful/unsuccessful uses of the init_module, finit_module, and delete_module system calls in NixOS must generate an audit record. |
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.,... |
|
V-268095
|
Medium |
Successful/unsuccessful uses of the rename, unlink, rmdir, renameat, and unlinkat system calls in NixOS must generate an audit record. |
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.,... |
|
V-268094
|
Medium |
Successful/unsuccessful uses of the mount syscall in NixOS must generate an audit record. |
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.,... |
|
V-268093
|
Medium |
NixOS must allocate an audit_backlog_limit of sufficient size to capture processes that start prior to the audit daemon. |
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.
If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems... |
|
V-268092
|
Medium |
NixOS must enable auditing of processes that start prior to the audit daemon. |
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.
If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems... |
|
V-268091
|
Medium |
NixOS must generate audit records for all usage of privileged commands. |
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... |
|
V-268090
|
Medium |
The NixOS audit package must be installed. |
Without establishing what type of events occurred, 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... |
|
V-268088
|
Medium |
NixOS must monitor remote access methods. |
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... |
|
V-268087
|
Medium |
NixOS must provide the capability for users to directly initiate a session lock for all connection types. |
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... |
|
V-268086
|
Medium |
NixOS must initiate a session lock after a 10-minute period of inactivity for graphical user login. |
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... |
|
V-268084
|
Medium |
NixOS must be configured to display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a graphical user login. |
|
|
V-268083
|
Medium |
NixOS must be configured to display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via an SSH login. |
|
|
V-268082
|
Medium |
NixOS must be configured to display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a command line user login. |
|
|
V-268081
|
Medium |
NixOS must enforce the limit of three consecutive invalid login attempts by a user during a 15-minute time period. |
By limiting the number of failed login 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-000021-GPOS-00005, SRG-OS-000329-GPOS-00128, SRG-OS-000470-GPOS-00214 |
|
V-268080
|
Medium |
NixOS must enable the audit daemon. |
Once an attacker establishes 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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
Note: For the "security.audit.enable"... |
|
V-268079
|
Medium |
NixOS emergency or temporary user accounts must be provisioned with an expiration time of 72 hours or less. |
If emergency or 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 emergency or temporary accounts must be set upon account creation.
Temporary accounts are established as part... |
|
V-268078
|
Medium |
NixOS must enable the built-in firewall. |
Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking place would not be immediately stopped.
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... |
|
V-268085
|
Low |
NixOS must be configured to limit the number of concurrent sessions to ten for all accounts and/or account types. |
Operating system management includes the ability to control the number of users and user sessions that use an 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... |
