In part 1, I discussed the general workflow the Threat Intelligence team at Fastly uses to plan for projects. After performing research and seeing what others have done in this space, we can now move forward with technology selection.

We’ve recently restructured some of our internal engineering teams in an effort to improve shipping velocity, and dedicated resources are working on an HTTP/2 strategy that meets Fastly standards.

Building a great team is one of the most difficult challenges security managers encounter. Luckily, there are a few initiatives that make things easier on us, including the Information Security Talent Search (ISTS) at the Rochester Institute of Technology.

Event Logs help you keep track of key changes to your Fastly service, increasing visibility and improving troubleshooting.

We’re pleased to announce we now support log streaming to Google Cloud Storage (GCS) endpoints. Fastly’s GCS support strengthens our existing Log Streaming capabilities for common endpoints.

On February 25, we hosted 50+ security researchers and engineers from the Bay Area and beyond in our San Francisco office for the first event in the Fastly Security Speaker Series. This event brought together security engineers and researchers to examine new perspectives around important security topics.

Today in conjunction with an OpenSSL Security Advisory several researchers announced a new attack on HTTPS they are calling “Decrypting RSA with Obsolete and Weakened Encryption,” or DROWN. Due to Fastly’s existing TLS configuration, our services, and customers using Fastly as their CDN, are not vulnerable to this attack.

Fastly Security Researcher Zack Allen discusses how you can draw from open source resources to build a lean and powerful Threat Intelligence plan for your organization.

Fastly has fixed a problem in our default Transport Layer Security (TLS) configuration that prevented proper certificate validation when connecting to customer origin servers. Services created after September 6th, 2015 were not affected. This advisory describes the issue to inform our customers of the potential exposure, the fix we’ve made, and additional improvements we’re making. This vulnerability has been assigned Fastly Security severity rating of HIGH.

Today we’re announcing Fastly Security Advisories. Fastly will publish these to address security concerns that either trigger customer interest or require customer action to address.

Magento merchants can now seamlessly enjoy the speed and flexibility of our Varnish-based CDN platform from within their Magento interface with zero code changes required.

On Tuesday, February 16th, researchers published details about a new vulnerability in the glibc library, a standard C library. The vulnerability existed in the code used to translate hostnames into IP addresses. Processes that use it are very common across network service providers, such as CDNs. Fastly immediately implemented a security update on affected systems. No customer action is required. Fastly’s service was not impacted.

Today we’re announcing the Fastly Security Speaker Series, an informal event for bringing together researchers and engineers to share research, tools, and ideas. Fastly will bring some of the most innovative and thoughtful security researchers to Fastly headquarters in San Francisco to share their work. Our first event is February 25th, and our first two speakers are Alex Pinto and Rolf Rolles.

Last Sunday over 111.9 million viewers tuned in for the Super Bowl. As a CDN, we’re in a unique position — we help companies handle the impact of successful Super Bowl ads, and monitor the results in real time. We thought it might be interesting to share some of the traffic patterns we noticed during the big game.

We’re proud to announce support for MPEG-DASH streaming format packaging. This feature lets you simplify the delivery of video content to your end users and reduce the operational costs associated with providing an exceptional user experience.

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.

Sales Engineer Léon Brocard created fastly2git, a Git repository for Fastly service changes, making it easy for you to see differences between versions. In this post, Léon discusses how fastly2git works, and how it can help you continue building great services on Fastly.

We launched Fastly in July 2011 with seven employees and a mission to make web experiences faster. Four years later, Fastly has 240 employees (and growing), five offices (including a newly opened office in Denver), 26 global points of presence (POPs), and powers tens of thousands of websites.