Security capabilities
B2B Integration SaaS security options include both secure protocols/transport methods and secure communications.
Secure protocols and transport methods
Several options exist to ensure secure communications. Using a Co-Managed VPN provides secure data encryption and authentication for communicating over the open internet. You can safely use any of the above protocols with a Co-Managed VPN connection. Without a Co-Managed VPN, another secure option is recommended.
The following table shows protocols that you should not use over the open internet because the data is not encrypted:
| Communications Protocol | Note |
|---|---|
| Connect:Direct® | Use Connect:Direct with a Secure + option. |
| EDIINT AS2 | You should not use EDIINT AS2 with plain text payload over HTTP. |
| FTP | |
| HTTP | |
| MQ | Use MQ with a secure channel. |
| POP3 | |
| SMTP | |
| SOAP | You should not use SOAP with plain text payload. |
|
X.400 |
In order to have secure communications there are several options. Using a Co-Managed VPN provides secure data encryption and authentication for communicating over the open internet. You can safely use any of the above protocols with a Co-Managed VPN connection.
The following table shows protocols that can be used without a Co-Managed VPN because they provide a layer of encryption. Therefore, no Co-Managed VPN is needed.
| Encrypted Communications Protocol | Note |
|---|---|
| ANX | |
| Connect:Direct | Requires Secure + option. |
| EDIINT AS1 | |
| EDIINT AS2 | Encrypted payload over HTTP or HTTPS. Using the compression option increases security. |
| SFTP | Not like traditional FTP, different protocol layered over SSH. |
| FTPS | Traditional FTP layered over a Secure(TLS) channel. |
| FTP/PGP | Traditional FTP with PGP encrypted payload. |
| HTTPS | |
| MQ | If using a secure channel. |
| OFTP2 | ODETTE-FTP layered over Secure(TLS) channel. |
| SOAP | With encrypted payload. |