SafetyCulture’s mission is to help companies achieve safer and higher quality workplaces all around the world through innovative mobile products. We deliver on our mission through our flagship Software-as-Service (SaaS) products such as SafetyCulture (iAuditor) and EdApp. Our products are used by more than 27,000 companies around the world in many industries in a variety of use cases.
We take pride in that SafetyCulture is a world leader in products that promote safety and quality and we know how important our role is in helping our customers improve their day-to-day operations.
We see our approach to cyber security as a key pillar in maintaining our status as a leader in this space, and this content summarizes how we approach cyber security as an organization.
SafetyCulture has an active, robust and continually improving cyber security program in place to ensure that our organization and the products we provide are secure. SafetyCulture’s cyber security program employs several controls at a technical and operational level to ensure that we have an effective, defense-in-depth approach to protect from cyber-attacks and secure the data handled by our SaaS applications.
Key features include:
The content below summarizes the various parts of our security program.
Our approach to security is focused on aligning with recommended best practices in recognized standards such as the NIST, ISO27001 and SOC frameworks.
SafetyCulture has a documented set of policies and procedures that define our approach to security as an organization. These policies and procedures are shared with all staff and reviewed and updated at least annually (and more frequently when material changes are required) to ensure our approach to security remains current.
We focus on ensuring accountability for security throughout our company. We have an information security management forum set up with key stakeholders from across SafetyCulture that regularly meet to review and discuss security related matters and make any decisions that have an influence on our approach to cyber security.
We ensure that access to systems in our IT environment, including the cloud platforms we use, is restricted to employees who specifically require this access for their work.
All administrator access requires multi-factor authentication, and employees accessing our environment are required to use an approved VPN solution.
Access permissions to our systems are regularly reviewed on an employee-by-employee basis and changed promptly. As part of our off-boarding process, all access to systems and services for departing employees is revoked.
We carefully review the security practices of third parties we engage – initially and actively to ensure their practices meet industry standards and comply with our own privacy and security policies and procedures. If a third party requires access to our systems, we ensure that access is limited specifically to the purpose for which they have been engaged.
As Amazon Web Services (AWS) is one of our primary providers, we engage with them using the Shared Responsibility Model for security and compliance, ensuring there is a clear definition of who assumes responsibility for what for security. AWS is accredited by and compliant with many of the latest industry standards – more information can be found here: https://aws.amazon.com/artifact.
For the processing of financial and credit card data, SafetyCulture uses several partners (Chargify, eWay and Stripe) whose security practices comply with the Payment Card Industry Data Security Standard (PCI-DSS).
SafetyCulture’s corporate networks are protected with firewalls. We have Intrusion Detection System (IDS) and Intrusion Penetration System (IPS) technology at the perimeter provided by dedicated network security devices so that we can detect and protect against any malicious traffic.
For our cloud-based platforms, we primarily use Amazon Web Services (AWS) who provide a multi-layered strategy to defend from external attacks. At an infrastructure level, AWS employs strategies such as network device access control, data segregation using firewalls and virtual private clouds to filter out malicious traffic and make use of extensive logging and monitoring to prevent network-based attacks. At an application level, we take advantage of Cloudflare’s Web Application Firewall (WAF) and Distributed Denial of Service (DDoS) protection to prevent web-based and denial of service attacks against our products.
SafetyCulture makes use of a centralized logging system, which includes application access audit events. These logs are retained for 90 days. We also use Amazon Elastic Load Balancing (ELB) logs to track service access requests (successful or not). Logs stored in AWS cannot be modified and access is restricted to those who require it for their role requirements.
We recognize the importance of reviewing logs regularly to identify malicious user activity and identify potential vulnerabilities with our products; we have automated monitoring in place that alerts us to specific types of potentially malicious events within our global infrastructure.
All SafetyCulture personnel undergo regular security awareness training for technical and non-technical roles. Additional security training material is provided to individual staff where required to ensure they are equipped to handle the specific security-oriented role challenges of their role.
Patching of our IT environment is one of the most important measures we take to stay secure against a potential security breach. To achieve this:
SafetyCulture takes the security of our customer’s data extremely seriously. We take several steps to ensure customer data is carefully protected.
SafetyCulture takes several measures to help protect customer data from inappropriate access or use by unauthorized persons (either external or internal). Customer data is only stored in our production environment, and access to that data by SafetyCulture employees is limited only to the employees who require access to perform their standard duties. Access to customer data is managed using access control and authentication tools (including the use of two factor authentication) provided by Amazon Web Services and our other cloud partners.
When SafetyCulture support employees need to access to specific customer data (for troubleshooting or support purposes) then SafetyCulture will always require consent from a customer before accessing this data.
We do not store or cache customer’s financial data used for billing through the SafetyCulture platform and our employees do not have direct access to billing data.
Customer data is hosted on infrastructure provided by Amazon Web Services which maintains physical security of their sites using industry best practice controls as outlined in their security and compliance website found here: https://aws.amazon.com/architecture/security-identity-compliance/.
No customer data is stored at our physical office locations.
SafetyCulture has mechanisms in place to ensure that our customers’ data is protected both at rest and when in transit. At rest, all customer data stored in systems is encrypted using AES-256 with keys managed through Amazon Web Services’ Key Management Service. All data is stored securely and subject to the security policies and procedures of AWS.
To protect data in transit, SafetyCulture uses Transport Layer Security (TLS) and enforces a minimum standard of TLS v1.2 using 128-bit cipher keys. We support connections with up to 256-bit cipher keys for use with an Advanced Encryption Standard (AES) cipher.
SafetyCulture data is backed up at regular intervals to disparate encrypted data storage solutions provided by Amazon Web Services. Backups are replicated to multiple AWS facilities within the AWS region.
Access to data backups is restricted to only those specific employees of SafetyCulture where that access is needed as part of their role requirements. Backups are encrypted and is stored in a read-only mode.
Our customer data is stored in, and subject to, the deletion and disposal procedures of Amazon Web Services. These procedures include a process to wipe secure retired media. Wiped media is then inspected to ensure to ensure the successful destruction of data.
Any SafetyCulture owned hardware that contains confidential data – including SafetyCulture backups – is subject to industry standard logical data destruction before recycling.
We recognize that for the bulk of customers, their principal experience with SafetyCulture will be through our products. Security forms an important part of the way this product is developed and operates, as discussed below.
As part of our product development process, every code and infrastructure change is reviewed prior to the release of the change into production. This review includes observance of security best practice. We also segregate our development, test and production environments, and do not use customer data in our non-production environments.
All changes to SafetyCulture products are actively tested during their development to ensure the impact to end users is evaluated prior to deployment. Any significant changes are included in the production release notes.
SafetyCulture employs change tracking and version control systems to monitor actively and manage changes to the code base or configuration of our infrastructure. We use automated processes to deploy changes to our environments and can revert changes as required. We use Amazon CloudTrail to track any underlying configuration changes to the cloud platform on which our products operate.
We work hard to minimize the number of vulnerabilities that arise in our products, and we recognize it is important to take proactive steps to make sure we address any vulnerabilities as quickly as possible. To that end, SafetyCulture performs annual penetration tests, and actively tests and monitors for vulnerabilities in our applications. We run a private bug bounty program because a community of independent security researchers incentivized to test our products actively to identify any potential issues will only strengthen the security of our products.
Where a vulnerability is identified (internally or externally) the issue is tracked and prioritized according to the potential severity of impact to our customers. For critical severity issues, this can include round-the-clock work by our developers until the issue is remediated.
Patches for issues are developed and released into the production environment through a continuous integration process (CI/CD) and applied as soon as possible.
Whilst we do our utmost to prevent any security incidents, we recognize that we also need to be prepared to handle these incidents should they arise to minimize the potential impact on our customers and SafetyCulture.
We have a range of measures in place, including:
SafetyCulture considers cyber security a fundamental part of our business, and of the products we provide to businesses around the world. Whilst the controls and measures we have in place extend significantly beyond what is covered here, this content serves to provide an overall understanding of the multi-faceted approach we take and our commitment to security.
If you have questions about the contents, or require more information about our approach to support, security or privacy, please contact us at the details below: