Serverless solutions are good news for developers, but they can cause plenty of headaches, including cold starts, regional latency, and a lack of observability. Compute, Fastly’s serverless compute environment — built on Wasm and run globally — can help solve those problems.

We believe Signal Sciences’ innovation earned them recognition in the 2019 Gartner Magic Quadrant for WAF, and it’s this kind of innovation that excites us as we merge forces — now that Signal Sciences is part of Fastly.

With two new solutions, Fastly is empowering video engineers to address the growing streaming-at-scale challenge head on with enhancements to its video-on-demand and live event services capabilities, helping them deliver quality user experiences no matter what their end users are streaming.

Now more than ever, engaging in our democracy is critical — and Fastly is invested in making sure our internal community has the tools and resources to do so effectively.

DoSomething.org, part of our Open Source and Nonprofit Program, believes in activating young people to support change. And in the face of COVID-19 and a U.S. election year, they’ve imagined all-new ways to connect with users and driver voter engagement.

The largest category of difficult-to-anticipate security design weaknesses come from side-channel attacks. In this post, we take a tour of some of the more foundational and out-there side channel-related exploits that have afflicted the security conscious over the years.

We’ve made improvements to our diff view by combining customer testing, feedback, and requests with our own inspiration with diff experiences we enjoy using. The result is an enhanced diff view experience that we think you’ll enjoy as much as we do.

We’ve been hard at work at Fastly this year working on updates to our Terraform provider and have some exciting ones to announce: Terraform now supports all our logging endpoints, plus Fastly web application firewall customers can now manage their WAF within Terraform.

Today, Fastly completed the acquisition of Signal Sciences and took a giant step forward toward our vision of modern, unified web application and API security. We will call on our shared view of empowering developers as we chart a path toward building an incredibly secure, performant platform and unlock all-new possibilities, together.

Fastly’s new Image Optimizer feature converts animated gifs to MP4 videos for a faster load time, smoother experience, and significant savings on end-users’ bandwidth. In fact, the new feature was able to condense BuzzFeed’s 250 MB, browser-freezing “100 Greatest Gifs of all Time” article to a much more manageable 6 MB.

Following WAF best practices is imperative to keep your business and customers secure. Learn about new regulations and security tips.

QUIC and HTTP/3 have entered the final stages of development at the IETF. Distinguished Engineer, Jana Iyengar, elaborates on the current state of the protocols, their deployment across the internet, and his expectations for QUIC and HTTP/3 in the near future.

On July 29th at 00:00 UTC, Fastly was notified by a customer (customer X) that a single log line intended for a different customer (customer Y) was received by customer X’s log system. Fastly promptly began to investigate and determined that when a complex series of conditions occur, a log line may be misrouted to an incorrect logging service. We were able to trace the root cause to an error in logic introduced by Fastly to improve performance in April 2012. This single report from one customer is the only instance that Fastly is aware of, where all necessary conditions aligned simultaneously in eight years.

We’ve been experimenting with Network Error Logging with Fastly Insights and discovered that processing the NEL reports is a great use case for Compute. In this post, we’ll look at our first attempt to build a NEL reporting pipeline, discuss where there was potential for optimization, and how Compute solves these problems while introducing performance and security improvements along the way.

Security has always been a part of Fastly’s DNA, not just within products, but in our vision of trust and safety as a modern platform. Today, we are pleased to announce that we have announced our intent to acquire Signal Sciences.

Fastly CISO Mike Johnson and Brave Software Senior DevOps Engineer Ben Kero share their practical advice for cementing more holistic security practices within your CI/CD pipeline.

Developer-centricity is now a mission-critical philosophy for companies to embrace. And during COVID-19, we all know that the stakes have never been higher. We’ve seen that businesses that operate with a dev-first mindset at their core will have the strategic advantage and will only increase it, today and into the future.

Fastly was notified of the issue on May 21, 2020 13:30 UTC. Fastly immediately launched an investigation, identifying which origin servers responded with a test port number in the redirect response, in order to understand the vulnerability and possible solutions. After the investigation, Fastly first notified potentially affected customers on July 15, 2020 at 04:30 UTC. The vulnerability is a variant of a [previously reported vulnerability](https://www.fastly.com/security-advisories/cache-poisoning-leveraging-various-x-headers), and ultimately the result of constructing cacheable origin responses based on user-defined data. The issue occurs when an attacker issues an HTTPS request and specifies within the Host header a port number that is not actually being used for any services. It is possible to cache a resource in such a way as to deny future requests from being serviced properly.