Secure and compliant DAM software

Even with AWS’s excellent record of data redundancy in S3, we use an entirely different set of S3 buckets to store your backups.

Any asset you upload to Asset Bank will be instantly replicated to this secondary bucket, where it will be safely stored until 90 days after you remove the original asset from Asset Bank.

Our comprehensive disaster recovery strategy also means that database and application backups are taken regularly so that we can restore your entire application with a Recovery Point Objective (RPO) of, maximum, twelve hours.

Access to any technical system at Asset Bank is granted in line with our ISO-compliant access control policies, utilising roles-based access and the principle of least privilege.

To gain access to our AWS cloud environment, the connection must be made from our own IP address using a secure, encrypted tunnel. And, in a world of hybrid working, our VPN is managed so that only approved devices may access our networks.

Our Asset Bank security management team is trained in – and tests – our ISO-compliant business continuity plan to make sure that, in the event of a disaster, we are able to resume our service as soon as possible. But with your data in AWS and our distributed workforce, we’re minimising the risk of any one event affecting our service in any way.

When you access Asset Bank via your web browser, your connection is secured with HTTPS encryption, ensuring your activity remains private and protected from interception.

Our certificates use Let’s Encrypt to automatically re-issue expiring certs, and you can choose a custom domain for your app too.

Your digital assets, stored in AWS S3, and the metadata in the database, is encrypted at rest. This means that, even if your data was compromised in any way, it would not be readable by the threat actor. All backups are also encrypted in transit and at rest.