Cloud-Native and Serverless are the next evolution of application architecture. But protecting these applications is not easy. Where do I install my agent? How do I monitor network traffic? What APIs are exposed?
The adoption of containers started this challenge a few years ago by abstracting the application from the operating system. In order to get visibility into these containers, we used kernel modules, privileged containers, or side cars. But we quickly learned that instrumenting the application from within was the best approach, especially as we entered the early days of the serverless movement. Amazon Web Service’s Lambda and Fargate were the early signs, but new cloud-native services continue to enter the market.
So where does that leave security? Do we monitor the network? Do we monitor the application? Do we monitor the APIs? Do we monitor the container? Do we monitor the service? All of the above! That’s where Signal Sciences comes in. Signal Sciences provides a hybrid SaaS solution that deploys natively via any serverless application framework, from Docker to Kubernetes, AWS Lambda to Google AppEngine and can deploy easily in major cloud provider’s “containers as a service” offerings like Google Kubernetes Engine, AWS Fargate, Azure Container Service or RedHat OpenShift Container Platform.
We recently had Alfred Chung, Sr. Product Manager at Signal Sciences, on Application Security Weekly to discuss their capabilities, including their support for Azure App Service and Envoy Proxy. Signal Sciences breadth of capabilities, integrated into a unified management console, provides some of the most comprehensive protections for cloud-native and serverless applications with great benefits, including:
- Rapid Deployment from within Development and Cloud tools
- Protection Anywhere – Cloud, Containers, On-premise, Hybrid, etc.
- Scaled for Reliability, including denial of service and abuse requests