Encryption and signing
Encrypting, decrypting and signing data from application code: a document wrapped for one recipient, a payload signed so its origin can be checked, a value enciphered with a key both sides hold. Encryption of a connection, TLS, is set up in the system and is outside this concern.
Overview
The SSF library for the ABAP stack creates and verifies PKCS#7 digital signatures and encrypts and decrypts documents, through SSF_KRN_SIGN, SSF_KRN_VERIFY, SSF_KRN_ENVELOPE and SSF_KRN_DEVELOPE.
Not covered: At PKCS#7. The SSF page names no call for a symmetric cipher such as AES or Blowfish in a chosen mode, and none for OpenPGP.
How the community cipher implementations relate to the SSF library has not been assessed.
On BTP the concern is where the keys are kept: the application runs the signing or the encryption in its own code and retrieves the keystore from a service instead of carrying it in its bundle.
SAP Keystore ServiceSAP Keystore ServiceA repository for cryptographic keys and certificates in SAP BTP's Neo data centres, which an application retrieves at runtime for signing, encryption and SSL communication.sap official, btp holds the keys and certificates an application retrieves at runtime and uses itself to sign and verify digital signatures and to encrypt and decrypt messages.
Not covered: In the Neo environment. Its one plan is listed in Neo data centres and in Moscow and Riyadh, and in the regions marked Neo the service leaves the Eligible Cloud Services List on December 31, 2028.
One provider on this door and it is SAP's, so core-only is a assessment of the corpus rather than a quote from the core.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:encryption- JSON
- /capabilities/encryption.json
- MCP
- Connecting an agent