All of our services run in the cloud. We don’t host or run our own routers, load balancers, DNS servers, or physical servers.

• Our service is built on Amazon Web Services (AWS). They provide strong security measures to protect our infrastructure and are compliant with most certifications. 🔗 View AWS Security Information

• Brolly is a multi-tenant platform, and customer data is segregated logically. The logical separation has been extended throughout the entire platform to prevent customers from accessing one another’s data

Our network security architecture consists of multiple security zones. We monitor and protect our network to make sure no unauthorised access is performed using:

• A virtual private cloud (VPC), a bastion host or VPN with network access control lists (ACLs) and no public IP addresses.

• A firewall that monitors and controls incoming and outgoing network traffic.

• An Intrusion Detection and/or Prevention technologies (IDS/IPS) solution that monitors and blocks potential malicious packets.

• IP address filtering

• We use systems to monitor and protect our infrastructure from automated scanners, bots and targeted attacks. It blocks attacks and alerts in case of critical threats. It also brings additional features like IP blocking etc.

• Multi-factor authentication (MFA) and role-based access

• IP whitelisting and user-level permissions

• Least-privilege admin access

We use Distributed Denial of Service (DDoS) mitigation services powered by an industry-leading solution.

All data within the Brolly platform is transmitted over HTTPS and uses AES-256 encryption at rest & TLS 1.2+ encryption in transit.

Encryption in transit

• All data sent to or from our infrastructure is encrypted in transit via industry best practices using Transport Layer Security (TLS). 🔗 View our SSLLabs report.

Encryption at rest

• All our user data (including passwords) is encrypted using battled-proofed encryption algorithms in the database.

We retain our users’ data for a period of 90 days after the trials end. All data is then completely removed from the dashboard and server. Users can request the removal of their usage data by contacting support. Read more about our privacy settings.

We back up all our critical assets and regularly test the restoration of the backups to ensure a swift recovery in the event of a disaster. All our backups are encrypted.

• We use a real-time security monitoring solution to get visibility into our application security, identify attacks and respond quickly to a data breach.

• We use technologies to monitor exceptions, logs and detect anomalies in our applications.

• We collect and store logs to provide an audit trail of our applications activity.

• We use systems to monitor our applications. Security events are logged and notifications are sent in case of critical attacks to allow for fast remediation.

• View the latest independent penetration test

We develop the following security best practices and frameworks (OWASP Top 10, SANS Top 25). We use the following best practices to ensure the highest level of security in our software:

• Developers participate in regular security training to learn about common vulnerabilities and threats

• We use Secure Development Lifecycle (SDLC) with static analysis and pre-release testing

• We review our code for security vulnerabilities

• We regularly update our dependencies and make sure none of them has known vulnerabilities

• We use Static Application Security Testing (SAST) to detect basic security vulnerabilities in our codebase

• We use Dynamic Application Security Testing (DAST) to scan our applications

Account takeover protection – We protect our users against data breaches by monitoring and blocking brute force attacks.

• Our strict internal procedure prevents any employee or administrator from gaining access to user data. Limited exceptions can be made for customer support.

• Our employees undergo police checks, sign a Non-Disclosure and Confidentiality Agreement to protect our customers’ sensitive information.