7 Steps to Engineer Security into Ongoing and Future Container Adoption Efforts (Podcast Series)

reportActive / Technical Report | Accesssion Number: AD1147918 | Open PDF

Abstract:

What is exciting about containers for me, just from a software development perspective, is because the containers include the software dependencies and the resources you need to run on different hardware, the container allows software to be deployed in different hardware environments with the same container. I remember the days when we did desktop applications and we had to run around each desktop and install the software, configure it, and then hope it ran. Containers are the complete opposite end of that spectrum. If you are running an application and container in one environment, and you switch hosts or switch environments, or move from desktop to cloud - provided that the new environment has a container engine running that supports the container you have - you can easily move the containers around, allowing that portability. That also allows you to leverage different stacks of hardware you might have laying around. So, instead of old hardware becoming obsolete, as long as it has enough resources on it, I can put a container engine on it and still use that old hardware.

Security Markings

DOCUMENT & CONTEXTUAL SUMMARY

Distribution Code:
A - Approved For Public Release
Distribution Statement: Public Release

RECORD

Collection: TRECMS
Subject Terms