| Internet-Draft | The Terminal Access Controller Access-Co | May 2024 |
| Dahm, et al. | Expires 22 November 2024 | [Page] |
The Terminal Access Controller Access-Control System Plus (TACACS+) Protocol provides device administration for routers, network access servers and other networked computing devices via one or more centralized servers. This document adds Transport Layer Security (TLS 1.3) support to TACACS+ and obsoletes former inferior security mechanisms.¶
This document updates RFC8907.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 22 November 2024.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Terminal Access Controller Access-Control System Plus (TACACS+) Protocol [RFC8907] provides Device Administration for routers, network access servers and other networked computing devices via one or more centralized servers. The protocol provides authentication, authorization and accounting services (AAA) for TACACS+ clients within the Device Administration use case.¶
While the content of the protocol is highly sensitive, TACACS+ lacks effective confidentiality, integrity, and authentication of the connection and network traffic between the server and client, requiring secure transport to safeguard a deployment. The existing TACACS+ mechanisms are extremely weak as described in Section 10 of [RFC8907].¶
To address these deficiencies, this document updates the TACACS+ protocol to use TLS 1.3 [RFC8446] authentication and encryption, and obsoletes the use of its former mechanisms (Section 10.5 of [RFC8907]).¶
The terms defined in Section 3 of [RFC8907] are fully applicable here and will not be repeated. The following terms are also used in this document.¶
TACACS+ was originally intended to incorporate a mechanism for securing the body of its packets. The algorithm is categorized as Obfuscation in Section 10.5.2 of [RFC8907]. The term should be interpreted to mean "plaintext", it is used to ensure that the algorithm is not mistaken for encryption.¶
This term refers to the connection defined in [RFC8907]. It is a connection without TLS and therefore being plaintext or possibly using unsecure TACACS+ authentication and obfuscation. The use of well-known TCP/IP server port number 49 is specified as the default for Non-TLS connections.¶
A TLS connection is a TCP/IP connection with TLS authentication and encryption used by TACACS+ for transport. A TLS connection for TACACS+ is always between one TACACS+ client and one TACACS+ Server.¶
A TACACS+ server is an instance of the server as defined in Section 3.2 of [RFC8907] that responds to TACACS+ traffic bound to a specific port number on a host. This document distinguishes the TACACS+ server instance from the host itself. A host may have multiple TACACS+ servers running, each listening on different port numbers.¶
The peer of a TACACS+ client (or server) in the context of a TACACS+ connection, is a server (or client). Together, the ends of a TACACS+ connection are referred to as peers.¶
TACACS+ over TLS takes the protocol defined in [RFC8907], removes the option for MD5 obfuscation, and specifies that TLS 1.3 MUST be used for transport (Section 3.1 elaborates TLS version support). A new well-known default server port number is used. The next sections provide further details and guidance.¶
TLS is introduced into TACACS+ to fulfill the following requirements:¶
All data exchanged by TACACS+ peers MUST be encrypted, including the mutual authentication of the peers. Therefore, when a TCP connection is established for the service, a TLS handshake begins immediately.¶
To ensure separation of TACACS+ traffic that uses TLS from that which does not (Section 5.3), they will be deployed on different ports. Due to the widespread use of default port number settings in numerous existing TACACS+ client configurations, a well-known system TCP/IP port number will be requested from IANA. Client implementations can ensure traffic is kept separate. The designated port number is [TBD] (Section 7) with the service name [TBDN] (Section 7).¶
Under exceptional circumstances, this document permits any other TCP port number to be configured when required by deployment specifics, but the implications in Section 5.3 have to be considered by operators.¶
A TACACS+ client initiates a TLS connection by making a TCP connection to a configured server on the TACACS+ TLS port number ([TBD]) (Section 3.1). Once the TCP connection is established, the client MUST immediately begin the TLS negotiation before sending any TACACS+ protocol data.¶
TLS 1.3 [RFC8446] MUST be used for transport, though it is expected that TACACS+ as described in this document will work with future versions of TLS. Earlier versions of TLS MUST NOT be used.¶
When resumption is supported, the resumption ticket_lifetime SHOULD be configurable, including a zero seconds lifetime.¶
Once the TLS connection is established, the exchange of TACACS+ data proceeds as defined in [RFC8907], except that it is transmitted over TLS as TLS application data and without TACACS+ obfuscation (Section 4)¶
The connection persists until the server or client closes it, either due to an error, or at the conclusion of the TACACS+ session, or, if Single Connection Mode Section 4.3 of [RFC8907] has been negotiated, when an inactivity timeout occurs. Why it closed has no bearing on TLS resumption, unless closed by a TLS error, in which case the ticket might be invalidated.¶
Implementations MUST support the TLS 1.3 mandatory cipher suites (TLS 1.3 [RFC8446] Section 9.1). The cipher suites offered or accepted SHOULD be configurable so that operators can adapt.¶
This document makes no cipher suite recommendations, please refer to [BCP195] for guidance.¶
Certificate based mutual authentication MUST be supported. Each peer MUST validate the certificate path of the remote peer, including revocation checking, as described in Section 3.2.2.1.¶
If the verification succeeds, the authentication is successful and the connection is permitted. Policy may impose further constraints upon the peer, allowing or denying the connection based on certificate fields or any other parameters exposed by the implementation.¶
Unless disabled by configuration, a peer MUST not permit connection of any peer that presents an invalid TLS Certificate.¶
In addition to full certificate-based TLS authentication, implementations MAY support:¶
The details of these mechanisms are considered out-of-scope for this document. Please refer to the RFCs above for implementation, deployment, and security considerations.¶
The implementation of certificate based mutual authentication MUST support certificate Path verification as described in Section 6 of [RFC5280].¶
In some deployments, a peer could be isolated from a remote peer's Certification Authority (CA). Implementations for these deployments MUST support certificate chains (a.k.a. bundles or chains of trust), where the entire chain of the remote's certificate is stored on the local peer.¶
TLS Cached Information Extension [RFC7924] SHOULD be implemented. This MAY be augmented with Raw Public Keys [RFC7250], though revocation must be handled as it is not part of the standard. .¶
Other approaches may be used for loading the intermediate certificates onto the client, but MUST include support for revocation checking. For example, [RFC5280] details the AIA (Authority Information Access) extension to provide information about the issuer of the certificate in which the extension appears. It can be used to provide the address of the Online Certificate Status Protocol (OCSP) responder from where revocation status of the certificate (which includes the extension) can be checked.¶
For the client-side validation of presented server identities, implementations MUST follow [RFC9525] validation techniques. Identifier types DNS-ID, IP-ID or SRV-ID are applicable for use with the TLS TACACS+ protocol, selected by operators depending upon the deployment design. TLS TACACS+ does not use URI-IDs for server identity verification. The wildcard character MUST NOT be included in the presented server identities.¶
For the server-side validation of client identities, Implementations must support the ability to configure which fields of a certificate are used for client identification, to verify that the client is a valid source for the received certificate and that it is permitted access to TACACS+. Implementations MUST support either:¶
Network address based validation methods as described in Section 5.2 of [RFC5425].¶
or¶
Client Identity validation of a shared identity in the certificate subjectAltName. This is applicable in deployments where the client securely supports an identity which is shared with the server. This approach allows a client's network location to be reconfigured without issuing a new client certificate, in this case, only the server mapping needs to be updated.¶
Implementations MUST support the TLS Server Name Indication extension (SNI) (Section 3 of [RFC6066]), and MUST support the ability to configure the server's domain name, so that it may be included in the SNI "server_name" extension of the client hello. Please see Section 5.1.5 for securitly related operator considerations.¶
Certificate provisioning is out of scope of this document.¶
[RFC8907] describes the obfuscation mechanism, documented in Section 5.2 of [RFC5425]. Such a method is weak.¶
The introduction of TLS PSK, certificate peer authentication, and TLS encryption to TACACS+ replaces these former mechanisms and so obfuscation is hereby obsoleted. This section describes how the TACACS+ client and servers MUST operate with regards to the obfuscation mechanism.¶
Peers MUST NOT use obfuscation with TLS.¶
A TACACS+ client initiating a TACACS+ TLS connection MUST set the TAC_PLUS_UNENCRYPTED_FLAG bit, thereby asserting that obfuscation is not used for the session. All subsequent packets MUST have the TAC_PLUS_UNENCRYPTED_FLAG set.¶
A TACACS+ server that receives a packet with the TAC_PLUS_UNENCRYPTED_FLAG not set (cleared) over a TLS connection, MUST return an error of TAC_PLUS_AUTHEN_STATUS_ERROR, TAC_PLUS_AUTHOR_STATUS_ERROR, or TAC_PLUS_ACCT_STATUS_ERROR as appropriate for the TACACS+ message type, with the TAC_PLUS_UNENCRYPTED_FLAG set, and terminate the session. This behavior corresponds to that defined in Section 4.5 of [RFC8907] Data Obfuscation for TAC_PLUS_UNENCRYPTED_FLAG or key mismatches.¶
A TACACS+ client that receives a packet with the TAC_PLUS_UNENCRYPTED_FLAG not set (i.e., cleared), MUST terminate the session, and SHOULD log this error.¶
This document improves the confidentiality, integrity, and authentication of the connection and network traffic between TACACS+ peers by adding TLS support.¶
Simply adding TLS support to the protocol does not guarantee the protection of the server and clients. It is essential for the operators and equipment vendors to adhere to the latest best practices for ensuring the integrity of network devices and selecting secure TLS key and encryption algorithms.¶
RFC9325 offers substantial guidance for implementing protocols that use TLS and their deployment. Those implementing and deploying Secure TACACS+ must adhere to the recommendations relevant to TLS 1.3 outlined in RFC9325, or its subsequent versions.¶
This document outlines additional restrictions permissible under RFC9325. For example, any recommendations referring to TLS 1.2, including the mandatory support, are not relevant for Secure TACACS+ as TLS 1.3 or above is mandated.¶
Non-TLS connections should not be used for new TACACS+ deployments.¶
TACACS+ servers that have TLS support MUST NOT allow Non-TLS connections, because of the threat of downgrade attacks, as described in Section 5.2. Instead, separate Non-TLS TACACS+ servers can be set up to cater for these clients.¶
Further, TLS TACACS+ servers and Non-TLS TACACS+ servers SHOULD NOT be deployed on the same host. Non-TLS connections would be better served by deploying the required Non-TLS TACACS+ servers on separate hosts.¶
It is NOT RECOMMENDED to deploy TACACS+ without TLS authentication and encryption, unless within test and debug environments. Also see [RFC3365].¶
TLS 1.3 resumption and PSK techniques make it possible to send Early Data, aka. 0-RTT data, data that is sent before the TLS handshake completes. Replay of this data is a risk. Given the sensitivity of TACACS+ data, clients MUST NOT send data until the full TLS handshake completes; that is, clients MUST NOT send 0-RTT data and servers MUST abruptly disconnect clients that do.¶
Recommendations in [BCP195] MUST be followed, in order to determine which TLS versions and algorithms should be supported, deprecated, obsoleted, or abandoned.¶
Also useful are TLS 1.3 specifications themselves (TLS 1.3 [RFC8446]), which prescribes mandatory support in Section 9.¶
Operators should be cognizant of the potential of server and/or client isolation from their peer's CA by network failures. Isolation from a public key certificate's CA will cause the verification of the certificate to fail and thus TLS authentication of the peer to fail. The approach mentioned in Section 3.2.2.1 can help address this, and should be considered where implemented.¶
Operators should be aware that the TLS SNI extension is part of the TLS client hello, and is therefore subject to eavesdropping. Also see Section 11.1 of [RFC6066].¶
Implementors must ensure that the configuration scheme introduced for enabling TLS is straightforward and leaves no room for ambiguity regarding whether TLS or Non-TLS will be used between the TACACS+ client and the TACACS+ server.¶
This document recommends the use of a separate port number that TLS enabled TACACS+ servers will listen to. Where deployments have not overridden the defaults explicitly, TACACS+ client implementations MUST use the correct values:¶
Implementors may offer a single option for TACACS+ clients and servers to disable all Non-TLS TACACS+ operations. When enabled on a TACACS+ server, it will not respond to any requests from Non-TLS TACACS+ client connections. When enabled on a TACACS+ client, it will not establish any Non-TLS TACACS+ server connections.¶
A new port is considered appropriate and superior to a "STARTTLS" command or other negotiation method because it allows:¶
However, co-existence of inferior authentication and obfuscated, whether an Non-TLS connection or deprecated parts that compose TLS, also presents opportunity for down-grade attacks. Causing failure of connections to the TLS-enabled service or the negotiation of shared algorithm support are two such down-grade attacks.¶
The simplest way to address exposure from Non-TLS connection methods is to refuse Non-TLS connections at the server entirely, perhaps using separate servers for Non-TLS connections and TLS.¶
Another approach is mutual configuration that requires TLS. Clients and servers SHOULD support configuration that requires peers, globally and individually, use TLS. Furthermore, peers SHOULD be configurable to limit offered or recognized TLS versions and algorithms to those recommended by standards bodies and implementers.¶
Operational and deployment considerations are spread throughout the document. While avoiding repetition, it is useful for the impatient to direct particular attention to Sections 5.2 and 5.1.5. However, it is important that the entire Section 5 is observed.¶
In Section 5.2, it is mentioned that for an optimal deployment of TLS TACACS+, TLS should be universally applied throughout the deployment. However, during the migration process from a Non-TLS TACACS+ deployment, operators may need to support both TLS and Non-TLS TACACS+ servers. This migration phase allows operators to gradually transition their deployments from an insecure state to a more secure one, but it is important to note that it is vulnerable to downgrade attacks. Therefore, the migration phase should be considered insecure until it is fully completed. To mitigate this hazard:¶
Some TACACS+ client devices in a deployment may not implement TLS. These devices will require access to Non-TLS TACACS+ servers. Operators must follow the recommendation of Section 5.1.1 and deploy separate TACACS+ servers for these Non-TLS clients from those used for the TLS clients.¶
The authors request that, when this draft is accepted by the working group, the OPSAWG Chairs submit a request to IANA for an early allocation, per [RFC4020] and [RFC6335], of a new well-known system TCP/IP port number for the service name "tacacss" (referenced in this document also as "TACACS+ TLS well-known port ([TBD])"), described as "TACACS+ over TLS". The service name "tacacss" follows the common practice of appending an "s" to the name given to the Non-TLS well-known port name. This allocation is justified in Section 5.3.¶
This document requests IANA to add a new entity from the "Service name and Transport Protocol Port Number Registry" available at https://www.iana.org/assignments/service-name-port-numbers/¶
Service Name: tacacss¶
Port Number: [TBD]¶
Transport Protocol: TCP¶
Description: TLS Secure Login Host Protocol (TACACSS)¶
Assignee: IESG¶
Contact: IETF Chair¶
Reference: [TBDN] (This Document)¶
RFC EDITOR: this port number should replace "[TBD]" and the service name should replace "[TBDN]" within this document.¶
Considerations about service discovery are out of scope of this document.¶
The author(s) would like to thank Russ Housley, Steven M. Bellovin, Stephen Farrell, Alan DeKok, Warren Kumari, Tom Petch and Mohamed Boucadair for their support, insightful review, and/or comments. [RFC5425] was also used as a basis for the approach to TLS.¶