際際滷

際際滷Share a Scribd company logo

Adobe Commerce cloud.pptx

Download as PPTX, PDF
Shyju Mundayadan
Shyju Mundayadan

Adobe Commerce relies on content delivery networks like Fastly to optimize content flow between users and the Commerce environment. All user traffic should be secured using HTTPS, either using a shared SSL certificate included with Commerce or a customer's own SSL certificate. Customers are responsible for acquiring and managing their own SSL certificate. Outbound communications from Commerce are re-encrypted after processing by the CDN. Payment information is passed from users to a payment gateway integrated with Commerce. Customers must verify any extensions to Commerce either do not process payment or PII data, or are PCI-compliant if handling that data.

1 of 1
Download to read offline
Commerce Data Flow Adobe relies on content delivery networks (CDNs), such as Fastly, to optimize content flow between users and the Commerce environment. All user traffic should be secured using HTTPS, either using a shared SSL certification included with the Commerce solution (and hosted on the Fastly CDN) or the customers own SSL certificate. If the customer chooses the latter option, acquisition and management of this certificate to support HTTPS traffic is the customers responsbility. Customers can contact their Adobe representative for additional assistance. 4 Outbound communications from Commerce to the user are re-encrypted after they are processed by the CDN. The CDN service supports SHA-256 certificates signed by publicly trusted certificate authorities that have a minimum key size of 2048 bits for RSA. Checkout and account pages are always served using HTTPS. The best practice is to serve all pages in a site under HTTPS. Payment Gateway Commerce requires integration with a payment gateway to pass credit card data from the user to the payment gateway. Extensions The customer is responsible for verifying that any extensions to Commerce either a) do not process and/or store payment information or other personally identifable information (PII), or b) that those extensions are certified as PCI- compliant if they must handle that data. Data Storage Adobe速 Commerce uses Amazon Elastic Block Store (EBS) for storage. All EBS volumes are encrypted by Amazon using the AES-256 algorithm, meaning data is encrypted at rest. Commerce also encrypts data in transit between the between the CDN and users as well as between the CDN and all Commerce servers. All secure communications are encrypted using TLS 1.2. Passwords created for the various Commerce system accounts are stored as hashes using Argon2id. Sensitive credentials, including those used for the payment gateway, are encrypted using AES-256. Commerce does not support column-level or row-level encryption or encryption when the data is in transit, i.e., in transit between servers. The customer can manage encryption keys from within the Commerce. Keys used by the infrastructure are stored in AWS Key Management System and must be managed in Commerce in order to deliver key functionality of the environment.

More Related Content

Adobe Commerce cloud.pptx

  • 1. Commerce Data Flow Adobe relies on content delivery networks (CDNs), such as Fastly, to optimize content flow between users and the Commerce environment. All user traffic should be secured using HTTPS, either using a shared SSL certification included with the Commerce solution (and hosted on the Fastly CDN) or the customers own SSL certificate. If the customer chooses the latter option, acquisition and management of this certificate to support HTTPS traffic is the customers responsbility. Customers can contact their Adobe representative for additional assistance. 4 Outbound communications from Commerce to the user are re-encrypted after they are processed by the CDN. The CDN service supports SHA-256 certificates signed by publicly trusted certificate authorities that have a minimum key size of 2048 bits for RSA. Checkout and account pages are always served using HTTPS. The best practice is to serve all pages in a site under HTTPS. Payment Gateway Commerce requires integration with a payment gateway to pass credit card data from the user to the payment gateway. Extensions The customer is responsible for verifying that any extensions to Commerce either a) do not process and/or store payment information or other personally identifable information (PII), or b) that those extensions are certified as PCI- compliant if they must handle that data. Data Storage Adobe速 Commerce uses Amazon Elastic Block Store (EBS) for storage. All EBS volumes are encrypted by Amazon using the AES-256 algorithm, meaning data is encrypted at rest. Commerce also encrypts data in transit between the between the CDN and users as well as between the CDN and all Commerce servers. All secure communications are encrypted using TLS 1.2. Passwords created for the various Commerce system accounts are stored as hashes using Argon2id. Sensitive credentials, including those used for the payment gateway, are encrypted using AES-256. Commerce does not support column-level or row-level encryption or encryption when the data is in transit, i.e., in transit between servers. The customer can manage encryption keys from within the Commerce. Keys used by the infrastructure are stored in AWS Key Management System and must be managed in Commerce in order to deliver key functionality of the environment.