Several times during the CRWD Call, I heard repeated, what is the most salient fact and my personal investment thesis for this company:
‘Security Transformation has to happen prior to Digital Transformation, and the moving of anything to the Cloud. Every phone/laptop, traditional end point, spins up multiple cloud instances, each of which each must be protected.
And-
CRWD is a layer of protection in the cloud under each instance and/or container so that App Developers don’t have to include security into their development architectures.
Then I read the Today’s addition to SSI,by Peter Offringa, discussing the Etsy group that 5 years ago formed the newly acquired security company just purchased by FSLY. And tell me if I’m wrong; but, Peter is explaining below here that FSLY is speeding up the EdgeCloud adoption with this Secure@edge integration.
SSI-
The plan is to integrate the application security capabilities from both companies together into a single new product offering called Secure@Edge. This will complement the Compute@Edge platform, but also be a key component within it. Secure@Edge will be built on top of the Compute@Edge platform, using the same development tooling as any other edge compute application. This architecture approach reinforces the notion that Compute@Edge is a platform for building applications. It also encourages dogfooding of the serverless platform for Fastly’s own engineering teams. This approach is similar to the strategy employed by Cloudflare in building the Teams product on top of Workers.
Building Secure@Edge into Compute@Edge also ensures that the application security capabilities are available to new edge compute applications by default. These wouldn’t need a separate layer in front of the application runtime to provide WAF or DDOS protection, which isn’t feasible at the edge. This is a powerful combination and completely changes the previous web application deployment paradigm, which used a layered approach to application security. The result for customers will be lower operational costs, simpler maintenance and more effective response. Release cycles will be faster, as they won’t need to be coordinated with application security configuration changes and will automatically integrate with existing CI/CD pipelines. The Signal Sciences’ platform includes more than 30 integrations into the most common DevOps and security tools – such as Slack, Jira, PagerDuty, Datadog, Splunk, and Cisco Threat Response.
Me here: this last part about Signal Sciences/Secure@edge ability to function as a platform is particularly interesting and might be reason for me to add some more to my 10% position in FSLY.
Jason