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.
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.
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 : firstname.lastname@example.org
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
So, you’ve got your Kubernetes cluster up and running, and now its time to expose workloads to the outside world in a secure fashion.
There is a great plugin out there that helps connecting Jenkins to your Bitbucket account called Bitbucket Branch Source Plugin.
This plugin comes really handy especially if your project has multiple branches. In Jenkins lingo “Multibranch Project”.
Security is critical to any organization. In the tech world, security can be defined as a set of controls and policies that protect and secure applications, data, and the technological infrastructures they operate on. In this blog we will be looking at the most common AWS security best practices.