One Article Review
| Source |  Network World |
|---|---|
| Identifiant | 303898 |
| Date de publication | 2017-02-01 05:26:00 (vue: 2017-02-01 05:26:00) |
| Titre | 5 things DevOps needs to do to secure containers |
| Texte | Can't we all get along Image by PixabayDo deepening adoption and broader deployment of container technologies (from the likes of Docker, CoreOS and others) threaten to escalate into the latest skirmish between operations, developers and information security? Certainly, the potential exists to widen the rift, but in fact there is far more common ground than would initially suggest. Containerization introduces new infrastructure that operates dynamically and is open in nature, with more potential for cross-container activity. Containerization presents an almost unprecedented opportunity to embed security into the software delivery pipeline – rather than graft on security checks, container monitoring and policy for access controls as an afterthought.To read this article in full or to leave a comment, please click here |
| Envoyé | Oui |
| Condensat | access activity adoption afterthought all almost alongimage article between broader but can certainly checks click comment common container containerization containers controls coreos cross deepening delivery deployment developers devops docker dynamically embed escalate exists fact far from full get graft ground here information infrastructure initially introduces latest leave likes monitoring more nature needs new open operates operations opportunity others pipeline pixabaydo please policy potential presents rather read rift secure security skirmish software suggest technologies than things threaten unprecedented widen would |
| Tags | |
| Stories | |
| 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.