Hierarchy

⤷

⤷

IMG Activity
ID | ECHVC_ENCRYPTION | Define Encryption of the Paylod |
Transaction Code | S_SI3_21000034 | (empty) |
Created on | 20120424 | |
Customizing Attributes | ECHVC_ENCRYPTION | Define Encryption of the Paylod |
Customizing Activity | ECHVC_ENCRYPTION | Define Encryption of the Paylod |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ECHVC_ENCRYPTION |
Use
You use this Customizing activity to encrypt the payload of postprocessing orders on database level for better data security. You can assign an encryption key to the business processes of the error and conflict handler. You use this key to encrypt the payloads of newly created postprocessing orders.
This means that all appropriately configured postprocessing order payloads are encrypted when stored in the database. Users that start a database query, for example, with SQL, cannot read the contents of the payload.
Requirements
Before you can assign an encryption key, you first need to define the encryption key and determine the personal security environment (PSE). Proceed as follows:
- Choose Application-Specific SSF Parameters (Transaction SSFA).
- Choose New Entries.
- Select the SSF application ECH Key 1 - Payload Encryption This SSF application is included in this delivery.
- Choose Save.
- Select a secure encryption algorithm, such as TRIPLE_DES.
- Save your changes.
- Repeat these steps for the SSF application ECH Key 2 - Payload Encryption.
- Select Trust Manager (Transaction STRUST).
- Position the cursor on the entry ECH Key 1 - Payload Encryption.
- In the context menu, choose Create.
- Select RSA as the algorithm.
- Repeat these steps for the entry ECH Key 2 - Payload Encryption.
- Check whether the entries for all application servers are correct (green light).
Note
Note the following recommendations in your activities involving transaction STRUST:
- Select an appropriate key length (2048 bytes are recommended).
- If the scenario requirements allow it, select a suitably long validity time for the key. Otherwise, take the appropriate measures to prepare your business processes and systems for the key procedure.
- Create a backup copy of the key by exporting it.
- If you want to delete a key, check your plan first. Some messages that cannot be read with the key may still be saved to the database.
Check the use of the key
You can find out which payloads have been encrypted with each encryption key.
Example
If a key has been disclosed, you can find out whether it is still being used for payload encryption. To do so, execute the following step:
- Select the Object Navigator (Transaction SE80).
- Start the Encrypting and Reassigning Payloads program (FEHR_CHANGE_ENCRYPTION_KEY).
- Run the simulation.
Use the Simulate Processes function to determine the number of payloads that have been encrypted with this key. If you have changed or deleted the encryption key in this Customizing activity, you can encrypt, reassign, or decrypt payloads.
Standard settings
If no entry exists for a business process or if no encryption key is specified, then the payload is not encrypted when saved to the database.
Activities
- Assign an encryption key to the required business process by selecting one in the Private Address Book for SSF field.
- Save your entries.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | ECHVC_ENCRYPTION | 0 | ABA0000491 | Error and Conflict Handler |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
ECHVC_ENCRYPTION | V - View | SM30 |
History
Last changed by/on | SAP | 20120425 |
SAP Release Created in | 732 |