{"stig":{"title":"F5 BIG-IP TMOS NDM Security Technical Implementation Guide","version":"1","release":"2"},"checks":[{"vulnId":"V-266064","ruleId":"SV-266064r1024595_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to limit the number of concurrent sessions to the Configuration Utility to 10 or an organization-defined number.","description":"Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator is helpful in limiting risks related to denial-of-service (DoS) attacks.\n\nThis requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. \n\nSatisfies: SRG-APP-000001-NDM-000200, SRG-APP-000435-NDM-000315","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Verify that System Settings view is set to Advanced.\n4. Verify Maximum HTTP connections to Configuration Utility is set to 10 or an organization-defined number.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list sys httpd max-clients\n\nIf the device is not configured to limit the number of concurrent sessions to the Configuration Utility to 10 or an organization-defined number, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Set System Settings view to Advanced.\n4. Maximum HTTP connections to Configuration Utility: enter 10 or an organization-defined number.\n5. Update.\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh modify sys httpd max-clients <10 or an organization-defined number>\ntmsh save sys config","ccis":["CCI-000054","CCI-002385"]},{"vulnId":"V-266065","ruleId":"SV-266065r1024596_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must terminate shared/group account credentials when members leave the group.","description":"A shared/group account credential is a shared form of authentication that allows multiple individuals to access the network device using a single account. If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even though they are no longer authorized. There may also be instances when specific user actions need to be performed on the network device without unique administrator identification or authentication. Examples of credentials include passwords and group membership certificates.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. User List.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth user\n\nIf there are any shared accounts that must not be active, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. User List.\n4. Check the box next to any shared/group accounts that must not be active.\n5. Click \"Delete\".\n6. Click \"Delete\" again on the next page.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh delete auth user <username>\ntmsh save sys config","ccis":["CCI-002142"]},{"vulnId":"V-266066","ruleId":"SV-266066r1051115_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.","description":"Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary.\n\nThe account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit must be added to the envelope as a record. Administrators must secure the credentials and disable the root account (if possible) when not needed for system administration functions.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. User List.\n4. Verify there is only one account of last resort listed.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth user\n\nIf there is more than one account of last resort listed, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. User List.\n4. Delete any local users that are not the account of last resort.\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh delete auth user <username>\ntmsh save sys config","ccis":["CCI-001358","CCI-002111"]},{"vulnId":"V-266067","ruleId":"SV-266067r1024598_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be configured to assign appropriate user roles or access levels to authenticated users.","description":"Successful identification and authentication must not automatically give an entity full access to a network device or security domain. \n\nAuthorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset or set of resources. Information systems use access control policies and enforcement mechanisms to implement this requirement. The F5 BIG-IP appliance must enforce organization-defined roles to control privileged access to configure the types or objects a user can manage and/or the tasks a user can perform.\n\nFor each BIG-IP user account, a different user role can be assigned to each administrative partition to which the user has access. This allows assignment of multiple user roles to each user account on the system. Users can assign a specific user role to each administrative partition to grant the user access. In this way, the BIG-IP configuration objects that the user can manage are controlled, as well as the types of actions the user can perform on those objects.\n\nSatisfies: SRG-APP-000033-NDM-000212, SRG-APP-000329-NDM-000287","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Remote Role Groups.\n4. Verify configured groups are assigned the appropriate role.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth remote-role\n\nNote: Verify configured groups are assigned the appropriate role.\n\nIf the BIG-IP appliance is not configured to assign appropriate user roles or access levels to authenticated users, this is a finding.","fixText":"Remote Roles (e.g., RADIUS, LDAP groups)\nFrom the BIG-IP GUI:\n1. System.\n2. Users.\n3. Remote Role Groups.\n4. Select the Group Name.\n5. Modify the Properties of the group to the appropriate access level.\n6. Update.\n\nLocal Users\n1. System.\n2. Users.\n3. User List.\n4. Select the user.\n5. Modify \"Partition Access\" to the appropriate access level.\n6. Update.","ccis":["CCI-000213","CCI-000366","CCI-002169"]},{"vulnId":"V-266068","ruleId":"SV-266068r1029557_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to audit the execution of privileged functions such as accounts additions and changes.","description":"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.\n\nSatisfies: SRG-APP-000343-NDM-000289, SRG-APP-000026-NDM-000208, SRG-APP-000027-NDM-000209, SRG-APP-000028-NDM-000210, SRG-APP-000029-NDM-000211, SRG-APP-000319-NDM-000283, SRG-APP-000080-NDM-000220, SRG-APP-000516-NDM-000334, SRG-APP-000091-NDM-000223, SRG-APP-000495-NDM-000318, SRG-APP-000499-NDM-000319, SRG-APP-000503-NDM-000320, SRG-APP-000504-NDM-000321, SRG-APP-000095-NDM-000225, SRG-APP-000096-NDM-000226, SRG-APP-000097-NDM-000227, SRG-APP-000098-NDM-000228, SRG-APP-000099-NDM-000229, SRG-APP-000100-NDM-000230, SRG-APP-000101-NDM-000231, SRG-APP-000381-NDM-000305","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Logs.\n3. Configuration.\n4. Options.\n5. Under Local Traffic Logging:\n a. MCP: Notice.\n b. SSL: Informational.\n c. Traffic Management OS: Informational.\n6. Under Audit Logging:\n a. MCP: Enable.\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh list sys daemon-log-settings tmm os-log-level\n\nNote: This command must return a value of \"informational\".\n\ntmsh list sys daemon-log-settings tmm ssl-log-level\n\nNote: This must return a value of \"informational\":\n\ntmsh list sys daemon-log-settings mcpd audit\n\nNote: This must return a value of \"enabled\".\n\ntmsh list sys daemon-log-settings mcpd log-level\n\nNote: This must return a value of \"notice\".\n\ntmsh list sys db log.ssl.level value\n\nNote: This must return a value of \"informational\".\n\nIf the BIG-IP appliance is not configured to audit the execution of privileged functions, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Logs.\n3. Configuration.\n4. Options.\n5. Under \"Local Traffic Logging\":\n a. MCP: Notice.\n b. SSL: Informational.\n c. Traffic Management OS: Informational.\n6. Under \"Audit Logging\":\n a. MCP: Enable.\n7. Update.\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh modify sys daemon-log-settings tmm os-log-level informational\ntmsh modify sys daemon-log-settings tmm ssl-log-level informational\ntmsh modify sys daemon-log-settings mcpd audit enabled\ntmsh modify sys daemon-log-settings mcpd log-level notice\ntmsh modify sys db log.ssl.level value informational\ntmsh save sys config","ccis":["CCI-002234","CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000166","CCI-000169","CCI-000366","CCI-000172","CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-001487","CCI-000135","CCI-001814"]},{"vulnId":"V-266069","ruleId":"SV-266069r1024600_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for at least 15 minutes.","description":"By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify Maximum Login Failures set to \"3\".\n5. Verify User Lockout set to \"Automatically enable locked-out user after 900 seconds\".\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth password-policy max-login-failures\n\nNote: Check for a value of \"3\".\n\ntmsh list auth password-policy lockout-duration\n\nNote: Check for a value of \"900\".\n\nIf the BIG-IP appliance is not configured to enforce the limit of three consecutive invalid logon attempts and lock out users for 900 seconds, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Set Maximum Login Failures to \"3\".\n5. Set User Lockout to \"Automatically enable locked-out user after 900 seconds\".\n6. Update.\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh modify auth password-policy max-login-failures 3\ntmsh modify auth password-policy lockout-duration 900\ntmsh save sys config","ccis":["CCI-000044"]},{"vulnId":"V-266070","ruleId":"SV-266070r1024881_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to display the Standard Mandatory DOD Notice and Consent Banner upon access to the TMOS User Interface.","description":"Display of the DOD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Security Banner Text To Show On The Login Screen.\n4. Review the \"Security Banner Text To Show On The Login Screen\" under the \"Security Settings\" section for the following verbiage:\n\n\"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.\"\n\nIf the banner is not presented, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Security Banner Text To Show On The Login Screen.\n4. Enter the text below in the \"Security Banner Text To Show On The Login Screen\" under the \"Security Settings\" section and then click \"Update\" to save.\n\n\"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.\"\n\nSSH Banner:\nFrom the BIG-IP GUI:\n1. System.\n2. Configuration.\n3. Device.\n4. SSHD.\n5. Check the box for \"Show The Security Banner On The Login Screen\".\n6. Enter the following in the \"Security Banner Text To Show On The Login Screen\" under the \"Security Settings\" section:\n\n\"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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"\n\n7. Update.\n8. From the BIG-IP console, type the following commands:\n\ntmsh modify sys sshd banner enabled\ntmsh modify sys sshd 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.\"\ntmsh save sys config","ccis":["CCI-000048"]},{"vulnId":"V-266074","ruleId":"SV-266074r1024605_rule","severity":"low","ruleTitle":"The F5 BIG-IP appliance must manage local audit storage capacity in accordance with organization-defined audit record storage requirements.","description":"To ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. \n\nThe value for the organization-defined audit record storage requirement will depend on the amount of storage available on the network device, the anticipated volume of logs, the frequency of transfer from the network device to centralized log servers, and other factors.","checkContent":"Verify the site configures the local audit record storage capacity using any of the following log-related elements in accordance with the site's System Security Plan:\n- Log rotation frequency.\n- Age at which log files become eligible for removal.\n- The number of archive copies that the system retains.\n- The message count for alertd log check.\n\nIf the site does not manage log storage capacity in compliance with the SSP or if the process is not documented, this is a finding.","fixText":"To manage audit record storage capacity, configure the following log-related elements on the BIG-IP system in accordance with the site's System Security Plan:\n- Change the log rotation frequency.\n- Change the age at which log files become eligible for removal.\n- Change the number of archive copies that the system retains.\n- Change the message count for alertd log check.","ccis":["CCI-001849"]},{"vulnId":"V-266075","ruleId":"SV-266075r1024607_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must generate audit records and send records to redundant central syslog servers that are separate from the appliance.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration.\n\nWithout 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.\n\nMCP audit records are generated from various components within the network device. For example, it logs the creation of DNS objects and DNSSEC configuration, including key creations.\n\nSatisfies: SRG-APP-000515-NDM-000325, SRG-APP-000360-NDM-000295, SRG-APP-000516-NDM-000350","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Logs.\n3. Configuration.\n4. Remote Logging.\n\nFrom the BIG-IP Console, issue the following command:\n\ntmsh list sys syslog remote-servers\n\nNote: This must return at least two remote IP addresses of syslog server.\n\nIf the BIG-IP appliance does not send audit records to one or more central syslog servers that are separate from the appliance, this is a finding.","fixText":"Configure two or more central syslog servers.\n\nFrom the BIG-IP GUI:\n1. System.\n2. Logs.\n3. Configuration.\n4. Remote Logging.\n5. Add the IP address of a syslog server in the \"Remote IP\" field, modify the port if necessary, and click \"Add\".\n6. Click \"Update\".\n\nFrom the BIG-IP Console, issue the following commands:\n\n     tmsh modify sys syslog remote-servers add { <name> { host <ip address> remote-port <port> } }\n     tmsh save sys config","ccis":["CCI-001851","CCI-001858","CCI-002605"]},{"vulnId":"V-266077","ruleId":"SV-266077r1024609_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).","description":"If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.\n\nTime stamps generated by the application include date and time. Time is commonly expressed in UTC, a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Platform.\n3. Verify that \"UTC\" is configured for \"Time Zone\".\n\nFrom the BIG-IP Console, issue the following commands:\n\ntmsh list sys ntp timezone\n\nNote: This must return a value of \"UTC\".\n\nIf the BIG-IP appliance is not configured for the UTC time zone, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Platform.\n3. Set \"UTC\" for \"Time Zone\".\n4. Click \"Update\".\n\nFrom the BIG-IP Console, issue the following commands:\n\ntmsh modify sys ntp timezone UTC\ntmsh save sys config","ccis":["CCI-001890"]},{"vulnId":"V-266078","ruleId":"SV-266078r1024610_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.","description":"Changes to any software components can have significant effects on the overall security of the network device. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the software has not been tampered with and has been provided by a trusted vendor. \n\nAccordingly, patches, service packs, or application components must be signed with a certificate recognized and approved by the organization.\n\nVerifying 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 has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The device must 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 certificate authority (CA).","checkContent":"From the BIG-IP console, type the following command:\n\ntmsh list /sys db liveinstall.checksig value\n\nNote: This must return a value of \"enable\".\n\nIf the db variable is not set to \"enable\", this is a finding.","fixText":"From the BIG-IP console, type the following commands:\n\ntmsh modify /sys db liveinstall.checksig value \"enable\"\ntmsh save sys config","ccis":["CCI-001749"]},{"vulnId":"V-266079","ruleId":"SV-266079r1024884_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be configured to use at least two authentication servers to authenticate administrative users.","description":"Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important protection against the insider threat. With robust centralized management, audit records for administrator account access to the organization's network devices can be more readily analyzed for trends and anomalies. The alternative method of defining administrator accounts on each device exposes the device configuration to remote access authentication attacks and system administrators with multiple authenticators for each network device.","checkContent":"From the BIG-IP GUI:\nRADIUS:\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - RADIUS\", verify different Primary and Secondary Hosts exist in the configuration.\nNote: To view Primary and Secondary Hosts, the \"Server Configuration\" must be set to \"Primary & Secondary\".\n\nTACACS+\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - TACACS+\", verify multiple servers exist in the configuration.\n5. Verify \"Authentication\" is set to \"Authenticate to each server until success\".\n\nIf the BIG-IP appliance is not configured to use at least two authentication servers to authenticate administrative users, this is a finding.","fixText":"From the BIG-IP GUI:\nRADIUS:\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - RADIUS\", click \"Change\" at the bottom.\n5. Configure values for Primary and Secondary servers.\nNote: To view Primary and Secondary Hosts, the \"Server Configuration\" must be set to \"Primary & Secondary\".\n6. Click \"Finished\".\n\nTACACS+\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - TACACS+\", click \"Change\" at the bottom\n5. Add multiple IP Addresses to the \"Servers\" field.\n6. Set \"Authentication\" to \"Authenticate to each server until success\".\n7. Click \"Finished\".","ccis":["CCI-000366","CCI-000370"]},{"vulnId":"V-266080","ruleId":"SV-266080r1024886_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be running an operating system release that is currently supported by the vendor.","description":"Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Configuration.\n3. Device.\n4. General.\n5. Verify \"Version\" is currently supported according to the vendor support site.\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh list cm device version\n\nNote: Verify the version is currently supported on the vendor's website.\n\nIf the BIG-IP appliance is not running an operating system release that is currently supported by the vendor, this is a finding.","fixText":"If the release is not a supported version, then update the version.\n\nFrom the BIG-IP GUI:\n1. Import .iso.\na. System.\nb. Software Management.\nc. Image List.\nd. Import .iso of supported BIG-IP operating system.\ne. Import the corresponding .iso.sig file.\nf. Install.\n2. Switch boot location to new install.\na. System.\nb. Software Management.\nc. Boot Locations.\nd. Select new install location.\ne. Optionally change \"Install Configuration\" to \"Yes\".\nf. Activate.","ccis":["CCI-000366"]},{"vulnId":"V-266083","ruleId":"SV-266083r1024615_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must obtain its public key certificates from an appropriate certificate policy through an approved service provider.","description":"For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority (CA) will suffice.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Certificate Management.\n3. Device Certificate Management.\n4. Device Certificate.\n5. Verify the Issuer is an approved CA.\n\nFrom the BIG-IP console, type the following command:\n\nopenssl x509 -in /config/httpd/conf/ssl.crt/server.crt -text\n\nNote: Verify the issuer is an approved CA.\n\nIf the BIG-IP appliance does not obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Certificate Management.\n3. Device Certificate Management.\n4. Device Certificate Signing Request.\n5. Click \"Renew\".\n6. Select \"Certificate Authority\" in \"Issuer\" and complete the form.\n7. Copy or download and submit CSR to an approved CA.\n8. Import the certificate via Device Certificate Management >> Device Certificate >> Import.","ccis":["CCI-000366","CCI-001159"]},{"vulnId":"V-266084","ruleId":"SV-266084r1043177_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.","description":"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 unused or unnecessary physical and logical ports/protocols on information systems.\n\nNetwork devices 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., email and web services); however, doing so increases risk over limiting the services provided by any one component.\n\nTo support the requirements and principles of least functionality, the network device 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. Some network devices have capabilities enabled by default; if these capabilities are not necessary, they must be disabled. If a particular capability is used, then it must be documented and approved.","checkContent":"From the BIG-IP GUI:\n1. Local Traffic.\n2. Virtual Servers.\n3. Verify the list of virtual servers are not configured to listen on unnecessary and/or nonsecure functions, ports, protocols, and/or services.\n\nIf the BIG-IP appliance is configured to listen or run unnecessary and/or nonsecure functions, ports, protocols, and/or services, this is a finding.","fixText":"Check the PPSM CAL and the site's System Security Plan/documentation for a list of prohibited ports, protocols, and services.\n\nFrom the BIG-IP GUI:\n1. Local Traffic.\n2. Virtual Servers.\n3. For any virtual server(s) listening on all unnecessary and/or nonsecure functions, ports, protocols, and/or services, check the box next to the virtual server and click \"Delete\".\n4. Click \"Delete\" again.","ccis":["CCI-000382"]},{"vulnId":"V-266085","ruleId":"SV-266085r1113746_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be configured to use multifactor authentication (MFA) for interactive logins.","description":"MFA is when two or more factors are used to confirm the identity of an individual who is requesting access to digital information resources. Valid factors include something the individual knows (e.g., username and password), something the individual has (e.g., a smartcard or token), or something the individual is (e.g., a fingerprint or biometric). Legacy information system environments only use a single factor for authentication, typically a username and password combination. Although two pieces of data are used in a username and password combination, this is still considered single factor because an attacker can obtain access simply by learning what the user knows. Common attacks against single-factor authentication are attacks on user passwords. These attacks include brute force password guessing, password spraying, and password credential stuffing. MFA, along with strong user account hygiene, helps mitigate the threat of having account passwords discovered by an attacker. Even in the event of a password compromise, with MFA implemented and required for interactive login, the attacker still needs to acquire something the user has or replicate a piece of the user’s biometric digital presence.\n\nPrivate industry recognizes and uses a wide variety of MFA solutions. However, DOD public key infrastructure (PKI) is the only prescribed method approved for DOD organizations to implement MFA. For authentication purposes, centralized DOD certificate authorities (CA) issue PKI certificate key pairs (public and private) to individuals using the prescribed x.509 format. The private certificates that have been generated by the issuing CA are downloaded and saved to smartcards which, within DOD, are referred to as common access cards (CAC) or personal identity verification (PIV) cards. This happens at designated DOD badge facilities. The CA maintains a record of the corresponding public keys for use with PKI-enabled environments. Privileged user smartcards, or “alternate tokens”, function in the same manner, so this requirement applies to all interactive user sessions (authorized and privileged users).\n\nNote: This requirement is used in conjunction with the use of a centralized authentication server (e.g., AAA, RADIUS, LDAP), a separate but equally important requirement. The MFA configuration of this requirement provides identification and the first phase of authentication (the challenge and validated response, thereby confirming the PKI certificate that was presented by the user). The centralized authentication server will provide the second phase of authentication (the digital presence of the PKI ID as a valid user in the requested security domain) and authorization. The centralized authentication server will map validated PKI identities to valid user accounts and determine access levels for authenticated users based on security group membership and role. In cases where the centralized authentication server is not used by the network device for user authorization, the network device must map the authenticated identity to the user account for PKI-based authentication.\n\nSatisfies: SRG-APP-000149-NDM-000247, SRG-APP-000177-NDM-000263, SRG-APP-000153-NDM-000249","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify \"User Directory\" is configured to use RADIUS or TACACS+.\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh list auth source\n\nVerify \"User Directory\" is configured to use RADIUS or TACACS+.\n\nIf the BIG-IP appliance is not configured to use DOD PKI with RADIUS or TACACS+ for interactive logins, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Click \"Change\".\n5. Select RADIUS, or TACACS+ from the \"Remote\" options and fill out the configuration depending on the chosen option.\n6. Fill out all other fields as appropriate for the environment.\n7. Click \"Finished\".\n\nNote: This method has been verified with the vendor and DISA for use in DOD. Other methods are not recommended/have not been tested to determine if DOD requirements have been met or if additional licenses and AO approval are required.","ccis":["CCI-000765","CCI-000166","CCI-000187","CCI-000764","CCI-000770"]},{"vulnId":"V-266086","ruleId":"SV-266086r1024925_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.","description":"If NTP is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.","checkContent":"From the BIG-IP Console:\ncat /etc/ntp/keys\n\n#Verify this key is installed on all the NTP servers and clients participating in the NTP time synchronization.\n\ntmsh list sys ntp include\n\n#Verify there is a line similar to the following:\n#server <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys>\n\nIf the BIG-IP appliance is not configured to authenticate Network Time Protocol sources using authentication that is cryptographically based, this is a finding.","fixText":"From the BIG-IP console, type the following commands:\n\necho \"1 M <passphrase> #MD5 Key\" > /etc/ntp/keys\n\nNote: This command assumes that no other keys have been previously configured in the /etc/ntp/keys file. Running this command will overwrite the file.\n\n#Make sure this key is installed on all the NTP servers and clients participating in the NTP time synchronization.\n\ntmsh edit sys ntp all-properties\n\n#Replace the \"include\" section with the following (add as many ntp server lines as necessary for the environment, but configure at least 2):\n\ninclude \"server <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys>\nserver <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys>\"\n\ntmsh save sys config","ccis":["CCI-001967"]},{"vulnId":"V-266087","ruleId":"SV-266087r1024891_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must enforce a minimum 15-character password length.","description":"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.\n\nThe shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify that \"Secure Password Enforcement\" is set to \"Enabled\".\n5. Verify that \"Minimum Length\" is set to at least 15.\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh list auth password-policy minimum-length\n\nNote: Verify the value is set to at least 15.\n\nIf the BIG-IP appliance is not configured to enforce a minimum 15-character password length, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Under \"Password Policy\" set \"Secure Password Enforcement\" to \"Enabled\".\n5. Configure \"Minimum Length\" to 15.\n6. Click \"Update\".\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh modify auth password-policy minimum-length 15\ntmsh save sys config","ccis":["CCI-000205"]},{"vulnId":"V-266088","ruleId":"SV-266088r1024894_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must enforce password complexity by requiring that at least one uppercase character be used.","description":"Use of a complex passwords 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.\n\nPassword complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised.\n\nMultifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords must only be used when MFA using PKI is not available, and for the account of last resort and root account.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify that \"Secure Password Enforcement\" is set to \"Enabled\".\n5. Verify under \"Required Characters\" that \"Uppercase\" is set to at least 1.\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh list auth password-policy required-uppercase\n\nNote: Verify the value is set to at least 1.\n\nIf the BIG-IP appliance is not configured to enforce password complexity by requiring that at least one uppercase character be used, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Under \"Password Policy\" set \"Secure Password Enforcement\" to \"Enabled\".\n5. Under \"Required Characters\" set \"Uppercase\" to at least 1.\n6. Click \"Update\".\n\nFrom the BIG-IP console, type the following command(s):\n\ntmsh modify auth password-policy required-uppercase 1\ntmsh save sys config","ccis":["CCI-000192"]},{"vulnId":"V-266089","ruleId":"SV-266089r1024622_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must enforce password complexity by requiring that at least one lowercase character be used.","description":"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.\n\nPassword complexity is one factor of several that determine 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.\n\nMultifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords must only be used when MFA using PKI is not available, and for the account of last resort and root account.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify that \"Secure Password Enforcement\" is set to \"Enabled\".\n5. Verify under \"Required Characters\" that \"Lowercase\" is set to at least 1.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth password-policy required-lowercase\n\nNote: Verify the value is set to at least 1.\n\nIf the BIG-IP appliance is not configured to enforce password complexity by requiring that at least one lowercase character be used, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Under \"Password Policy\" set \"Secure Password Enforcement\" to \"Enabled\".\n5. Under \"Required Characters\" set \"Lowercase\" to at least 1.\n6. Click \"Update\".\n\nFrom the BIG-IP console, type the following commands:\n\ntmsh modify auth password-policy required-lowercase 1\ntmsh save sys config","ccis":["CCI-000193"]},{"vulnId":"V-266090","ruleId":"SV-266090r1024623_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must enforce password complexity by requiring that at least one numeric character be used.","description":"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.\n\nPassword complexity is one factor of several that determine 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.\n\nMultifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords must only be used when MFA using PKI is not available, and for the account of last resort and root account.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify that \"Secure Password Enforcement\" is set to \"Enabled\".\n5. Verify under \"Required Characters\" that \"Numeric\" is set to at least 1.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth password-policy required-numeric\n\nNote: Verify the value is set to at least 1.\n\nIf the BIG-IP appliance is not configured to enforce password complexity by requiring that at least one numeric character be used, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Under \"Password Policy\" set \"Secure Password Enforcement\" to \"Enabled\".\n5. Under \"Required Characters\" set \"Numeric\" to at least 1.\n6. Click \"Update\".\n\nFrom the BIG-IP console, type the following command:\n\ntmsh modify auth password-policy required-numeric 1\ntmsh save sys config","ccis":["CCI-000194"]},{"vulnId":"V-266091","ruleId":"SV-266091r1024624_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must enforce password complexity by requiring that at least one special character be used.","description":"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.\n\nPassword complexity is one factor of several that determine 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.\n\nMultifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords must only be used when MFA using PKI is not available, and for the account of last resort and root account.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Verify that \"Secure Password Enforcement\" is set to \"Enabled\".\n5. Verify under \"Required Characters\" that \"Other\" is set to at least 1.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list auth password-policy required-special\n\nNote: Verify the value is set to at least 1.\n\nIf the BIG-IP appliance is not configured to enforce password complexity by requiring that at least one special character be used, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. Under \"Password Policy\" set \"Secure Password Enforcement\" to \"Enabled\".\n5. Under \"Required Characters\" set \"Other\" to at least 1.\n6. Click \"Update\".\n\nFrom the BIG-IP console, type the following command:\n\ntmsh modify auth password-policy required-special 1\ntmsh save sys config","ccis":["CCI-001619"]},{"vulnId":"V-266092","ruleId":"SV-266092r1043189_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must require that when a password is changed, the characters are changed in at least eight of the positions within the password.","description":"If the application 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.\n\nThe 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.\n\nMultifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords must only be used when MFA using PKI is not available, and for the account of last resort and root account.","checkContent":"From the BIG-IP console, type the following command:\n\ntmsh list sys db password.difok\n\nNote: Verify the value is set to at least 8.\n\nIf the BIG-IP appliance is not configured to require that when a password is changed, the characters are changed in at least eight of the positions within the password, this is a finding.","fixText":"If this setting has been changed from the default value of 8, reset the value.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh modify sys db password.difok value 8\ntmsh save sys config","ccis":["CCI-000195"]},{"vulnId":"V-266093","ruleId":"SV-266093r1024899_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must prohibit the use of cached authenticators after eight hours or less.","description":"Some authentication implementations can be configured to use cached authenticators.\n\nIf cached authentication information is out-of-date, the validity of the authentication information may be questionable.\n\nThe organization-defined time period must be established for each device depending on the nature of the device; for example, a device with just a few administrators in a facility with spotty network connectivity may merit a longer caching time period than a device with many administrators.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - ClientCert LDAP\", verify \"OCSP Response Max Age\" is configured for an organization-defined time period.\nNote: The OCSP Override option must be set to \"on\" to view the OCSP Response Max Age value.\n\nIf the BIG-IP appliance is not configured to prohibit the use of cached authenticators after an organization-defined time period, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. If ClientCert LDAP is used as the remote authentication type, configure \"OCSP Response Max Age\" for an organization-defined time period.\nNote: The OCSP Override option must be set to \"on\" to view the OCSP Response Max Age value.","ccis":["CCI-002007"]},{"vulnId":"V-266094","ruleId":"SV-266094r1024902_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must be configured to use DOD approved OCSP responders or CRLs to validate certificates used for PKI-based authentication.","description":"Once issued by a DOD certificate authority (CA), public key infrastructure (PKI) certificates are typically valid for three years or shorter within the DOD. However, there are many reasons a certificate may become invalid before the prescribed expiration date. For example, an employee may leave or be terminated and still possess the smartcard on which the PKI certificates were stored. Another example is that a smartcard containing PKI certificates may become lost or stolen. A more serious issue could be that the CA or server which issued the PKI certificates has become compromised, thereby jeopardizing every certificate keypair that was issued by the CA. These examples of revocation use cases and many more can be researched further using internet cybersecurity resources.\n\nPKI user certificates presented as part of the identification and authentication criteria (e.g., DOD PKI as multifactor authentication [MFA]) must be checked for validity by network devices. For example, valid PKI certificates are digitally signed by a trusted DOD certificate authority (CA). Additionally, valid PKI certificates are not expired, and valid certificates have not been revoked by a DOD CA.\n\nNetwork devices can verify the validity of PKI certificates by checking with an authoritative CA. One method of checking the status of PKI certificates is to query databases referred to as certificate revocation lists (CRL). These are lists which are published, updated, and maintained by authoritative DOD CAs. For example, once certificates are expired or revoked, issuing CAs place the certificates on a CRL. Organizations can download these lists periodically (i.e., daily or weekly) and store them locally on the devices themselves or even onto another nearby local enclave resource. Storing them locally ensures revocation status can be checked even if internet connectivity is severed at the enclave’s point of presence (PoP). However, CRLs can be rather large in storage size and further, the use of CRLs can be rather taxing on some computing resources.\n\nAnother method of validating certificate status is to use the online certificate status protocol (OCSP). Using OCSP, a requestor (i.e., the network device which the user is trying to authenticate to) sends a request to an authoritative CA challenging the validity of a certificate that has been presented for identification and authentication. The CA receives the request and sends a digitally signed response indicating the status of the user’s certificate as valid, revoked, or unknown. Network devices must only allow access for responses that indicate the certificates presented by the user were considered valid by an approved DOD CA. OCSP is the preferred method because it is fast, provides the most current status, and is lightweight.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. If \"User Directory\" is configured for \"Remote - ClientCert LDAP\", verify the \"OCSP Responder\" configured is DOD approved\nNote: The OCSP Override option must be set to \"on\" to view the OCSP Responder value.\n\nIf the BIG-IP appliance is not configured to use DOD-approved OCSP responders or CRLs to validate certificates used for PKI-based authentication, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Users.\n3. Authentication.\n4. If ClientCert LDAP is used as the remote authentication type, click \"Change\".\n6. Set \"OCSP Responder\" IP address to one that is DOD approved.\nNote: The OCSP Override option must be set to \"on\" to view the OCSP Responder value.\n7. Click \"Finish\".","ccis":["CCI-000185"]},{"vulnId":"V-266095","ruleId":"SV-266095r1024904_rule","severity":"high","ruleTitle":"The F5 BIG-IP appliance must set the idle time before automatic logout to five minutes of inactivity except to fulfill documented and validated mission requirements.","description":"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. \n\nTerminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level, or deallocating 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 device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.\n\nSatisfies: SRG-APP-000190-NDM-000267, SRG-APP-000003-NDM-000202","checkContent":"If a documented and validated reason for not implementing the five-minute idle timeout exists, this is not a finding.\n\nFrom the BIG-IP GUI:\nHTTPD/TMSH:\n1. System.\n2. Preferences.\n3. Under Security Settings, verify \"Idle Time Before Automatic Logout\" is configured for 300 seconds or less.\n\nSSHD:\n1. System.\n2. Configuration.\n3. Device.\n4. SSHD.\n5. Verify \"Idle Time Before Automatic Logout\" is configured for 300 seconds or less.\n\nFrom the BIG-IP Console, issue the following commands:\nHTTPD/TMSH:\n\ntmsh list sys httpd auth-pam-idle-timeout\nNote: This must return a value of 300 or less.\n\ntmsh list sys httpd auth-pam-dashboard-timeout\nNote: This must return a value of \"on\".\n\ntmsh list sys global-settings console-inactivity-timeout\nNote: This must return a value of 300 or less.\n\ntmsh list cli global-settings idle-timeout\nNote: This must return a value of 5.\n\nSSHD:\ntmsh list sys sshd inactivity-timeout\nNote: This must return a value of 300 or less.\n\nIf the BIG-IP appliance is not configured to terminate inactive sessions after five minutes of inactivity, this is a finding.","fixText":"From the BIG-IP GUI:\nHTTPD/TMSH:\n1. System.\n2. Preferences.\n3. Under Security Settings configure \"Idle Time Before Automatic Logout\" to 300 seconds.\n4. Click \"Update\".\n\nSSHD:\n1. System.\n2. Configuration.\n3. Device.\n4. SSHD.\n5. Configure \"Idle Time Before Automatic Logout\" to 300 seconds.\n6. Click \"Update\".\n\nFrom the BIG-IP Console, issue the following commands:\nHTTPD/TMSH:\ntmsh modify sys httpd auth-pam-idle-timeout 300\n\ntmsh modify sys httpd auth-pam-dashboard-timeout on\n\ntmsh modify sys global-settings console-inactivity-timeout 300\n\ntmsh modify cli global-settings idle-timeout 5\n\nSSHD:\ntmsh modify sys sshd inactivity-timeout 300\n\ntmsh save sys config","ccis":["CCI-001133","CCI-000057"]},{"vulnId":"V-266096","ruleId":"SV-266096r1024630_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must conduct backups of the configuration at a weekly or organization-defined frequency and store on a separate device.","description":"Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system configuration and security settings. If this information were not backed up, and a system failure were to occur, the security settings would be difficult to reconfigure quickly and accurately. Maintaining a backup of information system and security-related documentation provides for a quicker recovery time when system outages occur.\n\nThis control requires the network device to support the organizational central backup process for user account information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Archives.\n3. Review the list of archives to verify backups are conducted in accordance with the local backup policy.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh list sys ucs\n\nIf the BIG-IP appliance is not configured to back up at system-level information weekly or at an organization-defined frequency this is a finding.","fixText":"Document this process in the system security plan (SSP) and perform periodic manual backups. This process backs up the current configuration. Backups must be weekly or a documented organization-defined frequency.\n\nFrom the BIG-IP GUI:\n1. System.\n2. Archives.\n3. Create.\n\nFrom the BIG-IP console, type the following command:\n\ntmsh save sys ucs <name>","ccis":["CCI-000366","CCI-000539"]},{"vulnId":"V-266134","ruleId":"SV-266134r1024908_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to display the Standard Mandatory DOD Notice and Consent Banner when accessing via SSH.","description":"Display of the DOD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Configuration.\n3. Device.\n4. SSHD.\n5. Verify the box for “Show The Security Banner On The Login Screen” is checked.\n6. Review the \"Security Banner Text To Show On The Login Screen\" under the \"Security Settings\" section for the following verbiage:\n\n\"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.\"\n\nIf such a banner is not presented, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Configuration.\n3. Device.\n4. SSHD.\n5. Check the box for \"Show The Security Banner On The Login Screen\".\n6. Enter the following in the \"Security Banner Text To Show On The Login Screen\" under the \"Security Settings\" section and then select \"Update\" to save.\n\n\"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.\"\n\nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n\"I've read & consent to terms in IS user agreem't.\"","ccis":["CCI-000050"]},{"vulnId":"V-266135","ruleId":"SV-266135r1024669_rule","severity":"medium","ruleTitle":"The F5 BIG-IP appliance must be configured to restrict a consistent inbound IP for the entire management session.","description":"This security measure helps limit the effects of denial-of-service (DoS) attacks by employing anti-session hijacking security safeguards. Session hijacking, also called cookie hijacking, is the exploitation of a valid computer session to gain unauthorized access to an application. The attacker steals (or hijacks) the cookies from a valid user and attempts to use them for authentication.","checkContent":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Under \"Security Settings\", verify \"Require A Consistent Inbound IP For The Entire Web Session\" box is checked.\n\nIf the BIG-IP appliance is not configured to require a consistent inbound IP for the entire session for management sessions, this is a finding.","fixText":"From the BIG-IP GUI:\n1. System.\n2. Preferences.\n3. Under \"Security Settings\", check \"Require A Consistent Inbound IP For The Entire Web Session\".\n4. Update.","ccis":["CCI-002385"]}]}