Security at Magna

Keeping our customers' data secure is the most important thing that Magna does. We go to considerable lengths to ensure that all data sent to Magna is handled securely - keeping Magna secure is fundamental to the nature of our business. We want to share some of the details of what we do to keep things secure, and some of the work that we're doing to continually improve the security of your data. This document is a living document, and we will add to it from time to time. You are probably also interested in checking out our Terms of Use and Privacy Policy too. If you have any questions, as ever please contact us at .

Our team has relevant experience

Our team includes people who've played lead roles in designing, building and operating highly secure Internet facing systems, such as payment processing platforms, cloud services and content distribution networks. We also have people who've successfully built a number of startups from scratch, and others who have worked in well established smaller Internet businesses.

We host in world class facilities

The vast majority of our services and data are hosted in Amazon Web Services facilities in the USA. Further details about the considerable measures Amazon take in securing their facilities and services can be found here:

We follow best practices

At Magna we follow a number of best practices that improve our security posture. Here are a few examples:

We have functioning, frequently used automation in place so that we can safely and reliably rollout changes to both our application and operating platform within minutes. We typically deploy dozens of times a day, so we have high confidence that we can get a security fix out quickly when required.
All data sent to Magna is encrypted in transit. Our API and application endpoints are TLS/SSL only and score an "A+" rating on SSL Labs' tests.
We regularly engage with well-regarded third-party auditors to audit our code-base and infrastructure, and work with them to resolve potential issues.
We use two-factor authentication whenever possible. We ask vendors to enforce two factor authentication in all our accounts. We discourage use of shared accounts on any system. We review which accounts can access our systems and the permissions they have regularly.
We have a documented incident response plan and educate all staff on security procedures and policies.
External penetration testing twice a year performed by dedicated external security partners.
Any changes to the Magna code base have been peer reviewed and are automatically tested as part of our CI/CD process to identify any regression or security flaws using static analysis.

PreviousPrivacy & Terms NextData Protection

Last updated 11 months ago

Was this helpful?

Our team has relevant experience

We follow best practices

At Magna we follow a number of best practices that improve our security posture. Here are a few examples:

We have functioning, frequently used automation in place so that we can safely and reliably rollout changes to both our application and operating platform within minutes. We typically deploy dozens of times a day, so we have high confidence that we can get a security fix out quickly when required.

All data sent to Magna is encrypted in transit. Our API and application endpoints are TLS/SSL only and score an "A+" rating on SSL Labs' tests.

We regularly engage with well-regarded third-party auditors to audit our code-base and infrastructure, and work with them to resolve potential issues.

We use two-factor authentication whenever possible. We ask vendors to enforce two factor authentication in all our accounts. We discourage use of shared accounts on any system. We review which accounts can access our systems and the permissions they have regularly.

We have a documented incident response plan and educate all staff on security procedures and policies.

External penetration testing twice a year performed by dedicated external security partners.

Any changes to the Magna code base have been peer reviewed and are automatically tested as part of our CI/CD process to identify any regression or security flaws using static analysis.