Best practices to help prevent and respond to a security incident

Adobe Commerce security operates under a Shared Responsibility model. It is key to understand what Adobe and your technical teams are responsible for. Below we summarize Security Best Practices for ensuring your project has the best security controls in place and how best to respond to a security incident.

Affected products and versions

All supported versions of:

  • Adobe Commerce on cloud infrastructure

Respond to an incident

There are many considerations as you respond to a security incident. If you suspect that you have encountered a recent security incident for your Adobe Commerce on cloud infrastructure project, it is important to audit all admin user account access, enable advanced multi-factor authentication (MFA) controls, preserve critical logs, and review security upgrades for your version of Adobe Commerce.

More recommendations are detailed below. They can help prevent unauthorized access and begin the process for further incident analysis.

How to prevent security incidents

Follow these security best practices to proactively prevent security incidents that impact your Adobe Commerce sites and storefronts:

  • Enable 2FA for admin access.
    Two-factor authentication is widely used, and it is common to generate access codes for different websites on the same app. This ensures that only you can log in to your user account. If you lose your password or a bot guesses it, two-factor authentication adds a layer of protection.
  • Enable MFA for SSH access.
    When MFA is enabled on a project, all Adobe Commerce on cloud infrastructure accounts with SSH access must follow an authentication workflow that requires either a two-factor authentication (2FA) code, or an API token and a SSH certificate to access the environment.
  • Upgrade to the latest release of Adobe Commerce.
    Adobe releases security and functional patches for each supported release Adobe Commerce.
  • Setup and use a non-default admin URL.
    Adobe recommends that you use a unique, custom Admin URL instead of the default admin or a common term such as backend. Although this configuration change does not directly protect your site from a determined bad actor, it can reduce exposure to scripts that try to gain unauthorized access.
  • Prevent configuration values from being edited or updated in the Admin by using the bin/magento config:set CLI command with the lock env configuration option. This option either locks the configuration value so that it cannot be edited in the Admin, or prevents changes to a setting that is already locked. When you use this option, configuration changes are written to the <Commerce base dir>/app/etc/env.php file.
  • Setup and run the Adobe Commerce Security Scan Tool.
    The enhanced security scan allows you to monitor each of your Adobe Commerce sites, including PWA, for known security risks and malware, and to receive patch updates and security notifications.
  • Review and update Admin user access and security settings.
    • We recommend removing any old, unused, or suspicious accounts and rotate passwords for all Admin users.
    • Review and update the Advance Security Settings< for your project. The Admin security configuration gives you the ability to add a secret key to URLs, require passwords to be case-sensitive, and to limit the length of Admin sessions, including the lifetime of passwords, and the number of login attempts that can be made before the Admin user account is locked. For increased security, you can configure the length of keyboard inactivity before the current session expires, and require the username and password to be case-sensitive.
  • Audit Adobe Commerce on cloud project users.
    We recommend removing any old, unused, or suspicious accounts and requesting users to change their passwords.
  • Audit SSH keys for Adobe Commerce on cloud infrastructure.
    We recommend reviewing, deleting, and rotating SSH keys.
  • Implement Access Control List (ACL) for Admin.
    You can use a Fastly Edge ACL list in combination with a custom VCL code snippet to filter incoming requests and allow access by IP address to Admin.

Analyze an incident

The first step of incident analysis is to gather as many facts as you can, as quickly as you can. Gathering information surrounding the incident may help you determine the potential cause of the incident. Adobe Commerce provides the tools below to assist with your incident analysis.

  • Audit Admin Action Logs.
    The Action Logs Report displays a detailed record of all admin actions that are enabled for logging. Each record is time stamped and registers the IP address and name of the user. The log detail includes admin user data and related changes that were made during the action.
  • Analyze events with the Observation for Adobe Commerce tool.
    The Observation for Adobe Commerce tool allows you to analyze complex problems to help identify root causes. Instead of tracking disparate data, you can spend your time correlating events and errors to gain deeper insights into the causes of performance bottlenecks.
    The tool is intended to give a clear view of some of the potential site issues to help you identify the root cause and keep sites performing optimally. Click the link to the Observation for Adobe Commerce tool documentation above to access the tool documentation. There is a section in the documentation that details all the information that can be found on the Security tab.
  • Analyze logs with New Relic Logs. Adobe Commerce on cloud infrastructure Pro projects include the New Relic Logs service. The service is pre-configured to aggregate all log data from your Staging and Production environments to display it in a centralized log management dashboard.
    You can use the New Relic Logs service to complete the following tasks:
    • Use New Relic queries to search aggregated log data.
    • Visualize log data through the New Relic Logs application.

Additional information

On this page