App-IDs for SSL-Secured Versions of Well-Known Services

App-IDs for SSL-Secured Versions of Well-Known Services

129233
Created On 09/25/18 17:41 PM - Last Modified 10/28/26 20:19 PM


Symptom


SSL/TLS-secured services such as SMTPS, IMAPS, POP3S, LDAPS, and FTPS may be identified as ssl instead of their corresponding protocol App-IDs (smtp, imap, pop3, ldap, or ftp) in PAN-OS Traffic logs.

As a result, a Security policy configured to allow only the protocol-specific App-ID may not match the traffic, causing the connection to be denied or dropped.



Environment


  • PAN-OS


Cause


Several well-known application protocols support encrypted communication using TLS.

These services can use two different TLS negotiation methods:

  1. Implicit TLS: The TLS handshake begins immediately after TCP connection establishment, typically on a dedicated secure port.

  2. Explicit TLS: The connection initially uses the application protocol, and encryption is subsequently negotiated using commands such as STARTTLS, STLS, or AUTH TLS.

When the application payload is encrypted, the firewall may identify the session as ssl rather than the underlying application.

Application identification depends on the available App-ID signatures, protocol decoding, observed traffic, and whether SSL decryption is performed.

Therefore, encrypted traffic is not guaranteed to be identified as the underlying protocol App-ID, even when a standard service port is used.



Resolution


Details

Many well-known services, including LDAP, IMAP, POP3, SMTP, and FTP, support TLS-secured communication.

Depending on how TLS is negotiated and whether decryption is enabled, the firewall may identify the traffic as ssl rather than the corresponding application.

Common SSL/TLS-Secured Services

ProtocolStandard PortImplicit TLS PortCommon TLS Mechanism
LDAPTCP/389TCP/636STARTTLS / LDAPS
SMTPTCP/25, 587TCP/465STARTTLS / SMTPS
IMAPTCP/143TCP/993STARTTLS / IMAPS
POP3TCP/110TCP/995STLS / POP3S
FTPTCP/21TCP/990AUTH TLS / FTPS

Note: Explicit FTPS commonly uses TCP/21 with AUTH TLS. FTPS may also require separate data connections, including passive-mode ports.

There are several approaches to configuring Security policies for these services.

Option 1: Use Explicit TLS Where Supported

Where supported by the client and server, use the protocol's explicit TLS negotiation mechanism on its standard port.

Examples include:

  • SMTP: STARTTLS

  • IMAP: STARTTLS

  • POP3: STLS

  • LDAP: STARTTLS

  • FTP: AUTH TLS

With explicit TLS, the firewall may identify the underlying protocol before encryption begins.

However, this does not guarantee that the final application classification will remain the protocol-specific App-ID. Identification depends on the protocol decoder, available signatures, and observed traffic.

Verify the application displayed in the Traffic logs.

Option 2: Create Service Objects and Allow the SSL App-ID

When encrypted traffic is identified as ssl, create a Security policy permitting the ssl application on the required destination port.

Step 1: Create the service object

Navigate to:

Objects > Services > Add

For example, create the following service object:

  • Name: IMAPS-TCP-993

  • Protocol: TCP

  • Destination Port: 993

Step 2: Configure the Security policy

Navigate to:

Policies > Security > Add

Example configuration:

FieldConfiguration
Source ZoneTrusted
Destination ZoneUntrust
Source AddressRequired client IPs
Destination AddressSpecific IMAPS server
Applicationssl
ServiceIMAPS-TCP-993
ActionAllow

Commit the configuration.

Repeat the procedure for other required services, such as TCP/465, TCP/995, TCP/636, and TCP/990.

Important: Allowing ssl on a specific destination port does not guarantee that only the intended application is permitted. Other TLS applications matching the same Security policy criteria may also be allowed.

Restrict the source and destination addresses and zones as appropriate.

When using a protocol-specific App-ID, verify whether its application-default ports include the required secure port.

Option 3: Create a Custom Application

For environments requiring more specific application identification, consider creating a custom App-ID using supported application signature contexts.

Certificate-related identification may be possible in some scenarios, depending on the TLS version and information visible to the firewall.

For example, TLS 1.3 encrypts certificate messages, which limits certificate-based identification without decryption.

Custom application signatures should be validated against representative application traffic before deployment.

Option 4: Enable SSL Decryption

SSL decryption may provide additional visibility into the underlying application protocol.

Depending on the traffic direction and deployment:

  • SSL Forward Proxy: Used for outbound connections from internal clients to external servers.

  • SSL Inbound Inspection: Used for inbound connections to servers for which the administrator controls the required certificate and private key.

Configure the appropriate Decryption policy and certificates.

After successful decryption, the firewall may identify the underlying protocol more specifically, depending on the application signatures and protocol support.

Note: Decryption does not guarantee that all encrypted services will be identified by their protocol-specific App-ID. Validate application behavior and decryption compatibility before deployment.

Verification

  1. Generate traffic to the required SSL/TLS-secured service.

  2. Navigate to Monitor > Logs > Traffic.

  3. Filter the logs by destination IP, port, or application.

For example, to find SSL traffic on TCP/993:

( app eq ssl ) and ( port.dst eq 993 )
  1. Review the following fields:

    • Application

    • Security Rule

    • Action

    • Destination Port

    • Session End Reason

  2. Verify that the session matches the intended Security policy.

If decryption is configured, also review the Decryption logs and confirm whether decryption was successful.

Troubleshooting

If the connection is not matching the expected Security policy:

  1. Verify the destination port used by the client.

  2. Check whether the traffic is identified as ssl or a protocol-specific App-ID.

  3. Verify that the Security policy permits the observed application and service.

  4. Check whether a Decryption policy applies to the traffic.

  5. Review the Traffic logs for denied sessions or unexpected session termination.

  6. Capture representative traffic to determine whether the application uses implicit or explicit TLS.

The following CLI commands can help inspect active sessions:

show session all filter source <source-ip>
show session all filter destination <destination-ip>
show session id <session-id>

Note: Session inspection commands require the relevant session to remain active in the firewall session table.

See Also



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClHqCAK&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language