[ale] Containers... use?

[Jim Kinney]

I'm very close to the point of isolating my docker junkies in every possible way and letting their stuff get broken into. That will be the only way to get the political leverage to be able tell a PhD faculty "NO. It ALL runs through me and upstream university security. No exception."

On September 18, 2017 9:34:37 AM EDT, Solomon Peachy <pizza at shaftnet.org> wrote:
>On Mon, Sep 18, 2017 at 09:18:46AM -0400, Jerald Sheets wrote:
>> All containers should be curated by Systems.  The Developers should 
>> submit them for security scanning, or you should employ a DevSecOps 
>> model for deployment.  i.e., federate security scanning by providing 
>> OS, App, transport, penetration, and network security testing as APIs
>
>> that devs can leverage instead of leaving them to security.  Left to 
>> their own devices, unreasonable deploy timelines set for them, and 
>> golf-playing pointy-hairs with unreasonable ship date requirements, 
>> it’ll never happen.
>
>> This should all be automated and part of a security CI/CD pipeline 
>> without which a “pass” from the security field, cannot ever be 
>> deployed into production.  This is how we do it.
>
>The unspoken assumption here is that your needs are sufficient to make 
>this (completely necessary!) administrative overhead worthwhile.  
>
>Unfortunately, much like VMs before, most shops just "download an
>image" 
>from the likes of DockerHub and then deploy it, with no real thought
>towards ongoing maintainence or security concerns.  Because those cost
>time/effort -- and therefore and money.
>
> - Solomon </grumble>
>-- 
>Solomon Peachy			       pizza at shaftnet dot org
>Coconut Creek, FL                          ^^ (email/xmpp) ^^
>Quidquid latine dictum sit, altum videtur.

-- 
Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20170918/7329ace3/attachment.html>