Site Security

Industry leading, military grade protection to keep your information safe.

Our commitment to the protection of your data

The fileroom platform operates on the Heroku enterprise infrastructure, designed to protect your information from threats by applying security controls at every layer from physical to application. It provides the simplicity and success of the cloud, combined with the network and trust controls historically only available with on premise, behind the firewall deployments.

For additional information see:
Salesforce trust and compliance policies

Security assessments and compliance

Data centres

Our Heroku enterprise infrastructure is hosted and managed within Amazon’s secure data centres and utilises the Amazon Web Service (AWS) technology. Amazon continually manages risk and undergoes recurring assessments to ensure compliance with industry standards. Amazon’s data centre operations have been accredited under:

  • ISO 27001
  • SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
  • PCI Level 1
  • FISMA Moderate
  • Sarbanes-Oxley (SOX)

For additional information see:
AWS Security Policy

PCI

We use PCI compliant payment processor Braintree for encrypting and processing credit card payments.

Network security

Firewalls

Firewalls are utilised by our infrastructure to restrict access to systems from external networks and between systems internally. Security groups restrict access to only the ports and protocols required for a system’s specific function to mitigate risk.

Host-based firewalls restrict our application from establishing local host connections over the loopback network interface to further isolate our application.

DDoS Mitigation

Our Heroku infrastructure provides DDoS mitigation techniques including TCP Syn cookies and connection rate limiting in addition to maintaining multiple backbone connections and internal bandwidth capacity that exceeds the Internet carrier supplied bandwidth.

Spoofing and sniffing protections

Managed firewalls prevent IP, MAC, and ARP spoofing on the network and between virtual hosts to ensure spoofing is not possible. Packet sniffing is prevented by infrastructure including the hypervisor which will not deliver traffic to an interface which it is not addressed to. Heroku utilises application isolation, operating system restrictions, and encrypted connections to further ensure risk is mitigated at all levels.

Port scanning

Port scanning is prohibited, and every reported instance is investigated by our infrastructure provider. When port scans are detected, they are stopped, and access is blocked.

Data security

Customer applications

The fileroom application on the Heroku platform runs within its own isolated environment and cannot interact with other applications or areas of the system. This restrictive operating environment is designed to prevent security and stability issues. These self-contained environments isolate processes, memory, and the file system using LXC while host-based firewalls restrict applications from establishing local network connections.

For additional technical information see: Heroku dyno isolation

Heroku postgres

Fileroom data is stored in separate access-controlled databases per application. Each database requires a unique username and password that is only valid for that specific database and is unique to a single application.

Connections to fileroom postgres databases require SSL encryption to ensure a high level of security and privacy. Stored data is encrypted by fileroom’s applications to meet data security requirements.

System security

Heroku system configuration

Heroku’s system configuration and consistency is maintained through standard, up-to-date images, configuration management software, and by replacing systems with updated deployments. Systems are deployed using up-to-date images that are updated with configuration changes and security updates before deployment. Once deployed, existing systems are decommissioned and replaced with up-to-date systems.

Application isolation

Fileroom runs on the Heroku platform run within our own isolated environment and cannot interact with other applications or areas of the system to prevent security and stability issues. Our self-contained environment isolates processes, memory, and the file system while host-based firewalls restrict our application from establishing local network connections.

For additional technical information see:
Heroku dyno isolation

System authentication

Heroku’s operating system access is limited to Heroku staff and requires username and key authentication. Operating systems do not allow password authentication to prevent password brute force attacks, theft, and sharing.

Vulnerability management

Heroku’s vulnerability management process is designed to remediate risks without customer interaction or impact. Heroku is notified of vulnerabilities through internal and external assessments, system patch monitoring, and third-party mailing lists and services. Each vulnerability is reviewed to determine if it is applicable to Heroku’s environment, ranked based on risk, and assigned to the appropriate team for resolution.

New systems are deployed with the latest updates, security fixes, and Heroku configurations and existing systems are decommissioned as customers are migrated to the new instances. This process allows Heroku to keep the environment up-to-date. Since customer applications run in isolated environments, they are unaffected by these core system updates.

To further mitigate risk, each component type is assigned to a unique network security group. These security groups are designed to only allow access to the ports and protocols required for the specific component type. For example, user applications running within an isolated dyno are denied access to the Heroku management infrastructure as each is within its own network security group and access is not allowed between the two.

Heroku application security

Heroku undergoes penetration tests, vulnerability assessments, and source code reviews to assess the security of its application, architecture, and implementation. Third-party security assessments cover all areas of the platform including testing for OWASP Top 10 web application vulnerabilities and customer application isolation. Heroku works closely with external security assessors to review the security of the Heroku platform and applications and apply best practices.

