AmqpHosting Security Policy

This Security Policy was last revised on December 21, 2016.

A certain amount of confidence is needed when relying on third party vendors to manage and handle your online data securely. Cloud security is important, because it is essential for protecting hosted information - we understand that even small gaps in security coverage can put everything at risk including your data, customer information, uptime, and potentially a company’s reputation. Therefore the need exists for a general understanding of what we at AmqpHosting are doing to protect the integrity of your data.

This document will give a brief introduction to the security policies in AmqpHosting. It is a living document that is continually updated. Our security policies are not limited to this document, effective security is a team effort that we evolve all the time. We routinely audits and manages the security of our services and applies security best practices.

Our internal development, operations, and processes themselves have been constructed to provide maximum data security.

1. System security
1.1 Coding standards and development
A well built environment starts with high coding standards that guard against attempted security breaches and are accompanied by code reviews and tests. We have strict development processes and we are following specified coding standards to ensure the best security practices.

1.2 Application Security
System components undergo tests (various black box and white box tests) and source code reviews to assess the security of our application interface, architecture, and services layers before we deploy code into production. AmqpHosting always reviews third-party applications before we adopt them into AmqpHosting services.

1.3 System Configuration
Server and system access is limited to some people in AmqpHosting and requires ssh keys when identifying trusted computers along with usernames and passwords. Furthermore, everyone at AmqpHosting is mandated to enable 2-factor authentication on every cloud platform that provides it. We do not share individual authentication credentials.

1.4 Patch Management
AmqpHosting always applies patches based on advisory for our servers, and associated devices. Critical patches are applied within 48 hours of release of the patch.

2 Physical Data Center Security
Our physical infrastructure is hosted and managed on a range of different datacenter’s (DigitalOcean, Linode, Hetzner, AWS etc). We rely on their flexible and secure cloud infrastructure to store data logically. The data centers ensures the utmost in data security and protection. They all ensure that all data is stored in highly secure data centers. All data centers that run our solution are secured and monitored 24/7. Physical access to datacenter facilities is strictly limited to select cloud staff. They continually manage risk and undergo recurring assessments to ensure compliance with industry standards.

How specific datacenters are handling fire detection, power loss, climate disasters, temperature control, datacenter management, etc., can be found on the respective datacenters' websites.

3 Customer Data Security
AmqpHosting provides several security capabilities and services to increase privacy. No one will be able to connect or view your RabbitMQ server as long as you take care of your connection credentials.

3.1 AmqpHosting employees
A few employees at AmqpHosting will have the possibility to access the server/s. We ensure that we will not view any messages sent across our servers without permissions. AmqpHosting cannot access message payloads that have been encrypted at client level.

3.2 Data in Transit
AmqpHosting uses SSL/TLS to secure data in transit. SSL certificates are updated on a regular basis or in an event of a security advisory from external security centers. You have to enable TLS/SSL to and from your application to ensure secure transit between AmqpHosting and your application.

3.3 Data in rest
Messages and payloads can be encrypted for additional security of data at rest.

3.4 Security capabilities - Customer Best Practices
This section describe what you can do to protect your account in the best way possible.

3.4.1 Password protection
You are responsible for maintaining the secrecy of your unique password and account information at all times. We recommend that you use a strong password preferably generated by a good password generator/manager.

3.4.2 Unusual account activity
We want to keep you in the loop on important actions on your AmqpHosting account. Therefore we will notify you via email if we detect something unusual about a recent access.

3.4.3 TLS and encrypted data
AmqpHosting does support TLS(SSL) where you can encrypt your data in transit to protect sensitive data transmitted to and from applications. Note that TLS will only secure messages during the transport. What we recommend for highly sensitive information (HIPAA, PCI etc) is that you encrypt your message bodies on your side and that you have a shared key between your publishers and your consumers.

Contact us
Please feel free to contact us with any questions about this Security Policy, suggestions or concerns about any of the points outlined above at

"Advanced Message Queueing Protocol (AMQP 0-9-1)" are trademarks of The AMQP Working Group.
RabbitMQ and the RabbitMQ logo are trademarks of Pivotal Software, Inc. (“Pivotal”)
"OASIS" and "Advanced Message Queueing Protocol (AMQP) v1.0" are trademarks of OASIS, the open standards consortium where the (AMQP) v1.0 specification is owned and developed. (AMQP) v1.0 is a copyrighted © work of OASIS Open.
All rights reserved. All copyrights & trademarks belong to their respective owners.
The copyright & trademark owners/holders are not connected with and do not sponsor or endorse AmqpHosting.