Security updates take place in several steps.

• Step one: Test updates in an isolated branch

• Step one approval: Test and approve the security update

• Step two: Tag branch and deploy for more testing

• Step two approval: Final testing and approval

• Step three: Deploy tested tag to production

Step one: Test updates in an isolated branch

Owner: Acquia Remote Administration

The steps within Step one will not affect the operation of production, stage, or development servers. Acquia’s automated security update process will:

• Create a branch from the tag or branch deployed to your production environment.

• Deploy this branch to the RA Environment.

• Copy the production database(s) to the RA environment.

• Use Drush or Composer to apply all security updates to this branch.

• Create a ticket to inform your team the security update branch is ready for testing and approval.

Step one approval: Test and approve the security update

Owner: Customer

Your team receives a Support ticket informing you that the security update branch is ready for testing and approval. You can find this ticket under the My Cases section of the Acquia Help Center. For more information on accessing Support tickets, see Support and TAM ticket information.

There is a summary of the changes and next steps within the ticket feed, as well as in the Description of Issue on the right. In the Remote Administration Workflow section in the bottom right, your team can review the RA Workflow State and provide your approval for the next phase of the RA process. From the Approval Needed dropdown menu in this section, your team informs the RA team that you are ready for the next step of the RA process.

Review and test the security update available in your RA environment on your Cloud Platform application.

When your team finishes testing:

• Navigate to the ticket within the Acquia Help Center.

• Locate the Remote Administration Workflow section in the bottom corner of the ticket.

• In Approval Needed, select Approved.

• Click Save.

After you approve the security update branch in the dropdown menu, Acquia will proceed with the next step.

Step two: Tag branch and deploy for more testing

Owner: Acquia Remote Administration

Once your team has approved the branch provided in the first step, RA Automation will:

• Make a tag of the approved security update branch. The only difference between this tag and the source from step one should be the tested and approved security updates.

• Backup all databases on your preferred testing environment.

• Copy the latest databases from production into your preferred test environment which defaults to the Stage environment. This ensures the final test is against the most recent production data.

• Deploy the tag to the testing environment for final testing.

• Inform your team the tag is ready for testing and approval to deploy to production. Acquia cannot move updated code to production without your explicit approval.

Step two approval: Final testing and approval

Owner: Customer

Review the tag in your Cloud Platform application and complete final testing of the security update.

When your team finishes testing, your team must provide explicit approval in the support ticket for the RA team to deploy the update. Your team can specify the day/time of the deployment for the update in your RA preferences. For more information on how to schedule your RA update deployments, see Remote Administration preferences.

To provide approval to the RA team:

• Navigate to the ticket within the Acquia Help Center.

• Locate the Remote Administration Workflow section in the bottom corner of the ticket.

• In Approval Needed, select Approved.

• Click Save.

After you approve the security update branch in the dropdown menu, Acquia will proceed with deploying the tag to production.

Step three: Deploy tested tag to production

Owner: Acquia Remote Administration

Once your team approves the tag, it will be deployed to production. You can schedule this for a specific time with a 24-hour notice within normal business hours. See Scheduling production deploy windows for details.

After you have set a deploy time in your RA preferences and approved the tag for release to production on the ticket, RA automation will do the following:

• Make a tag of the approved security update branch. The only difference between this tag and the source from step one should be the tested and approved security updates.

• Back up the production database(s).

• Deploy the tag.

• Run any required database updates.

• Inform you that production has been updated and must be tested.

• Your RA preference setting will determine who merges the security branch into your development branch:

  • If you set your RA preference to merge, RA automation will try to merge the update into your development branch. If the merge into the development branch requires troubleshooting, either Acquia or your team can create a new ticket (Legacy Premium RA only).

  • If you don’t set your RA preference to merge, you should merge the branch/tag into your preferred development branch. This ensures the security updates are included in all future work.

Security update process