> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran/final-recommendations-for-cryptography.md).

# Final recommendations for cryptography

For all these reasons, it is recommended to use the exchange key management application for exchanges (interface and parameters) and also to use TRIPLE DES in the operational DES key (confidentiality) and RSA key in the exchange key (authentication), since this is clearly the most secure cryptographic system presented:

* In editran, indicate (X and Y are the subsystems that are defined)

```
|                       CRYPTOGRAPHY (Y/N).......: S                          |
| CRYPTOGRAPHIC VERSION......: 4 00                                           |
| DATA ENCRYPTION ALGORITHM.: AES1     AUTHENTICATION ALGORITHM ...: RSA      |
| LOCAL SUBSYSTEM...........: X        REMOTE SUBSYSTEM..........: Y        |
| LOCAL KEY:                                                                  |
| REMOTE KEY:                                                                  |
```

&#x20;If a table had to be prepared based on the security of the cryptographic system used, from lowest to highest, indicating the requirements:&#x20;

<table data-header-hidden><thead><tr><th width="227.65020751953125" valign="top"></th><th width="89.4814453125" valign="top"></th><th width="93.3045654296875" valign="top"></th><th width="223.79833984375" valign="top"></th><th width="215.3785400390625" valign="top"></th><th width="305.7777099609375" valign="top"></th></tr></thead><tbody><tr><td valign="top">Cryptography type</td><td valign="top"><p>Requires</p><p>DES</p></td><td valign="top"><p>Requires</p><p>RSA</p><p> </p></td><td valign="top"><p>Exchanged keys</p><p>without exchange key management</p></td><td valign="top"><p>Exchanged keys</p><p>with exchange key management</p></td><td valign="top">Drawbacks</td></tr><tr><td valign="top">Version 3.00, DES authentication, TD3C confidentiality</td><td valign="top">X</td><td valign="top"> </td><td valign="top">X</td><td valign="top"> </td><td valign="top">DES exchange key in clear text</td></tr><tr><td valign="top">Version 3.00, DES authentication, TD3C confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">X</td><td valign="top">It is better to exchange RSA keys</td></tr><tr><td valign="top">Version 3.00, RSA authentication, TD3C confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">Better to use exchange key management</td></tr><tr><td valign="top">Version 3.00, RSA authentication, TD3C confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">X</td><td valign="top"> </td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES1 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">Better to use exchange key management</td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES1 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">X</td><td valign="top">Better to use TD3C confidentiality</td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES2 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">Better to use exchange key management</td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES2 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">X</td><td valign="top">Better to use TD3C confidentiality</td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES3 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top">Better to use exchange key management</td></tr><tr><td valign="top">Version 4.00, RSA authentication, AES3 confidentiality</td><td valign="top">X</td><td valign="top">X</td><td valign="top"> </td><td valign="top"><p>X</p><p> </p></td><td valign="top"> </td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran/final-recommendations-for-cryptography.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
