Áú»¢¶Ä²© follows a strict process when developing new versions of our software, according to the? Áú»¢¶Ä²© life cycle and release policy. All tasks are subject to strict standards imposed by Áú»¢¶Ä²©:?
To assure our customers that Áú»¢¶Ä²© is a well-managed and professional organization, that appropriate information security measures are applied as necessary, and that customers can trust the source code, our professional services, and our Áú»¢¶Ä²© Cloud service, Áú»¢¶Ä²© has:?
Every customer's Áú»¢¶Ä²© instance is isolated from one another.?
Every customer's Áú»¢¶Ä²© instance data is on EBS volumes and encrypted at-rest with AES-256.
Every customer node uses Amazon Time Sync Service NTP pools (time.aws.com) as a time source.
AWS Snapshot technology and EBS encryption with AES-256 at-rest data encryption is used for customer backups.
All in-transit communications both internally and externally use at least TLS 1.2 and (where possible) TLS 1.3 certificates.
Áú»¢¶Ä²© Cloud provides multiple ways of user authentication:
Local accounts: Users can sign up with a valid email address and set their password in the Áú»¢¶Ä²© Cloud platform. OTP codes are used for security purposes.
Existing accounts: Users can also leverage their existing Github, Google, and Microsoft accounts to use Áú»¢¶Ä²© Cloud with the single sign-on functionality.
Customer passwords for local accounts are protected with a BCRYPT hashing algorithm, so Áú»¢¶Ä²© employees do not have access to your password and cannot retrieve it for you. The only option if you lose your password is to reset it.
In cases where Áú»¢¶Ä²© employees need to connect to a customer's backend or frontend components, review log files, solve any issue with Services, at a customer¡¯s explicit request for technical support reasons, or as required by law, we use combination of enterprise grade key management services and secret management technologies. There are no standing privileges for engineers or support team. We practice Just-in-Time access for as brief a period as possible.??
Every employee working within Áú»¢¶Ä²© and accessing Áú»¢¶Ä²© Cloud in any way is using company owned and managed devices with XDR and at-rest encryption.
Multiple sets of best practices are used ¨C systems are hardened using CIS, AWS VPC best practices, AWS IAM best practices, etc.
We have several internal solutions in place that are used for monitoring our systems, availability, performance, and other critical parameters.
System availability can be checked at
Before reporting the issue:
Make sure that the issue you are submitting is not related to server configuration, 3rd party scripts and utilities. In order to avoid any possible issues with server configuration we advise Áú»¢¶Ä²© users to read
Best practices for secure Áú»¢¶Ä²© setup.
in the Áú»¢¶Ä²© Security Reports (ZBXSEC) section of the public bug tracker describing the problem (and a proposed solution if possible) in detail. This way, we can ensure that only the Áú»¢¶Ä²© security team and the reporter have access to the case.
The following information will be helpful for the Áú»¢¶Ä²© Security team:
Developed in partnership with HackerOne, the world's leading platform for ethical hackers, the Áú»¢¶Ä²© bug bounty program contributes to the security of the product by allowing hackers to discover potential security vulnerabilities in different Áú»¢¶Ä²© components. The program offers up to $3,000 as a reward for discovering and reporting a bug. More information can be found in the .