Stay secure

Take a deeper dive into Sociality.io security docs, which provide an overview of the security practices we’ve put in action so that social media teams can succeed with peace of mind.

Dedicated security team

Our security team is comprised of security experts dedicated to improving the security of our organization. Our employees are trained in security incident response and are on call 24/7.

Cloud infrastructure

All of our services run on the cloud. We don’t host or run our own routers, load balancers, DNS servers, or physical servers. Instead, our services are built on Amazon Web Services (AWS) and Google Cloud Platform. These platforms offer strong security measures that protect our infrastructure and are compliant with most certifications. You can read more about their practices here:

• •AWS
• •Google Cloud Platform

Network-level security monitoring and protection

Our network security architecture consists of multiple security zones. We monitor and protect our network to ensure that no unauthorized access is gained using:

• •A virtual private cloud (VPC), 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 (IDS/IPS) solution that monitors and blocks potential malicious packets
• •IP address filtering

DDoS protection

We use distributed denial of service (DDoS) mitigation services powered by an industry-leading solution.

Data encryption

Encryption in transit: All data sent to or from our infrastructure is encrypted in transit via industry best practices using Transport Layer Security (TLS). Encryption at rest: All our user data (including passwords) are encrypted using battled-proofed encryption algorithms in the database.

Data retention and removal

We retain your usage data for a period of 30 days after your trial. All of your data is then completely removed from the dashboard and server. Every customer can request the removal of their usage data by contacting support. Read more about our privacy settings at sociality.io/privacy.

Business continuity and disaster recovery

We back up all of our critical assets and regularly attempt to restore our backups to guarantee fast recovery in the case of disaster. All our backups are encrypted.

Application security monitoring

• •We use a security monitoring solution to gain visibility in our application security, identify attacks, and respond quickly to data breaches.
• •We use technologies to monitor exceptions, logs, and anomalies in our applications.
• •We collect and store logs to provide an audit trail of our applications’ activity.
• •We use monitoring methods such as open tracing in our microservices.

Application security protection

• •We use a runtime protection system that identifies and blocks OWASP Top 10 and business logic attacks in real time.
• •We use security headers to protect our users from attacks.
• •We use security automation capabilities that automatically detect and respond to threats targeting our apps.

Secure development

Our development process adheres to security best practices and frameworks, including the OWASP Top 10 and the SANS Top 25.In particular, 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 review our code for security vulnerabilities.
• •We regularly update our dependencies and ensure that none of them has any known vulnerabilities.
• •We use static application security testing (SAST) to detect basic security vulnerabilities within our codebase.
• •We use dynamic application security testing (DAST) to scan our applications.
• •We rely on third-party security experts to perform yearly penetration tests of our applications.

Responsible disclosure

For everyone who practices responsible disclosure and complies with our policies and terms of service, we encourage you to participate in our bug bounty program. Please avoid automated testing and only perform security testing with your own data. Please do not disclose any information regarding vulnerabilities until we fix them. Rewards will be granted at our discretion, depending on the criticality of the vulnerabilities reported.

Currently, in exchange for vulnerability detection, we are offering credits that you can use on Sociality.io plans. In the future, we will add more options.

You can report vulnerabilities by contacting [email protected]. Please include a proof of concept. We will respond to your submission as quickly as possible and won’t take any legal action if you follow the rules.

Coverage

• •*.sociality.io

Exclusions

• •sociality.io/blog

Accepted vulnerabilities include:

• •Cross-site scripting (XSS)
• •Open redirect
• •Cross-site request forgery (CSRF)
• •Command/file/URL inclusion
• •Authentication issues
• •Code execution
• •Code or database injections

The bug bounty program does NOT include:

• •Logout CSRF
• •Account/email enumerations
• •Denial of service (DoS)
• •Attacks that could harm the reliability/integrity of our business
• •Spam attacks
• •Clickjacking on pages without authentication and/or sensitive state changes
• •Mixed-content warnings
• •Lack of DNSSEC
• •Content spoofing/text injection
• •Timing attacks
• •Social engineering
• •Phishing
• •Insecure cookies for nonsensitive or third-party cookies
• •Vulnerabilities that require exceedingly unlikely user interaction
• •Exploits that require physical access to a user's machine

Two-factor authentication

We provide a two-factor authentication mechanism to protect our users from account takeover attacks. Setting up this extra security measure is optional but highly recommended to increase the security of sensitive data.

Account takeover protection

We protect our users against data breaches by monitoring and blocking brute force attacks.

Single sign-on

Single sign-on (SSO) is offered for our enterprise customers and can be accessed through a Google account.

Role-based access control

Role-based access control (RBAC) is offered on all our accounts and allows our users to define roles and permissions.

Payment information

All of our payment instrument processing is safely outsourced to Stripe, a certified PCI Level 1 Service Provider. We don’t collect any payment information and are thus not subject to PCI obligations.

Employee access

• •Our strict internal procedure prevents any employee or administrator from gaining access to user data. Limited exceptions can be made for customer support.
• •All of our employees sign a Non-Disclosure and Confidentiality Agreement upon joining the company to protect our customers’ sensitive information.