The tools you use will differ if you’re running a Platform as a Service (PaaS), running a mobile application, or serving as a bank. Nevertheless, there are some core Key Performance Indicators (KPIs) that should be common to all of these environments. This article will take you through the KPIs you should either evaluate or revisit and examine what you should consider when measuring success.
Tunneling is the practice of embedding messages of one network protocol within messages of a different network protocol. In a security context, tunneling is a way for an attacker to bypass security boundaries like the perimeter firewall of a cloud deployment by encapsulating malicious traffic within permitted traffic. This blog explores the challenges of detecting DNS tunneling, and offers a solution to how you can detect a DNS tunneling attack on you cloud environments.
Last week our team came back from KubeCon Seattle, CNCF largest event to date with over 8000 attendees (!) where they showcased our Microservices Firewall, and I thought that now would be a good time to touch base again and talk about Kubernetes security.
Following part 1 of our blog series, here's part 2.
We are happy to announce that Alcide's Cloud-Native Security Platform it is now available on the new AWS Marketplace for Containers.
AWS has announced today, Tuesday November 27th, during AWS re:Invent week on AWS Marketplace for Containers which adds support for software products that use Docker containers.
The post is part one of a blog series on the evolution of serverless security. The process of building applications has changed over time. Today, applications are designed to make use of multiple public clouds in addition to on-premises IT resources. They are also designed to use microservices, containers, and serverless. Each of these steps has been part of the evolution of application design, moving us towards applications that are inextricably interwoven with the infrastructure and workload automation software that controls the applications themselves.
Here’s a recent scenario: an organization’s security team receives an alert from the monitoring system on their Slack channel with the content below:
AWS Account : SomeCompany_Development
IAM User : email@example.com
AWS API : AllowSecurityGroupIngress
Source IP Address : xxx.xxx.xxx.xxx
Security Group ID : sg-4fxxx4dx
Security Group Region : us-east-2
IP Protocol : tcp
From : 22
To : 22
IPRange : 0.0.0.0/0
Micro-segmentation is an emerging practice that is quickly becoming a critical facet of cloud security. Its objective is not only to prevent compromise, but also to deal with what happens after compromise occurs. The purpose of micro-segmentation is to isolate applications and services from one another in order to prevent attackers from achieving their goals—even if they succeed in initially breaching the organization’s IT defenses.
“For most organizations, we believe serverless PaaS adoption is a matter of when, not if — with enterprise adoption rates exceeding 90% by 2021... However, as with the adoption of VMs and containers, support for securing serverless will initially have visibility and control gaps...Further, new types of attacks will emerge against serverless PaaS, requiring new approaches and techniques.” 1