Security FAQ
How do you connect to my data in Marketo?
Madison Logic connects to Marketo using publicly documented REST APIs.
We authenticate to Marketo using three necessary fields to authorize API access : Client ID, Client Secret and Identity URL. These are apart of Marketo Web services which allow API access to the data.
More information on the installation process can be found hereÂ
What data do you retrieve from Marketo?
We query the following entities from Marketo:
- Leads
- Smartlists
We ONLY retrieve the fields that you define as "field mappings" during configuration of our Marketo integration module. From these entities we retrieve the following information:
- Leads Email - We extract domain from the emails to target the account.
- Lead ID.
- Company name
Where do you physically store my data?
Madison Logic stores your CRM data in the United States, in the state of Virginia, within the Amazon Web Services region us-east-1.
How is my data secured in transit?
When Madison Logic retrieves your data from Marketo APIs, it is secured in transit by encryption using Transport Layer Security (TLS) version 1.2.
When your CRM data is transferred within Madison Logic systems, it is also secured in transit by encryption using TLS 1.2.
How is my data secured at rest?
Your data is secured at rest by encrypting it using AWS Key Management Service APIs.
AWS KMS uses the Advanced Encryption Standard (AES) algorithm in Galois/Counter Mode (GCM), known as AES-GCM. AWS KMS uses this algorithm with 256-bit secret keys.
Is my data isolated from other customers? If so, how?
Yes. Your CRM credentials and data are stored within a service dedicated to managing CRM data. Our "crm-api" functions as a lockbox for your data, to ensure that only you are permitted access to your data.
The only data we copy out of the "crm-api" lockbox into other Madison Logic systems is the list of target domains required to execute a campaign.
Is there a process in place for removing our content and data at the end of the use agreement?
Yes. We can ensure that your content is securely removed from Madison Logic systems. Contact us for more information.
What type of compliance and controls are in place?
Security and quality controls in Amazon Web Services have been validated and certified by the following compliance schemes:
- AWS Service Organization Controls (SOC 1, SOC 2, and SOC 3) Reports. You can request a copy of these reports from AWS Compliance.
- PCI DSS Level 1. For more details on PCI DSS compliant services in AWS, you can read the PCI DSS FAQs.
- ISO 27017. For more details on ISO 27017 compliant services in AWS, you can read the ISO-27017 FAQs.
- ISO 27018. For more details on ISO 27018 compliant services in AWS, you can read the ISO-27018 FAQs.
- ISO 9001. For more details on ISO 9001 compliant services in AWS, you can read the ISO-9001 FAQs.
- In evaluation for FIPS 140-2. For more details, you can view the FIPS 140-2 Implementation Under Test List.Â
References
Marketo Developer Documentation
Amazon Web Services Documentation
- AWS Key Management Services
- KMS - Cryptography Basics describes the cipher used: Advanced Encryption Standard (AES) algorithm in Galois/Counter Mode (GCM), known as AES-GCM. AWS KMS uses this algorithm with 256-bit secret keys.