Fastly WAF (Legacy)
Fastly is announcing the end of life (EOL) schedule for our Fastly WAF (Legacy and WAF 2020). This will allow us to focus more of our resources on the replacement product, the Fastly Next-Gen WAF, which is an enhanced offering.
We’re looking forward to helping you transition to this product as soon as you are able.
- The official EOL for the Fastly WAF is April 30th, 2023 at 00:00 UTC.
The product will continue to be supported until this date.
We’re happy to help you get you started with a proof-of-concept (POC) evaluation of our Next-Gen WAF so you can see how the two solutions compare. To get started, contact us via email at email@example.com.
For additional information and/or questions about End-of-Life efforts, please contact us via email at firstname.lastname@example.org.
This issue has been identified and a fix is being implemented.
Fastly engineers have corrected an issue with navigating to Legacy WAF administration pages. Please note that Legacy WAF functionality, WAF API, and NGWAF services were not affected by this UI bug.
We are continuing to investigate and monitor this issue as an isolated incident, please continue to send and monitor ticket updates via email (email@example.com) while we investigate.
Issue has been isolated and determined to be impacting customers whom have enabled SSO and have not accepted the invite sent from the console. Logging in directly from SSO will prevent customers from viewing, updating and interacting with tickets in the console. Fastly advises customers to accept the invite send from the console to resolve their issues with ticket logging and interactions.
Fastly is aware of an expected critical vulnerability the OpenSSL project is expected to disclose in the near future. We are studying the currently available information surrounding this vulnerability and do not currently believe that Signal Sciences is vulnerable. We will continue to monitor as additional information is released and will provide our customers with more information as available.
Fastly has reviewed the initial notification from OpenSSL regarding CVE-2022-3786 and CVE-2022-3602. We have analyzed the versions of OpenSSL in use at Fastly, and verified that we do not use OpenSSL 3.x. Fastly and customer usage of Fastly services are not vulnerable to CVE-2022-3786 or CVE-2022-3602.