Issues found in Heroku applications are risk ranked, prioritised, assigned to the responsible team for remediation, and Heroku’s security team reviews each remediation plan to ensure proper resolution.

Backups

Fileroom platform application

Fileroom’s application is automatically backed up as part of the deployment process on secure, access controlled, and redundant storage. Heroku uses these backups to deploy our application across the private cloud and to automatically bring our application back online in the event of an outage.

Fileroom postgres databases

Continuous Protection keeps data safe. Every change to data in our application is written to write-ahead logs, which are shipped to multi-datacentre, high-durability storage. In the unlikely event of unrecoverable hardware failure, these logs can be automatically 'replayed' to recover the database to within seconds of its last known state.

For additional technical information see:
Heroku pg backups

Fileroom configuration and meta-information

Fileroom’s configuration and meta-information is backed up every minute to the same high-durability, redundant infrastructure used to store your database information. These frequent backups allow capturing changes made to the running application configuration added after the initial deployment.

Heroku platform

From instance images to databases, each component is backed up to secure, access-controlled, and redundant storage. The platform allows for recovering databases to within seconds of the last known state, restoring system instances from standard templates, and deploying customer applications and data. In addition to standard backup practices, Heroku’s infrastructure is designed to scale and be fault tolerant by automatically replacing failed instances and reducing the likelihood of needing to restore from backup.

Disaster recovery

Fileroom applications and databases

Heroku automatically restores fileroom’s applications and databases in the case of an outage. The Heroku platform is designed to dynamically deploy our application within the Heroku cloud, monitor for failures, and recover failed platform components including our applications and databases.

Heroku platform

Heroku’s platform is designed for stability, scaling, and inherently mitigates common issues that lead to outages while maintaining recovery capabilities. The platform maintains redundancy to prevent single points of failure, can replace failed components, and utilises multiple data centres designed for resiliency. In the case of an outage, the platform is deployed across multiple data centres using current system images and data is restored from backups. Heroku reviews platform issues to understand the root cause, impact to customers, and improve the platform and processes.

Data retention and destruction

Fileroom defines what data our applications store and we can purge data from our databases to comply with our data retention requirements. Should we ever deprovision our application and the associated database, the database’s storage volume will be maintained on the Heroku platform for one week after which time its automatically destroyed rendering the data unrecoverable.

Any decommissioning of Heroku’s hardware is managed by AWS, the infrastructure provider, using a process designed to prevent customer data exposure. AWS uses techniques outlined in DoD 5220.22-M (“National Industrial Security Program Operating Manual “) or NIST 800-88 (“Guidelines for Media Sanitization”) to destroy data.

For additional information see:
AWS Security Policy

Privacy

Fileroom has a published privacy policy that clearly defines what data is collected and how it is used. Fileroom is committed to your privacy and providing transparency in all we do.
We take steps to protect the privacy of our customers and protect data stored within our application. Some of the protections inherent to the products include authentication, access controls, data transport encryption, HTTPS support for our applications, and encrypted stored data.

For additional information see:
Fileroom's Privacy Policy

Access to your data

Fileroom staff only have access to your data in your brand room, master files folder, content uploaded by you while ordering services and your delivery box. This is based on permission provided by you on sign-up and again during the ordering process. Fileroom staff does not have access to any information in your content room or any of your created personal folders.

Heroku staff does not access or interact with fileroom data or applications as part of normal operations. There may be cases where Heroku is requested to interact with fileroom data or applications at our request for support purposes or where required by law. Fileroom data is access controlled and all access by Heroku staff is accompanied by fileroom approval or government mandate, reason for access, actions taken by staff, and support start and end time.

Fileroom security best practices

Encrypt data in transit

Enable HTTPS for applications and SSL database connections to protect sensitive data transmitted to and from applications.

Encrypt sensitive data at rest

Encrypted stored files and data within databases to meet their data security requirements. Data encryption can be deployed using industry standard encryption and the best practices for our language and framework.

Secure development practices

Apply development best practices for our development language and framework to mitigate known vulnerability types such as those on the OWASP Top 10 Web Application Security Risks.

Authentication

Strong passphrase for user accounts and SSH keys, store SSH keys securely to prevent disclosure, replace keys if lost or disclosed, and use of Heroku’s RBAC model to invite contributors rather than sharing user accounts.

Logging

Logging is critical for troubleshooting and investigating issues. Fileroom can receive all 3 types of logs via syslog from the Heroku platform, choose to send logs to a Heroku add-on, or interact with logs in real-time through the Heroku client.

For additional technical information see:
Heroku logging

Need more information?

Please send an email to support@fileroom.com.au if you have questions for us. Alternatively, please complete a support request below and we will be in touch with you. For urgent or out of hours requests, please tick the relevant box on the form.

Support Request

Have more questions? Please visit our knowledge centre to learn more.