RB2B is built with security by design, meaning encryption, privacy, and data integrity are foundational elements across every part of the platform. We use industry-leading encryption standards to protect customer data both in transit (as it moves between systems) and at rest (when stored in our databases).
This article provides an overview of the encryption methods and protocols RB2B uses to ensure that your data remains private, secure, and tamper-proof at every stage.
Encryption Overview
Encryption is the process of converting readable information into encoded data that can only be deciphered with the proper cryptographic key.
At RB2B, encryption is applied at multiple layers to provide comprehensive protection:
At rest — when data is stored in databases or backups.
In transit — when data moves between servers, services, or devices.
During authentication and API interactions — when user data or credentials are exchanged between your system and RB2B.
These layers work together to protect your information from unauthorized access and interception, even in the unlikely event of a security breach.
Database Encryption (At Rest)
All RB2B databases are encrypted at rest. This means that when data is not actively being accessed or modified, it remains encrypted and unreadable to anyone without the appropriate credentials or encryption keys.
RB2B uses AES-256 (Advanced Encryption Standard, 256-bit) — the same algorithm trusted by banks, governments, and major technology providers.
Data is stored in an encrypted format that protects against both digital and physical intrusion.
Encryption keys are stored and managed securely through controlled key management systems with strict access policies.
This ensures that even if a physical or network security control were to fail, the stored data would remain protected and indecipherable.
Secure Queue Service (SQS) Encryption in Transit
RB2B uses a Secure Queue Service (SQS) to handle asynchronous processing between internal services. All messages sent through this service are encrypted while in transit.
Messages containing identifiers, metadata, or workflow instructions are protected as they travel between RB2B systems.
We use TLS 1.3 (Transport Layer Security) to ensure that these communications cannot be intercepted or altered.
Encryption keys are managed using secure, cloud-based key management systems that meet current compliance standards.
This guarantees that data exchanged between RB2B services remains confidential and tamper-proof.
Endpoint and API Encryption
All communication with RB2B service endpoints is encrypted using SSL/TLS to ensure secure transmission between your device and RB2B systems.
This applies to all primary communication channels, including:
API requests and responses — All data exchanged with the RB2B API is encrypted to prevent exposure or unauthorized interception.
User authentication and session data — Login credentials, tokens, and session information are encrypted to prevent credential theft or replay attacks.
Data transfer events — Any data moving through the dashboard or integrations is protected with TLS 1.3, ensuring the strongest encryption available.
Through these measures, RB2B ensures that no sensitive information is ever transmitted in plain text.
HTTPS for Website Security
The RB2B dashboard and all associated web properties are served exclusively over HTTPS (Hypertext Transfer Protocol Secure), which provides a secure communication channel between the user’s browser and RB2B servers.
HTTPS ensures that the data transmitted between browser and server cannot be read or modified by third parties.
The connection is protected using SSL/TLS encryption.
Users can verify secure access by checking for the lock icon in the browser’s address bar.
This guarantees that any data entered through the RB2B web interface remains encrypted and confidential during transmission.
Signature Algorithm: SHA-256 with RSA Encryption
To ensure the integrity and authenticity of data transmitted between systems, RB2B uses the SHA-256 with RSA signature algorithm.
SHA-256 is a cryptographic hash function that verifies data integrity by producing a secure, fixed-length hash for transmitted content.
RSA encryption ensures that only authorized parties can verify the authenticity of signed data.
Together, these technologies prevent tampering and confirm that received data originates from a trusted RB2B source.
This combination provides cryptographic assurance that your data has not been modified, intercepted, or falsified during transfer.
TLS 1.3 for Data in Transit
RB2B enforces TLS 1.3 for all data transmitted to and from its systems. TLS 1.3 is the most recent and secure version of the Transport Layer Security protocol and provides several improvements over earlier versions:
Stronger encryption algorithms and key exchange mechanisms.
Reduced latency through a simplified handshake process.
Forward secrecy, ensuring that even if future keys were compromised, past data transmissions would remain protected.
All customer communications, API traffic, and service-to-service data transfers use TLS 1.3 by default.
Summary
RB2B employs multiple layers of encryption to protect your data in every state:
Encryption Type | Protection Scope | Protocol / Standard |
Database Encryption | Data stored at rest | AES-256 |
Message Queue Encryption | Internal system messages | TLS 1.3 |
API and Authentication | User and system communications | TLS 1.3 |
Website Traffic | Browser-to-server connections | HTTPS (SSL/TLS) |
Data Integrity Verification | Authenticity and tamper protection | SHA-256 with RSA |
In summary, RB2B uses AES-256 for stored data, TLS 1.3 for transmitted data, and SHA-256 with RSA for authenticity and validation. These standards represent the highest levels of security currently available, ensuring that your data remains protected, encrypted, and trusted at all times.