Dynamify

Security isn't a single yes/no, but Dynamify is SOC 2 compliant and holds GDPR, PCI DSS. SOC2C verifies its compliance posture and shows how strongly each fact is proven.

Dynamify hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@dynamify.com or via a /security page (Dynamify lists a security contact).

Dynamify lists 3 subprocessors on its trust center, including Amazon Web Services, Google Workspace, Vanta. Buyers use this for fourth-party risk review.

Dynamify hosts on AWS, and handles Customer personally identifiable information, Employee personally identifiable information, Credit card information, Personal health information. Data residency details are on its trust center.

Dynamify's trust center is at https://trust.dynamify.com. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.

Data at Rest. All datastores with customer data, in addition to S3 buckets, are encrypted at rest. Sensitive collections and tables also use column-level encryption. This means the data is encrypted even before it hits the database so that neither physical access, nor logical access to the database, is enough to read the most sensitive information. Data in Transit. Dynamify uses TLS 1.3 everywhere data is transmitted over potentially insecure networks. We also use features such as HSTS (HTTP Strict Transport Security) to maximize the security of our data in transit. Server TLS keys and certificates are managed by AWS and deployed via Application Load Balancers. Secret Management. Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and Dynamify. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs. Application secrets are encrypted and stored securely via AWS Secrets Manager and Parameter Store, and access to these values is strictly limited.

Vulnerability Scanning. Dynamify requires vulnerability scanning at least monthly and also at key stages of our Secure Development Lifecycle (SDLC): - Static analysis (SAST) testing of code during pull requests and on an ongoing basis - Malicious dependency scanning to prevent the introduction of malware into our software supply chain - Network vulnerability scanning on a period basis - Software composition analysis (SCA) to identify known vulnerabilities in our software supply chain - Dynamic analysis (DAST) of running applications - External attack surface management (EASM) continuously running to discover new external-facing assets Penetration Testing. Dynamify engages with a different penetration testing consulting firm at least annually. All areas of the Dynamify product and cloud infrastructure are in-scope for these assessments, and source code is fully available to the testers in order to maximize the effectiveness and coverage. Remediation. Security gaps and known weaknesses (e.g. baseline configuration changes, missing patches, end-of-life-status, invalid registry, etc.) are tracked, prioritised according to severity (determined by the rating provided by the National Institute of Standards and Technology (NIST) Common Vulnerability Scoring System (CVSS)), and remediated on a timely basis.

Dynamify does not store, process and/or transmit cardholder data Dynamify develops and maintains merchant-branded applications that integrate with third-party PCI-validated Level 1 payment service providers (PSP). This encompasses card-not-present (using a PSP-hosted iframe) and card-present (using P2PE card machines); tokenization is used in all cases and HSTS is used to enforce HTTPS on API calls. Card brands accepted include American Express, Visa, Mastercard, Discover, and JCB Dynamify is a Level 1 PCI Service Provider

No Security is core at Dynamify and we will continue to make every effort to avoid experiencing a security incident. If a security incident were to arise in the future, Dynamify's incident response team will follow their regular training in implementing an iterative response process designed to investigate, contain exploitation, eradicate the threat, recover system and services, remediate vulnerabilities, and document a post-mortem report including the lessons learned from the incident.

Yes! Single Sign-On (SSO) removes the friction associated with accessing applications powered by Dynamify. Instead of having to create an account with a new username and password, front- and/or back-of-house users simply and securely log in using their institution’s credentials. Multi-factor authentication (MFA) can be enabled as part of SSO. Once logged in, users are authenticated until the sooner of self-performed sign-out or mandatory re-authentication at a frequency specified by the SSO client (e.g. every 90 days) In addition to being more convenient, SSO is more secure: reducing the need to remember passwords (which helps eliminate weak password use) and therefore minimising attack surfaces Dynamify has extensive experience implementing SSO, including with highly-regulated global publicly-listed companies, and supports all major protocols and providers For more information, refer to the Single Sign On (“SSO”) Integration Guide within the Documents section of Dynamify's Trust Report page