AT-TLS (Application Transparent TLS)
E752536
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
All labels observed (1)
| Label | Occurrences |
|---|---|
| AT-TLS (Application Transparent TLS) canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8706952 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AT-TLS (Application Transparent TLS) Context triple: [z/OS Communications Server, supportsFeature, AT-TLS (Application Transparent TLS)]
-
A.
UTA (Using TLS in Applications)
UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
-
B.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
C.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
D.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: AT-TLS (Application Transparent TLS) Target entity description: AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
-
A.
UTA (Using TLS in Applications)
UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
-
B.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
C.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
D.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf | IBM z/OS networking function ⓘ |
| belongsTo |
z/OS Communications Server IP Services
ⓘ
linked to:
z/OS Communications Server
|
| canBeUsedWith |
IBM CICS
ⓘ
linked to:
CICS Transaction Server
IBM DB2 for z/OS ⓘ
linked to:
IBM DB2
IBM IMS ⓘ batch TCP/IP applications ⓘ |
| canProtect |
FTP traffic
ⓘ
HTTP and HTTPS traffic ⓘ TN3270 traffic ⓘ custom TCP applications ⓘ |
| category | transport-layer security technology ⓘ |
| configuredBy |
network administrators
ⓘ
z/OS system programmers ⓘ |
| configuredIn |
Policy Agent (PAGENT)
ⓘ
linked to:
Policy Agent
|
| developedBy | IBM ⓘ |
| documentedIn |
IBM z/OS Communications Server IP Configuration Guide
ⓘ
linked to:
z/OS Communications Server
IBM z/OS Communications Server IP Configuration Reference ⓘ
linked to:
z/OS Communications Server
|
| fullName | Application Transparent TLS ⓘ |
| integratesWith |
TCP/IP stack on z/OS
ⓘ
z/OS Communications Server ⓘ |
| operatesAt | transport layer ⓘ |
| operatesOn | TCP connections ⓘ |
| primaryGoal |
separate security from application logic
ⓘ
simplify deployment of TLS on z/OS ⓘ |
| provides |
TLS decryption
ⓘ
TLS encryption ⓘ application-transparent TLS protection ⓘ |
| requires | no application code changes ⓘ |
| runsOn |
IBM mainframe
ⓘ
z/OS ⓘ |
| securityDomain | network security ⓘ |
| supports |
inbound connections
ⓘ
outbound connections ⓘ |
| supportsEnvironment |
high-availability mainframe workloads
ⓘ
sysplex ⓘ |
| supportsFeature |
cipher suite negotiation
ⓘ
client authentication ⓘ server authentication ⓘ session resumption ⓘ |
| supportsProtocol |
SSL (legacy)
ⓘ
linked to:
SSL
TLS ⓘ |
| transparentTo | applications ⓘ |
| usedFor |
encrypting data in transit
ⓘ
meeting compliance encryption requirements ⓘ securing client-server communications ⓘ |
| uses |
System SSL on z/OS
ⓘ
digital certificates ⓘ policy-based rules ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: AT-TLS (Application Transparent TLS) Description of subject: AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.