Origin Inspector provides you with a dataset and visualizations that offer real-time and historical visibility into responses delivered from your origin servers to our edge cloud. And we’re happy to say that it’s now in limited availability.

We’re sharing our latest data and new insights into the Log4j/Log4Shell vulnerability (CVE-2021-44228 + CVE-2021-45046) in this post in order to help the engineering community cope with the situation. We also share our guidance around testing your environment against many of the new obfuscation methods that have been seen.

Our new WAF efficacy framework provides a standardized way to measure the effectiveness of a WAF’s detection capabilities through continuous verification and validation. Here’s how it works.

CVE-2021-44228 is a Remote Code Execution vulnerability in the Apache Log4j library being actively exploited. We provide our observations into the exploit and a summary of its impact.

The web’s infrastructure — and the applications we build on it — must constantly evolve to meet the ever-transforming expectations of modern and future end users. We’ve gathered five lessons today’s builders can use to drive the next three decades of the web.

In this post, we’ll show how you can use information from an origin response to add an abuse IP address to our penalty box. We've been touting the promise of security at the edge, and this is just one example of what it can do.

A couple of weeks ago Cloudflare, one of our competitors, claimed that their edge compute platform is roughly three times as fast as Compute@Edge. The false claim is a great example of how statistics can be used to mislead.

We analyzed traffic from Thanksgiving Thursday to Cyber Monday in order to understand the traffic, buying, and security trends of ecommerce's big week.

To create more secure and resilient web experiences, we must design, build, and execute applications with security top of mind, and consider how the lessons of the past 30 years inform how we think about the future of security.

The key to customer retention is serving the most up-to-date content instantly, personalizing that content for readers, and ensuring online experiences are responsive, safe, and secure. Here are three ways a modern content delivery network, or CDN, can help you do just that.

On November 11th 2021, Fastly Engineering received alerts related to segmentation faults on Compute@Edge. A Fastly investigation into CVE-2021-43790, a bug in Lucet, a dependency of Compute@Edge, is disclosed in a recent Bytecode Alliance security advisory. Fastly investigations have not identified additional impact outside of the single case disclosed in this advisory. It's our goal in this Fastly Security Advisory to illustrate our knowledge about the bug discovered and the actions we have taken to prevent further possible impact to our customers.

Many websites today are really applications, and we should be building them as such. To do that, we need application architectures and networks that are capable of supporting fast, secure, and scalable user experiences. We must embrace a more dynamic mindset in how we approach web development and consider the tools we need to get there.

As we look back to celebrate the 30th anniversary of the website, it’s also worth thinking about the next 30 years. There are a couple of areas where we — as engineers, developers, and builders in general — can champion innovation, mainly around architecture and security.

In this video from Web Summit 2021, we discuss how you build and ensure your company culture when you have some team members in person and some at home.

Compute, our serverless compute environment, can be used to solve headaches dealing with attackers looking to modify and manipulate resources. In this post, we tell you how.

Fastly customers have been using our Fiddle tool for years to try out ideas for edge logic in VCL. With the advent of Compute last year, we made our edge compute network accessible to any language that compiles to WebAssembly, and now you can write Compute code in Fiddle too.

In this tutorial, we’ll walk you through the basic steps of outputting messages to STDIO and tailing that output with the Fastly CLI as well as configuring a log streaming endpoint, emitting logs in your application, and confirming the delivery of those logs to your target logging destination.

Compute is now available for everyone to use, and we’re throwing in free credits so you can explore the platform with no strings attached. Read on for a crash course in how to stand up an experiment and experience the flexibility, security, and power of Compute for yourself.