Authentication, Authorization, and Accounting Services (AAA) Security Requirements Guide

This Security Requirements Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R1

Published: 2018-10-01

Updated At: 2018-12-08 11:44:47

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-95525r1_rule SRG-APP-000142-AAA-000010 CCI-000382 HIGH AAA Services must be configured to use secure protocols when connecting to directory services. Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Application communication sessions are protected utilizing transport encryption protocols, such as TLS.
    SV-95527r1_rule SRG-APP-000142-AAA-000020 CCI-000382 HIGH AAA Services must be configured to use protocols that encrypt credentials when authenticating clients, as defined in the PPSM CAL and vulnerability assessments. Authentication protection of the client credentials (specifically the password or shared secret) prevents unauthorized access to resources. The RADIUS protocol encrypts the password field in the access-request packet, from the client to the AAA server. Th
    SV-95529r1_rule SRG-APP-000023-AAA-000030 CCI-000015 MEDIUM AAA Services must be configured to provide automated account management functions. Enterprise environments make account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. A comprehensive account management process that includes automation helps to
    SV-95531r1_rule SRG-APP-000024-AAA-000050 CCI-000016 MEDIUM AAA Services must be configured to automatically remove authorizations for temporary user accounts after 72 hours. When temporary user accounts remain active after no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary user accounts must be set upon account crea
    SV-95533r1_rule SRG-APP-000234-AAA-000060 CCI-001682 MEDIUM AAA Services must be configured to prevent automatically removing emergency accounts. 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 thes
    SV-95535r1_rule SRG-APP-000234-AAA-000070 CCI-001682 LOW AAA Services must be configured to prevent automatically disabling emergency accounts. 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 thes
    SV-95537r1_rule SRG-APP-000025-AAA-000080 CCI-000017 MEDIUM AAA Services must be configured to automatically disable accounts after a 35-day period of account inactivity. Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need t
    SV-95539r1_rule SRG-APP-000026-AAA-000090 CCI-000018 MEDIUM AAA Services must be configured to automatically audit account creation. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation is one method
    SV-95541r1_rule SRG-APP-000027-AAA-000100 CCI-001403 MEDIUM AAA Services must be configured to automatically audit account modification. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify an existing account. Auditing of account modification is o
    SV-95543r1_rule SRG-APP-000028-AAA-000110 CCI-001404 MEDIUM AAA Services must be configured to automatically audit account disabling actions. When application accounts are disabled, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to disable authorized accounts to disrupt services or prevent the implementation of countermeasures.
    SV-95545r1_rule SRG-APP-000029-AAA-000120 CCI-001405 MEDIUM AAA Services must be configured to automatically audit account removal actions. When application accounts are removed, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to remove authorized accounts to disrupt services or prevent the implementation of countermeasures. A
    SV-95547r1_rule SRG-APP-000291-AAA-000130 CCI-001683 MEDIUM AAA Services must be configured to notify the system administrators and ISSO when accounts are created. Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Sending notification of account crea
    SV-95549r1_rule SRG-APP-000292-AAA-000140 CCI-001684 MEDIUM AAA Services must be configured to notify the system administrators and ISSO when accounts are modified. When application accounts are modified, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account modification events to the system admin
    SV-95551r1_rule SRG-APP-000293-AAA-000150 CCI-001685 MEDIUM AAA Services must be configured to notify the system administrators and ISSO for account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account disabling events to the system administ
    SV-95553r1_rule SRG-APP-000294-AAA-000160 CCI-001686 MEDIUM AAA Services must be configured to notify the system administrators and ISSO for account removal actions. When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying users or for identifying the application processes themselves. Sending notification of account removal events to the system administrator and ISSO
    SV-95555r1_rule SRG-APP-000319-AAA-000170 CCI-002130 MEDIUM AAA Services must be configured to automatically audit account enabling actions. Once an attacker establishes access to an application, 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. Automatically auditing ac
    SV-95557r1_rule SRG-APP-000320-AAA-000180 CCI-002132 MEDIUM AAA Services must be configured to notify system administrators and ISSO of account enabling actions. Once an attacker establishes access to an application, 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. Sending notification of a
    SV-95559r1_rule SRG-APP-000329-AAA-000190 CCI-002169 LOW AAA Services must be configured to use Role-Based Access Control (RBAC) policy for levels of access authorization. RBAC is an access control policy that restricts information system access to authorized users. Without these security policies, access control and enforcement mechanisms will not prevent unauthorized access. Organizations can create specific roles based
    SV-95561r1_rule SRG-APP-000065-AAA-000200 CCI-000044 MEDIUM AAA Services must be configured to automatically lock user accounts after three consecutive invalid logon attempts within a 15-minute time period. 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.
    SV-95565r1_rule SRG-APP-000345-AAA-000210 CCI-002238 MEDIUM AAA Services must be configured to maintain locks on user accounts until released by an administrator. 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.
    SV-95567r1_rule SRG-APP-000095-AAA-000220 CCI-000130 MEDIUM AAA Services configuration audit records must identify what type of events occurred. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit record content that may be necessary to satisfy the require
    SV-95569r1_rule SRG-APP-000096-AAA-000230 CCI-000131 MEDIUM AAA Services configuration audit records must identify when (date and time) the events occurred. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personne
    SV-95571r1_rule SRG-APP-000097-AAA-000240 CCI-000132 MEDIUM AAA Services configuration audit records must identify where the events occurred. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personn
    SV-95573r1_rule SRG-APP-000098-AAA-000250 CCI-000133 MEDIUM AAA Services configuration audit records must identify the source of the events. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the application, the application must also produce audi
    SV-95575r1_rule SRG-APP-000099-AAA-000260 CCI-000134 MEDIUM AAA Services configuration audit records must identify the outcome of the events. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event succ
    SV-95577r1_rule SRG-APP-000100-AAA-000270 CCI-001487 MEDIUM AAA Services configuration audit records must identify any individual user or process associated with the event. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Event identifiers (if
    SV-95579r1_rule SRG-APP-000358-AAA-000280 CCI-001851 MEDIUM AAA Services must be configured to send audit records to a centralized audit server. 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.
    SV-95581r1_rule SRG-APP-000108-AAA-000290 CCI-000139 MEDIUM AAA Services must be configured to alert the SCA and ISSO when any audit processing failure occurs. 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 opera
    SV-95583r1_rule SRG-APP-000109-AAA-000300 CCI-000140 MEDIUM AAA Services must be configured to generate audit records overwriting the oldest audit records in a first-in-first-out manner. It is critical that when AAA Services are at risk of failing to process audit logs as required, they take action to mitigate the failure. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit sto
    SV-95585r1_rule SRG-APP-000109-AAA-000310 CCI-000140 MEDIUM AAA Services must be configured to queue audit records locally until communication is restored when any audit processing failure occurs. It is critical that when AAA Services are at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit stora
    SV-95587r1_rule SRG-APP-000116-AAA-000320 CCI-000159 MEDIUM AAA Services must be configured to use internal system clocks to generate time stamps for audit records. Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when
    SV-95589r1_rule SRG-APP-000375-AAA-000330 CCI-001889 MEDIUM AAA Services must be configured with a minimum granularity of one second to record time stamps for audit records. Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchr
    SV-95591r1_rule SRG-APP-000374-AAA-000340 CCI-001890 MEDIUM AAA Services must be configured to use or map to Coordinated Universal Time (UTC) to record time stamps for audit records. If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in Coordinated Universal Time (UTC
    SV-95593r1_rule SRG-APP-000516-AAA-000350 CCI-000366 LOW AAA Services must be configured to use at least two NTP servers to synchronize time. Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. S
    SV-95595r1_rule SRG-APP-000516-AAA-000360 CCI-000366 MEDIUM AAA Services must be configured to authenticate all NTP messages received from NTP servers and peers. Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. S
    SV-95597r1_rule SRG-APP-000516-AAA-000370 CCI-000366 LOW AAA Services must be configured to use their loopback or OOB management interface address as the source address when originating NTP traffic. Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. S
    SV-95599r1_rule SRG-APP-000089-AAA-000380 CCI-000169 MEDIUM AAA Services must be configured to audit each authentication and authorization transaction. Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the
    SV-95601r1_rule SRG-APP-000148-AAA-000390 CCI-000764 HIGH AAA Services must be configured to uniquely identify and authenticate organizational users. 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 org
    SV-95603r1_rule SRG-APP-000149-AAA-000400 CCI-000765 MEDIUM AAA Services must be configured to require multifactor authentication using Personal Identity Verification (PIV) credentials for authenticating privileged user accounts. Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g.
    SV-95605r1_rule SRG-APP-000150-AAA-000410 CCI-000766 MEDIUM AAA Services must be configured to require multifactor authentication using Common Access Card (CAC) Personal Identity Verification (PIV) credentials for authenticating non-privileged user accounts. 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 authentica
    SV-95607r1_rule SRG-APP-000158-AAA-000420 CCI-000778 MEDIUM AAA Services used for 802.1x must be configured to uniquely identify network endpoints (supplicants) before the authenticator establishes any connection. Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of identification claims
    SV-95609r1_rule SRG-APP-000394-AAA-000430 CCI-001958 MEDIUM AAA Services used for 802.1x must be configured to authenticate network endpoint devices (supplicants) before the authenticator establishes any connection. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of authentication cla
    SV-95611r1_rule SRG-APP-000516-AAA-000440 CCI-000366 MEDIUM AAA Services used for 802.1x must be configured to use secure Extensible Authentication Protocol (EAP), such as EAP-TLS, EAP-TTLS, and PEAP. Additional new EAP methods/types are still being proposed. However, the three being considered secure are EAP-TLS, EAP-TTLS, and PEAP. PEAP is the preferred EAP type to be used in DoD for its ability to support a greater number of operating systems and it
    SV-95613r1_rule SRG-APP-000164-AAA-000450 CCI-000205 MEDIUM AAA Services must be configured to enforce a minimum 15-character password length. 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 passwor
    SV-95615r1_rule SRG-APP-000166-AAA-000460 CCI-000192 MEDIUM AAA Services must be configured to enforce password complexity by requiring that at least one upper-case character be used. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time and resources required to compromise the password. The more c
    SV-95617r1_rule SRG-APP-000167-AAA-000470 CCI-000193 MEDIUM AAA Services must be configured to enforce password complexity by requiring that at least one lower-case character be used. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time and resources required to compromise the password. The more c
    SV-95619r1_rule SRG-APP-000168-AAA-000480 CCI-000194 MEDIUM AAA Services must be configured to enforce password complexity by requiring that at least one numeric character be used. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time and resources required to compromise the password. The more c
    SV-95621r1_rule SRG-APP-000169-AAA-000490 CCI-001619 MEDIUM AAA Services must be configured to enforce password complexity by requiring that at least one special character be used. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time and resources required to compromise the password. The more c
    SV-95623r1_rule SRG-APP-000170-AAA-000500 CCI-000195 MEDIUM AAA Services must be configured to require the change of at least eight of the total number of characters when passwords are changed. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time and resources required to compromise the password. The more c
    SV-95625r1_rule SRG-APP-000172-AAA-000520 CCI-000197 HIGH AAA Services must be configured to encrypt transmitted credentials using a FIPS-validated cryptographic module. 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. AAA Services can accomplish this by making dir
    SV-95627r1_rule SRG-APP-000173-AAA-000530 CCI-000198 MEDIUM AAA Services must be configured to enforce 24 hours as the minimum password lifetime. 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 sp
    SV-95629r1_rule SRG-APP-000174-AAA-000540 CCI-000199 MEDIUM AAA Services must be configured to enforce a 60-day maximum password lifetime restriction. 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 application does not limit
    SV-95631r1_rule SRG-APP-000165-AAA-000550 CCI-000200 MEDIUM AAA Services must be configured to prohibit password reuse for a minimum of five generations. 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
    SV-95633r1_rule SRG-APP-000397-AAA-000560 CCI-002041 MEDIUM AAA Services must be configured to allow the use of a temporary password at initial logon with an immediate change to a permanent password. 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 typical
    SV-95635r1_rule SRG-APP-000175-AAA-000570 CCI-000185 HIGH AAA Services must be configured to only accept certificates issued by a DoD-approved Certificate Authority for PKI-based authentication. Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is
    SV-95637r1_rule SRG-APP-000175-AAA-000580 CCI-000185 HIGH AAA Services must be configured to not accept certificates that have been revoked for PKI-based authentication. Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is
    SV-95639r1_rule SRG-APP-000176-AAA-000590 CCI-000186 MEDIUM AAA Services must be configured to enforce authorized access to the corresponding private key for PKI-based authentication. If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the priva
    SV-95641r1_rule SRG-APP-000177-AAA-000600 CCI-000187 MEDIUM AAA Services must be configured to map the authenticated identity to the user account for PKI-based authentication. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.
    SV-95643r1_rule SRG-APP-000231-AAA-000610 CCI-001199 HIGH AAA Services must be configured to protect the confidentiality and integrity of all information at rest. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive) within an organizational information system. Mobile devices, laptops, desktops, and storage devices can be either los
    SV-95645r1_rule SRG-APP-000516-AAA-000620 CCI-000366 MEDIUM AAA Services must not be configured with shared accounts. Shared accounts configured for use on a network device do not allow for accountability or repudiation of individuals using them. If shared accounts are not changed when someone leaves the group, that person could possibly gain control of the network devic
    SV-95647r1_rule SRG-APP-000516-AAA-000630 CCI-000366 MEDIUM AAA Services used to authenticate privileged users for device management must be configured to connect to the management network. Using standardized authentication protocols such as RADIUS, TACACS+, and Kerberos, an authentication server provides centralized and robust authentication services for the management of network components. In order to control access to the servers as well
    SV-95649r1_rule SRG-APP-000516-AAA-000640 CCI-000366 MEDIUM AAA Services must be configured to use a unique shared secret for communication (i.e. RADIUS, TACACS+) with clients requesting authentication services. Using standardized authentication protocols such as RADIUS, TACACS+, and Kerberos, an authentication server provides centralized and robust authentication services for the management of network components. An authentication server is very scalable as it s
    SV-95651r1_rule SRG-APP-000516-AAA-000650 CCI-000366 MEDIUM AAA Services must be configured to use IP segments separate from production VLAN IP segments. When policy assessment and remediation have been implemented and the advanced AAA server dynamic VLAN is misconfigured, logical separation of the production VLAN may not be assured. Non-trusted resources are resources that are not authenticated in a NAC
    SV-95653r1_rule SRG-APP-000516-AAA-000660 CCI-000366 MEDIUM AAA Services must be configured to place non-authenticated network access requests in the Unauthorized VLAN or the Guest VLAN with limited access. Devices having an IP address that do not pass authentication can be used to attack compliant devices if they share VLANs. When devices proceed into the NAC AAA (radius) functions they must originate in the Unauthorized VLAN by default. If the device fails
    SV-95655r1_rule SRG-APP-000141-AAA-000670 CCI-000381 MEDIUM AAA Services must be configured to disable non-essential modules. It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to
    SV-95657r1_rule SRG-APP-000142-AAA-000680 CCI-000382 MEDIUM AAA Services must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. 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 po
    SV-95659r1_rule SRG-APP-000516-AAA-000690 CCI-000366 MEDIUM AAA Services 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. Configuring the application 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 p
    SV-95661r1_rule SRG-APP-000024-AAA-000040 CCI-000016 MEDIUM AAA Services must be configured to automatically remove temporary user accounts after 72 hours. When temporary user accounts remain active after no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary user accounts must be set upon account crea
    SV-95663r1_rule SRG-APP-000171-AAA-000510 CCI-000196 HIGH AAA Services must be configured to encrypt locally stored credentials using a FIPS-validated cryptographic module. 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. AAA Services must enforce cryptographic repre