One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 1932079 |
| Date de publication | 2020-09-22 11:00:00 (vue: 2020-09-22 11:05:48) |
| Titre | Why misconfigurations are such an issue in your containers and Kubernetes |
| Texte | This blog was written by an independent guest author. Organizations are increasingly incorporating containers and Kubernetes into their IT infrastructure. As reported by ZDNet, Flexera’s “2020 State of the Cloud Report” found that about two-thirds (65%) of organizations were using Docker and that another 14% intended to begin using it at some point. Slightly fewer organizations (58%) were using Kubernetes at the time of the survey, by comparison, with 22% of participants saying they planned to adopt it. Even so, misconfigurations with both containers and Kubernetes are posing a problem. StackRox’s “State of Kubernetes and Container Security Winter 2020” report found that nearly all (94%) of respondents had experienced a security incident in their container environments over the past 12 months, per Security magazine’s coverage. The majority (69%) of those security events amounted to a misconfiguration incident, followed by runtime issues and vulnerabilities at 27% and 24%, respectively. In keeping with those experiences, 61% of survey participants cited misconfigurations as their most worrisome security risk for their container and Kubernetes environments followed by vulnerabilities (27%) and runtime attacks (12%). These findings beg the question: why are misconfigurations such an issue for organizations’ Kubernetes and container environments? This blog post will answer this question by first defining containers and Kubernetes and explaining the benefits of each technology. It will then explore how misconfigurations open the door for attacks from malicious actors. Finally, it will briefly provide a few recommendations on how organizations can reduce the probability of suffering a misconfiguration incident. Why use containers and Kubernetes? According to CIO, a container contains everything that’s needed to run a software program. It includes an application along with its dependencies, libraries and other components. Bundling these components together enables a container to run regardless of the system’s OS distribution or the underlying infrastructure. Those aren’t the only benefits of containers, either. Containers might be only tens of megabytes in size, for instance. A server can therefore host more containers than virtual machines, notes CIO, as a virtual machine consists of an entire OS that might be several gigabytes in size. Consequently, virtual machines usually take several minutes to boot up and begin running, while containers can run almost instantly. This quality makes containers more dynamic in that organizations can spin them up and wind them down at a moment’s notice. Finally, organizations can take advantage of containers’ smaller size and dynamism to split an application into several modules that extend across several containers. Under this approach, developers can make changes to a module and deploy them without needing to redesign the whole app. As the number of containers grows, organizations need some way of managing them all in an organized fashion. That’s where Kubernetes comes in as an orchestration platform. Per its website, Kubernetes enables organizations to manage their containerized workloads and services. It allows organizations to load balance and distribute network traffic in order to stabilize a deployment. It also enables organizations to restart containers that fail and kill those |
| Envoyé | Oui |
| Condensat | “2020 2020” about above access according across activated actor actors address administrators adopt advantage against all allows almost along also always amounted another answer anyone app application applications apply approach are aren’t arrive attacks author automated automation balance based because become beg begin behave benchmarks benefits best binaries blog boot both briefly bundled bundling can center challenges changes channels check cio cis cited cloud code come comes communicate communication comparison components compromise compromised configuration consequently consists container container’s containerized containers containers’ contains context control controls could coverage dark data default defend defining dependencies depending deploy deployment described detect detected developers digital discussed distribute distribution docker does don’t door down downloads dynamic dynamism each either enable enables entire environment environments even events everything example experienced experiences experts explained explaining explains exploit explore extend fail fashion fewer finally findings firewall first flexera’s followed found frameworks from function gigabytes grows guest had health highlighted host how identify identity image inadvertently incident includes incorporating increasingly independent industry infect information informationweek informed infrastructure instance instantly intended internet involve issue issues it’s its job just keeping kill kubernetes laterally libraries like limit limiting load machine machines magazine’s majority make makes malicious malware manage management managing manual means measures megabytes might minutes misconfiguration misconfigurations module modules moment’s months more most move native nearly need needed needing network not notes notice notwithstanding number once one only open orchestration order organization’s organizations organizations’ organized other out over oversights part participants pass past per planned platform pod pods point policies policy posing possible post posture potentially practices privileges probability problem process program proper provide purpose quality question question: reading recommendations recording redesign reduce reflecting regardless regulating report report” reported repository resource’s respectively respondents restart restrict risk role rules run running runtime saying scope security sensitive server services several should single size slightly smaller software some specified spin split stabilize stackrox stackrox’s “state standard start state stealing such suffer suffering survey system’s take talk teams technology tens than that’s them then theoretically thereby therefore these they’ve thirds those throughout time together traffic two types under underlying undermine use using usually violations virtual vulnerabilities way webinar website where which who whole whose why will wind winter without workloads worrisome written your zdnet |
| Tags | Malware |
| Stories | Uber |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.