Blog Back to all stories
Sean Leach
Chief Product ArchitectGartner names Fastly a Challenger in the 2021 Magic Quadrant for Web Application and API Protection.
With JavaScript now available for WebAssembly and Compute@Edge, you can get started faster than ever with a language you already know, while ensuring the speed and security you need in a…
Here are four repeatable steps that will help you pay down your security technical debt, make your apps and APIs more secure, and move you toward consolidated security tooling.
As the internet landscape gets more complex, more API driven, and more distributed, many security and IT professionals are left wondering — why aren’t the security tools that were good…
Layer 7 is a primary battleground for web application and API security. Fastly and Okta have partnered together to share threat intelligence, so security and development teams can better…
The rise of secure DevOps has left many security professionals vying for the attention and support of their engineering counterparts. What can engineering leaders do to bridge the gap? We…
Nearly everything we know about building web applications and APIs has changed in the last few decades. So why hasn't security? We argue it's time for a new approach to web app and API…
Progressive developers are increasingly using the edge of the network to power more performant and customized apps. With the use cases mounting, it seems there's very little that can't be…
Building our own compiler toolchain allows Compute@Edge to be both performant and secure. It also means we have to bring developers’ most-loved language into the fold in the right way.
Watch our Compute@Edge demo, and see the possibilities of our new serverless compute environment.
Earlier this year we updated you on our revised deprecation plan for TLS 1.0 and 1.1. We’re happy to announce that you can now request migration to TLS 1.2-only hosts if you’ve purchased a…
Last October, we announced our deprecation plan for TLS 1.0 and 1.1. The PCI Security Standards has since updated their guidance, and we are revising our deprecation schedule accordingly.