You decide to purchase an extension from the Magento Marketplace that fulfills a business requirement and has very good ratings. It is mandatory no security vulnerabilities are introduced by the extension to keep the merchant and the customer data state. How do you apply due diligence?

The most critical step in due diligence is an independent code review by a qualified developer. While the Magento Marketplace Extension Quality Program (EQP) performs security checks, it is a baseline review and cannot guarantee the absence of all vulnerabilities. New security issues can emerge, or specific vulnerabilities might be missed. The ultimate responsibility for the security and integrity of a live production environment rests with the merchant and their development team. A dedicated code audit ensures the extension adheres to security best practices and is safe to deploy within the specific context of the merchant's site.

A. Relying solely on the Magento Marketplace team is insufficient. Their review is a valuable first step, but it does not absolve the merchant of their own security responsibilities.
B. The Magento Community Engineering team contributes to the Magento core codebase; they are not responsible for reviewing or validating third-party extensions on the Marketplace.
C. While vendors should provide secure extensions, "checking the vendor" is vague and trusting them without verification is not adequate due diligence. A code review is an active verification step.

1. Adobe Commerce - Security Best Practices Guide: In the "Development and Deployment" section

under "Secure development

" the official documentation explicitly states: "Perform a security code audit of all new code

including third-party extensions and customizations

before deploying to production." This directly supports the requirement for a developer review.

(Source: Adobe Experience League

Adobe Commerce Security Best Practices

Development and Deployment > Secure development)

2. Adobe Commerce - PHP Developer Guide: The guide details secure coding standards and practices that Magento extensions are expected to follow. A developer performing a review would use these standards as a benchmark to evaluate the extension's code quality and security posture

a task that cannot be delegated to an automated scan or a third party.

(Source: Adobe Experience League

Adobe Commerce PHP Developer Guide

Fundamentals > Coding Standards)

3. Adobe Commerce Marketplace - Extension Quality Program: The documentation for the EQP describes the review process

which includes automated checks and manual QA. While comprehensive

it is a standardized process. A custom code review (as suggested in option D) can identify issues specific to the merchant's environment or business logic that a general review might miss.

(Source: Adobe Experience League

Commerce Marketplace > Extension Quality Program > Technical Review)