> This page is for Applications Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.humansecurity.com/llms.txt.

# Upgrading the Enforcer

To upgrade to a newer version of the HUMAN Fastly Enforcer, [contact us](/applications/human-customer-support).\
You will be asked to provide the following information for HUMAN to start work on upgrading the VCL:

* Your current version of VCL
* Copies of the following files:
  * main.vcl
  * px_custom.vcl
  * px_configs.vcl
  * px.vcl
* Application name/ID

An alternative upgrade process would be to provide the [Fastly API token](https://docs.fastly.com/en/guides/using-api-tokens) with engineering permissions to our solution architects team to enable HUMAN to auto upgrade your VCL files directly in your Fastly account.

#### Upgrading to Fastly 9.0.0 and above

If your current Enforcer version is below 9.0.0, in addition to the above upgrade process you must:

* Add HTTPS loggers that send activities to HUMAN's servers. For more information, see [Installing the Enforcer](https://docs.perimeterx.com/docs/installing-the-enforcer-fastly#logging).
* Delete the `PX-Syslog` syslog logger, which is no longer in use.
* Delete the `PX-Syslog-Condition` condition, which is no longer in use.
* If you implemented the `px_custom_activity_headers` function in the `px_custom.vcl` file, refactor it to fit the new format.\
  See the comments as example.