diff --git a/benchmarks/DISA/U_F5_BIG-IP_Access_Policy_Manager_STIG_V2R3_Manual-xccdf.xml b/benchmarks/DISA/U_F5_BIG-IP_Access_Policy_Manager_STIG_V2R3_Manual-xccdf.xml
new file mode 100644
index 000000000..6d005779b
--- /dev/null
+++ b/benchmarks/DISA/U_F5_BIG-IP_Access_Policy_Manager_STIG_V2R3_Manual-xccdf.xml
@@ -0,0 +1,643 @@
+acceptedF5 BIG-IP Access Policy Manager Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 3 Benchmark Date: 29 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-NET-000015-ALG-000016<GroupDescription></GroupDescription>F5BI-AP-000003The BIG-IP APM module must enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.<VulnDiscussion>Successful authentication must not automatically give an entity access to an asset or security boundary. The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. All DoD systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access.
+
+Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization.
+
+Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. ALGs must use these policies and mechanisms to control access on behalf of the application for which it is acting as intermediary.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-59929SV-74359CCI-000213If user access control intermediary services are provided as part of the traffic management functions of the BIG-IP Core, configure the BIG-IP APM module to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.If the BIG-IP APM module does not provide user access control intermediary services as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP APM module is configured to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles >> Access Profiles List.
+
+Review Access Policy Profiles to verify configuration for authorization by employing identity-based, role-based, and/or attribute-based security policies.
+
+If the BIG-IP APM is not configured to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies, this is a finding.SRG-NET-000041-ALG-000022<GroupDescription></GroupDescription>F5BI-AP-000023The F5 BIG-IP appliance providing user access control intermediary services must display the Standard Mandatory DOD-approved Notice and Consent Banner before granting access to resources.<VulnDiscussion>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.
+
+System use notifications are required only for access via logon interfaces with human users.
+
+The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for network elements that can accommodate banners of 1300 characters:
+
+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
+
+By using this IS (which includes any device attached to this IS), you consent to the following conditions:
+
+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
+
+-At any time, the USG may inspect and seize data stored on this IS.
+
+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
+
+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
+
+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+This policy only applies to ALGs (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-59931SV-74361CCI-000048From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Click the "+" sign after the point in the policy where the user's UPN has been verified.
+6. "General Purpose" tab.
+7. Select "Decision Box".
+8. Click "Add Item".
+9. Enter the DOD-approved Notice and Consent Banner in the Decision Box Title.
+
+"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."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+10. Click "Save".
+11. Click "Apply Access Policy".If the BIG-IP appliance does not provide user access control intermediary services, this is not applicable.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Verify a Decision Box object exists that displays the DOD-approved Notice and Consent Banner.
+6. Review the "Security Banner Text To Show On The Login Screen" under the "Security Settings" section for the following verbiage:
+
+"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."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+If a DOD-approved Notice and Consent Banner does not exist in the Access Profile VPE, this is a finding.SRG-NET-000042-ALG-000023<GroupDescription></GroupDescription>F5BI-AP-000025The BIG-IP APM module must retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users accessing virtual servers acknowledge the usage conditions and take explicit actions to log on for further access.<VulnDiscussion>The banner must be acknowledged by the user prior to allowing the user access to the network. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law.
+
+To establish acceptance of the application usage policy, a click-through banner at application logon is required. The network element must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74363V-59933CCI-000050If user access control intermediary services are provided, configure an access policy in the BIG-IP APM module to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.If the BIG-IP APM module does not provide user access control intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and takes explicit actions to log on for further access.
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users accessing virtual servers acknowledge the usage conditions and take explicit actions to log on for further access.
+
+If the BIG-IP APM module is not configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access, this is a finding.SRG-NET-000043-ALG-000024<GroupDescription></GroupDescription>F5BI-AP-000027The BIG-IP APM module must display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the publicly accessible network element ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. This requirement applies to network elements that have the concept of a user account and have the logon function residing on the network element.
+
+The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for network elements that can accommodate banners of 1300 characters:
+
+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
+
+By using this IS (which includes any device attached to this IS), you consent to the following conditions:
+
+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
+
+-At any time, the USG may inspect and seize data stored on this IS.
+
+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
+
+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
+
+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services off-loaded from the application. Publicly access systems are used in DoD to provide benefit information, pay information, or public services. There may also be self-registration and authorization services provided by these gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60025SV-74455CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388If user access control intermediary services are provided, configure an access policy in the BIG-IP APM module to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.If the BIG-IP APM module does not provide user access control intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.
+
+If the BIG-IP APM module is not configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications, this is a finding.SRG-NET-000138-ALG-000063<GroupDescription></GroupDescription>F5BI-AP-000073The BIG-IP APM module must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users) when connecting to virtual servers.<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
+
+Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses except the following:
+
+1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and
+
+2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.
+
+This requirement applies to ALGs that provide user proxy services, including identification and authentication. This service must use the site's directory service (e.g., Active Directory). Directory services must not be installed onto the gateway.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74457V-60027CCI-000764If user access control intermediary services are provided, configure an access policy in the BIG-IP APM module to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
+
+If the BIG-IP APM is not configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users), this is a finding.SRG-NET-000138-ALG-000088<GroupDescription></GroupDescription>F5BI-AP-000075The BIG-IP APM module must be configured with a pre-established trust relationship and mechanisms with appropriate authorities (e.g., Active Directory or authentication, authorization, and accounting (AAA) server) that validate user account access authorizations and privileges when providing access control to virtual servers.<VulnDiscussion>User account and privilege validation must be centralized in order to prevent unauthorized access using changed or revoked privileges.
+
+ALGs can implement functions such as traffic filtering, authentication, access, and authorization functions based on computer and user privileges. However, the directory service (e.g., Active Directory or LDAP) must not be installed on the ALG, particularly if the gateway resides on the untrusted zone of the Enclave.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74459V-60029CCI-000764If user access control intermediary services are provided, configure an access policy in the BIG-IP APM module with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges.If the BIG-IP APM module does not provide user access control intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured with a pre-established trust relationship and mechanisms with appropriate authorities (e.g., Active Directory or AAA server) that validate user account access authorizations and privileges.
+
+If the BIG-IP APM is not configured with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges, this is a finding.SRG-NET-000138-ALG-000089<GroupDescription></GroupDescription>F5BI-AP-000077The BIG-IP APM module must restrict user authentication traffic to specific authentication server(s) when providing user authentication to virtual servers.<VulnDiscussion>User authentication can be used as part of the policy filtering rule sets. Some URLs or network resources can be restricted to authenticated users only. Users are prompted by the application or browser for credentials. Authentication service may be provided by the ALG as an intermediary for the application; however, the authentication credential must be stored in the site's directory services server.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., proxy capability). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74461V-60031CCI-000764If user authentication intermediary services are provided, configure an access policy in the BIG-IP APM module to restrict user authentication traffic to specific authentication server(s).If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured to restrict user authentication traffic to specific authentication server(s).
+
+If the BIG-IP APM module is not configured to restrict user authentication traffic to a specific authentication server(s), this is a finding.SRG-NET-000140-ALG-000094<GroupDescription></GroupDescription>F5BI-AP-000079The BIG-IP APM module must use multifactor authentication for network access to non-privileged accounts.<VulnDiscussion>To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
+
+Multifactor authentication uses two or more factors to achieve authentication. Factors include:
+
+1) Something you know (e.g., password/PIN);
+
+2) Something you have (e.g., cryptographic, identification device, token); and
+
+3) Something you are (e.g., biometric).
+
+Non-privileged accounts are not authorized on the network element regardless of configuration.
+
+Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection.
+
+The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
+
+This requirement applies to ALGs that provide user authentication intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74463V-60033CCI-000766If user authentication intermediary services are provided, configure an access policy in the BIG-IP APM module to use multifactor authentication for network access to non-privileged accounts.If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM is configured to use multifactor authentication for network access to non-privileged accounts.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for granting access.
+
+Verify the Access Profile is configured to use multifactor authentication for network access to non-privileged accounts.
+
+If the BIG-IP APM module is not configured to use multifactor authentication for network access to non-privileged accounts, this is a finding.SRG-NET-000166-ALG-000101<GroupDescription></GroupDescription>F5BI-AP-000085The BIG-IP APM module must map the authenticated identity to the user account for PKI-based authentication to virtual servers.<VulnDiscussion>Authorization for access to any network element requires an approved and assigned individual account identifier. To ensure only the assigned individual is using the account, the account must be bound to a user certificate when PKI-based authentication is implemented.
+
+This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60035SV-74465CCI-000187If the BIG-IP APM module provides PKI-based, user authentication intermediary services, configure a profile in the BIG-IP APM module to map the authenticated identity to the user account for PKI-based authentication.If the BIG-IP APM module does not provide PKI-based, user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module maps the authenticated identity to the user account for PKI-based authentication.
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for PKI-based authentication.
+
+Verify the Access Profile is configured to map the authenticated identity to the user account for PKI-based authentication.
+
+If the BIG-IP APM module does not map the authenticated identity to the user account for PKI-based authentication, this is a finding.SRG-NET-000169-ALG-000102<GroupDescription></GroupDescription>F5BI-AP-000087The BIG-IP APM module must be configured to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.<VulnDiscussion>Lack of authentication enables anyone to gain access to the network or possibly a network element that provides opportunity for intruders to compromise resources within the network infrastructure. By identifying and authenticating non-organizational users, their access to network resources can be restricted accordingly.
+
+Non-organizational users will be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access. Authorization requires an individual account identifier that has been approved, assigned, and configured on an authentication server. Authentication of user identities is accomplished through the use of passwords, tokens, biometrics, or in the case of multifactor authentication, some combination thereof.
+
+This control applies to application layer gateways that provide content filtering and proxy services on network segments (e.g., DMZ) that allow access by non-organizational users. This requirement focuses on authentication requests to the proxied application for access to destination resources and policy filtering decisions rather than administrator and management functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60037SV-74467CCI-000804If the BIG-IP APM module provides user authentication intermediary services to non-organizational users, configure a profile in the BIG-IP APM module to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.If the BIG-IP APM module does not provide user authentication intermediary services to non-organizational users, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used to identify and authenticate non-organizational users.
+
+Verify the Access Profile is configured to uniquely identify and authenticate non-organizational users.
+
+If the BIG-IP APM module is not configured to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers, this is a finding.SRG-NET-000313-ALG-000010<GroupDescription></GroupDescription>F5BI-AP-000153The BIG-IP APM module access policy profile must control remote access methods to virtual servers.<VulnDiscussion>Remote access devices, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies).
+
+This requirement applies to ALGs providing remote access proxy services as part of its intermediary services (e.g., OWA or TLS gateway). ALGs that proxy remote access must be capable of taking enforcement action (i.e., blocking, restricting, or forwarding to an enforcement mechanism) if traffic monitoring reveals unauthorized activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60043SV-74473CCI-002314If intermediary services for remote access communications traffic are provided, configure the BIG-IP APM module to control remote access methods.If the BIG-IP APM module does not serve as an intermediary for remote access traffic (e.g., web content filter, TLS and webmail), this is not applicable.
+
+Verify the BIG-IP APM module is configured to control remote access methods.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for managing remote access.
+
+Verify the Access Profile is configured to control remote access methods.
+
+If the BIG-IP APM module is not configured to control remote access methods, this is a finding.SRG-NET-000337-ALG-000096<GroupDescription></GroupDescription>F5BI-AP-000191The BIG-IP APM module must require users to reauthenticate when the user's role or information authorizations are changed.<VulnDiscussion>Without reauthentication, users may access resources or perform tasks for which authorization has been removed.
+
+In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations. Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation and role changes.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of user authentication (e.g., VPN or ALG capability). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60045SV-74475CCI-002038Configure an access policy in the BIG-IP APM module to require users to reauthenticate when the user's role or information authorizations are changed.
+
+This will also require the administrator to force reauthentication when changes occur that the system cannot automatically detect. Update administrator training and the site's SSP to document this process.If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for each Access Profile used for organizational access.
+
+If the BIG-IP APM module is not configured or process is not documented to require users to reauthenticate when the user's role or information authorizations are changed, this is a finding.SRG-NET-000339-ALG-000090<GroupDescription></GroupDescription>F5BI-AP-000193The BIG-IP APM module must be configured to require multifactor authentication for remote access with non-privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.<VulnDiscussion>For remote access to non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+An example of compliance with this requirement is the use of a one-time password token and PIN coupled with a password or the use of a CAC/PIV card and PIN coupled with a password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74477V-60047CCI-001951If user authentication intermediary services are provided, configure an access policy in the BIG-IP APM module to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for remote access for non-privileged accounts.
+
+Verify the Access Profile is configured to require multifactor authentication for remote access with non-privileged accounts.
+
+If the BIG-IP APM module is not configured to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access, this is a finding.SRG-NET-000340-ALG-000091<GroupDescription></GroupDescription>F5BI-AP-000195The BIG-IP APM module must be configured to require multifactor authentication for remote access with privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.<VulnDiscussion>For remote access to privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74479V-60049CCI-001948If user authentication intermediary services are provided, configure an access policy in the BIG-IP APM module to require 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.If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for remote access for privileged accounts.
+
+Verify the Access Profile is configured to require multifactor authentication for remote access with privileged accounts.
+
+If the BIG-IP APM module is not configured to require 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, this is a finding.SRG-NET-000349-ALG-000106<GroupDescription></GroupDescription>F5BI-AP-000211The BIG-IP APM module must conform to FICAM-issued profiles.<VulnDiscussion>Without conforming to Federal Identity, Credential, and Access Management (FICAM)-issued profiles, the information system may not be interoperable with FICAM-authentication protocols, such as SAML 2.0 and OpenID 2.0.
+
+Use of FICAM-issued profiles addresses open identity management standards.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of a non-organizational user, (e.g., ALG capability that is the front end for an application in a DMZ).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60061SV-74491CCI-002014If the BIG-IP APM module provides user authentication intermediary services to non-organizational users, configure a profile in the BIG-IP APM module that conforms to FICAM-issued profiles.If the BIG-IP APM module does not provide user authentication intermediary services to non-organizational users, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used to identify and authenticate non-organizational users.
+
+Verify the Access Profile is configured to conform to FICAM-issued profiles.
+
+If the BIG-IP APM module is not configured to conform to FICAM-issued profiles, this is a finding.SRG-NET-000380-ALG-000128<GroupDescription></GroupDescription>F5BI-AP-000229The BIG-IP APM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.<VulnDiscussion>A common vulnerability of network elements is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
+
+The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notifying the appropriate personnel, creating an audit record, and rejecting invalid input.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher layer proxy functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74493V-60063CCI-002754Configure the BIG-IP APM module to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.Verify the BIG-IP APM module is configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.
+
+This can be demonstrated by the SA sending an invalid input to a virtual server. Provide evidence that the virtual server was able to handle the invalid input and maintain operation.
+
+If the BIG-IP APM module is not configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives, this is a finding.SRG-NET-000517-ALG-000006<GroupDescription></GroupDescription>F5BI-AP-000147The BIG-IP APM module access policy profile must be configured to automatically terminate user sessions for users connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.<VulnDiscussion>Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.
+
+Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.
+
+This capability is typically reserved for specific system functionality where the system owner, data owner, or organization requires additional trigger events based on specific mission needs. Conditions or trigger events requiring automatic session termination can include, for example, targeted responses to certain types of incidents and time-of-day restrictions on information system use.
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018SV-74469V-60039CCI-002361If user access control intermediary services are provided, configure an access policy in the BIG-IP APM module to automatically terminate a user session when organization-defined conditions or trigger events occur that require a session disconnect.If the BIG-IP Am module does not provide user access control intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for organizational access.
+
+Verify the Access Profile is configured to automatically terminate user sessions when organization-defined conditions or trigger events occur that require a session disconnect.
+
+If the BIG-IP APM module is not configured to automatically terminate a user session when organization-defined conditions or trigger events occur that require a session disconnect, this is a finding.SRG-NET-000519-ALG-000008<GroupDescription></GroupDescription>F5BI-AP-000151The BIG-IP APM module access policy profile must be configured to display an explicit logoff message to users, indicating the reliable termination of authenticated communications sessions when disconnecting from virtual servers.<VulnDiscussion>If a user cannot explicitly end a session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated.
+
+Logoff messages for access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions, including, for example, remote logon, information systems typically send logoff messages as final messages prior to terminating sessions.
+
+This policy only applies to ALGs (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018V-60041SV-74471CCI-002364CCI-000366If user access control intermediary services are provided, configure the BIG-IP APM module to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.If the BIG-IP APM module does not provide user access control intermediary services, this is not applicable.
+
+Verify the BIG-IP APM module is configured as follows:
+
+Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles.
+
+Click "Edit..." in the "Access Policy" column for an Access Profile used for connecting to virtual servers.
+
+Verify the Access Profile is configured to display an explicit logoff message to users, indicating the reliable termination of authenticated communications sessions.
+
+If the BIG-IP APM module is not configured to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions, this is a finding.SRG-NET-000337-ALG-000096<GroupDescription></GroupDescription>F5BI-AP-000230The F5 BIG-IP appliance must be configured to set a "Maximum Session Timeout" value of 8 hours or less.<VulnDiscussion>The Maximum Session Timeout setting configures a limit on the maximum amount of time a user's session is active without needing to reauthenticate. If the value is set to 0 (zero), the user's session is active until either the user terminates the session or the Inactivity Timeout value is reached (the default value is set to 604,800 seconds). When determining how long the maximum user session can last, it may be useful to review the access policy. For example, if the access policy requires that the user's antivirus signatures cannot be older than 8 hours, the Maximum Session Timeout should not exceed that time limit.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-002038From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. In the "Settings" section, set the value for "Maximum Session Timeout" to 28800 seconds (8 hours) or less.
+Note: If the setting is grayed out, check the box to the right of the setting and then update it.
+6. Click "Update".
+7. Click "Apply Access Policy".If the BIG-IP APM module does not provide user authentication intermediary services, this is not applicable.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. In the "Settings" section, verify the value for "Maximum Session Timeout" is set to 28800 seconds (8 hours) or less.
+
+If the F5 BIG-IP APM access policy is not configured for a "Maximum Session Timeout" value of 28,800 seconds (8 hours) or less, this is a finding.SRG-NET-000345-ALG-000099<GroupDescription></GroupDescription>F5BI-AP-000231The F5 BIG-IP appliance must be configured to deny access when revocation data is unavailable using OCSP.<VulnDiscussion>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).
+
+Caching of CRL files on BIG-IP is not feasible or possible due to the large sizes of DOD/DISA CRL files. Use the alternate mitigation, configuring the system to deny access when revocation data is unavailable, which is done in the APM VPE.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001991Update the OCSP Auth.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Add an "OCSP Auth" in the Access Profile.
+Note: To create an OCSP Responder, go to Access >> Authentication >> OCSP Responder.
+6. Ensure the fallback branch goes to a "Deny" ending.
+7. Click "Apply Access Policy".If the BIG-IP appliance does not provide PKI-based user authentication intermediary services, this is not applicable.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Verify an "OSCP Auth" object is configured in the Access Profile VPE AND that the fallback branch of this object leads to a "Deny" ending.
+
+If the BIG-IP appliance is not configured to deny access when revocation data is unavailable, this is a finding.SRG-NET-000164-ALG-000100<GroupDescription></GroupDescription>F5BI-AP-000232The F5 BIG-IP appliance must configure OCSP to ensure revoked user credentials are prohibited from establishing an allowed session.<VulnDiscussion>A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.
+
+Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-000185Add OCSP Auth to Access Policy.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Add an "OCSP Auth" with certificate type of "User" and/or a "CRLDP Auth" object in the Access Profile.
+Note: To create an OCSP Responder, go to Access >> Authentication >> OCSP Responder.
+Note: To create a CRLDP Server object, go to Access >> Authentication >> CRLDP. Add an "OCSP Auth" object in the Access Profile and select an OCSP Responder.
+6. Click "Update".If the BIG-IP appliance does not provide intermediary services for TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS), this is not applicable.
+
+Access Policy:
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Verify an "OCSP Auth" object is configured in the Access Profile for "User" type or a CRLDP object is configured.
+
+If the BIG-IP appliance is not configured to use OCSP or CRLDP to ensure revoked user credentials are prohibited from establishing an allowed session, this is a finding.SRG-NET-000164-ALG-000100<GroupDescription></GroupDescription>F5BI-AP-000233The F5 BIG-IP appliance must configure OCSP to ensure revoked machine credentials are prohibited from establishing an allowed session.<VulnDiscussion>A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.
+
+Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-000185If the Access Profile is configured to pull a machine cert using the "Machine Cert Auth" object in the policy, perform the following actions. Note that pulling a Machine Cert requires the use of the APM Edge Client installed on the client.
+
+To add OCSP machine certificate verification to an access policy:
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Click the "+" icon on the Successful branch of the Machine Cert Auth object.
+6. "Authentication" tab.
+7. Select OCSP Auth.
+8. Click "Add Item".
+9. From the OCSP Responder list, select an OCSP responder.
+Note: To create an OCSP Responder. go to Access >> Authentication >> OCSP Responder.
+10. From the Certificate Type list, select "Machine".
+11. Click "Save".
+12. Click "Apply Access Policy".
+
+To add CRLDP certificate verification to an access policy:
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Click the "+" icon on the Successful branch of the Machine Cert Auth object.
+6. "Authentication" tab.
+7. Select CRLDP Auth.
+8. Click "Add Item".
+9. Select an item from the CRLDP Server list.
+Note: To create a CRLDP Server, go to Access >> Authentication >> CRLDP.
+10. Click "Save".
+11. Click "Apply Access Policy".If the BIG-IP appliance does not provide intermediary services for TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS), this is not applicable.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Verify an "OCSP Auth" object is configured in the Access Profile for "Machine" type or a CRLDP object is configured.
+
+If the BIG-IP appliance is not configured to use OCSP or CRLDP to ensure revoked machine credentials are prohibited from establishing an allowed session, this is a finding.SRG-NET-000230-ALG-000113<GroupDescription></GroupDescription>F5BI-AP-000234The F5 BIG-IP appliance must not use the On-Demand Cert Auth VPE agent as part of the APM Policy Profiles.<VulnDiscussion>By requiring mutual authentication before any communication, it becomes significantly challenging for attackers to impersonate a client or server and exploit vulnerabilities. Furthermore, the encryption of all data transmitted between the client and server ensures that even if an attacker intercepts the data, it remains unintelligible without the correct keys.
+
+To ensure the use of the mutual TLS (mTLS) for session authentication, the On-Demand Cert Auth VPE agent should not be used. Typically, when a client makes an HTTPS request, an SSL handshake request occurs at the start of an SSL session. However, if On-Demand is configured, the client SSL profile skips the initial SSL handshake, and On-Demand Cert Auth action can renegotiate the SSL connection from an access policy by sending a certificate request to the user. This prompts a certificate screen to open. Setting ODCA to "require" the client cert means the client cannot get any further in the APM VPE without providing a valid certificate. "Request" would ask the client for a certificate, but the client could still continue if they did not provide one. Thus, the Client Certificate should be set to "require" in the client SSL profile (F5BI-LT-000213) since removing ODCA from the VPE alone will result in the client never being prompted for a certificate.
+
+Within the Virtual Policy Editor (VPE) of the relevant Access Profile, do not use the On-Demand Cert Auth VPE agent. Configure only the Client Certification Inspection VPE Agent. This adjustment directs the BIG-IP to scrutinize the Client Certificate during the mTLS handshake process and extract the Certificate's details into APM session variables.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001184Remove On-Demand Cert.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Remove any "On-Demand Cert Auth" agents in the profile.
+6. Add a "Client Cert Inspection" object in place of the previous "On Demand Cert Auth" agent.
+7. Click "Apply Access Policy".Verify removal of the On-Demand Cert Auth VPE agent.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Verify the On-Demand Cert Auth agent is not configured in any part of the profile.
+
+If the On-Demand Cert Auth agent is used in any Access Policy Profile, this is a finding.SRG-NET-000355-ALG-000117<GroupDescription></GroupDescription>F5BI-AP-000235The F5 BIG-IP appliance APM Access Policies that grant access to web application resources must allow only client certificates that have the User Persona Name (UPN) value in the User Persona Client Certificates.<VulnDiscussion>To enhance the security, it is advisable to append additional checks and APM Deny/Fallback branches to APM Access Profiles in scenarios where a UPN cannot be extracted. To guarantee the exclusive use of User Persona DISA Certificates for accessing Web Applications, it is recommended to carry out additional APM Access Policy checks against the Client Certificate. DISA incorporates a User Principal Name (UPN) in their User Persona Client Certificates. However, this key/value pair is not present in the DISA server certificates.
+
+Based on DOD session authentication policy, the LTM+APM configuration will include Client Certificate Authentication, OCSP Revocation Check, a Variable Assignment to extract the UserPrincipalName, followed by an LDAP query. This query verifies the existence of a corresponding Active Directory User object for the provided UserPrincipalName. Subsequently, the identified sAMAccountName is set as an APM Session variable for use by the SSO Profile. Once an APM LTM+APM session is granted, the User-Agent is permitted to transmit data to the Server-Side of the proxy, which will invoke the SSO Profile if applicable.
+
+To ensure that only DISA Client Certificates from CACs can access the Web Application, an additional branch was added to the Variable Assignment. The scripts were adjusted to verify the existence of the UserPrincipalName. If it does not exist, the value of the UserPrincipalName APM session variable is set to "UPN Collection Error", which would be directed to an APM Policy Deny.
+
+NPE Certificates issued by DISA incorporate both the TLS WWW Client Authentication (OID.1.3.6.1.5.5.7.3.2) and TLS WWW Server Authentication
+(OID.1.3.6.1.5.5.7.3.1) key usage policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-002470Note: If NPE certificates are not in use, implementation is REQUIRED.
+
+Note: If NPE certificates are in use, implementation is OPTIONAL. Sites should test this configuration to prevent operational impacts since this process may potentially flag server and NPE certificates, resulting in denied sessions.
+
+Configure each APM Access Policy to verify use of user persona DISA client certificates for accessing web applications.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" on each profile listed to enter the VPE.
+5. Click on the object where the Certificate UPN is extracted and assigned to a variable.
+6. Append a known variable to the end of the variable assignment expression that will trigger if the UPN cannot be extracted from the client certificate, such as:
+
+else {
+ return "UPN Collection Error"
+}
+
+7. Click "Finished".
+8. In the same Variable Assign object, click the "Branch Rules" tab.
+9. On the branch that continues the policy evaluation (Does not lead to Deny ending) click the "change" link next to "Expression".
+10. "Advanced" tab.
+11. Enter an expression that verifies the UPN was extracted successfully, such as:
+
+expr {[mcget {session.logon.last.upn}] !="UPN Collection Error"}
+Note - the above assumes the UPN variable name is "session.logon.last.upn". Adjust this if another variable name is used to store the client UPN.
+
+12. Click "Finished".
+13. Click "Save".
+14. Click "Apply Access Policy".If the BIG-IP appliance does not provide user authentication intermediary services, this is not applicable.
+
+If the site has documented that this setting has been tested operationally and is operationally harmful because of false positives, this is not a finding.
+
+1. Review the applicable Access Control Profiles that give access to web application resources.
+2. Verify that a Branch Rule exists to check for the UPN on the session certificate.
+3. Verify there is a check for failed extractions that results in an APM Policy Deny.
+
+If any BIG-IP appliance APM Access Policies do not deny sessions using client certificates that do not have the DISA UPN, this is a finding.SRG-NET-000230-ALG-000113<GroupDescription></GroupDescription>F5BI-AP-000236The F5 BIG-IP appliance must be configured to limit authenticated client sessions to initial session source IP.<VulnDiscussion>The "Restrict to Single Client IP" is a safeguard against session hijacking or cookie theft. Even if an attacker manages to steal a session cookie, the cookie cannot be used from a different source IP address that the address used to initiate the session. This security measure is set within the APM Access Pro?les.
+
+Sites should test this setting within their network prior to implementing. Users behind a shared proxy address may be denied access. Optionally, the F5 BIG-IP APM can be installed and used to produce access reports to find recurring IP sources within the user community.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001184Note: Implementation is OPTIONAL. Setting should be tested to ensure that a denial of service (DoS) does not result.
+
+From the BIG-IP GUI:
+1. System.
+2. Access.
+3. Profiles/Policies.
+4. Access Profiles.
+5. Click the Access profile name.
+6. Under "Settings", check "Restrict to Single Client IP".
+Note: If the box is grayed out, check the box all the way to the right of the setting first and then check the box.
+7. Click "Update".
+8. Click "Apply Access Policy".If the site has documented that this setting has been tested operationally and is operationally harmful because of false positives, this is not a finding.
+
+From the BIG-IP GUI:
+1. System.
+2. Access.
+3. Profiles/Policies.
+4. Access Profiles.
+5. Click the Access profile name.
+6. Under "Settings", verify "Restrict to Single Client IP" is checked.
+
+If the BIG-IP appliance is not configured to limit authenticated client sessions to initial session source IP, this is a finding.SRG-NET-000053-ALG-000001<GroupDescription></GroupDescription>F5BI-AP-000239The F5 BIG-IP appliance must be configured to set the "Max In Progress Sessions per Client IP" value to 10 or less.<VulnDiscussion>The "Max In Progress Sessions Per Client IP" setting in an APM Access Pro?le is a security con?guration that limits the number of simultaneous sessions that can be initiated from a single IP address. This is particularly helpful in preventing a session ?ood, where a hacker might attempt to overwhelm the system by initiating many sessions from a single source. By capping the number of sessions per IP, this setting can help maintain the system's stability and integrity while also providing a layer of protection against such potential attacks.
+
+False positives may result from this setting in networks where users are behind a shared proxy. Sites should conduct operational testing to determine if there are adverse operational impacts. Log reports should be obtained to identify recurring IP sources within the user community.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-000054Note: Implementation is OPTIONAL. This setting may break some known proxies. Testing should be performed in advance to prevent operational impact.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. In the "Settings" section, set "Max In Progress Sessions per Client IP" to 10 or less.
+Note: If the setting is grayed out, check the box to the right of the setting and then update it.
+6. Click "Update".
+7. Click "Apply Access Policy".If the site has documented that this setting has been tested operationally and is operationally harmful because of false positives, this is not a finding.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. In the "Settings" section, verify "Max In Progress Sessions per Client IP" is set to 10 or less.
+
+If the F5 BIG-IP APM access policy is not configured to set a "Max In Progress Sessions per Client IP" value to 10 or less, this is a finding.SRG-NET-000015-ALG-000016<GroupDescription></GroupDescription>F5BI-AP-000240The F5 BIG-IP appliance must enforce approved authorizations for logical access to resources by explicitly configuring assigned resources with an authorization list.<VulnDiscussion>Authentication alone must not be sufficient to assign APM resources to a connecting client. Access to APM resources (e.g., Portal, VPN, Webtop, Remote Desktop, etc.,) must be granted only after a successful authorization check occurs. Resource assignments can be configured using APM Access Policy Advanced Resource Assign VPE agents and Resource Assign VPE agents. These agents must be configured explicitly with an authorization list. If resources are assigned to these types of agents with empty expressions, that expression acts as the default authorization list.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-000213For each APM Access Policy, ensure that for each resource, all Advanced Resource Assign agents used in the configuration are explicitly configured to use an authorization list.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Click on any items that use the Advanced Resource Assign VPE object.
+6. For each entry with an Expression that is "Empty", click "change".
+7. Add an appropriate expression that validates the user's authorization to access the resource specified in the item.
+8. Click "Finished".
+9. Click "Save".
+10. Click "Apply Access Policy".If Advanced Resource Assign VPE agent is not used in any policy, this is not a finding.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click "Edit" under "Per-Session Policy" for the Access Profile.
+5. Review each Resource.
+ - If the Advanced Resource Assign agent is used, verify that each Expression listed is explicitly configured to use an authorization list.
+
+If the F5 BIG-IP appliance Access Policy has any assigned resources that are not configured with a specific authorization list, this is a finding.SRG-NET-000233-ALG-000115<GroupDescription></GroupDescription>F5BI-AP-000241When the Access Profile Type is LTM+APM and it is not using any connectivity resources (such as Network Access, Portal Access, etc.) in the VPE, the F5 BIG-IP appliance must be configured to enable the HTTP Only flag.<VulnDiscussion>To guard against cookie hijacking, only the BIG-IP APM controller and client must be able to view the full session ID. Setting the APM HTTP Only flag ensures that a third party will not have access to the active session cookies.
+
+This option is only applicable to the LTM+APM access profile type. Other access profile types require access to various session cookies to fully function. Sites must conduct operational testing prior to enabling this setting. For implementations with connectivity resources (such as Network Access, Portal Access, etc.), do not set BIG-IP APM cookies with the HTTP Only flag.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001664When the Access Profile Type is LTM+APM and it is not using any connectivity resources (such as Network Access, Portal Access, etc.) in the VPE, set the HTTP Only flag.
+
+From the BIG-IP GUI:
+1. Access >> Profiles/Policies >> Access profile name >> SSO/Auth Domains.
+2. Under "Cookie Options", check the box next to "HTTP Only".If the Access Profile Type is not LTM+APM and it uses connectivity resources (such as Network Access, Portal Access, etc.) in the VPE, this is not a finding.
+
+From the BIG-IP GUI:
+1. Access >> Profiles/Policies >> Access profile name >> SSO/Auth Domains.
+2. Under "Cookie Options", verify "HTTP Only" is enabled.
+
+If the F5 BIG-IP appliance does not enable the HTTP Only flag, this is a finding.SRG-NET-000233-ALG-000115<GroupDescription></GroupDescription>F5BI-AP-000242The F5 BIG-IP appliance must be configured to enable the "Secure" cookie flag.<VulnDiscussion>To guard against cookie hijacking, only the BIG-IP APM controller and client must be able to view the full session ID. Session cookies are set only after the SSL handshake between the BIG-IP APM system and the user has completed, ensuring that the session cookies are protected from interception with SSL encryption.
+
+To ensure that the client browser will not send session cookies unencrypted, the HTTP header that the BIG-IP APM uses when sending the session cookie is set with the secure option (default). This option is only applicable to the LTM+APM access profile type.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001664Configure each Access Profile to enable the "Secure" cookie flag.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. "SSO/Auth Domains" tab.
+6. Under "Cookie Options", check "Secure".
+7. Click "Update".
+8. Click "Apply Access Policy".From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. "SSO/Auth Domains" tab.
+6. Under "Cookie Options", verify "Secure" is enabled.
+
+If the F5 BIG-IP appliance APM Policy does not enable the "Secure" cookie flag, this is a finding.SRG-NET-000233-ALG-000115<GroupDescription></GroupDescription>F5BI-AP-000243The F5 BIG-IP appliance must be configured to disable the "Persistent" cookie flag.<VulnDiscussion>For BIG-IP APM deployments with connectivity resources (such as Network Access, Portal Access, etc.), BIG-IP APM cookies cannot be set as "Persistent". This is by design since cookies are stored locally on the client's hard disk and thus could be exposed to unauthorized external access. For some deployments of the BIG-IP APM system, cookie persistence may be required. When cookie persistence is selected, persistence is hard coded at 60 seconds.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Access Policy ManagerDISADPMS TargetF5 BIG-IP Access Policy Manager4018CCI-001664Note: Testing must be performed prior to implementation to prevent operational impact. This setting may break access to certain applications that require cookie persistence.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. "SSO/Auth Domains" tab.
+6. Under "Cookie Options", uncheck "Persistent".
+7. Click "Update."
+8. Click "Apply Access Policy".If the Access Profile is used for applications that require cookie persistence, this is not a finding.
+
+From the BIG-IP GUI:
+1. Access.
+2. Profiles/Policies.
+3. Access Profiles.
+4. Click the Access profile name.
+5. "SSO/Auth Domains" tab.
+6. Under "Cookie Options", verify "Persistent" is disabled.
+
+If the F5 BIG-IP appliance APM Policy has the "Persistent" cookie flag enabled, this is a finding.
\ No newline at end of file
diff --git a/benchmarks/DISA/U_F5_BIG-IP_Advanced_Firewall_Manager_STIG_V2R1_Manual-xccdf.xml b/benchmarks/DISA/U_F5_BIG-IP_Advanced_Firewall_Manager_STIG_V2R1_Manual-xccdf.xml
new file mode 100644
index 000000000..e1570d967
--- /dev/null
+++ b/benchmarks/DISA/U_F5_BIG-IP_Advanced_Firewall_Manager_STIG_V2R1_Manual-xccdf.xml
@@ -0,0 +1,81 @@
+acceptedF5 BIG-IP Advanced Firewall Manager Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 29 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-NET-000018-ALG-000017<GroupDescription></GroupDescription>F5BI-AF-000005The BIG-IP AFM module must be configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.<VulnDiscussion>Information flow control regulates where information is allowed to travel within a network. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network infrastructure or data.
+
+Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems. Examples of information flow control restrictions include keeping export-controlled information from being transmitted in the clear to the Internet or blocking information marked as classified but being transported to an unapproved destination.
+
+Application Layer Gateways (ALGs) enforce approved authorizations by employing security policy and/or rules that restrict information system services, provide packet filtering capability based on header or protocol information and/or message filtering capability based on data content (e.g., implementing key word searches or using document characteristics).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Advanced Firewall ManagerDISADPMS TargetF5 BIG-IP Advanced Firewall Manager4002SV-74347V-59917CCI-001368If the BIG-IP AFM module is used to support user access control intermediary services for virtual servers, configure the BIG-IP AFM module to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.If the BIG-IP AFM module is not used to support user access control intermediary services for virtual servers, this is not applicable.
+
+Verify the BIG-IP AFM module is configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+Navigate to the BIG-IP System manager >> Security >> Network Firewall >> Active Rules.
+
+Verify an active rule is configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+If the BIG-IP AFM module is not configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic, this is a finding.SRG-NET-000019-ALG-000018<GroupDescription></GroupDescription>F5BI-AF-000007The BIG-IP AFM module must be configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.<VulnDiscussion>Information flow control regulates where information is allowed to travel within a network and between interconnected networks. Blocking or restricting detected harmful or suspicious communications between interconnected networks enforces approved authorizations for controlling the flow of traffic.
+
+This requirement applies to the flow of information between the Application Layer Gateway (ALG) when used as a gateway or boundary device which allows traffic flow between interconnected networks of differing security policies.
+
+The ALG installed and configured in such a way that restricts or blocks information flows based on guidance in the Ports, Protocols, & Services (PPSM) regarding restrictions for boundary crossing for ports, protocols, and services. Information flow restrictions may be implemented based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+The ALGs must be configured with policy filters (e.g., security policy, rules, and/or signatures) that restrict or block information system services; provide a packet filtering capability based on header information; and/or perform message filtering based on message content. The policy filters used depend upon the type of application gateway (e.g., web, email, or TLS).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Advanced Firewall ManagerDISADPMS TargetF5 BIG-IP Advanced Firewall Manager4002V-59921SV-74351CCI-001414If the BIG-IP AFM module is used to support user access control intermediary services for virtual servers, configure the BIG-IP AFM module to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.If the BIG-IP AFM module is not used to support user access control intermediary services for virtual servers, this is not applicable.
+
+Verify the BIG-IP AFM module is configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+Navigate to the BIG-IP System manager >> Security >> Network Firewall >> Active Rules.
+
+Verify an active rule is configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+If the BIG-IP AFM module is not configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic, this is a finding.SRG-NET-000074-ALG-000043<GroupDescription></GroupDescription>F5BI-AF-000039The BIG-IP AFM module must be configured to produce audit records containing information to establish what type of events occurred.<VulnDiscussion>Without establishing what type of event 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, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the gateway logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element.
+
+This requirement does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Advanced Firewall ManagerDISADPMS TargetF5 BIG-IP Advanced Firewall Manager4002V-59923SV-74353CCI-000130Configure the BIG-IP AFM module to produce audit records containing information to establish what type of events occurred.
+
+Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
+
+Click on 'Create'.
+
+Name the Profile.
+
+Check the box next to 'Network Firewall'.
+
+Configure settings to log required information.
+
+Click 'Finished'.Verify the BIG-IP AFM module is configured to produce audit records containing information to establish what type of events occurred.
+
+Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
+
+Verify list of Profiles 'Enabled' for 'Network Firewall'.
+
+If the BIG-IP AFM module does not produce audit records containing information to establish what type of events occurred, this is a finding.SRG-NET-000364-ALG-000122<GroupDescription></GroupDescription>F5BI-AF-000223The BIG-IP AFM module must be configured to only allow incoming communications from authorized sources routed to authorized destinations.<VulnDiscussion>Unrestricted traffic may contain malicious traffic that poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth and other resources.
+
+Access control policies and access control lists implemented on devices that control the flow of network traffic (e.g., application-level firewalls and Web content filters) ensure the flow of traffic is only allowed from authorized sources to authorized destinations. Networks with different levels of trust (e.g., the Internet or CDS) must be kept separate.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Advanced Firewall ManagerDISADPMS TargetF5 BIG-IP Advanced Firewall Manager4002V-59925SV-74355CCI-002403Configure the BIG-IP AFM module to only allow incoming communications from authorized sources routed to authorized destinations.If the BIG-IP AFM module is not used to support user access control intermediary services for virtual servers, this is not applicable.
+
+Verify the BIG-IP AFM module is configured to only allow incoming communications from authorized sources routed to authorized destinations.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select the applicable Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Network Firewall" is assigned a local Network Firewall Policy.
+
+Verify configuration of the identified Network Firewall policy:
+
+Navigate to the BIG-IP System manager >> Security >> Network Firewall >> Active Rules.
+
+Select the Network Firewall policy that was assigned to the Virtual Server.
+
+Review the configuration of the "Protocol", "Source", "Destination", and "Action" sections at a minimum to ensure that the policy is only allowing incoming communications from authorized sources enroute to authorized destinations.
+
+If the BIG-IP AFM module is not configured to only allow incoming communications from unauthorized sources routed to unauthorized destinations, this is a finding.SRG-NET-000380-ALG-000128<GroupDescription></GroupDescription>F5BI-AF-000229The BIG-IP AFM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.<VulnDiscussion>A common vulnerability of network elements is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
+
+The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher layer proxy functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Advanced Firewall ManagerDISADPMS TargetF5 BIG-IP Advanced Firewall Manager4002V-59927SV-74357CCI-002754Configure the BIG-IP AFM module to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.Verify the BIG-IP AFM module is configured to handle invalid input in a predictable and documented manner that reflects organizational and system objectives.
+
+This can be demonstrated by the SA sending an invalid input to a virtual server. Provide evidence that the virtual server was able to handle the invalid input and maintain operation.
+
+If the BIG-IP AFM module is not configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives, this is a finding.
\ No newline at end of file
diff --git a/benchmarks/DISA/U_F5_BIG-IP_Application_Security_Manager_STIG_V2R1_Manual-xccdf.xml b/benchmarks/DISA/U_F5_BIG-IP_Application_Security_Manager_STIG_V2R1_Manual-xccdf.xml
new file mode 100644
index 000000000..a115420b9
--- /dev/null
+++ b/benchmarks/DISA/U_F5_BIG-IP_Application_Security_Manager_STIG_V2R1_Manual-xccdf.xml
@@ -0,0 +1,377 @@
+acceptedF5 BIG-IP Application Security Manager Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 29 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-NET-000061-ALG-000009<GroupDescription></GroupDescription>F5BI-AS-000031The BIG-IP ASM module supporting intermediary services for remote access communications traffic must ensure inbound traffic is monitored for compliance with remote access security policies.<VulnDiscussion>Automated monitoring of remote access traffic allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by inspecting connection activities of remote access capabilities.
+
+Remote access methods include both unencrypted and encrypted traffic (e.g., web portals, web content filter, TLS, and webmail). With inbound TLS inspection, the traffic must be inspected prior to being allowed on the enclave's web servers hosting TLS or HTTPS applications.
+
+Remote access security policies provide the guidance and define the traffic that will be monitored. These policies consist of local policies, organizational policies, and DoD policies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74497V-60067CCI-000067If intermediary services for remote access communications traffic for virtual servers is supported by the BIG-IP ASM module, configure an ASM security policy to monitor inbound traffic for compliance with remote access security policies, to be applied to the applicable virtual servers in the BIG-IP LTM module.If the BIG-IP ASM module does not support intermediary services for remote access traffic (e.g., web content filter, TLS, and webmail) for virtual servers, this is not applicable.
+
+When the BIG-IP ASM module is used to support intermediary services for remote access communications traffic to virtual servers, verify the security policy is configured as follows:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select the applicable Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify an ASM policy is assigned and Enabled for "Application Security Policy".
+
+Verify configuration of the identified ASM policy:
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Review the list under "Active Security Policies" for a security policy that monitors inbound traffic for compliance with remote access security policies.
+
+Verify "Enforcement Mode" is set to "Transparent" or "Blocking" in accordance with the requirements for the applicable virtual server.
+
+If the BIG-IP ASM module is not configured with a policy to monitor inbound traffic for compliance with remote access security policies and applied to the applicable virtual servers, this is a finding.SRG-NET-000074-ALG-000043<GroupDescription></GroupDescription>F5BI-AS-000039The BIG-IP ASM module must be configured to produce ASM Event Logs containing information to establish what type of unauthorized events occurred.<VulnDiscussion>Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Event log content that may be necessary to satisfy this requirement includes, for example, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the event logs provide a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element.
+
+This requirement does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003V-60069SV-74499CCI-000130Configure the BIG-IP ASM module to produce ASM Event Logs containing information to establish what type of unauthorized events occurred.
+
+Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
+
+Click on 'Create'.
+
+Name the Profile.
+
+Check the box next to 'Application Security'.
+
+Set "Request Type" to "Illegal requests, and requests that include staged attack signatures" under "Storage Filter".
+
+Click 'Finished'.
+
+Apply Logging Profile to applicable Virtual Server(s).
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to assign the ASM Event Logging Profile.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Under "Log Profile" set to Enabled and move new Logging Profile from "Available" to "Selected".
+
+Click "Update".Verify the BIG-IP ASM module is configured to produce ASM Event Logs containing information to establish what type of unauthorized events occurred.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration for ASM Event Logging.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Verify that "Log Profile" is Enabled and a logging profile is assigned under "Selected".
+
+Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
+
+Select the Logging Profile that was assigned to the virtual server.
+
+Verify "Request Type" is set to "Illegal requests, and requests that include staged attack signatures" is selected under "Storage Filter".
+
+If the BIG-IP ASM module does not produce ASM Event Logs containing information to establish what type of unauthorized events occurred, this is a finding.SRG-NET-000246-ALG-000132<GroupDescription></GroupDescription>F5BI-AS-000109The BIG-IP ASM module must be configured to update malicious code protection mechanisms and signature definitions when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policy and procedures.<VulnDiscussion>Malicious code protection mechanisms include, but are not limited to, anti-virus and malware detection software. In order to minimize any potential negative impact to the organization caused by malicious code, malicious code must be identified and eradicated. Malicious code includes viruses, worms, Trojan horses, and Spyware.
+
+This requirement is limited to ALGs, web content filters, and packet inspection firewalls that perform malicious code detection as part of their functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74501V-60071CCI-001240If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP ASM module to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures.
+
+Verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policies and procedures.
+
+Navigate to the BIG-IP System manager >> Security >> Options >> Application Security >> Attack Signatures >> Attack Signature Updates.
+
+Review the following settings to confirm compliance with organizational configuration management policies and procedures:
+
+Update Mode is set to "Manual", unless defined differently by the Organization.
+
+Delivery Mode is set to "Automatic", unless defined differently by the Organization.
+
+Verify that "Auto Apply New Signatures Configurations After Update" is NOT "Enabled", unless defined differently by the Organization.
+
+If the BIG-IP ASM module does not update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures, this is a finding.SRG-NET-000251-ALG-000131<GroupDescription></GroupDescription>F5BI-AS-000119The BIG-IP ASM module must be configured to automatically update malicious code protection mechanisms when providing content filtering to virtual servers.<VulnDiscussion>The malicious software detection functionality on network elements needs to be constantly updated in order to identify new threats as they are discovered.
+
+All malicious software detection functions must come with an update mechanism that automatically updates the application and any associated signature definitions. The organization (including any contractor to the organization) is required to promptly install security-relevant malicious code protection updates. Examples of relevant updates include anti-virus signatures, detection heuristic rule sets, and/or file reputation data employed to identify and/or block malicious software from executing.
+
+Malicious code includes viruses, worms, Trojan horses, and Spyware.
+
+This requirement is limited to ALGs, web content filters, and packet inspection firewalls that perform malicious code detection as part of their functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74503V-60073CCI-001247If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP ASM module to update malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policies and procedures.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures.
+
+Verify the BIG-IP ASM module is configured to update malicious code protection mechanisms when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policies and procedures.
+
+Navigate to the BIG-IP System manager >> Security >> Options >> Application Security >> Attack Signatures >> Attack Signature Updates.
+
+Review the following settings to confirm compliance with organizational configuration management policies and procedures:
+
+Update Mode is set to "Manual", unless defined differently by the Organization.
+
+Delivery Mode is set to "Automatic", unless defined differently by the Organization.
+
+Verify that "Auto Apply New Signatures Configurations After Update" is NOT "Enabled", unless defined differently by the Organization.
+
+If the BIG-IP ASM module does not update malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policies and procedures, this is a finding.SRG-NET-000318-ALG-000014<GroupDescription></GroupDescription>F5BI-AS-000157To protect against data mining, the BIG-IP ASM module must be configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections.
+
+Compliance requires the Application Layer Gateway (ALG) to have the capability to prevent code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74505V-60075CCI-002346If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module prevents code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to prevent code injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select the Security Policy that has been assigned to the Virtual Server(s).
+
+Verify the "Enforcement Mode" is Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assigned Signature Sets" listed above have the "Block" button checked.
+
+If the BIG-IP ASM module is not configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.SRG-NET-000318-ALG-000151<GroupDescription></GroupDescription>F5BI-AS-000159To protect against data mining, the BIG-IP ASM module must be configured to prevent code injection attacks launched against application objects, including, at a minimum, application URLs and application code when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections.
+
+Compliance requires the ALG to have the capability to prevent code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74507V-60077CCI-002346If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to prevent code injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select the Security Policy that has been assigned to the Virtual Server(s).
+
+Verify the "Enforcement Mode" is Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assigned Signature Sets" listed above have the "Block" button checked.
+
+If the BIG-IP ASM module is not configured to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code, this is a finding.SRG-NET-000318-ALG-000152<GroupDescription></GroupDescription>F5BI-AS-000161To protect against data mining, The BIG-IP ASM module must be configured to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server.
+
+Compliance requires the ALG to have the capability to prevent SQL code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003V-60079SV-74509CCI-002346If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to prevent SQL injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select the Security Policy that has been assigned the Virtual Server(s).
+
+Verify the "Enforcement Mode" is Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Verify "Signature Staging" is Enabled.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assigned Signature Sets" listed above have the "Block" button checked.
+
+If the BIG-IP ASM module is not configured to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.SRG-NET-000319-ALG-000015<GroupDescription></GroupDescription>F5BI-AS-000163To protect against data mining, The BIG-IP ASM module must be configured to detect code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational databases may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections.
+
+ALGs with anomaly detection must be configured to protect against unauthorized code injections. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003V-60081SV-74511CCI-002347If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to prevent code injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select the Security Policy that has been assigned to the Virtual Server(s).
+
+Verify the "Enforcement Mode" is Transparent or Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assignment Signature Sets" listed above have the "Alarm" button checked.
+
+If the BIG-IP ASM module is not configured to detect code injection attacks launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.SRG-NET-000319-ALG-000020<GroupDescription></GroupDescription>F5BI-AS-000165To protect against data mining, The BIG-IP ASM module must be configured to detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational databases may result in the compromise of information.
+
+SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server.
+
+ALGs with anomaly detection must be configured to protect against unauthorized data mining attacks. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74513V-60083CCI-002347If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module detects SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to detect SQL injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select a Security Policy that has been assigned to Virtual Server(s).
+
+Verify the "Enforcement Mode" is Transparent or Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assignment Signature Sets" listed above have the "Alarm" button checked.
+
+If the BIG-IP ASM module is not configured to detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.SRG-NET-000319-ALG-000153<GroupDescription></GroupDescription>F5BI-AS-000167The BIG-IP ASM module must be configured to detect code injection attacks launched against application objects including, at a minimum, application URLs and application code, when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational applications may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database, or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections.
+
+ALGs with anomaly detection must be configured to protect against unauthorized code injections. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74515V-60085CCI-002347If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to detect code injection attacks.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
+
+Select the Security Policy that has been assigned to the Virtual Server(s).
+
+Verify "Enforcement Mode" is Transparent or Blocking.
+
+Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
+
+Review the list under "Assigned Signature Sets" for the following signatures:
+
+Generic Detection Signatures
+
+Custom Systems Signature Set (based on systems identified in the application make-up).
+
+Verify the "Assignment Signature Sets" listed above have the "Alarm" button checked.
+
+If the BIG-IP ASM module is not configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code, this is a finding.SRG-NET-000380-ALG-000128<GroupDescription></GroupDescription>F5BI-AS-000229The BIG-IP ASM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.<VulnDiscussion>A common vulnerability of network elements is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
+
+The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notifying the appropriate personnel, creating an audit record, and rejecting invalid input.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher layer proxy functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003V-60087SV-74517CCI-002754Configure the BIG-IP ASM module to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.Verify the BIG-IP ASM module is configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.
+
+This can be demonstrated by the SA sending an invalid input to a virtual server. Provide evidence that the virtual server was able to handle the invalid input and maintain operation.
+
+If the BIG-IP ASM module is not configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives, this is a finding.SRG-NET-000390-ALG-000139<GroupDescription></GroupDescription>F5BI-AS-000239The BIG-IP ASM module must continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.<VulnDiscussion>If inbound communications traffic is not continuously monitored, hostile activity may not be detected and prevented. Output from application and traffic monitoring serves as input to continuous monitoring and incident response programs.
+
+Internal monitoring includes the observation of events occurring on the network crossing internal boundaries at managed interfaces such as web content filters. Depending on the type of ALG, organizations can monitor information systems by monitoring audit activities, application access patterns, characteristics of access, content filtering, or unauthorized exporting of information across boundaries. Unusual/unauthorized activities or conditions may include large file transfers, long-time persistent connections, unusual protocols and ports in use, and attempted communications with suspected malicious external addresses.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003V-60089SV-74519CCI-002661Configure a policy in the BIG-IP ASM module to continuously monitor inbound communications traffic for unusual or unauthorized activities or conditions.
+
+Apply the ASM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to continuously monitor inbound communications traffic for unusual or unauthorized activities or conditions.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to continuously monitor inbound communications traffic for unusual or unauthorized activities or conditions.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify the configuration for ASM Event Logging.
+
+Navigate to the Security >> Policies tab.
+
+Set "Policy Settings" to "Advanced".
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
+
+Verify that "Log Profile" is Enabled and a logging profile is assigned under "Selected".
+
+Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
+
+Select the Logging Profile that was assigned to the virtual server.
+
+Verify "Request Type" is set to "Illegal requests, and requests that include staged attack signatures" is selected under "Storage Filter".
+
+If the BIG-IP ASM module is not configured to continuously monitor inbound communications traffic for unusual or unauthorized activities or conditions, this is a finding.SRG-NET-000401-ALG-000127<GroupDescription></GroupDescription>F5BI-AS-000261The BIG-IP ASM module must check the validity of all data inputs except those specifically identified by the organization.<VulnDiscussion>Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior potentially leading to an application or information system compromise. Invalid input is one of the primary methods employed when attempting to compromise an application.
+
+Network devices with the functionality to perform application layer inspection may be leveraged to validate data content of network communications. Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software typically follows well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If network elements use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Pre-screening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher-layer proxy functionality.
+
+Note: A limitation of ~200 policies per cluster currently exists on the BIG-IP Core. If this requirement cannot be met due to this limitation, documentation from the AO is required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Application Security ManagerDISADPMS TargetF5 BIG-IP Application Security Manager4003SV-74495V-60065CCI-001310If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to check the validity of all data inputs except those specifically identified by the organization.If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
+
+Verify the BIG-IP ASM module is configured to check the validity of all data inputs except those specifically identified by the organization.
+
+Navigate to the BIG-IP System manager >> Application Security >> Parameters >> Parameters List.
+
+Select the policy for "Current Edited Policy" used for checking data inputs.
+
+Review the parameters under the "Parameters List" section.
+
+Verify parameters are configured to check the validity of all data inputs except those specifically identified by the organization.
+
+If the BIG-IP ASM module is not configured to check the validity of all data inputs except those specifically identified by the organization, this is a finding.
\ No newline at end of file
diff --git a/benchmarks/DISA/U_F5_BIG-IP_Device_Management_STIG_V2R3_Manual-xccdf.xml b/benchmarks/DISA/U_F5_BIG-IP_Device_Management_STIG_V2R3_Manual-xccdf.xml
new file mode 100644
index 000000000..4ff52aa19
--- /dev/null
+++ b/benchmarks/DISA/U_F5_BIG-IP_Device_Management_STIG_V2R3_Manual-xccdf.xml
@@ -0,0 +1,732 @@
+acceptedF5 BIG-IP Device Management Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 3 Benchmark Date: 29 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000001-NDM-000200<GroupDescription></GroupDescription>F5BI-DM-000003The BIG-IP appliance must limit the number of concurrent sessions to the Configuration Utility to 10 or an organization-defined number.<VulnDiscussion>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 DoS attacks.
+
+This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74521V-60091CCI-000054Configure the BIG-IP appliance either to limit the number of concurrent sessions to 10 or an organization-defined number.Verify the BIG-IP appliance is configured to limit the number of concurrent sessions to 10 or an organization-defined number.
+
+Navigate to the BIG-IP System manager >> System >> Preferences.
+
+Set "System Settings:" to "Advanced".
+
+Verify "Maximum HTTP Connections to Configuration Utility" is set to the organization-defined number of concurrent sessions.
+
+If neither of these configurations is present, this is a finding.SRG-APP-000026-NDM-000208<GroupDescription></GroupDescription>F5BI-DM-000019The BIG-IP appliance must automatically audit account creation.<VulnDiscussion>Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. Notification of account creation helps to mitigate this risk. Auditing account creation provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74533V-60103CCI-000018Configure the BIG-IP appliance to use an approved remote authentication server that automatically audits the creation of accounts.Verify the BIG-IP appliance is configured to use a remote authentication server that automatically audits account creation.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that automatically audits account creation.
+
+If the BIG-IP appliance is not configured to use a remote authentication server that automatically audits account creation, this is a finding.SRG-APP-000027-NDM-000209<GroupDescription></GroupDescription>F5BI-DM-000021The BIG-IP appliance must automatically audit account modification.<VulnDiscussion>Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel with the appropriate and necessary privileges. Auditing account modification along with an automatic notification to appropriate individuals will provide the necessary reconciliation that account management procedures are being followed. If modifications to management accounts are not audited, reconciliation of account management procedures cannot be tracked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74535V-60105CCI-001403Configure the BIG-IP appliance to use an approved authentication server that automatically audits account modifications.Verify the BIG-IP appliance is configured to use a remote authentication server that automatically audits account modifications.
+
+Verify the BIG-IP appliance is configured to utilize a properly configured authentication server.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured to use an approved remote authentication server that automatically audits account modification.
+
+If account modification is not automatically audited, this is a finding.SRG-APP-000028-NDM-000210<GroupDescription></GroupDescription>F5BI-DM-000023The BIG-IP appliance must automatically audit account-disabling actions.<VulnDiscussion>Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account disabling actions will support account management procedures. When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74537V-60107CCI-001404Configure the BIG-IP appliance to use an approved authentication server that automatically audits account-disabling actions.Verify the BIG-IP appliance is configured to use a remote authentication server that automatically audits account-disabling actions.
+
+Verify the BIG-IP appliance is configured to use a properly configured authentication server.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured to use an approved remote authentication server that automatically audits account-disabling actions.
+
+If account disabling is not automatically audited, this is a finding.SRG-APP-000029-NDM-000211<GroupDescription></GroupDescription>F5BI-DM-000025The BIG-IP appliance must automatically audit account removal actions.<VulnDiscussion>Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will support account management procedures. When device management accounts are terminated, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74539V-60109CCI-001405Configure the BIG-IP appliance to use an approved authentication server that automatically audits account removal actions.Verify the BIG-IP appliance is configured to use a remote authentication server that automatically audits account removal actions.
+
+Verify the BIG-IP appliance is configured to use a properly configured authentication server.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured to use an approved remote authentication server that automatically audits account removal actions.
+
+If account removal is not automatically audited, this is a finding.SRG-APP-000033-NDM-000212<GroupDescription></GroupDescription>F5BI-DM-000027The BIG-IP appliance must be configured to enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level in accordance with applicable policy for the device.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Network devices use access control policies and enforcement mechanisms to implement this requirement.
+
+Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the network device to control access between administrators (or processes acting on behalf of administrators) and objects (e.g., device commands, files, records, processes) in the network device.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74541V-60111CCI-000213Configure the BIG-IP appliance to enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level in accordance with applicable policy for the device.Verify the BIG-IP appliance is configured to enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level in accordance with applicable policy for the device.
+
+Verify the BIG-IP appliance is configured to utilize a properly configured authentication server.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured to use an approved remote authentication server that enforces the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level.
+
+If the BIG-IP appliance is not configured to enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level, this is a finding.SRG-APP-000065-NDM-000214<GroupDescription></GroupDescription>F5BI-DM-000031The BIG-IP appliance must be configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74543V-60113CCI-000044Configure the BIG-IP appliance to use an approved remote authentication server to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.Verify the BIG-IP appliance is configured to use a remote authentication server to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
+
+If the BIG-IP appliance is not configure to use a remote authentication server to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period, this is a finding.SRG-APP-000068-NDM-000215<GroupDescription></GroupDescription>F5BI-DM-000033The BIG-IP appliance must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.<VulnDiscussion>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.
+
+System use notifications are required only for access via logon interfaces with human users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74671V-60241CCI-000048Configure the BIG-IP appliance to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.Verify the BIG-IP appliance is configured to present a DoD-approved banner formatted in accordance with DTM-08-060.
+
+Navigate to the BIG-IP System manager >> System >> Preferences.
+
+Verify "Show The Security Banner On The Login Screen" is Enabled.
+
+Review the "Security Banner Text To Show On The Login Screen" under the "Security Settings" section for the following verbiage:
+
+"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."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+If such a banner is not presented, this is a finding.SRG-APP-000080-NDM-000220<GroupDescription></GroupDescription>F5BI-DM-000043The BIG-IP appliance must be configured to protect against an individual (or process acting on behalf of an individual) falsely denying having performed system configuration changes.<VulnDiscussion>This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration management process. All configuration changes to the network device are logged, and administrators authenticate with two-factor authentication before gaining administrative access. Together, these processes will ensure the administrators can be held accountable for the configuration changes they implement.
+
+To meet this requirement, the network device must log administrator access and activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74551V-60121CCI-000166Configure the BIG-IP appliance to use a properly configured authentication server to protect against an individual (or process acting on behalf of an individual) falsely denying having performed system configuration changes.Verify the BIG-IP appliance is configured to use a properly configured authentication server that protects against an individual (or process acting on behalf of an individual) falsely denying having performed system configuration changes.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that protects against an individual falsely denying having performed system configuration changes.
+
+If the BIG-IP appliance is not configured to protect against an individual (or process acting on behalf of an individual) falsely denying having performed system configuration changes, this is a finding.SRG-APP-000119-NDM-000236<GroupDescription></GroupDescription>F5BI-DM-000075The BIG-IP appliance must be configured to protect audit information from unauthorized modification.<VulnDiscussion>Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit network device activity.
+
+If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity would be impossible to achieve.
+
+To ensure the veracity of audit data, the network device must protect audit information from unauthorized modification.
+
+This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions and limiting log data locations.
+
+Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74559V-60129CCI-000163Configure the BIG-IP appliance to protect audit information from unauthorized modification.Verify the BIG-IP appliance protects audit information from any type of unauthorized modification.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Verify authorized access is configured for each role under "Log Access".
+
+If the BIG-IP appliance is not configured to protect audit information from unauthorized modification, this is a finding.SRG-APP-000120-NDM-000237<GroupDescription></GroupDescription>F5BI-DM-000077The BIG-IP appliance must be configured to protect audit information from unauthorized deletion.<VulnDiscussion>Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
+
+If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity would be impossible to achieve.
+
+To ensure the veracity of audit data, the network device must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files receive the proper file system permissions utilizing file system protections, restricting access, and backing up log data to ensure log data is retained.
+
+Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order to make access decisions regarding the deletion of audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74561V-60131CCI-000164Configure the BIG-IP appliance to protect audit information from unauthorized deletion.Verify the BIG-IP appliance protects audit information from any type of unauthorized deletion.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Verify authorized access is configured for each role under "Log Access".
+
+If the BIG-IP appliance is not configured to protect audit information from unauthorized deletion, this is a finding.SRG-APP-000121-NDM-000238<GroupDescription></GroupDescription>F5BI-DM-000079The BIG-IP appliance must be configured to protect audit tools from unauthorized access.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.
+
+Network devices providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools.
+
+Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74563V-60133CCI-001493Configure the BIG-IP appliance to protect audit tools from unauthorized access.Verify the BIG-IP appliance protects audit tools from unauthorized access.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Verify authorized access is configured for each role under "Log Access".
+
+If the BIG-IP appliance is not configured to protect its audit tools from unauthorized access, this is a finding.SRG-APP-000142-NDM-000245<GroupDescription></GroupDescription>F5BI-DM-000093The BIG-IP appliance must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused or unnecessary physical and logical ports/protocols on information systems.
+
+Network 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.
+
+To 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 to conduct official business or to address authorized quality of life issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74569V-60139CCI-000382Configure the BIG-IP appliance to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.Verify the BIG-IP appliance prohibits the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
+
+Navigate to the BIG-IP System manager >> System >> Services.
+
+Verify no unauthorized services are configured or running.
+
+If any unnecessary or nonsecure functions are permitted, this is a finding.SRG-APP-000153-NDM-000249<GroupDescription></GroupDescription>F5BI-DM-000101The BIG-IP appliance must be configured to ensure administrators are authenticated with an individual authenticator prior to using a group authenticator.<VulnDiscussion>To assure individual accountability and prevent unauthorized access, administrators must be individually identified and authenticated.
+
+Individual accountability mandates that each administrator is uniquely identified. A group authenticator is a shared account or some other form of authentication that allows multiple unique individuals to access the network device using a single account.
+
+If a device allows or provides for group authenticators, it must first individually authenticate administrators prior to implementing group authenticator functionality.
+
+Some devices may not have the need to provide a group authenticator; this is considered a matter of device design. In those instances where the device design includes the use of a group authenticator, this requirement will apply. This requirement applies to accounts created and managed on or by the network device.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74575V-60145CCI-000770Configure the BIG-IP appliance to authenticate administrators with an individual authenticator prior to using a group authenticator.Verify the BIG-IP appliance is configured to authenticate administrators with an individual authenticator prior to using a group authenticator.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that authenticates administrators to an administrators group.
+
+Navigate to System >> Users >> Remote Role Groups.
+
+Verify that administrators are assigned to the Administrator Role.
+
+If the BIG-IP appliance is not configured to authenticate administrators with an individual authenticator prior to using a group authenticator, this is a finding.SRG-APP-000164-NDM-000252<GroupDescription></GroupDescription>F5BI-DM-000107The BIG-IP appliance must be configured to enforce a minimum 15-character password length.<VulnDiscussion>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.
+
+The 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74577V-60147CCI-000205Configure the BIG-IP appliance to use a properly configured authentication server to enforce a minimum 15-character password length.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces a minimum 15-character password length.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces a minimum of 15-character password length.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server to enforce a minimum 15-character password length, this is a finding.SRG-APP-000166-NDM-000254<GroupDescription></GroupDescription>F5BI-DM-000111If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one upper-case character be used.<VulnDiscussion>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.
+
+Password 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74679V-60249CCI-000192Configure the BIG-IP appliance to use a properly configured authentication server to enforce password complexity by requiring that at least one upper-case character be used.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforce password complexity by requiring that at least one upper-case character be used.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces password complexity by requiring that at least one upper-case character be used.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces password complexity by requiring that at least one upper-case character be used, this is a finding.SRG-APP-000167-NDM-000255<GroupDescription></GroupDescription>F5BI-DM-000113If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one lower-case character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor of several that 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74581V-60151CCI-000193Configure the BIG-IP appliance to use a properly configured authentication server to enforce password complexity by requiring that at least one lower-case character be used.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces password complexity by requiring that at least one lower-case character be used.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces password complexity by requiring that at least one lower-case character be used.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces password complexity by requiring that at least one lower-case character be used, this is a finding.SRG-APP-000168-NDM-000256<GroupDescription></GroupDescription>F5BI-DM-000115If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one numeric character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor of several that 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74681V-60251CCI-000194Configure the BIG-IP appliance to use a properly configured authentication server to enforce password complexity by requiring that at least one numeric character be used.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces password complexity by requiring that at least one numeric character be used.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces password complexity by requiring that at least one numeric character be used.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces password complexity by requiring that at least one numeric character be used, this is a finding.SRG-APP-000169-NDM-000257<GroupDescription></GroupDescription>F5BI-DM-000117If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one special character be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74583V-60153CCI-001619Configure the BIG-IP appliance to use a properly configured authentication server to enforce password complexity by requiring that at least one special character be used.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces password complexity by requiring that at least one special character be used.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces password complexity by requiring that at least one special character be used.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces password complexity by requiring that at least one special character be used, this is a finding.SRG-APP-000170-NDM-000329<GroupDescription></GroupDescription>F5BI-DM-000119If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must require that when a password is changed, the characters are changed in at least eight (8) of the positions within the password.<VulnDiscussion>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.
+
+The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74585V-60155CCI-000195Configure the BIG-IP appliance to use a properly configured authentication server to require when a password is changed, the characters are changed in at least eight (8) of the positions within the password. Verify the BIG-IP appliance is configured to use a properly configured authentication server that requires when a password is changed, the characters are changed in at least eight (8) of the positions within the password.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that requires when a password is changed, the characters are changed in at least eight (8) of the positions within the password.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that requires when a password is changed, the characters are changed in at least eight (8) of the positions within the password, this is a finding.SRG-APP-000171-NDM-000258<GroupDescription></GroupDescription>F5BI-DM-000121The BIG-IP appliance must only store encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
+
+Network devices must enforce password encryption using an approved cryptographic hash function, when storing passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74587V-60157CCI-000196Configure the BIG-IP appliance to use a properly configured authentication server that only stores encrypted representations of passwords.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces password encryption for storage.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that only stores encrypted representations of passwords.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that stores encrypted representations of passwords, this is a finding.SRG-APP-000172-NDM-000259<GroupDescription></GroupDescription>F5BI-DM-000123The BIG-IP appliance must only transmit encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
+
+Network devices can accomplish this by making direct function calls to encryption modules or by leveraging operating system encryption capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74589V-60159CCI-000197Configure the BIG-IP appliance or its associated authentication server to transmit only encrypted representations of passwords.Verify the BIG-IP appliance is configured to use a properly configured authentication server that transmits only encrypted representations of passwords.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that only transmits encrypted representations of passwords.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that only transmits encrypted representations of passwords, this is a finding.SRG-APP-000178-NDM-000264<GroupDescription></GroupDescription>F5BI-DM-000133The BIG-IP appliance must be configured to obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.<VulnDiscussion>To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the network device must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.
+
+Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. For example, displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74593V-60163CCI-000206Configure the BIG-IP appliance to use SSL communications when connecting to a properly configured authentication server.Verify if the BIG-IP appliance is configured to obscure feedback of authentication information during the authentication process.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Encryption" is configured to use SSL for the authentication process with a properly configured authentication server.
+
+If the BIG-IP appliance is not configured to obscure feedback of authentication information during the authentication process, this is a finding.SRG-APP-000179-NDM-000265<GroupDescription></GroupDescription>F5BI-DM-000135The BIG-IP appliance must be configured to use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.<VulnDiscussion>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.
+
+Network devices utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
+
+FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74685V-60255CCI-000803Configure the BIG-IP appliance to use a properly configured authentication server that uses mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.Verify the BIG-IP appliance is configured to use a properly configured authentication server that uses mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that uses mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that uses mechanisms that meet the requirements for authentication to a cryptographic module, this is a finding.SRG-APP-000186-NDM-000266<GroupDescription></GroupDescription>F5BI-DM-000137The BIG-IP appliance must be configured to terminate all management sessions after 10 minutes of inactivity.<VulnDiscussion>If a device management session or connection remains open after management is completed, it may be hijacked by an attacker and used to compromise or damage the network device.
+
+Nonlocal device management and diagnostic activities are activities conducted by individuals communicating through an external network (e.g., the internet) or an internal network.
+
+If the remote node has abnormally terminated or an upstream link from the managed device is down, BIG IP F5 terminates the management session and associated connection by default, and this is not configurable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74595V-60165CCI-000879CCI-000057CCI-001133Verify the BIG-IP appliance is configured to terminate all sessions and network connections when nonlocal device maintenance is completed.
+
+Navigate to the BIG-IP System manager >> System >> Preferences.
+
+Verify "Idle Time Before Automatic Logout" is set to 900 seconds (or less) and "Enforce Idle Timeout While View Dashboard" is enabled.
+
+If the BIG-IP appliance is not configured to terminate all idle sessions after 10 minutes or less, this is a finding.Verify the BIG-IP appliance is configured to terminate all sessions and network connections when nonlocal device maintenance is completed.
+
+Navigate to the BIG-IP System manager >> System >> Preferences.
+
+Verify "Idle Time Before Automatic Logout" is set to 900 seconds (or less) and "Enforce Idle Timeout While View Dashboard" is enabled.
+
+If the BIG-IP appliance is not configured to terminate all idle sessions after 10 minutes or less, this is a finding.SRG-APP-000319-NDM-000283<GroupDescription></GroupDescription>F5BI-DM-000171The BIG-IP appliance must be configured to automatically audit account-enabling actions.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of application user accounts and notifies administrators and Information System Security Officers (ISSO). Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74617V-60187CCI-002130Configure the BIG-IP appliance to use a properly configured remote authentication server to automatically audit account-enabling actions.Verify the BIG-IP appliance is configured to use a properly configured remote authentication server that automatically audits account-enabling actions.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that automatically audits account-enabling actions.
+
+If the BIG-IP appliance is not configured to use a properly configured remote authentication server to automatically audit account-enabling actions, this is a finding.SRG-APP-000329-NDM-000287<GroupDescription></GroupDescription>F5BI-DM-000179The BIG-IP appliance must be configured to enforce organization-defined role-based access control policies over defined subjects and objects.<VulnDiscussion>Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the organization-defined roles. When administrators are assigned to the organizational roles, they inherit the authorizations or privileges defined for those roles. RBAC simplifies privilege administration for organizations because privileges are not assigned directly to every administrator (which can be a significant number of individuals for mid- to large-size organizations) but are instead acquired through role assignments. RBAC can be implemented either as a mandatory or discretionary form of access control.
+
+The RBAC policies and the subjects and objects are defined uniquely for each network device, so they cannot be specified in the requirement.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74623V-60193CCI-002169CCI-000366Configure the BIG-IP appliance to use a properly configured authentication server to enforce organization-defined role-based access control policy over defined subjects and objects.Verify the BIG-IP appliance enforces organization-defined role-based access control policy over defined subjects and objects.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server that assigns authenticated users to an appropriate group.
+
+Navigate to System >> Users >> Remote Role Groups.
+
+Verify Remote Role Groups are assigned proper Role Access and Partition Access.
+
+If the BIG-IP appliance is not configured to enforce organization-defined role-based access control policies over defined subjects and objects, this is a finding.SRG-APP-000357-NDM-000293<GroupDescription></GroupDescription>F5BI-DM-000191The BIG-IP appliance must be configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.<VulnDiscussion>In order 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.
+
+The 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74631V-60201CCI-001849Configure the BIG-IP appliance to use a properly configured syslog server to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.Verify the BIG-IP appliance is configured to off-load audit records to a remote syslog server that allocates audit record storage capacity in accordance with organization-defined audit record storage requirements.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Remote Logging.
+
+Verify a syslog destination is configured that allocates audit record storage capacity in accordance with organization-defined audit record storage requirements.
+
+If audit record store capacity is not allocated in accordance with organization-defined audit record storage requirements, this is a finding.SRG-APP-000373-NDM-000298<GroupDescription></GroupDescription>F5BI-DM-000201The BIG-IP appliance must be configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources.<VulnDiscussion>The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions.
+
+Multiple time sources provide redundancy by including a secondary source. Time synchronization is usually a hierarchy; clients synchronize time to a local source while that source synchronizes its time to a more accurate source. The network device must utilize an authoritative time server and/or be configured to use redundant authoritative time sources. This requirement is related to the comparison done in CCI-001891.
+
+DoD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DoD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region from the primary time source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74635V-60205CCI-001893CCI-000366Configure the BIG-IP appliance to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources.Determine if the BIG-IP appliance is configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources.
+
+Navigate to the BIG-IP System manager >> Configuration >> Device >> NTP.
+
+Verify there is a primary time source and a secondary time source configured that are in different geographic regions.
+
+If the BIG-IP appliance is not configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources, this is a finding.SRG-APP-000380-NDM-000304<GroupDescription></GroupDescription>F5BI-DM-000213The BIG-IP appliance must be configured to enforce access restrictions associated with changes to device configuration.<VulnDiscussion>Failure to provide logical access restrictions associated with changes to device configuration may have significant effects on the overall security of the system.
+
+When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the device can potentially have significant effects on the overall security of the device.
+
+Accordingly, only qualified and authorized individuals should be allowed to obtain access to device components for the purposes of initiating changes, including upgrades and modifications.
+
+Logical access restrictions include, for example, controls that restrict access to workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74639V-60209CCI-001813Configure the BIG-IP appliance to use role-based access to enforce access restrictions associated with changes to device configuration.Verify the BIG-IP appliance is configured to enforce access restrictions associated with changes to device configuration.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server that assigns authenticated users to an appropriate group.
+
+Navigate to System >> Users >> Remote Role Groups.
+
+Verify Remote Role Groups are assigned proper Role Access and Partition Access to enforce access restrictions associated with changes to device configuration.
+
+If the BIG-IP appliance is not configured to enforce such access restrictions, this is a finding.SRG-APP-000381-NDM-000305<GroupDescription></GroupDescription>F5BI-DM-000215The BIG-IP appliance must be configured to audit the enforcement actions used to restrict access associated with changes to the device.<VulnDiscussion>Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions.
+
+Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74641V-60211CCI-001814Configure the BIG-IP appliance to audit the enforcement actions used to restrict access associated with changes to the device.Verify the BIG-IP appliance is configured to audit the enforcement actions used to restrict access associated with changes to the device.
+
+Navigate to the BIG-IP System manager >> Logs >> Configuration >> Options.
+
+Review configuration in the "Audit Logging" section.
+
+Verify that "MCP" is set to Debug.
+
+If the BIG-IP appliance is not configured to audit the enforcement actions used to restrict access associated with changes to the device, this is a finding.SRG-APP-000435-NDM-000315<GroupDescription></GroupDescription>F5BI-DM-000239The BIG-IP appliance must be configured to protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the BIG-IP appliance management network by limiting the number of concurrent sessions.<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.
+
+This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.
+
+The security safeguards cannot be defined at the DoD level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (for example, firewalls performing packet filtering to block DoS attacks).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74647V-60217CCI-002385Configure the BIG-IP appliance to limit the effects of DoS attacks by employing security safeguards to limit the number of concurrent sessions to the configuration utility.Verify the BIG-IP appliance is configured to protect against or to limit the effects of DoS attacks by limiting the number of concurrent sessions.
+
+Review organizational Standard Operating Procedures (SOP) to ensure there is an organizational-defined threshold for the number of allowed connections to the management console.
+
+Navigate to the BIG-IP System manager >> System >> Preferences.
+
+Set "System Settings:" to "Advanced".
+
+Verify "Maximum HTTP Connections To Configuration Utility" is set to the number of allowed connections defined in the local SOP.
+
+If the BIG-IP appliance is not configured to protect against or limit the effects of DoS attacks by limiting the number of concurrent sessions, this is a finding.SRG-APP-000515-NDM-000325<GroupDescription></GroupDescription>F5BI-DM-000257The BIG-IP appliance must be configured to off-load audit records onto a different system or media than the system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+
+Off-loading is a common process in information systems with limited audit storage capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74649V-60219CCI-001851Configure the BIG-IP appliance to off-load audit records onto a different system or media than the system being audited.Verify the BIG-IP appliance is configured to off-load audit records onto a different system or media than the system being audited.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Remote Logging.
+
+Verify a syslog destination is configured that off-loads audit records from the BIG-IP appliance that is different from the system being audited.
+
+If BIG-IP appliance is not configured to off-load audit records onto a different system or media, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000259The BIG-IP appliance must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.<VulnDiscussion>Configuring the network device to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the network device. Security-related parameters are those parameters impacting the security state of the network device, including the parameters required to satisfy other security control requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74651V-60221CCI-000366Configure the BIG-IP appliance to be in compliance with the applicable security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.Verify the BIG-IP appliance is configured in accordance with the security configuration settings based on applicable DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
+
+If the BIG-IP appliance is not configured in accordance with the designated security configuration settings, this is a finding.SRG-APP-000516-NDM-000336<GroupDescription></GroupDescription>F5BI-DM-000269The BIG-IP appliance must be configured to employ automated mechanisms to centrally manage authentication settings.<VulnDiscussion>The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local administrator accounts for daily usage on each network device without centralized management is not scalable or feasible. Without centralized management, it is likely that credentials for some network devices will be forgotten, leading to delays in administration, which itself leads to delays in remediating production problems and in addressing compromises in a timely fashion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74657V-60227CCI-000366CCI-000370Configure the BIG-IP appliance to use an approved remote authentication server to employ automated mechanisms to centrally manage authentication settings.Verify the BIG-IP appliance is configured to use a remote authentication server to centrally manage authentication settings.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that employs automated mechanisms to centrally manage authentication settings.
+
+If authentication settings are not managed centrally using automated mechanisms, this is a finding.SRG-APP-000516-NDM-000340<GroupDescription></GroupDescription>F5BI-DM-000277The BIG-IP appliance must create backups of system-level information contained in the information system when changes occur or weekly, whichever is sooner.<VulnDiscussion>System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the execution and operation of the device. Information system backup is a critical step in ensuring system integrity and availability. If the system fails and there is no backup of the system-level information, a denial of service condition is possible for all who utilize this critical network component.
+
+This control requires the network device to support the organizational central backup process for system-level 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74663V-60233CCI-000366CCI-000537Configure the BIG-IP appliance to create backups of system-level information contained in the information system when changes occur or weekly, whichever is sooner.Verify the BIG-IP appliance is capable of creating backups of system-level information contained in the information system when changes occur.
+
+Navigate to the BIG-IP System manager >> System >> Archives.
+
+Review the list of archives to verify backups are conducted in accordance with the local backup policy.
+
+If the BIG-IP appliance does not support the creating backups of system-level information contained in the information system when changes occur or weekly, this is a finding.SRG-APP-000516-NDM-000341<GroupDescription></GroupDescription>F5BI-DM-000279The BIG-IP appliance must be configured to create backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner.<VulnDiscussion>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.
+
+This 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74665V-60235CCI-000539CCI-000366Configure the BIG-IP appliance to create backups of information system documentation, including security-related documentation, when changes occur.Verify the BIG-IP appliance is configured to off-load logs to a remote log server when changes occur.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Remote Logging.
+
+Verify a log destination is configured to allow for backups of information system documentation when changes occur.
+
+If the BIG-IP appliance does not backup the information system documentation, including security-related documentation, when changes occur, this is a finding.SRG-APP-000516-NDM-000344<GroupDescription></GroupDescription>F5BI-DM-000283The BIG-IP appliance must be configured to obtain its public key certificates from an appropriate certificate policy through a DoD-approved service provider.<VulnDiscussion>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 will suffice.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74669V-60239CCI-000366CCI-001159Configure the BIG-IP appliance to obtain its public key certificates from an appropriate certificate policy through a DoD-approved service provider.Verify the BIG-IP appliance is configured to obtain public key certificates from an appropriate certificate policy through a DoD-approved service provider.
+
+Navigate to the BIG-IP System manager >> System >> Device Certificates >> Device Certificate.
+
+Verify the device certificate has been obtained from an approved service provider.
+
+If the BIG-IP appliance does not obtain its public key certificates from an appropriate certificate policy through a DoD-approved service provider, this is a finding.SRG-APP-000142-NDM-000245<GroupDescription></GroupDescription>F5BI-DM-000284The F5 BIG-IP must ensure SSH is disabled for root user logon to prevent remote access using the root account.<VulnDiscussion>The F5 BIG-IP shell must be locked down to limit the ability to modify the configuration through the shell. Preventing attackers from remotely accessing management functions using root account mitigates the risk that unauthorized individuals or processes may gain superuser access to information or privileges. Additionally, the audit records for actions taken using the group account will not identify the specific person who took the actions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-106833V-97729CCI-000366To ensure that the F5 BIG-IP meets the requirements within the STIG, limit the ability to modify the configuration at the command line. SSH into the command line interface and type in the following commands.
+
+(tmos)# modify sys db systemauth.disablerootlogin value true
+(tmos)# modify sys db systemauth.disablebash value true
+(tmos)# save sys configVerify the F5 BIG-IP shell is locked down to limit the ability to modify the configuration through the shell.
+Log in to the Configuration utility as the administrative user.
+
+Navigate to System > Platform.
+Under Root Account, verify the Disable login and Disable bash check boxes are checked.
+
+If the value of systemauth.disablerootlogin and db systemauth.disablebash is not set to “true”, then this is a finding.
+SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000013The BIG-IP appliance must provide automated support for account management functions.<VulnDiscussion>Account management functions include: assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The network device must be configured to automatically provide account management functions, and these functions must immediately enforce the organization's current account policy.
+
+All accounts used for access to the network device are privileged or system-level accounts. Therefore, if account management functions are not automatically enforced, an attacker could gain privileged access to a vital element of the network security architecture.
+
+This control does not include emergency administration accounts that provide access to the network device components in case of network failure. There must be only one such locally defined account.
+
+All other accounts must be defined. All other accounts must be created and managed on the site's authentication server (e.g., RADIUS, LDAP, or Active Directory). This requirement is applicable to account management functions provided by the network device application. If the function is provided by the underlying OS or an authentication server, it must be secured using the applicable security guide or STIG.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60095SV-74525CCI-000366CCI-000015Configure the BIG-IP appliance to use an approved remote authentication server that provides automated support for account management.Verify the BIG-IP appliance is configured to use a remote authentication server that provides automated account management.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that provides automated support for account management functions.
+
+If the BIG-IP appliance is not configured to use a remote authentication server to provide automated account management, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000015The BIG-IP appliance must automatically remove or disable temporary user accounts after 72 hours.<VulnDiscussion>Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. If temporary accounts remain active when no longer needed, they may be used to gain unauthorized access. The risk is greater for the network device since these accounts have elevated privileges. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74527V-60097CCI-000366CCI-000016Configure the BIG-IP appliance to use an approved remote authentication server that automatically removes or disables temporary user accounts after 72 hours.Verify the BIG-IP appliance is configured to use a remote authentication server to automatically disable or remove temporary accounts after 72 hours.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that automatically removes or disables temporary user accounts after 72 hours.
+
+If the use of temporary accounts is prohibited, this is not a finding.
+
+If the BIG-IP appliance is not configured to use a remote authentication server that automatically disables or removes temporary accounts after 72 hours, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000017The BIG-IP appliance must automatically disable accounts after a 35-day period of account inactivity.<VulnDiscussion>Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Inactive accounts could be reactivated or compromised by unauthorized users, allowing exploitation of vulnerabilities and undetected access to the network device.
+
+This control does not include emergency administration accounts, which are meant for access to the network device components in case of network failure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74529V-60099CCI-000366CCI-000017Configure the BIG-IP appliance to use an approved remote authentication server that automatically disables accounts after 35 days of inactivity.Verify the BIG-IP appliance is configured to use a remote authentication server that automatically disables accounts after 35 days of inactivity.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that automatically disables accounts after a 35-day period of account inactivity.
+
+If the BIG-IP appliance is not configured to use a remote authentication server that automatically disables accounts after a 35-day period of account inactivity, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000037Upon successful logon, the BIG-IP appliance must be configured to notify the administrator of the date and time of the last logon.<VulnDiscussion>Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the date and time of their last successful logon allows them to determine if any unauthorized activity has occurred. This incorporates all methods of logon, including, but not limited to, SSH, HTTP, HTTPS, and physical connectivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74545V-60115CCI-000052CCI-000366Configure the BIG-IP appliance to use an approved remote authentication server to notify the administrator of the date and time of the last logon upon successful logon.Verify the BIG-IP appliance is configured to use a remote authentication server to notify the administrator of the date and time of their last logon.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server to notify the administrator of the date and time of the last logon.
+
+If the administrator is not notified of the date and time of the last logon upon successful logon, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000039Upon successful logon, the BIG-IP appliance must be configured to notify the administrator of the number of unsuccessful logon attempts since the last successful logon.<VulnDiscussion>Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the number of unsuccessful attempts made to logon to their account allows them to determine if any unauthorized activity has occurred. Without this information, the administrator may not be aware that unauthorized activity has occurred. This incorporates all methods of logon, including, but not limited to, SSH, HTTP, HTTPS, and physical connectivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60117SV-74547CCI-000053CCI-000366Configure the BIG-IP appliance to use an approved remote authentication server to notify the administrator of the number of unsuccessful logon attempts since the last successful logon, upon successful logon.Verify the BIG-IP appliance is configured to use a remote authentication server to notify the administrator of the number of unsuccessful logon attempts since the last successful logon.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server to notify the administrator of the number of unsuccessful logon attempts since the last successful logon.
+
+If the administrator is not notified of the number of unsuccessful logon attempts since the last successful logon, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000067The BIG-IP appliance must be configured to alert the ISSO and SA (at a minimum) in the event of an audit processing failure.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
+
+Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60123SV-74553CCI-000366CCI-000139Configure the BIG-IP appliance to alert the ISSO and SA (at a minimum) in the event of an audit processing failure.Verify the BIG-IP appliance is configured to alert the ISSO and SA (at a minimum) in the event of an audit processing failure.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Verify "MCP" under the "Audit Logging" section is set to Debug.
+
+If the BIG-IP appliance is not configured to alert in the event of an audit processing failure, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000073The BIG-IP appliance must be configured to protect audit information from any type of unauthorized read access.<VulnDiscussion>Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
+
+If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could use to his or her advantage.
+
+To ensure the veracity of audit data, the information system and/or the network device must protect audit information from any and all unauthorized read access.
+
+This requirement can be achieved through multiple methods that will depend upon system architecture and design. Commonly employed methods for protecting audit information include least privilege permissions as well as restricting the location and number of log file repositories.
+
+Additionally, network devices with user interfaces to audit records should not allow for the unfettered manipulation of or access to those records via the device interface. If the device provides access to the audit data, the device becomes accountable for ensuring audit information is protected from unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74557V-60127CCI-000366CCI-000162Configure the BIG-IP appliance to protect audit information from any type of unauthorized read access.Verify the BIG-IP appliance is configured to protect audit information from any type of unauthorized read access.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Verify authorized access is configured for each role under "Log Access".
+
+If the BIG-IP appliance does not protect audit information from any type of unauthorized read access, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000087The BIG-IP appliance must be configured to use NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest.<VulnDiscussion>Audit records may be tampered with. If the integrity of audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
+
+Protection of audit records and audit data, including audit configuration settings, is of critical importance. Cryptographic mechanisms are the industry-established standard used to protect the integrity of audit data. An example of a cryptographic mechanism is the computation and application of a cryptographic-signed hash using asymmetric cryptography.
+
+This requirement is not intended to cause a new cryptographic hash to be generated every time a record is added to a log file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74567V-60137CCI-000366CCI-001350Configure the BIG-IP appliance to off-load audit information to a system that uses NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest.Verify the BIG-IP appliance is configured to off-load audit information to a logging system that uses NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Remote Logging.
+
+Verify a syslog destination is configured that uses NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest.
+
+If the BIG-IP appliance does not off-load audit information to a remote logging system that uses NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000095The BIG-IP appliance must be configured to uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators).<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational administrators must be uniquely identified and authenticated for all network management accesses to prevent potential misuse and compromise of the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74573V-60143CCI-000366CCI-000764Configure the BIG-IP appliance to use a properly configured authentication server that uniquely identifies and authenticates organizational administrators.Verify the BIG-IP appliance is configured to use a properly configured authentication server that uniquely identifies and authenticates organizational administrators.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that uniquely identifies and authenticates organizational administrators.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that uniquely identifies and authenticates organizational administrators, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000109The BIG-IP appliance must be configured to prohibit password reuse for a minimum of five generations.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+To meet password policy requirements, passwords need to be changed at specific policy-based intervals.
+
+If the network device allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60149SV-74579CCI-000366CCI-000200Configure the BIG-IP appliance to use a properly configured authentication server to prohibit password reuse for a minimum of five generations.Verify the BIG-IP appliance is configured to use a properly configured authentication server that prohibits password reuse for a minimum of five generations.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that prohibits password reuse for a minimum of five generations.
+
+If the BIG-IP appliance is not configured to use an associated authentication server that prohibits password reuse for a minimum of five generations, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000125The BIG-IP appliance must be configured to enforce 24 hours/1 day as the minimum password lifetime.<VulnDiscussion>Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement.
+
+Restricting this setting limits the user's ability to change their password. Passwords need to be changed at specific policy-based intervals; however, if the network device allows the user to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74683V-60253CCI-000366CCI-000198Configure the BIG-IP appliance to use a properly configured authentication server that enforces 24 hours/1 day as the minimum password lifetime.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces 24 hours/1 day as the minimum password lifetime.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces 24 hours/1 day as the minimum password lifetime.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces 24 hours/1 day as the minimum password lifetime, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000127The BIG-IP appliance must be configured to enforce a 60-day maximum password lifetime restriction.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals.
+
+One method of minimizing this risk is to use complex passwords and periodically change them. If the network device does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the passwords could be compromised.
+
+This requirement does not include emergency administration accounts that are meant for access to the network device in case of failure. These accounts are not required to have maximum password lifetime restrictions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60161SV-74591CCI-000366CCI-000199Configure the BIG-IP appliance or its associated authentication server to enforce a 60-day maximum password lifetime.Verify the BIG-IP appliance is configured to use a properly configured authentication server that enforces a 60-day maximum password lifetime.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify "Authentication: User Directory" is configured for an approved remote authentication server that enforces a 60-day maximum password lifetime restriction.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server that enforces a 60-day maximum password lifetime, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000149The BIG-IP appliance must be configured to automatically remove or disable emergency accounts after 72 hours.<VulnDiscussion>Emergency accounts are administrator accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes.
+
+If emergency accounts remain active when no longer needed, they may be used to gain unauthorized access. The risk is greater for the network device since these accounts have elevated privileges. To mitigate this risk, automated termination of all emergency accounts must be set upon account creation.
+
+Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by network administrators when network or normal logon/access is not available). Infrequently used accounts also remain available and are not subject to automatic termination dates. However, an emergency account is normally a different account that is created for use by vendors or system maintainers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74601V-60171CCI-000366CCI-001682Configure the BIG-IP appliance to use a properly configured remote authentication server to automatically disable or remove emergency accounts after 72 hours.Verify the BIG-IP appliance is configured to use a properly configured remote authentication server to automatically disable or remove emergency accounts after 72 hours.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that automatically removes or disables emergency accounts after 72 hours.
+
+If the use of emergency accounts is prohibited, this is not a finding.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server to automatically disable or remove emergency accounts after 72 hours, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000151The application must be configured to reveal error messages only to authorized individuals (ISSO, ISSM, and SA).<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state. Additionally, sensitive account information must not be revealed through error messages to unauthorized personnel or their designated representatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60173SV-74603CCI-000366CCI-001314Configure the BIG-IP appliance to reveal error messages only to authorized individuals (ISSO, ISSM, and SA).Verify the BIG-IP appliance is configured to reveal error messages only to authorized individuals (ISSO, ISSM, and SA).
+
+Navigate to the BIG-IP System manager >> Logs >> Configuration >> Options.
+
+Verify that "Log Access" is granted only to authorized individuals (ISSO, ISSM, and SA).
+
+If the BIG-IP appliance reveals error messages to any unauthorized individuals (ISSO, ISSM, and SA), this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000153The BIG-IP appliance must be configured to activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.<VulnDiscussion>Predictable failure prevention requires organizational planning to address device failure issues. If components key to maintaining the device's security fail to function, the device could continue operating in an unsecure state. If appropriate actions are not taken when a network device failure occurs, a denial of service condition may occur that could result in mission failure since the network would be operating without a critical security monitoring and prevention function. Upon detecting a failure of network device security components, the network device must activate a system alert message, send an alarm, or shut down.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60175SV-74605CCI-000366CCI-001328Configure the BIG-IP appliance to activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.Verify the BIG-IP appliance is configured to activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.
+
+Navigate to the BIG-IP System manager >> Logs >> Configuration >> Options.
+
+Verify that "MCP" under the "Audit Logging" section is set to Debug.
+
+Navigate to the BIG-IP System manager >> System >> High Availability >> Fail-Safe >> System.
+
+Verify "Switch Board Failure" under the "System Trigger Properties" section is set to perform the appropriate action based on the location of the device.
+
+If the BIG-IP appliance is not configured to activate a system alert message, send an alarm, or automatically shut down when a component failure is detected, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000155The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are created.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of accounts and notifies administrators and the ISSO. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74607V-60177CCI-000366CCI-001683Configure the BIG-IP appliance to use a properly configured authentication server to send a notification message to the administrators and ISSO when accounts are created.Verify the BIG-IP appliance is configured to generate alerts that can be forwarded to the administrators and ISSO when accounts are created.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that generates alerts that can be forwarded to the administrators and ISSO when accounts are created.
+
+If the BIG-IP appliance is not configured to use an authentication server that would perform this function, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000157The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are modified.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify an existing account. Notification of account modification is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the modification of device administrator accounts and notifies administrators and the ISSO. Such a process greatly reduces the risk that accounts will be surreptitiously modified and provides logging that can be used for forensic purposes.
+
+The network device must generate the alert. Notification may be done by a management server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60179SV-74609CCI-000366CCI-001684Configure the BIG-IP appliance to use a properly configured authentication server to send a notification message to the administrators and ISSO when accounts are modified.Verify the BIG-IP appliance is configured to use a properly configured authentication server that generates alerts that can be forwarded to the administrators and ISSO when accounts are modified.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that generates alerts that can be forwarded to the administrators and ISSO when accounts are modified.
+
+If the BIG-IP appliance is not configured to use an authentication server that would perform this function, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000159The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are disabled.<VulnDiscussion>When application accounts are disabled, administrator accessibility is affected. Accounts are utilized for identifying individual device administrators or for identifying the device processes themselves.
+
+In order to detect and respond to events that affect administrator accessibility and device processing, devices must audit account-disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that device accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74611V-60181CCI-000366CCI-001685Configure the BIG-IP appliance to use a properly configured authentication server to send a notification message to the administrators and ISSO when accounts are disabled.Verify the BIG-IP appliance is configured to use a properly configured authentication server that generates alerts that can be forwarded to the administrators and ISSO when accounts are disabled.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that generates alerts that can be forwarded to the administrators and ISSO when accounts are disabled.
+
+If the BIG-IP appliance is not configured to use an authentication server that would perform this function, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000161The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are removed.<VulnDiscussion>When application accounts are removed, administrator accessibility is affected. Accounts are utilized for identifying individual device administrators or for identifying the device processes themselves.
+
+In order to detect and respond to events that affect administrator accessibility and device processing, devices must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that device accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60183SV-74613CCI-000366CCI-001686Configure the BIG-IP appliance to use a properly configured authentication server to send a notification message to the administrators and ISSO when accounts are removed.Verify the BIG-IP appliance is configured to use a properly configured authentication server that generates alerts that can be forwarded to the administrators and ISSO when accounts are removed.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that generates alerts that can be forwarded to the administrators and ISSO when accounts are removed.
+
+If the BIG-IP appliance is not configured to use an authentication server that would perform this function, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000173The BIG-IP appliance must be configured to generate an immediate alert for account-enabling actions.<VulnDiscussion>Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of application user accounts and notifies administrators and ISSOs. Such a process greatly reduces the risk that accounts will be surreptitiously enabled and provides logging that can be used for forensic purposes.
+
+In order to detect and respond to events that affect network administrator accessibility and device processing, network devices must audit account-enabling actions and, as required, notify the appropriate individuals so they can investigate the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74619V-60189CCI-000366CCI-002132Configure the BIG-IP appliance to use a properly configured remote authentication server to generate an immediate alert for account-enabling actions.Verify the BIG-IP appliance is configured to use a properly configured remote authentication server to generate an immediate alert for account-enabling actions.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type to generate an immediate alert for account-enabling actions.
+
+If the BIG-IP appliance is not configured to use a properly configured remote authentication server to generate an immediate alert for account-enabling actions, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000175The BIG-IP appliance must be configured to transmit access authorization information using approved security safeguards to authorized information systems that enforce access control decisions.<VulnDiscussion>Protecting access authorization information (i.e., access control decisions) ensures that authorization information cannot be altered, spoofed, or otherwise compromised during transmission.
+
+In distributed information systems, authorization processes and access control decisions may occur in separate parts of the systems. In such instances, authorization information is transmitted securely so timely access control decisions can be enforced at the appropriate locations. To support the access control decisions, it may be necessary to transmit, as part of the access authorization information, supporting security attributes. This is because, in distributed information systems, there are various access control decisions that need to be made, and different entities (e.g., services) make these decisions in a serial fashion, each requiring some security attributes to make the decisions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74621V-60191CCI-000366CCI-002353Configure the BIG-IP appliance to use a properly configured authentication server that transmits access authorization information using approved security safeguards to authorized information systems that enforce access control decisions.Verify the BIG-IP appliance is configured to use a properly configured authentication server that transmits access authorization information using approved security safeguards to authorized information systems that enforce access control decisions.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server and SSL is set to use TLS.
+
+If the BIG-IP appliance transmits access authorization information without using approved security safeguards to authorized information systems that enforce access control decisions, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000185The BIG-IP appliance must be configured to automatically lock the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded.<VulnDiscussion>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. Limits are imposed by locking the account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74625V-60195CCI-000366CCI-002238Configure the BIG-IP appliance to use a properly configured remote authentication server to automatically lock the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded.Verify the BIG-IP appliance is configured to use a properly configured remote authentication server to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that automatically locks the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded.
+
+If an account is not automatically locked out until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000187The BIG-IP appliance must be configured to notify the administrator, upon successful logon (access), of the location of last logon (terminal or IP address) in addition to the date and time of the last logon (access).<VulnDiscussion>Administrators need to be aware of activity that occurs regarding their account. Providing them with information deemed important by the organization may aid in the discovery of unauthorized access or thwart a potential attacker.
+
+Organizations should consider the risks to the specific information system being accessed and the threats presented by the device to the environment when configuring this option. An excessive or unnecessary amount of information presented to the administrator at logon is not recommended.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74627V-60197CCI-000366CCI-002250Configure the BIG-IP appliance to use a properly configured authentication server that is able to notify the administrator upon successful logon of the location of last logon (terminal or IP address) in addition to the date and time of the last logon.Verify the BIG-IP appliance is configured to use a properly configured authentication server that is able to notify the administrator upon successful logon of the location of last logon (terminal or IP address) in addition to the date and time of the last logon.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that is able to notify the administrator upon successful logon of the location of last logon (terminal or IP address) in addition to the date and time of the last logon.
+
+If the administrator is not notified of the location of last logon (terminal or IP address) upon successful logon (terminal or IP address) in addition to the date and time of the last logon, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000193The BIG-IP appliance must be configured to generate an immediate alert when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.<VulnDiscussion>If security personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. This could lead to the loss of audit information. Note that while the network device must generate the alert, notification may be done by a management server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60203SV-74633CCI-000366CCI-001855Configure the BIG-IP appliance to use a properly configured syslog server to generate an immediate alert when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.Verify the BIG-IP appliance is configured to use a properly configured syslog server that generates an immediate alert when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Remote Logging.
+
+Verify a syslog destination is configured that generates an immediate alert when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.
+
+If an immediate alert is not generated when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000211The BIG-IP appliance must be configured to implement automated security responses if baseline configurations are changed in an unauthorized manner.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the device vulnerable to various attacks or allow unauthorized access to the device. Changes to device configurations can have unintended side effects, some of which may be relevant to security.
+
+Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the device. Examples of security responses include, but are not limited to, the following: halting application processing; halting selected functions; or issuing alerts/notifications to organizational personnel when there is an unauthorized modification of a configuration item. The appropriate automated security response may vary depending on the nature of the baseline configuration change, the role of the network device, the availability of organizational personnel to respond to alerts, etc.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60207SV-74637CCI-000366CCI-001744Configure the BIG-IP appliance to implement automated security responses if baseline configurations are changed in an unauthorized manner.Verify the BIG-IP appliance is configured to implement automated security responses if baseline configurations are changed in an unauthorized manner.
+
+Navigate to the BIG-IP System manager >> Logs >> Configuration >> Options.
+
+Review configuration in the "Audit Logging" section.
+
+Verify that "MCP" is set to Debug.
+
+If the BIG-IP appliance is not configured to implement automated security responses if baseline configurations are changed in an unauthorized manner, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000227The BIG-IP appliance must be configured to dynamically manage user accounts.<VulnDiscussion>Dynamic user account management prevents disruption of operations by minimizing the need for system restarts. Dynamic establishment of new user accounts will occur while the system is operational. New user accounts or changes to existing user accounts must take effect without the need for a system or session restart. Pre-established trust relationships and mechanisms with appropriate authorities (e.g., Active Directory or authentication server) that validate each user account are essential to prevent unauthorized access by changed or revoked accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74643V-60213CCI-000366CCI-001976Configure the BIG-IP appliance to use a properly configured authentication server to dynamically manage user accounts.Verify the BIG-IP appliance is configured to use a properly configured authentication server that dynamically manages user accounts.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that is configured to dynamically manage user accounts.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server to dynamically manage user accounts, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000229The BIG-IP appliance must be configured to allow the use of a temporary password for system logons with an immediate change to a permanent password.<VulnDiscussion>Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon.
+
+Temporary passwords are typically used to allow access to applications when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts that allow the users to log on yet force them to change the password once they have successfully authenticated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74645V-60215CCI-000366CCI-002041Configure the BIG-IP appliance to use an authentication server that allows the use of a temporary password for system logons with an immediate change to a permanent password.Verify the BIG-IP appliance is configured to use an authentication server that allows the use of a temporary password for system logons with an immediate change to a permanent password.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that allows the use of a temporary password for system logons with an immediate change to a permanent password.
+
+If the BIG-IP appliance is not configured to authenticate through an authentication server that allows the use of a temporary password for system logons with an immediate change to a permanent password, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000261The BIG-IP appliance must be configured to notify the administrator of the number of successful logon attempts occurring during an organization-defined time period.<VulnDiscussion>Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the date and time of their last successful logon allows the administrator to determine if any unauthorized activity has occurred. This incorporates all methods of logon, including, but not limited to, SSH, HTTP, HTTPS, and physical connectivity.
+
+The organization-defined time period is dependent on the frequency with which administrators typically log on to the network device.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74653V-60223CCI-000366CCI-001391Configure the BIG-IP appliance to use a properly configured authentication server to notify the administrator of the number of successful logon attempts occurring during an organization-defined time period.Verify the BIG-IP appliance is configured to use a properly configured authentication server that notifies the administrator of the number of successful logon attempts occurring during an organization-defined time period.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that notifies the administrator of the number of successful logon attempts occurring during an organization-defined time period.
+
+If the BIG-IP appliance is not configured to use a properly configured authentication server to notify the administrator of the number of successful logon attempts occurring during an organization-defined time period, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000263The BIG-IP appliance must be configured to use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and IAW with CJCSM 6510.01B.<VulnDiscussion>By immediately displaying an alarm message, potential security violations can be identified more quickly even when administrators are not logged onto the network device. An example of a mechanism to facilitate this would be through the utilization of SNMP traps.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60225SV-74655CCI-000366CCI-001274Configure the BIG-IP appliance to use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and IAW with CJCSM 6510.01B.Verify the BIG-IP appliance is configured to use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and IAW with CJCSM 6510.01B.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Log Destinations.
+
+Verify a log destination is configured for a CNDSP or other mechanism that is monitored by security personnel.
+
+If the BIG-IP appliance is not configured to use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and IAW with CJCSM 6510.01B, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000271The BIG-IP appliance must be configured to employ automated mechanisms to centrally apply authentication settings.<VulnDiscussion>The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local administrator accounts for daily usage on each network device without centralized management is not scalable or feasible. Without centralized management, it is likely that credentials for some network devices will be forgotten, leading to delays in administration, which itself leads to delays in remediating production problems and in addressing compromises in a timely fashion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60229SV-74659CCI-000366CCI-000371Configure the BIG-IP appliance to use an approved remote authentication server to employ automated mechanisms to centrally apply authentication settings.Verify the BIG-IP appliance is configured to use a remote authentication server to centrally apply authentication settings.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that employs automated mechanisms to centrally apply authentication settings.
+
+If authentication settings are not applied centrally using automated mechanisms, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000273The BIG-IP appliance must be configured to employ automated mechanisms to centrally verify authentication settings.<VulnDiscussion>The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local administrator accounts for daily usage on each network device without centralized management is not scalable or feasible. Without centralized management, it is likely that credentials for some network devices will be forgotten, leading to delays in administration, which itself leads to delays in remediating production problems and in addressing compromises in a timely fashion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74661V-60231CCI-000366CCI-000372Configure the BIG-IP appliance to use an approved remote authentication server to employ automated mechanisms to centrally verify authentication settings.Verify the BIG-IP appliance is configured to use a remote authentication server to centrally verify authentication settings.
+
+Navigate to the BIG-IP System manager >> System >> Users >> Authentication.
+
+Verify that "User Directory" is set to an approved authentication server type that employs automated mechanisms to centrally verify authentication settings.
+
+If authentication settings are not verified centrally using automated mechanisms, this is a finding.SRG-APP-000516-NDM-000317<GroupDescription></GroupDescription>F5BI-DM-000281The BIG-IP appliance must be configured to employ automated mechanisms to assist in the tracking of security incidents.<VulnDiscussion>Despite the investment in perimeter defense technologies, enclaves are still faced with detecting, analyzing, and remediating network breaches and exploits that have made it past the network device. An automated incident response infrastructure allows network operations to immediately react to incidents by identifying, analyzing, and mitigating any network device compromise. Incident response teams can perform root cause analysis, determine how the exploit proliferated, and identify all affected nodes, as well as contain and eliminate the threat.
+
+The network device assists in the tracking of security incidents by logging detected security events. The audit log and network device application logs capture different types of events. The audit log tracks audit events occurring on the components of the network device. The application log tracks the results of the network device content filtering function. These logs must be aggregated into a centralized server and can be used as part of the organization's security incident tracking and analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036V-60237SV-74667CCI-000366CCI-000833Configure the BIG-IP appliance to direct logs to a system that employs automated mechanisms to assist in the tracking of security incidents.Verify the BIG-IP appliance is configured to employ automated mechanisms to assist in the tracking of security incidents.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Log Destinations.
+
+Verify a log destination is configured for a system that employs automated mechanisms to assist in the tracking of security incidents.
+
+If such automated mechanisms are not employed, this is a finding.SRG-APP-000435-NDM-000315<GroupDescription></GroupDescription>F5BI-DM-000290If the BIG-IP appliance is being used to authenticate users for web applications, the HTTPOnly flag must be set.<VulnDiscussion>The HttpOnly attribute directs browsers to use cookies by way of the HTTP and HTTPS protocols only, ensuring that the cookie is not available by other means, such as JavaScript function calls. This setting mitigates the risk of attack utilizing Cross Site Scripting (XSS). This vulnerability allows an attacker to impersonate any authenticated user that has visited a page with the attack deployed, allowing them to potentially allowing the user to raise their permissions level. The vulnerability can be mitigated by setting HTTPOnly on the appropriate Access Policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036CCI-002385Configure a policy in the BIG-IP ASM module to enable the HTTPonly flag.
+
+Log in to the Configuration utility.
+
+Navigate to Security >> Options >> Application Security >> Advanced Configuration >> System Variables
+
+Create the variable cookie_httponly_attr.
+Set the Parameter to 1.If the BIG-IP ASM module is not used to support user authentication, this is not applicable.
+
+Navigate to Security >> Options >> Application Security >> Advanced Configuration >> System Variables
+Verify cookie_httponly_attr is set to 1.
+
+If the BIG-IP appliance is being used to authenticate users for web applications, the HTTPOnly flag must be set, this is a finding.SRG-APP-000435-NDM-000315<GroupDescription></GroupDescription>F5BI-DM-000163The F5 BIG-IP appliance must be configured to restrict a consistent inbound IP for the entire management session.<VulnDiscussion>This security measure helps limit the effects of denial-of-service 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036SV-74615V-60185CCI-002385Enable the "Require A Consistent Inbound IP For The Entire Web Session" setting using the Configuration utility.
+
+From the BIG-IP GUI:
+1. System.
+2. Preferences.
+3. Under "Security Settings", check "Require A Consistent Inbound IP For The Entire Web Session".
+4. Click "Update".From the BIG-IP GUI:
+1. System.
+2. Preferences.
+3. Under "Security Settings", verify "Require A Consistent Inbound IP For The Entire Web Session" box is checked.
+
+If the BIG-IP appliance is not configured to require a consistent inbound IP for the entire session for management sessions, this is a finding.SRG-APP-000068-NDM-000215<GroupDescription></GroupDescription>F5BI-DM-000291The F5 BIG-IP appliance providing user access control intermediary services must display the Standard Mandatory DOD-approved Notice and Consent Banner before granting access to SSH.<VulnDiscussion>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.
+
+System use notifications are required only for access via logon interfaces with human users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Device ManagementDISADPMS TargetF5 BIG-IP Device Management4036CCI-000048Add the SSH Banner.
+
+From the BIG-IP GUI:
+1. System.
+2. Configuration.
+3. Device.
+4. SSHD.
+5. Check the box for "Show The Security Banner On The Login Screen".
+6. Enter the following in the "Security Banner Text To Show On The Login Screen" under the "Security Settings" section:
+
+"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."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+7. Update.
+
+From the BIG-IP Console:
+tmsh modify sys sshd banner enabled
+tmsh 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."
+tmsh save sys configVerify the DoD banner is added to SSH.
+
+From the BIG-IP GUI:
+1. System.
+2. Configuration.
+3. Device.
+4. SSHD.
+5. Verify the box for "Show The Security Banner On The Login Screen" is checked.
+6. Review the "Security Banner Text To Show On The Login Screen" under the "Security Settings" section for the following verbiage:
+
+"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."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+From the BIG-IP Console:
+tmsh list sys sshd banner
+# should return a value of 'enabled'
+
+tmsh list sys sshd banner-text
+# should return a value of:
+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. At any time, the USG may inspect and seize data stored on this IS. Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."
+
+If such a banner is not presented, this is a finding.
\ No newline at end of file
diff --git a/benchmarks/DISA/U_F5_BIG-IP_Local_Traffic_Manager_STIG_V2R3_Manual-xccdf.xml b/benchmarks/DISA/U_F5_BIG-IP_Local_Traffic_Manager_STIG_V2R3_Manual-xccdf.xml
new file mode 100644
index 000000000..ec99a48ec
--- /dev/null
+++ b/benchmarks/DISA/U_F5_BIG-IP_Local_Traffic_Manager_STIG_V2R3_Manual-xccdf.xml
@@ -0,0 +1,1303 @@
+acceptedF5 BIG-IP Local Traffic Manager Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 3 Benchmark Date: 29 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-NET-000015-ALG-000016<GroupDescription></GroupDescription>F5BI-LT-000003The BIG-IP Core implementation must be configured to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.<VulnDiscussion>Successful authentication must not automatically give an entity access to an asset or security boundary. The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. All DoD systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access.
+
+Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization.
+
+Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography.
+
+ALGs must use these policies and mechanisms to control access on behalf of the application for which it is acting as intermediary and access control mechanisms are required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74687V-60257CCI-000213If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to enforce approved authorizations for logical access to information and system resources employing identity-based, role-based, and/or attribute-based security policies.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an access policy to enforce approved authorizations for logical access to information.
+
+If the BIG-IP Core is not configured to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies, this is a finding.SRG-NET-000018-ALG-000017<GroupDescription></GroupDescription>F5BI-LT-000005The BIG-IP Core implementation must be configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.<VulnDiscussion>Information flow control regulates where information is allowed to travel within a network. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network infrastructure or data.
+
+Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems. Examples of information flow control restrictions include keeping export-controlled information from being transmitted in the clear to the Internet or blocking information marked as classified but being transported to an unapproved destination.
+
+ALGs enforce approved authorizations by employing security policy and/or rules that restrict information system services, provide packet-filtering capability based on header or protocol information, and/or message filtering capability based on data content (e.g., implementing key word searches or using document characteristics).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74689V-60259CCI-001368If user packet-filtering intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP Advanced Firewall Manager (AFM) module to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of source, destination, headers, and/or content of the communications traffic.
+
+Apply the AFM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to enforce approved authorizations for controlling the flow of information within the network.If the BIG-IP Core does not perform packet-filtering intermediary services for virtual servers, this is not applicable.
+
+When packet-filtering intermediary services are performed, verify the BIG-IP Core is configured as follows:
+
+Verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an AFM policy to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Network Firewall" Enforcement is set to "Policy Rules..." and "Policy" is set to use an AFM policy to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+If the BIG-IP Core is not configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic, this is a finding.SRG-NET-000019-ALG-000018<GroupDescription></GroupDescription>F5BI-LT-000007The BIG-IP Core implementation must be configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.<VulnDiscussion>Information flow control regulates where information is allowed to travel within a network and between interconnected networks. Blocking or restricting detected harmful or suspicious communications between interconnected networks enforces approved authorizations for controlling the flow of traffic.
+
+This requirement applies the Application Layer Gateway (ALG) when used as a gateway or boundary device that allows traffic flow between interconnected networks of differing security policies.
+
+The ALG is installed and configured in such a way that it restricts or blocks information flows based on guidance in the Ports, Protocols, and Services Management (PPSM) regarding restrictions for boundary crossing for ports, protocols and services. Information flow restrictions may be implemented based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+The ALG must be configured with policy filters (e.g., security policy, rules, and/or signatures) that restrict or block information system services; provide a packet-filtering capability based on header information; and/or perform message filtering based on message content. The policy filters used depend upon the type of application gateway (e.g., web, email, or TLS).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74691V-60261CCI-001414If user packet-filtering intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP AFM module to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+Apply the AFM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks.If the BIG-IP Core does not perform packet-filtering intermediary services for virtual servers, this is not applicable.
+
+When packet-filtering intermediary services are performed, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module is configured with an AFM policy to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Network Firewall" Enforcement is set to "Policy Rules..." and "Policy" is set to use an AFM policy to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.
+
+If the BIG-IP Core is not configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic, this is a finding.SRG-NET-000041-ALG-000022<GroupDescription></GroupDescription>F5BI-LT-000023The BIG-IP Core implementation must be configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to virtual servers.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the virtual servers ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. This requirement applies to network elements that have the concept of a user account and have the logon function residing on the network element.
+
+The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for network elements that can accommodate banners of 1300 characters:
+
+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
+
+By using this IS (which includes any device attached to this IS), you consent to the following conditions:
+
+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
+
+-At any time, the USG may inspect and seize data stored on this IS.
+
+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
+
+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
+
+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+This policy only applies to ALGs (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74693V-60263CCI-000048If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to the virtual servers.
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to the virtual servers.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to the virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an access policy to display the Standard Mandatory DoD-approved Notice and Consent Banner.
+
+If the BIG-IP Core is not configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to the virtual servers, this is a finding.SRG-NET-000042-ALG-000023<GroupDescription></GroupDescription>F5BI-LT-000025The BIG-IP Core implementation must be configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users accessing virtual servers acknowledge the usage conditions and take explicit actions to log on for further access.<VulnDiscussion>The banner must be acknowledged by the user prior to allowing the user access to virtual servers. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law.
+
+To establish acceptance of the application usage policy, a click-through banner at application logon is required. The network element must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60265SV-74695CCI-000050If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an access policy to retain the Standard Mandatory DoD-approved Notice and Consent Banner.
+
+If the BIG-IP Core is not configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access, this is a finding.SRG-NET-000043-ALG-000024<GroupDescription></GroupDescription>F5BI-LT-000027The BIG-IP Core implementation must be configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the publicly accessible network element ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. This requirement applies to network elements that have the concept of a user account and have the logon function residing on the network element.
+
+The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for network elements that can accommodate banners of 1300 characters:
+
+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
+
+By using this IS (which includes any device attached to this IS), you consent to the following conditions:
+
+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
+
+-At any time, the USG may inspect and seize data stored on this IS.
+
+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
+
+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
+
+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."
+
+Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
+
+"I've read & consent to terms in IS user agreem't."
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services off-loaded from the application. Publicly accessed systems are used in DoD to provide benefit information, pay information, or public services. There may also be self-registration and authorization services provided by these gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60267SV-74697CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the APM module to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an access policy to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.
+
+If the BIG-IP Core is not configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to the publicly accessible systems, this is a finding.SRG-NET-000053-ALG-000001<GroupDescription></GroupDescription>F5BI-LT-000029The BIG-IP Core implementation must be configured to limit the number of concurrent sessions to an organization-defined number for virtual servers.<VulnDiscussion>Network element management includes the ability to control the number of users and user sessions that utilize a network element. Limiting the number of current sessions per user is helpful in limiting risks related to DoS attacks.
+
+This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts.
+
+The organization-defined number of concurrent sessions must be the same as the requirements specified for the application for which it serves as intermediary.
+
+This policy only applies to application gateways/firewalls (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60269SV-74699CCI-000054If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure the appropriate Virtual Server(s) in the BIG-IP LTM module to limit concurrent sessions to the organization-defined number for virtual servers.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core limits the number of concurrent sessions to an organization-defined number for virtual servers.
+
+Review organizational Standard Operating Procedures (SOP) to ensure there is an organization-defined threshold for the maximum number of concurrent session for each application the BIG-IP Core serves as intermediary.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select a Virtual Server from the list to verify that the connection limit is set.
+
+Select "Advanced" for "Configuration".
+
+Review the following under the "Configuration" section.
+
+Verify that 'Connection Limit' is set to the organization-defined number of concurrent connections and not set to zero (0).
+
+Verify that "Connection Rate Limit" is set to the organization-defined number of concurrent connections per second and not set to zero (0).
+
+If the BIG-IP Core is not configured to limit the number of concurrent sessions to an organization-defined number or is set to zero (0) for virtual servers, this is a finding.SRG-NET-000061-ALG-000009<GroupDescription></GroupDescription>F5BI-LT-000031The BIG-IP Core implementation must be configured to monitor inbound traffic for remote access policy compliance when accepting connections to virtual servers.<VulnDiscussion>Automated monitoring of remote access traffic allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by inspecting connection activities of remote access capabilities.
+
+A remote access policy establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed prior to allowing connections to the information systems.
+
+Remote access methods include both unencrypted and encrypted traffic (e.g., web portals, web content filter, TLS, and webmail). With inbound TLS inspection, the traffic must be inspected prior to being allowed on the enclave's web servers hosting TLS or HTTPS applications. With outbound traffic inspection, traffic must be inspected prior to being forwarded to destinations outside of the enclave, such as external email traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60271SV-74701CCI-000067If intermediary services for remote access communications traffic are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to monitor inbound traffic for remote access policy compliance.
+
+Apply policy to the applicable Virtual Server(s) in the BIG-IP LTM module to monitor inbound traffic for remote access policy compliance when accepting connections to virtual servers.If the BIG-IP Core does not serve as an intermediary for remote access traffic (e.g., web content filter, TLS, and webmail) for virtual servers, this is not applicable.
+
+When intermediary services for remote access communications traffic are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to inspect traffic or forward to a monitoring device for inspection prior to forwarding to inbound destinations.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to monitor inbound traffic for remote access policy compliance when accepting remote access connections to virtual servers.
+
+If the BIG-IP Core is not configured to monitor inbound traffic for compliance with remote access security policies, this is a finding.SRG-NET-000062-ALG-000011<GroupDescription></GroupDescription>F5BI-LT-000033The BIG-IP Core implementation must be configured to use encryption services that implement NIST SP 800-52 Revision 2 compliant cryptography to protect the confidentiality of connections to virtual servers.<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies).
+
+Encryption provides a means to secure the remote connection so as to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of confidentiality. The encryption strength of the mechanism is selected based on the security categorization of the information.
+
+This requirement applies to ALGs providing remote access proxy services as part of their intermediary services (e.g., OWA or TLS gateway).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60273SV-74703CCI-000068If intermediary services for remote access communications traffic are provided, configure the BIG-IP Core to use encryption services that implement NIST SP 800-52 Revision 2 compliant cryptography to protect the confidentiality of connections to virtual servers.If the BIG-IP Core does not serve as an intermediary for remote access traffic (e.g., web content filter, TLS, and webmail) for virtual servers, this is not applicable.
+
+When intermediary services for remote access communications are provided, verify the BIG-IP Core is configured to use encryption services that implement NIST SP 800-52 Revision 2 compliant cryptography to protect the confidentiality of connections to virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> SSL >> Client
+
+Verify a profile exists that is FIPS compliant.
+
+Select FIPS-compliant profile.
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify the BIG-IP Core is configured to use a FIPS-compliant profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that FIPS-compliant profile is in the "Selected" area for "SSL Profile (Client)".
+
+If the BIG-IP Core is not configured to use encryption services that implement NIST SP 800-52 Revision 1 compliant cryptography to protect the confidentiality of connections to virtual servers, this is a finding.SRG-NET-000062-ALG-000150<GroupDescription></GroupDescription>F5BI-LT-000035The BIG-IP Core implementation must be configured to comply with the required TLS settings in NIST SP 800-52 Revision 1 for TLS services to virtual servers.<VulnDiscussion>NIST SP 800-52 Revision 1 provides guidance on using the most secure version and configuration of the TLS/SSL protocol. Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
+
+This requirement applies to TLS gateways (also known as SSL gateways) and is not applicable to VPN devices. Application protocols such as HTTPS and DNSSEC use TLS/SSL as the underlying security protocol and thus are in scope for this requirement. NIST SP 800-52 Revision 1 provides guidance.
+
+NIST SP 800-52 Revision 1 sets TLS version 1.1 as a minimum version, thus all versions of SSL are not allowed (including for client negotiation) either on DoD-only or on public facing servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60275SV-74705CCI-000068If intermediary services for TLS are provided, configure the BIG-IP Core to comply with applicable required TLS settings in NIST PUB SP 800-52 Revision 1.If the BIG-IP Core does not provide intermediary services for TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS) for virtual servers, this is not applicable.
+
+When intermediary services for TLS are provided, verify the BIG-IP Core is configured to implement the applicable required TLS settings in NIST PUB SP 800-52 Revision 1.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> SSL >> Client
+
+Verify a profile exists that is FIPS compliant.
+
+Select FIPS-compliant profile.
+
+Select "Advanced" next to "Configuration".
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify the BIG-IP Core is configured to use FIPS-compliant server profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that the FIPS-compliant profile is in the "Selected" area for "SSL Profile (Client)".
+
+If the BIG-IP Core is not configured to implement the applicable required TLS settings in NIST PUB SP 800-52 Revision 1, this is a finding.SRG-NET-000063-ALG-000012<GroupDescription></GroupDescription>F5BI-LT-000037The BIG-IP Core implementation must be configured to use NIST SP 800-52 Revision 1 compliant cryptography to protect the integrity of remote access sessions to virtual servers.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies).
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.
+
+This requirement applies to ALGs providing remote access proxy services as part of their intermediary services (e.g., OWA or TLS gateway).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74707V-60277CCI-001453If intermediary services for remote access communications traffic are provided, configure the BIG-IP Core to use NIST SP 800-52 Revision 1 compliant cryptography to protect the integrity of remote access sessions to virtual servers.If the BIG-IP Core does not serve as an intermediary for remote access traffic (e.g., web content filter, TLS gateways, and webmail proxy views) for virtual servers, this is not applicable.
+
+When intermediary services for remote access communication traffic are provided, verify the BIG-IP Core uses NIST SP 800-52 Revision 1 compliant cryptography to protect the integrity of remote access sessions to virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that a FIPS-compliant profile is in the "Selected" area for "SSL Profile (Client)" and "SSL Profile (Server)".
+
+If the BIG-IP Core is not configured to use NIST SP 800-52 Revision 1 compliant cryptography to protect the integrity of remote access sessions, this is a finding.SRG-NET-000098-ALG-000056<GroupDescription></GroupDescription>F5BI-LT-000055The BIG-IP Core implementation must be configured to protect audit information from unauthorized read access.<VulnDiscussion>Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured network element. Thus, it is imperative that the collected log data from the various network elements, as well as the auditing tools, be secured and can only be accessed by authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74709V-60279CCI-000162Configure the BIG-IP Core to protect audit information from unauthorized read access.Verify the BIG-IP Core is configured to protect audit information from unauthorized read access.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit information from unauthorized read access, this is a finding.SRG-NET-000099-ALG-000057<GroupDescription></GroupDescription>F5BI-LT-000057The BIG-IP Core implementation must be configured to protect audit information from unauthorized modification.<VulnDiscussion>If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
+
+To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized modification.
+
+This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions and limiting log data locations.
+
+Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
+
+This does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74711V-60281CCI-000163Configure the BIG-IP Core to protect audit information from unauthorized modification.Verify the BIG-IP Core is configured to protect audit information from unauthorized modification.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit information from unauthorized modification, this is a finding.SRG-NET-000100-ALG-000058<GroupDescription></GroupDescription>F5BI-LT-000059The BIG-IP Core implementation must be configured to protect audit information from unauthorized deletion.<VulnDiscussion>If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
+
+To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions, and limiting log data locations.
+
+Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
+
+This requirement does not apply to audit logs generated on behalf of the device itself (device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60283SV-74713CCI-000164Configure the BIG-IP Core to protect audit information from unauthorized deletion.Verify the BIG-IP Core is configured to protect audit information from unauthorized deletion.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit information from unauthorized deletion, this is a finding.SRG-NET-000101-ALG-000059<GroupDescription></GroupDescription>F5BI-LT-000061The BIG-IP Core implementation must be configured to protect audit tools from unauthorized access.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.
+
+Network elements providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools.
+
+Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
+
+This does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60285SV-74715CCI-001493Configure the BIG-IP Core to protect audit tools from unauthorized access.Verify the BIG-IP Core is configured to protect audit tools from unauthorized access.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit tools from unauthorized access, this is a finding.SRG-NET-000102-ALG-000060<GroupDescription></GroupDescription>F5BI-LT-000063The BIG-IP Core implementation must be configured to protect audit tools from unauthorized modification.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.
+
+Network elements providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification of audit tools.
+
+Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
+
+This does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60287SV-74717CCI-001494Configure the BIG-IP Core to protect audit tools from unauthorized modification.Verify the BIG-IP Core is configured to protect audit tools from unauthorized modification.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit tools from unauthorized modification, this is a finding.SRG-NET-000103-ALG-000061<GroupDescription></GroupDescription>F5BI-LT-000065The BIG-IP Core implementation must be configured to protect audit tools from unauthorized deletion.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.
+
+Network elements providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the deletion of audit tools.
+
+Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
+
+This does not apply to audit logs generated on behalf of the device itself (management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60289SV-74719CCI-001495Configure the BIG-IP Core to protect audit tools from unauthorized deletion.Verify the BIG-IP Core is configured to protect audit information from unauthorized read access.
+
+Navigate to the BIG-IP System manager >> System >> Logs >> Configuration >> Options.
+
+Under 'Log Access', verify unauthorized roles are set to 'Deny'.
+
+If the BIG-IP Core is not configured to protect audit information from unauthorized deletion, this is a finding.SRG-NET-000131-ALG-000085<GroupDescription></GroupDescription>F5BI-LT-000067The BIG-IP Core implementation must be configured so that only functions, ports, protocols, and/or services that are documented for the server/application for which the virtual servers are providing connectivity.<VulnDiscussion>Information systems are capable of providing a wide variety of functions (capabilities or processes) and services. Some of these functions and services are installed and enabled by default. The organization must determine which functions and services are required to perform the content filtering and other necessary core functionality for each component of the ALG. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+
+The primary function of an ALG is to provide application-specific content filtering and/or proxy services. The ALG application suite may integrate related content filtering and analysis services and tools (e.g., IPS, proxy, malware inspection, black/white lists). Some gateways may also include email scanning, decryption, caching, and DLP services. However, services and capabilities which are unrelated to this primary functionality must not be installed (e.g., DNS, email client or server, FTP server, or web server).
+
+Next Generation ALGs (NGFW) and Unified Threat Management (UTM) ALGs integrate functions which have been traditionally separated. These products integrate content filtering features to provide more granular policy filtering. There may be operational drawbacks to combining these services into one device. Another issue is that NGFW and UTM products vary greatly with no current definitive industry standard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60291SV-74721CCI-000381Configure Virtual Servers in the BIG-IP LTM module with only functions, ports, protocols, and/or services that are documented for the servers/applications for which the BIG-IP Core implementation is providing connectivity.Review the BIG-IP Core configuration to determine if functions, ports, protocols, and/or services not required for operation, or not related to BIG-IP Core functionality (e.g., DNS, email client or server, FTP server, or web server) are enabled.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Review the Virtual Service List and validate all ports listed in the "Service Port" column are documented for each virtual server and are required for operation.
+
+If unnecessary services and functions are enabled on the BIG-IP Core, this is a finding.
+
+If the BIG-IP Core implementation is configured with functions, ports, protocols, and/or services that are not documented for the server/application for which the virtual servers are providing connectivity, this is a finding.SRG-NET-000131-ALG-000086<GroupDescription></GroupDescription>F5BI-LT-000069The BIG-IP Core implementation must be configured to remove or disable any functions, ports, protocols, and/or services that are not documented as required.<VulnDiscussion>Unrelated or unneeded proxy services increase the attack vector and add excessive complexity to the securing of the ALG. Multiple application proxies can be installed on many ALGs. However, proxy types must be limited to related functions. At a minimum, the web and email gateway represent different security domains/trust levels. Organizations should also consider separation of gateways that service the DMZ and the trusted network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74723V-60293CCI-000381Configure Virtual Servers in the BIG-IP LTM module with only proxy services that are related to the purpose of the BIG-IP Core.Review the BIG-IP Core configuration to determine if application proxies are installed that are not related to the purpose of the gateway.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Review the Virtual Service List and validate there are only ports listed in the "Service Port" column that are providing proxy services related to the purpose of the BIG-IP Core.
+
+If the BIG-IP Core has unrelated or unneeded application proxy services installed, this is a finding.SRG-NET-000132-ALG-000087<GroupDescription></GroupDescription>F5BI-LT-000071The BIG-IP Core implementation must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocol, and Service Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types); organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+
+ALGs 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. DoD continually assesses the ports, protocols, and services that can be used for network communications. Some ports, protocols, or services have known exploits or security weaknesses. Network traffic using these ports, protocols, and services must be prohibited or restricted in accordance with DoD policy. The ALG is a key network element for preventing these non-compliant ports, protocols, and services from causing harm to DoD information systems.
+
+The network ALG must be configured to prevent or restrict the use of prohibited ports, protocols, and services throughout the network by filtering the network traffic and disallowing or redirecting traffic as necessary. Default and updated policy filters from the vendors will disallow older versions of protocols and applications and will address most known non-secure ports, protocols, and/or services. However, sources for further policy filters are the IAVMs and the PPSM requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60295SV-74725CCI-000382Configure Virtual Servers in the BIG-IP LTM module to use only ports, protocols, and/or services required for operation of the BIG-IP Core.Review the BIG-IP Core to verify the minimum ports, protocols, and services that are required for operation of the BIG-IP Core are configured.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Compare enabled ports, protocols, and/or services in the "Service Port" column with the PPSM and IAVM requirements.
+
+If the BIG-IP Core is configured with ports, protocols, and/or services that are not required for operations or restricted by the PPSM, this is a finding.SRG-NET-000138-ALG-000063<GroupDescription></GroupDescription>F5BI-LT-000073The BIG-IP Core implementation must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users) when connecting to virtual servers.<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
+Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses except the following:
+
+1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication.
+
+2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.
+
+This requirement applies to ALGs that provide user proxy services, including identification and authentication. This service must use the site's directory service (e.g., Active Directory). Directory services must not be installed onto the gateway.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74727V-60297CCI-000764If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users) when connecting to virtual servers.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify the BIG-IP Core is configured with an APM policy to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy to uniquely identify and authenticate organizational users when connecting to virtual servers.
+
+If the BIG-IP Core does not uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users), this is a finding.SRG-NET-000138-ALG-000088<GroupDescription></GroupDescription>F5BI-LT-000075The BIG-IP Core implementation must be configured with a pre-established trust relationship and mechanisms with appropriate authorities (e.g., Active Directory or authentication, authorization, and accounting (AAA) server) that validate user account access authorizations and privileges when providing access control to virtual servers.<VulnDiscussion>User account and privilege validation must be centralized in order to prevent unauthorized access using changed or revoked privileges.
+
+ALGs can implement functions such as traffic filtering, authentication, access, and authorization functions based on computer and user privileges. However, the directory service (e.g., Active Directory or LDAP) must not be installed on the ALG, particularly if the gateway resides on the untrusted zone of the Enclave.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74729V-60299CCI-000764If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges.
+
+Apply the APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to validate user account access authorizations and privileges when providing access control to virtual servers.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured an APM policy with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy that has been configured with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges.
+
+If the BIG-IP Core is not configured with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges, this is a finding.SRG-NET-000138-ALG-000089<GroupDescription></GroupDescription>F5BI-LT-000077The BIG-IP Core implementation providing user authentication intermediary services must restrict user authentication traffic to specific authentication server(s) when providing access control to virtual servers.<VulnDiscussion>User authentication can be used as part of the policy filtering rule sets. Some URLs or network resources can be restricted to authenticated users only. Users are prompted by the application or browser for credentials. Authentication service may be provided by the ALG as an intermediary for the application; however, the authentication credential must be stored in the site's directory services server.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., proxy capability). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60301SV-74731CCI-000764If user authentication intermediary services are provided, configure the BIG-IP Core to use a specific authentication server(s) as follows:
+
+Configure a policy in the BIG-IP APM module to use authentication for network access to non-privileged accounts.
+
+Apply the APM policy to the applicable Virtual Server(s) in BIG-IP LTM module to restrict user authentication traffic to specific authentication server(s) when providing access control to virtual servers.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to use a specific authentication server(s).
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to use an APM access policy that has been configured with a pre-established trust relationship and mechanisms with appropriate authorities that validate each user access authorization and privileges.
+
+If the BIG-IP Core provides user authentication intermediary services and does not restrict user authentication traffic to a specific authentication server(s), this is a finding.SRG-NET-000140-ALG-000094<GroupDescription></GroupDescription>F5BI-LT-000079The BIG-IP Core implementation providing user authentication intermediary services must use multifactor authentication for network access to non-privileged accounts when granting access to virtual servers.<VulnDiscussion>To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
+
+Multifactor authentication uses two or more factors to achieve authentication. Factors include:
+
+1) Something you know (e.g., password/PIN);
+2) Something you have (e.g., cryptographic, identification device, token); and
+3) Something you are (e.g., biometric).
+
+Non-privileged accounts are not authorized on the network element regardless of configuration.
+
+Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection.
+
+The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
+
+This requirement applies to ALGs that provide user authentication intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60303SV-74733CCI-000766If user authentication intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to use multifactor authentication for network access to non-privileged accounts.
+
+Apply APM policy to the applicable Virtual Server(s) in BIG-IP LTM module to use multifactor authentication for network access to non-privileged accounts when granting access to virtual servers.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to use multifactor authentication for network access to non-privileged accounts.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy that uses multifactor authentication for network access to non-privileged accounts when granting access to virtual servers.
+
+If the BIG-IP Core provides user authentication intermediary services and does not use multifactor authentication for network access to non-privileged accounts, this is a finding.SRG-NET-000164-ALG-000100<GroupDescription></GroupDescription>F5BI-LT-000083The BIG-IP Core implementation must be configured to validate certificates used for TLS functions for connections to virtual servers by constructing a certification path (which includes status information) to an accepted trust anchor.<VulnDiscussion>A trust anchor is an authoritative entity represented via a public key. Within a chain of trust, the top entity to be trusted is the "root certificate" or "trust anchor" such as a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted.
+
+Deploying the ALG with TLS enabled may require the CA certificates for each proxy to be used for TLS traffic decryption/encryption. The installation of these certificates in each trusted root certificate store is used by proxied applications and browsers on each client.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74735V-60305CCI-000185If intermediary services for TLS are provided, configure the BIG-IP Core to validate certificates used for TLS functions by constructing a certification path with status information to an accepted trust anchor.If the BIG-IP Core does not provide intermediary services for TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS) for virtual servers, this is not applicable.
+
+When intermediary services for TLS are provided, verify the BIG-IP Core is configured to validate certificates used for TLS functions by constructing a certification path to an accepted trust anchor.
+
+Navigate to the BIG-IP System manager >> Local traffic >> Profiles >> SSL >> Server.
+
+Select a FIPS-compliant profile.
+
+Review the configuration under "Server Authentication" section.
+
+Verify "Server Certificate" is set to "Required".
+
+Verify "Trusted Certificate Authorities" is set to a DoD-approved CA bundle.
+
+If the BIG-IP Core is not configured to validate certificates used for TLS functions by constructing a certification path to an accepted trust anchor, this is a finding.SRG-NET-000166-ALG-000101<GroupDescription></GroupDescription>F5BI-LT-000085The BIG-IP Core implementation providing PKI-based, user authentication intermediary services must be configured to map the authenticated identity to the user account for PKI-based authentication to virtual servers.<VulnDiscussion>Authorization for access to any network element requires an approved and assigned individual account identifier. To ensure only the assigned individual is using the account, the account must be bound to a user certificate when PKI-based authentication is implemented.
+
+This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74737V-60307CCI-000187If PKI-based, user authentication intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to map the authenticated identity to the user account for PKI-based authentication.
+
+Apply APM policy to the applicable Virtual Server(s) in BIG-IP LTM module to map the authenticated identity to the user account for PKI-based authentication to virtual servers.If the BIG-IP Core does not provide PKI-based, user authentication intermediary services for virtual servers, this is not applicable.
+
+When PKI-based, user authentication intermediary services are provided, verify the BIG-IP LTM module is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to map the authenticated identity to the user account for PKI-based authentication.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy that maps the authenticated identity to the user account for PKI-based authentication to virtual servers.
+
+If the BIG-IP Core does not map the authenticated identity to the user account for PKI-based authentication, this is a finding.SRG-NET-000169-ALG-000102<GroupDescription></GroupDescription>F5BI-LT-000087The BIG-IP Core implementation must be configured to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.<VulnDiscussion>Lack of authentication enables anyone to gain access to the network or possibly a network element that provides opportunity for intruders to compromise resources within the network infrastructure. By identifying and authenticating non-organizational users, their access to network resources can be restricted accordingly.
+
+Non-organizational users will be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access. Authorization requires an individual account identifier that has been approved, assigned, and configured on an authentication server. Authentication of user identities is accomplished through the use of passwords, tokens, biometrics, or in the case of multifactor authentication, some combination thereof.
+
+This control applies to application layer gateways that provide content filtering and proxy services on network segments (e.g., DMZ) that allow access by non-organizational users. This requirement focuses on authentication requests to the proxied application for access to destination resources and policy filtering decisions rather than administrator and management functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60309SV-74739CCI-000804If user authentication intermediary services are provided, configure BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
+
+Apply APM policy to the applicable Virtual Server(s) in BIG-IP LTM module to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, review the BIG-IP LTM module authentication functions to verify identification and authentication are required for non-organizational users.
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+If the BIG-IP Core does not uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers, this is a finding.SRG-NET-000213-ALG-000107<GroupDescription></GroupDescription>F5BI-LT-000093The BIG-IP Core implementation must terminate all communications sessions at the end of the session or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity, and for user sessions (nonprivileged sessions), the session must be terminated after 15 minutes of inactivity.<VulnDiscussion>Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.
+
+Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating networking assignments at the application level if multiple application sessions are using a single operating system level network connection.
+
+ALGs may provide session control functionality as part of content filtering, load balancing, or proxy services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60311SV-74741CCI-001133CCI-000057Configure BIG-IP Core to terminate all communications sessions at the end of the session or as follows:
+
+- For in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity.
+- For user sessions (nonprivileged sessions), the session must be terminated after 15 minutes of inactivity.Verify the BIG-IP Core is configured to terminate all communications at the end of the session as follows:
+
+Verify a Protocol Profile is configured to terminate a session at the end of a specified time.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> Protocol >> TCP.
+
+Select a profile for an in-band managed session.
+
+Verify the TCP profile "idle-timeout" is set to 600/900 seconds.
+
+Select a profile for a user session.
+
+Verify the TCP profile "idle-timeout" is set to 600/900 seconds.
+
+Verify the BIG-IP LTM is configured to use the Protocol Profile.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select the appropriate virtual server.
+
+Verify the TCP profile "idle-timeout" is set to 600/900 seconds.
+
+If the BIG-IP Core is not configured to terminate all communications session at the end of the session or as follows, this is a finding:
+
+- For in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity.
+- For user sessions (nonprivileged sessions), the session must be terminated after 15 minutes of inactivity.SRG-NET-000230-ALG-000113<GroupDescription></GroupDescription>F5BI-LT-000097The BIG-IP Core implementation must be configured to protect the authenticity of communications sessions.<VulnDiscussion>Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
+
+This requirement focuses on communications protection for the application session rather than for the network packet and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Depending on the required degree of confidentiality and integrity, web services/SOA will require the use of TLS/TLS mutual authentication (two-way/bidirectional).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60313SV-74743CCI-001184Configure BIG-IP Core to protect the authenticity of communications sessions.Verify the BIG-IP Core is configured to protect the authenticity of communications sessions.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> SSL >> Client
+
+Verify a profile exists that is FIPS compliant.
+
+Select FIPS-compliant profile.
+
+Select "Advanced" next to "Configuration".
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify the BIG-IP Core is configured to use FIPS-compliant profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Server(s) from the list that the LTM module is managing the Client SSL side traffic.
+
+Verify under "Configuration" section, that FIPS-compliant profile is in the "Selected" area for "SSL Profile (Client)".
+
+If the BIG-IP Core is not configured to protect the authenticity of communications sessions, this is a finding.SRG-NET-000313-ALG-000010<GroupDescription></GroupDescription>F5BI-LT-000153The BIG-IP Core implementation providing intermediary services for remote access communications traffic must control remote access methods to virtual servers.<VulnDiscussion>Remote access devices, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies).
+
+This requirement applies to ALGs providing remote access proxy services as part of its intermediary services (e.g., OWA or TLS gateway). ALGs that proxy remote access must be capable of taking enforcement action (i.e., blocking, restricting, or forwarding to an enforcement mechanism) if traffic monitoring reveals unauthorized activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60325SV-74755CCI-002314If intermediary services for remote access communications traffic are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to control remote access methods.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to control remote access methods to virtual servers.If the BIG-IP Core does not serve as an intermediary for remote access traffic (e.g., web content filter, TLS, and webmail) for virtual servers, this is not applicable.
+
+When intermediary services for remote access communications are provided, verify the BIG-IP Core is configured to control remote access methods.
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to control remote access methods.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to use an APM access policy that controls remote access methods to virtual servers.
+
+If the BIG-IP Core does not control remote access methods, this is a finding.SRG-NET-000318-ALG-000014<GroupDescription></GroupDescription>F5BI-LT-000157To protect against data mining, the BIG-IP Core implementation must be configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections.
+
+Compliance requires the ALG to have the capability to prevent code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60327SV-74757CCI-002346If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.
+
+If the BIG-IP Core is not configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.SRG-NET-000318-ALG-000151<GroupDescription></GroupDescription>F5BI-LT-000159To protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections.
+
+Compliance requires the ALG to have the capability to prevent code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60329SV-74759CCI-002346If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs, and application code and application.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.
+
+If the BIG-IP Core is not configured to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code, this is a finding.SRG-NET-000318-ALG-000152<GroupDescription></GroupDescription>F5BI-LT-000161To protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information.
+
+SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server.
+
+Compliance requires the ALG to have the capability to prevent SQL code injections. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74761V-60331CCI-002346If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Apply a policy to the applicable Virtual Server(s) in BIG-IP LTM module that was configured in the ASM module to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+If the BIG-IP Core is not configured to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.SRG-NET-000319-ALG-000015<GroupDescription></GroupDescription>F5BI-LT-000163To protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to detect code injection attacks being launched against data storage objects.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational databases may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections.
+
+ALGs with anomaly detection must be configured to protect against unauthorized code injections. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60333SV-74763CCI-002347If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to detect code injection attacks being launched against data storage objects.
+
+Apply a policy to the applicable Virtual Server(s) in BIG-IP LTM module that was configured in the ASM module to detect code injection attacks being launched against data storage objects.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to detect code injection attacks being launched against data storage objects.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to detect code injection attacks being launched against data storage objects.
+
+If the BIG-IP Core is not configured to detect code injection attacks being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.SRG-NET-000319-ALG-000020<GroupDescription></GroupDescription>F5BI-LT-000165To protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational databases may result in the compromise of information.
+
+SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server.
+
+ALGs with anomaly detection must be configured to protect against unauthorized data mining attacks. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74765V-60335CCI-002347If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.
+
+If the BIG-IP Core is not configured to detect SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.SRG-NET-000319-ALG-000153<GroupDescription></GroupDescription>F5BI-LT-000167The BIG-IP Core implementation must be configured to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code, when providing content filtering to virtual servers.<VulnDiscussion>Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to detect attacks launched against organizational applications may result in the compromise of information.
+
+Injection attacks allow an attacker to inject code into a program or query or inject malware into a computer to execute remote commands that can read or modify a database or change data on a website. These attacks include buffer overrun, XML, JavaScript, and HTML injections.
+
+ALGs with anomaly detection must be configured to protect against unauthorized code injections. These devices must include rules and anomaly detection algorithms to monitor for atypical database queries or accesses. Examples include Web Application Firewalls (WAFs) or database application gateways.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74767V-60337CCI-002347If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code, when providing content filtering to virtual servers.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code, when providing content filtering to virtual servers.
+
+If the BIG-IP Core is not configured to detect code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code, this is a finding.SRG-NET-000337-ALG-000096<GroupDescription></GroupDescription>F5BI-LT-000191The BIG-IP Core implementation must require users to reauthenticate when the user's role, the information authorizations, and/or the maximum session timeout is exceeded for the virtual server(s).<VulnDiscussion>Without reauthentication, users may access resources or perform tasks for which authorization has been removed.
+
+In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations. Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation, idle timeout, maximum session timeout, and/or role changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74769V-60339CCI-002038If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to reauthenticate when the user's role, the information authorizations, and/or the maximum session timeout is exceeded for the virtual server(s).
+
+Apply APM policy to the applicable virtual server(s) in the BIG-IP LTM module.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to require users to reauthenticate when required by organization-defined circumstances or situations.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to use an APM access policy that requires users to reauthenticate to virtual servers when the user's role, the information authorizations, and/or the maximum session timeout is exceeded for the virtual server(s).
+
+If the BIG-IP Core is not configured to require users to reauthenticate when the user's role, the information authorizations, and/or the maximum session timeout is exceeded for the virtual server(s), this is a finding.SRG-NET-000339-ALG-000090<GroupDescription></GroupDescription>F5BI-LT-000193A BIG-IP Core implementation providing user authentication intermediary services must be configured to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.<VulnDiscussion>For remote access to non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+An example of compliance with this requirement is the use of a one-time password token and PIN coupled with a password; or the use of a CAC/PIV card and PIN coupled with a password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60341SV-74771CCI-001951If user authentication intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to use an APM access policy to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+If the BIG-IP Core does not implement multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access, this is a finding.SRG-NET-000340-ALG-000091<GroupDescription></GroupDescription>F5BI-LT-000195The BIG-IP Core implementation providing user authentication intermediary services must be configured to require multifactor authentication for remote access with privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.<VulnDiscussion>For remote access to privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60343SV-74773CCI-001948If user authentication intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to require multifactor authentication for remote access with privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to require multifactor authentication for remote access with privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to require multifactor authentication for remote access with privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy to require multifactor authentication for remote access with privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.
+
+If the BIG-IP Core does not 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, this is a finding.SRG-NET-000345-ALG-000099<GroupDescription></GroupDescription>F5BI-LT-000203The BIG-IP Core implementation must be configured to deny-by-default all PKI-based authentication to virtual servers supporting path discovery and validation if unable to access revocation information via the network.<VulnDiscussion>When revocation data is unavailable from the network, the system should be configured to deny-by-default to mitigate the risk of a user with a revoked certificate gaining unauthorized access. Local cached revocation data can be out of date or not able to be installed on the local system, which increases administration burden for the system.
+
+
+The intent of this requirement is to deny unauthenticated users access to virtual servers in case access to OCSP (required by CCI-000185) is not available.
+
+This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60349SV-74779CCI-001991If user access control intermediary services are provided, configure the BIG-IP Core to deny-by-default when access to revocation information via the network is inaccessible.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured to deny-by-default user access when revocation information is not accessible via the network.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> SSL >> Client.
+
+Select an SSL client profile that is used for client authentication with Virtual Server(s).
+
+Review the configuration under the "Client Authentication" section.
+
+Verify that "Client Certificate" is set to "require" if not using the APM.
+
+Verify that “On Demand Cert Auth” in the access profile is set to “Require” if using APM.
+
+If the BIG-IP Core is not configured to deny-by-default when unable to access revocation information via the network, this is a finding.
+SRG-NET-000349-ALG-000106<GroupDescription></GroupDescription>F5BI-LT-000211The BIG-IP Core implementation must be able to conform to FICAM-issued profiles when providing authentication to virtual servers.<VulnDiscussion>Without conforming to Federal Identity, Credential, and Access Management (FICAM)-issued profiles, the information system may not be interoperable with FICAM-authentication protocols, such as SAML 2.0 and OpenID 2.0.
+
+Use of FICAM-issued profiles addresses open identity management standards.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of a non-organizational user, (e.g., ALG capability that is the front end for an application in a DMZ).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60357SV-74787CCI-002014If user authentication intermediary services are provided, configure BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to conform to FICAM-issued profiles when providing authentication.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to conform to FICAM-issued profiles when providing authentication to virtual servers.If the BIG-IP Core does not provide user authentication intermediary services for virtual servers, this is not applicable.
+
+When user authentication intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to conform to FICAM-issued profiles when providing authentication.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to conform to FICAM-issued profiles when providing authentication to pools/nodes.
+
+If the BIG-IP Core is not configured to conform to FICAM-issued profiles, this is a finding.SRG-NET-000355-ALG-000117<GroupDescription></GroupDescription>F5BI-LT-000213The F5 BIG-IP appliance providing user authentication intermediary services must only accept end entity certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs) for the establishment of protected sessions.<VulnDiscussion>Non-DOD approved PKIs have not been evaluated to ensure that they have security controls and identity vetting procedures in place that are sufficient for DOD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable adversaries to impersonate legitimate users.
+
+The authoritative list of DOD-approved PKIs is published at https://cyber.mil/pki-pke/interoperability. DOD-approved PKI CAs may include Category I, II, and III certificates. Category I DOD-Approved External PKIs are PIV issuers. Category II DOD-Approved External PKIs are Non-Federal Agency PKIs cross-certified with the Federal Bridge Certification Authority (FBCA). Category III DOD-Approved External PKIs are Foreign, Allied, or Coalition Partner PKIs.
+
+This requirement focuses on communications protection for the application session rather than for the network packet. Thus, a critical part of the PKI configuration for BIG-IP appliances includes requiring mutual TLS (mTLS). Use of mTLS ensures session nonrepudiation, communication integrity, and confidentiality. This approach substantially reduces the likelihood of successful server-side exploits and cookie hijacking. In the Client Authentication section of the Client SSL Profile applied to the pertinent Virtual Server, the Client Certificate configuration session must be altered from "request/ignore" to "require". This modification mandates all connecting clients to furnish a Client Certificate issued from a credible source. If a client fails to comply with this requirement, they will be issued a TCP reset.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74789V-60359CCI-002470Update the Client SSL Profile.
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Profiles.
+3. SSL.
+4. Client.
+5. Click on the Name of the SSL Profile.
+6. Change "Configuration" to "Advanced".
+7. Under "Client Authentication", configure a DOD PKI certificate or bundle for "Trusted Certificate Authorities".
+8. Change the Client Certificate configuration setting to "require".
+9. Set the frequency to "always".
+10. Click "Update".
+11. Repeat for other SSL Profiles in use.
+
+Update the Virtual Server.
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Virtual Servers.
+3. Virtual Server List.
+4. Click the name of the Virtual Server.
+5. Configure "SSL Profile (Client)" to use an SSL profile that uses a DOD PKI certificate or bundle for "Trusted Certificate Authorities".
+6. Click "Update".
+7. Repeat for other Virtual Servers.If the BIG-IP appliance does not provide PKI-based user authentication intermediary services, this is not applicable.
+
+Client SSL Profile:
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Profiles.
+3. SSL.
+4. Client.
+5. Click the name of the client SSL profile.
+6. Change "Configuration" to "Advanced".
+7. Under "Client Authentication", verify a DOD PKI certificate or bundle is used for "Trusted Certificate Authorities".
+8. Verify the Client Certificate configuration setting is set to "require" and frequency is set to "always".
+
+Virtual Server:
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Virtual Servers.
+3. Virtual Server List.
+4. Click the name of the Virtual Server.
+5. Verify that "SSL Profile (Client)" is using an SSL profile that uses a DOD PKI certificate or bundle for "Trusted Certificate Authorities".
+6. Repeat for other Virtual Servers.
+
+If the BIG-IP appliance accepts non-DOD approved PKI end entity certificates, this is a finding.SRG-NET-000362-ALG-000112<GroupDescription></GroupDescription>F5BI-LT-000215The BIG-IP Core implementation must be configured to protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis when providing content filtering to virtual servers.<VulnDiscussion>If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users.
+
+Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume/type.
+
+Detection components that use rate-based behavior analysis can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks, which are new attacks for which vendors have not yet developed signatures. Rate-based behavior analysis can detect sophisticated, Distributed DoS (DDoS) attacks by correlating traffic information from multiple network segments or components.
+
+This requirement applies to the functionality of the ALG as it pertains to handling communications traffic rather than to the ALG device itself.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60361SV-74791CCI-002385If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core to protect against or limit the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with a security policy to protect against or limit the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "DoS Protection Profile" is Enabled and "Profile" is set to use locally configured DoS protection Profile.
+
+Verify the DoS protection profile that is set for the Virtual Server is set to employ rate-based attack prevention:
+
+Navigate to the BIG-IP System manager >> Security >> DoS Protection >> DoS Profiles.
+
+Select the DoS Protection Profile set for the Virtual Server.
+
+Verify that "Application Security" is Enabled under "General Configuration".
+
+Verify that the following are selected for "Prevention Policy" under TPS-base Anomaly in accordance with the organization requirements:
+
+"Source IP-Based Client Side Integrity Defense"
+"URL-Based Client Side Integrity Defense"
+"Site-wide" Client-Side Integrity Defense"
+"Source IP-Base Rate Limiting"
+"URL-Based Rate Limiting"
+"Site-wide Rate Limiting"
+
+Verify the Criteria for each of the selected Prevention Policies is set in accordance with organization requirements.
+
+If the BIG-IP Core is not configured to protect against or limit the effects of known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis, this is a finding.SRG-NET-000362-ALG-000120<GroupDescription></GroupDescription>F5BI-LT-000217The BIG-IP Core implementation must be configured to implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks to virtual servers.<VulnDiscussion>If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Load balancing provides service redundancy; which service redundancy reduces the susceptibility of the ALG to many DoS attacks.
+
+The ALG must be configured to prevent or mitigate the impact on network availability and traffic flow of DoS attacks that have occurred or are ongoing.
+
+This requirement applies to the functionality of the device as it pertains to handling network traffic. Some types of attacks may be specialized to certain network technologies, functions, or services. For each technology, known and potential DoS attacks must be identified and solutions for each type implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60363SV-74793CCI-002385Configure the BIG-IP Core to implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
+
+Navigate to the BIG-IP System manager >> System >> Configuration >> Local Traffic >> General.
+
+Make the following configurations under "Properties".
+
+Set "Reaper High-water Mark" to 95.
+
+Set "Reaper Low-water Mark" to 85.Verify the BIG-IP Core implements load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
+
+Navigate to the BIG-IP System manager >> System >> Configuration >> Local Traffic >> General.
+
+Verify "Reaper High-water Mark" is set to 95 and "Reaper Low-water Mark" is set to 85.
+
+If the device does not implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks, this is a finding.SRG-NET-000362-ALG-000126<GroupDescription></GroupDescription>F5BI-LT-000219The BIG-IP Core implementation must be configured to protect against known types of Denial of Service (DoS) attacks by employing signatures when providing content filtering to virtual servers.<VulnDiscussion> If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users.
+
+Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume, type, or protocol usage.
+
+Detection components that use signatures can detect known attacks by using known attack signatures. Signatures are usually obtained from and updated by the ALG component vendor.
+
+This requirement applies to the communications traffic functionality of the ALG as it pertains to handling communications traffic rather than to the ALG device itself.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74795V-60365CCI-002385If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core to protect against or limit the effects of known types of DoS attacks by employing signatures.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured to protect against known types of DoS attacks by employing signatures.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "DoS Protection Profile" is Enabled and "Profile" is set to use locally configured DoS protection Profile.
+
+If the BIG-IP Core does not protect against known types of DoS attacks by employing signatures, this is a finding.SRG-NET-000362-ALG-000155<GroupDescription></GroupDescription>F5BI-LT-000221The BIG-IP Core implementation must be configured to protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors when providing content filtering to virtual servers.<VulnDiscussion>If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users.
+
+Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks.
+
+Detection components that use pattern recognition pre-processors can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks, which are new attacks for which vendors have not yet developed signatures.
+
+This requirement applies to the communications traffic functionality of the ALG as it pertains to handling communications traffic, rather than to the ALG device itself.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60367SV-74797CCI-002385If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to protect against or limit the effects of known and unknown types of DoS attacks by employing pattern recognition pre-processors.
+
+Apply ASM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to protect against or limit the effects of known and unknown types of DoS attacks by employing pattern recognition pre-processors when providing content filtering to virtual servers.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core protects against or limits the effects of known and unknown types of DoS attacks by employing pattern recognition pre-processors.
+
+Verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors when providing content filtering to virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "DoS Protection Profile" is Enabled and "Profile" is set to use a locally configured DoS protection Profile.
+
+Verify the DoS protection profile that is set for the Virtual Server is set to employ pattern recognition pre-processors:
+
+Navigate to the BIG-IP System manager >> Security >> DoS Protection >> DoS Profiles.
+
+Select the DoS Protection Profile set for the Virtual Server.
+
+Verify that "Application Security" is Enabled under "General Configuration".
+
+Verify that the following are selected for "Prevention Policy" under TPS-base Anomaly in accordance with the organization requirements:
+
+"Source IP-Based Client Side Integrity Defense"
+"URL-Based Client Side Integrity Defense"
+"Site-wide" Client-Side Integrity Defense"
+
+Verify the Criteria for each of the selected Prevention Policies is set in accordance with organization requirements.
+
+If the BIG-IP Core is not configured to protect against or limit the effects of known and unknown types of DoS attacks by employing pattern recognition pre-processors, this is a finding.SRG-NET-000364-ALG-000122<GroupDescription></GroupDescription>F5BI-LT-000223The BIG-IP Core implementation must be configured to only allow incoming communications from authorized sources routed to authorized destinations.<VulnDiscussion>Unrestricted traffic may contain malicious traffic that poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth and other resources.
+
+Access control policies and access control lists implemented on devices that control the flow of network traffic (e.g., application-level firewalls and Web content filters), ensure the flow of traffic is only allowed from authorized sources to authorized destinations. Networks with different levels of trust (e.g., the Internet or CDS) must be kept separate.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74799V-60369CCI-002403If user packet-filtering intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP AFM module to only allow incoming communications from authorized sources routed to authorized destinations.
+
+Apply the AFM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to only allow incoming communications from authorized sources routed to authorized destinations.If the BIG-IP Core does not perform packet-filtering intermediary services for virtual servers, this is not applicable.
+
+When packet-filtering intermediary services are performed, verify the BIG-IP Core is configured to only allow incoming communications from authorized sources routed to authorized destinations as follows:
+
+Verify Virtual Server(s) are configured in the BIG-IP LTM module with policies to only allow incoming communications from authorized sources routed to authorized destinations.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Network Firewall" Enforcement is set to "Policy Rules..." and "Policy" is set to use an AFM policy to only allow incoming communications from authorized sources routed to authorized destinations.
+
+If the BIG-IP Core is configured to allow incoming communications from unauthorized sources routed to unauthorized destinations, this is a finding.SRG-NET-000380-ALG-000128<GroupDescription></GroupDescription>F5BI-LT-000229The BIG-IP Core implementation must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.<VulnDiscussion>A common vulnerability of network elements is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
+
+The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher-layer proxy functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74801V-60371CCI-002754Configure the BIG-IP Core to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.Verify the BIG-IP Core is configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.
+
+This can be demonstrated by the SA sending an invalid input to a virtual server. Provide evidence that the virtual server was able to handle the invalid input and maintain operation.
+
+If the BIG-IP Core is not configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives, this is a finding.SRG-NET-000390-ALG-000139<GroupDescription></GroupDescription>F5BI-LT-000239The BIG-IP Core implementation must continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.<VulnDiscussion>If inbound communications traffic is not continuously monitored, hostile activity may not be detected and prevented. Output from application and traffic monitoring serves as input to continuous monitoring and incident response programs.
+
+Internal monitoring includes the observation of events occurring on the network crossing internal boundaries at managed interfaces such as web content filters. Depending on the type of ALG, organizations can monitor information systems by monitoring audit activities, application access patterns, characteristics of access, content filtering, or unauthorized exporting of information across boundaries. Unusual/unauthorized activities or conditions may include large file transfers, long-time persistent connections, unusual protocols and ports in use, and attempted communications with suspected malicious external addresses.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60373SV-74803CCI-002661If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.If the BIG-IP Core does not perform content filtering as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content filtering is performed as part of the traffic management functionality, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.
+
+If the BIG-IP Core is not configured to continuously monitor inbound communications traffic for unusual or unauthorized activities or conditions, this is a finding.SRG-NET-000401-ALG-000127<GroupDescription></GroupDescription>F5BI-LT-000261The BIG-IP Core implementation must be configured to check the validity of all data inputs except those specifically identified by the organization.<VulnDiscussion>Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior potentially leading to an application or information system compromise. Invalid input is one of the primary methods employed when attempting to compromise an application.
+
+Network devices with the functionality to perform application layer inspection may be leveraged to validate data content of network communications. Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software typically follows well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If network elements use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Pre-screening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks such as cross-site scripting and a variety of injection attacks.
+
+This requirement applies to gateways and firewalls that perform content inspection or have higher-layer proxy functionality.
+
+Note: A limitation of ~200 policies per cluster currently exists on the BIG-IP Core. If this requirement cannot be met due to this limitation, documentation from the AO is required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60375SV-74805CCI-001310If the BIG-IP Core performs content inspection as part of the traffic management functionality, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP ASM module to check the validity of all data inputs except those specifically identified by the organization.
+
+Apply ASM policy to the applicable Virtual Server(s) in BIG-IP LTM module to check the validity of all data inputs except those specifically identified by the organization.If the BIG-IP Core does not perform content inspection as part of the traffic management functionality for virtual servers, this is not applicable.
+
+When content inspection is performed as part of the traffic management functionality, verify the BIG-IP Core is configured to check the validity of all data inputs except those specifically identified by the organization.
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an ASM policy to check the validity of all data inputs except those specifically identified by the organization.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Navigate to the Security >> Policies tab.
+
+Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy to check the validity of all data inputs except those specifically identified by the organization.
+
+If the BIG-IP Core is not configured to check the validity of all data inputs except those specifically identified by the organization, this is a finding.SRG-NET-000510-ALG-000025<GroupDescription></GroupDescription>F5BI-LT-000291The BIG-IP Core implementation must be configured to implement NIST FIPS-validated cryptography to generate cryptographic hashes when providing encryption traffic to virtual servers.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
+
+This requirement applies only to ALGs that provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74807V-60377CCI-002450If encryption intermediary services are provided, configure the BIG-IP Core to implement NIST FIPS-validated cryptography to generate cryptographic hashes.If the BIG-IP Core does not provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC) for virtual servers, this is not applicable.
+
+When encryption intermediary services are provided, verify the BIG-IP Core is configured to implement NIST FIPS-validated cryptography to generate cryptographic hashes.
+
+Navigate to the BIG-IP System manager >> Local traffic >> Profiles >> SSL >> Client.
+
+Verify a profile exists that is FIPS Compliant.
+
+Select a FIPS-compliant profile.
+
+Select "Advanced" next to "Configuration".
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify applicable virtual servers are configured in the BIG-IP LTM to use a FIPS-compliant client profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that a FIPS-compliant profile is in the "Selected" area of "SSL Profile (Client)".
+
+If the BIG-IP Core is not configured to implement NIST FIPS-validated cryptography to generate cryptographic hashes, this is a finding.SRG-NET-000510-ALG-000040<GroupDescription></GroupDescription>F5BI-LT-000293The BIG-IP Core implementation must be configured to implement NIST FIPS-validated cryptography for digital signatures when providing encrypted traffic to virtual servers.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
+
+This requirement applies only to ALGs that provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60379SV-74809CCI-002450If encryption intermediary services are provided, configure the BIG-IP Core to implement NIST FIPS-validated cryptography for digital signatures.If the BIG-IP Core does not provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC) for virtual servers, this is not applicable.
+
+When encryption intermediary services are provided, verify the BIG-IP Core is configured to implement NIST FIPS-validated cryptography for digital signatures.
+
+Navigate to the BIG-IP System manager >> Local traffic >> Profiles >> SSL >> Client.
+
+Verify a profile exists that is FIPS Compliant.
+
+Select a FIPS-compliant profile.
+
+Select "Advanced" next to "Configuration".
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify applicable virtual servers are configured in the BIG-IP LTM to use a FIPS-compliant client profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that a FIPS-compliant profile is in the "Selected" area of "SSL Profile (Client)".
+
+If the BIG-IP Core does not implement NIST FIPS-validated cryptography for digital signatures, this is a finding.SRG-NET-000510-ALG-000111<GroupDescription></GroupDescription>F5BI-LT-000295The BIG-IP Core implementation must be configured to use NIST FIPS-validated cryptography to implement encryption services when providing encrypted traffic to virtual servers.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
+
+This requirement applies only to ALGs that provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74811V-60381CCI-002450If encryption intermediary services are provided, configure the BIG-IP Core to use NIST FIPS-validated cryptography to implement encryption services.If the BIG-IP Core does not provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC) for virtual servers, this is not applicable.
+
+When encryption intermediary services are provided, verify the BIG-IP Core is configured to use NIST FIPS-validated cryptography to implement encryption services.
+
+Navigate to the BIG-IP System manager >> Local traffic >> Profiles >> SSL >> Client.
+
+Verify a profile exists that is FIPS Compliant.
+
+Select a FIPS-compliant profile.
+
+Select "Advanced" next to "Configuration".
+
+Verify "Ciphers" under "Configuration" section is configured to use FIPS-compliant ciphers.
+
+Verify applicable virtual servers are configured in the BIG-IP LTM to use a FIPS-compliant client profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Configuration" section, that a FIPS-compliant profile is in the "Selected" area of "SSL Profile (Client)".
+
+If the BIG-IP Core is not configured to use NIST FIPS-validated cryptography to implement encryption services, this is a finding.SRG-NET-000512-ALG-000064<GroupDescription></GroupDescription>F5BI-LT-000303The BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound SMTP and Extended SMTP communications traffic to virtual servers.<VulnDiscussion>Application protocol anomaly detection examines application layer protocols such as SMTP to identify attacks based on observed deviations in the normal RFC behavior of a protocol or service. This type of monitoring allows for the detection of known and unknown exploits that exploit weaknesses of commonly used protocols.
+
+Since protocol anomaly analysis examines the application payload for patterns or anomalies, an SMTP proxy must be included in the ALG. This ALG will be configured to inspect inbound SMTP and Extended SMTP communications traffic to detect protocol anomalies such as malformed message and command insertion attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60383SV-74813CCI-001125CCI-000366If the BIG-IP Core provides intermediary/proxy services for SMTP communications traffic, configure the BIG-IP Core as follows:
+
+Configure the BIG-IP LTM module to inspect for protocol compliance and protocol anomalies in inbound SMTP and Extended SMTP communications traffic.If the BIG-IP Core does not provide intermediary/proxy services for SMTP communications traffic for virtual servers, this is not applicable.
+
+When intermediary/proxy services for SMTP communication traffic are provided, verify the BIG-IP Core is configured as follows:
+
+Verify the BIG-IP LTM module is configured to inspect for protocol compliance and protocol anomalies in inbound SMTP and Extended SMTP communications traffic.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select a Virtual Server that has been configured as an SMTP proxy.
+
+Verify that "SMTP Profile" under the "Configuration" section is set to a locally configured SMTP profile.
+
+Verify the configuration of the selected SMTP profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> Services >> SMTP.
+
+Select the SMTP profile that was to configure the Virtual Server.
+
+Verify that "Protocol Security" is Enabled under the "Settings" section.
+
+If the BIG-IP Core does not inspect inbound SMTP and Extended SMTP communications traffic for protocol compliance and protocol anomalies, this is a finding.SRG-NET-000512-ALG-000065<GroupDescription></GroupDescription>F5BI-LT-000305The BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound FTP and FTPS communications traffic to virtual servers.<VulnDiscussion>Application protocol anomaly detection examines application layer protocols such as FTP to identify attacks based on observed deviations in the normal RFC behavior of a protocol or service. This type of monitoring allows for the detection of known and unknown exploits that exploit weaknesses of commonly used protocols.
+
+Since protocol anomaly analysis examines the application payload for patterns or anomalies, an FTP proxy must be included in the ALG. This ALG will be configured to inspect inbound FTP and FTPS communications traffic to detect protocol anomalies such as malformed message and command insertion attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74815V-60385CCI-000366CCI-001125If the BIG-IP Core provides intermediary/proxy services for FTP and FTPS communications traffic, configure the BIG-IP Core as follows:
+
+Configure the BIG-IP LTM module to inspect for protocol compliance and protocol anomalies in inbound FTP and FTPS communications traffic.If the BIG-IP Core does not provide intermediary/proxy services for FTP and FTPS communications traffic for virtual servers, this is not applicable.
+
+When intermediary/proxy services for FTP and FTPS communications traffic are provided, verify the BIG-IP Core is configured as follows:
+
+Verify the BIG-IP LTM module is configured to inspect for protocol compliance and protocol anomalies in inbound FTP and FTPS communications traffic.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select a Virtual Server that has been configured as an FTP proxy.
+
+Verify that "FTP Profile" under the "Configuration" section is set to a locally configured FTP profile.
+
+Verify the configuration of the selected FTP profile:
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> Services >> FTP.
+
+Select the FTP profile that was to configure the Virtual Server.
+
+Verify that "Protocol Security" is Enabled under the "Settings" section.
+
+If the BIG-IP Core does not inspect inbound FTP and FTPS communications traffic for protocol compliance and protocol anomalies, this is a finding.SRG-NET-000512-ALG-000066<GroupDescription></GroupDescription>F5BI-LT-000307The BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound HTTP and HTTPS traffic to virtual servers.<VulnDiscussion>Application protocol anomaly detection examines application layer protocols such as HTTP to identify attacks based on observed deviations in the normal RFC behavior of a protocol or service. This type of monitoring allows for the detection of known and unknown exploits that exploit weaknesses of commonly used protocols.
+
+Since protocol anomaly analysis examines the application payload for patterns or anomalies, an HTTP proxy must be included in the ALG. This ALG will be configured to inspect inbound HTTP and HTTPS communications traffic to detect protocol anomalies such as malformed message and command insertion attacks. Note that if mutual authentication is enabled, there will be no way to inspect HTTPS traffic with MITM.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74817V-60387CCI-000366CCI-001125If the BIG-IP Core provides intermediary/proxy services for HTTP and HTTPS communications traffic, configure the BIG-IP Core to inspect inbound HTTP and HTTPS communications traffic for protocol compliance and protocol anomalies.If the BIG-IP Core does not provide intermediary/proxy services for HTTP and HTTPS communications traffic for virtual servers, this is not applicable.
+
+When intermediary/proxy services for HTTP and HTTPS communications traffic are provided, verify the BIG-IP Core is configured as follows:
+
+Verify the BIG-IP LTM module is configured to inspect for protocol compliance and protocol anomalies in inbound HTTP and HTTPS communications traffic.
+
+Navigate to the BIG-IP System manager >> Security >> Protocol Security >> Security Profiles >> HTTP.
+
+Verify there is at least one profile for managing HTTP traffic.
+
+Select a Profile from the list to verify.
+
+Review each of the following tabs to verify the proper criteria are selected and are set to "Alarm" at a minimum:
+
+"HTTP Protocol Checks"
+"Request Checks"
+"Blocking Page"
+
+If the BIG-IP Core does not inspect inbound HTTP and HTTPS communications traffic for protocol compliance and protocol anomalies, this is a finding.SRG-NET-000517-ALG-000006<GroupDescription></GroupDescription>F5BI-LT-000147The BIG-IP Core implementation must automatically terminate a user session for a user connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.<VulnDiscussion>Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.
+
+Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.
+
+This capability is typically reserved for specific system functionality where the system owner, data owner, or organization requires additional trigger events based on specific mission needs. Conditions or trigger events requiring automatic session termination can include, for example, targeted responses to certain types of incidents and time-of-day restrictions on information system use.
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019SV-74751V-60321CCI-000366CCI-002361If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to automatically terminate a user session when organization-defined conditions or trigger events occur that require a session disconnect.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to automatically terminate a user session for a user connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to automatically terminate user sessions for users connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section that "Access Policy" has been set to use an APM access policy to automatically terminate a user session when organization-defined conditions or trigger events occur that require a session disconnect.
+
+If the BIG-IP Core is not configured to automatically terminate a user session when organization-defined conditions or trigger events occur that require a session disconnect, this is a finding.SRG-NET-000519-ALG-000008<GroupDescription></GroupDescription>F5BI-LT-000151The BIG-IP Core must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions when providing access to virtual servers.<VulnDiscussion>If a user cannot explicitly end a session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated.
+
+Logoff messages for access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, remote logon, information systems typically send logoff messages as final messages prior to terminating sessions.
+
+This policy only applies to ALGs (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60323SV-74753CCI-002364CCI-000366If user access control intermediary services are provided, configure the BIG-IP Core as follows:
+
+Configure a policy in the BIG-IP APM module to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.
+
+Apply APM policy to the applicable Virtual Server(s) in the BIG-IP LTM module to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions when providing access to virtual servers.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP Core is configured as follows:
+
+Verify Virtual Server(s) in the BIG-IP LTM module are configured with an APM policy to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions when providing access to virtual servers.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select Virtual Servers(s) from the list to verify.
+
+Verify under "Access Policy" section, that "Access Policy" has been set to use an APM access policy that displays an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.
+
+If the BIG-IP Core is not configured to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions, this is a finding.SRG-NET-000521-ALG-000002<GroupDescription></GroupDescription>F5BI-LT-000139The BIG-IP Core implementation must be configured to activate a session lock to conceal information previously visible on the display for connections to virtual servers.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.
+
+The session lock is implemented at the point where session activity can be determined. The network element session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.
+
+Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information.
+
+This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019V-60315SV-74745CCI-001494If user access control intermediary services are provided, configure the BIG-IP Core to conceal, via a session lock, information previously visible on the display with a publicly viewable image.If the BIG-IP Core does not provide user access control intermediary services for virtual servers, this is not applicable.
+
+When user access control intermediary services are provided, verify the BIG-IP LTM is configured to conceal, via a session lock, information previously visible on the display with a publicly viewable image.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Profiles >> Protocol >> TCP.
+
+Select a TCP Profile for user sessions.
+
+Verify "Reset On Timeout" is Enabled under the "Settings" section
+
+Verify the BIG-IP LTM is configured to use the Protocol Profile.
+
+Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
+
+Select appropriate virtual server.
+
+Verify "Protocol Profile (Client)" is set to a profile that limits session timeout.
+
+If the BIG-IP Core does not conceal, via a session lock, information previously visible on the display with a publicly viewable image, this is a finding.SRG-NET-000164-ALG-000100<GroupDescription></GroupDescription>F5BI-LT-000317The F5 BIG-IP appliance must configure OCSP to ensure revoked credentials are prohibited from establishing an allowed session.<VulnDiscussion>A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.
+
+Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target F5 BIG-IP Local Traffic ManagerDISADPMS TargetF5 BIG-IP Local Traffic Manager4019CCI-000185If the BIG-IP is performing Client Certificate Authentication add the Client SSL Profile.
+
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Profiles.
+3. SSL.
+4. Client.
+5. Click the name of the SSL profile.
+6. Under "Client Authentication", select a trusted CA certificate or bundle under "Trusted Certificate Authorities".
+Note: To create a Trusted CA certificate or bundle, go to System >> Certificate Management >> Traffic Certificate Management >> SSL Certificate List.
+7. If the BIG-IP is performing Client Certificate Constrained Delegation, select an OCSP responder under "Client Certificate Constrained Delegation".
+Note: To create an OCSP Responder, click the "+" next to "OCSP" or go to System >> Certificate Management >> Traffic Certificate Management >> OCSP.
+8. Click "Update".If the BIG-IP appliance does not provide intermediary services for TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS), this is not applicable.
+
+If the BIG-IP is performing Client Certificate Authentication:
+Client SSL Profile:
+From the BIG-IP GUI:
+1. Local Traffic.
+2. Profiles.
+3. SSL.
+4. Client.
+5. Click the name of the SSL profile.
+6. Under "Client Authentication", verify that "Trusted Certificate Authorities" is configured with a trusted CA certificate or bundle.
+7. If the BIG-IP is performing Client Certificate Constrained Delegation, verify an OCSP responder is selected under "Client Certificate Constrained Delegation".
+8. Verify the OCSP Responder is configured correctly by going to System >> Certificate Management >> Traffic Certificate Management >> OCSP.
+
+If the BIG-IP appliance is not configured to use OCSP to ensure revoked user credentials are prohibited from establishing an allowed session, this is a finding.
\ No newline at end of file
diff --git a/stigs.json b/stigs.json
index b52bb0f1a..ac1808151 100644
--- a/stigs.json
+++ b/stigs.json
@@ -4622,18 +4622,24 @@
"version": "V1R1",
"file": "https://raw.githubusercontent.com/mitre/inspec-profile-update-action/main/benchmarks/DISA/U_MS_Windows_Server_DNS_STIG_V1R1_Manual-xccdf.xml"
},
- {
- "id": "c04de80c-e97d-4187-a836-04ebfd3079e2",
- "name": "z/OS RACF Products - Ver 6, Rel 59",
- "url": "https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_zOS_RACF_V6R59_Products.zip",
- "size": "8.96 MB",
- "version": "V6R59"
- },
{
"id": "b8144450-c195-4103-a2b5-1958086e6aea",
"name": "z/OS ACF2 Products - Ver 6, Rel 59",
"url": "https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_zOS_ACF2_V6R59_Products.zip",
"size": "9.7 MB",
"version": "V6R59"
+ },
+ {
+ "id": "b758ee5f-9613-4b0b-b3fb-35663af7b7bd",
+ "name": "F5 BIG-IP STIG",
+ "url": "https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_F5_BIG-IP_Y24M01_STIG.zip",
+ "size": "1.5 MB"
+ },
+ {
+ "id": "0872c7bd-0054-4f67-b1ff-d6fc3d4c2b2a",
+ "name": "z/OS SRR Scripts - Ver 6, Rel 59",
+ "url": "https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_zOS_V6R59_SRR.zip",
+ "size": "1.89 MB",
+ "version": "V6R59"
}
]
\ No newline at end of file