STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

HPE Aruba Networking AOS NDM Security Technical Implementation Guide

Version

V1R1

Release Date

Oct 29, 2024

SCAP Benchmark ID

HPE_Aruba_AOS_NDM_STIG

Total Checks

37

Tags

network
CAT I: 9CAT II: 28CAT III: 0

This 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.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (37)

V-266903MEDIUMAOS must limit the number of concurrent sessions to a maximum of three for each administrator account and/or administrator account type.V-266908MEDIUMAOS must automatically audit account creation.V-266909HIGHAOS must be configured to assign appropriate user roles or access levels to authenticated users.V-266910MEDIUMAOS must enforce approved authorizations for controlling the flow of management information within the network device based on information flow control policies.V-266911MEDIUMAOS must be configured to enforce the limit of three consecutive invalid login attempts, after which time it must block any login attempt for 15 minutes.V-266912MEDIUMAOS must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the device.V-266913MEDIUMAOS must retain the Standard Mandatory DOD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access.V-266928HIGHAOS must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.V-266929HIGHAOS must be configured to use DOD public key infrastructure (PKI) as multifactor authentication (MFA) for interactive logins.V-266930MEDIUMAOS must implement replay-resistant authentication mechanisms for network access to privileged accounts.V-266931MEDIUMAOS must enforce a minimum 15-character password length.V-266932MEDIUMAOS must enforce password complexity by requiring that at least one uppercase character be used.V-266933MEDIUMAOS must enforce password complexity by requiring that at least one lowercase character be used.V-266934MEDIUMAOS must enforce password complexity by requiring that at least one numeric character be used.V-266935MEDIUMAOS must enforce password complexity by requiring that at least one special character be used.V-266937HIGHAOS must transmit only encrypted representations of passwords.V-266938HIGHAOS must be configured to use DOD-approved Online Certificate Status Protocol (OCSP) responders or Certificate Revocation Lists (CRLs) to validate certificates used for public key infrastructure (PKI)-based authentication.V-266940HIGHAOS must use FIPS 140-2/140-3 approved algorithms for authentication to a cryptographic module.V-266941HIGHAOS must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after five minutes of inactivity except to fulfill documented and validated mission requirements.V-266948MEDIUMAOS must enforce role-based access control policies over defined subjects and objects.V-266950MEDIUMAOS must audit the execution of privileged functions.V-266952MEDIUMAOS must generate an immediate real-time alert of all audit failure events requiring real-time alerts.V-266953MEDIUMAOS must be configured to synchronize internal information system clocks using redundant authoritative time sources.V-266954MEDIUMAOS must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).V-266958MEDIUMAOS must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).V-266959MEDIUMAOS must prohibit the use of cached authenticators after an organization-defined time period.V-266961MEDIUMAOS must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.V-266966MEDIUMAOS must off-load audit records onto a different system or media than the system being audited.V-266967MEDIUMAOS must require that when a password is changed, the characters are changed in at least eight of the positions within the password.V-266968MEDIUMAOS must generate log records for a locally developed list of auditable events.V-266970HIGHAOS must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access.V-266971MEDIUMAOS must be configured to conduct backups of system-level information contained in the information system when changes occur.V-266972MEDIUMAOS must support organizational requirements to conduct backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner.V-266973MEDIUMAOS must obtain its public key certificates from an appropriate certificate policy through an approved service provider.V-266975MEDIUMAOS must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.V-266976MEDIUMAOS must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.V-266977HIGHAOS must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).