r/devops • u/sensedeep • May 14 '17
Immutable infrastructure can be dramatically more secure
We switched to immutable servers and found it much easier to secure our sites. Detecting changes when you are doing updates, patches and upgrades becomes quite difficult. Immutable servers don't have this issue and thus it is much easier to detect a whole class of hacks.
Here is a full post about it: https://simplesecurity.sensedeep.com/immutable-infrastructure-can-be-dramatically-more-secure-238f297eca49
3
u/dada_ May 15 '17
This is interesting, but I wonder how many false positives I would get this way just from my applications saving configuration data and their own cache, and the like. Might take some trial and error?
0
May 15 '17
[deleted]
1
u/sensedeep May 15 '17
[Sorry - top posted this comment]
Correct, you should omit /var/log and some system directories. But you can completely lock down the binary and libraries directories. The list of directories is configurable.
1
u/sensedeep May 15 '17
Correct, you should omit /var/log and some system directories. But you can completely lock down the binary and libraries directories. The list of directories is configurable.
1
u/theanswriz42 Architect of things May 15 '17
It can also cause a management nightmare for large scale enterprises...
1
May 15 '17
Why would it be any different?
1
u/theanswriz42 Architect of things May 16 '17
Because you're functionally maintaining separate images/templates for each application. This gets complicated when you're working for companies with 500+ different applications. If you deploy to a vanilla image, it's considerably easier to maintain since you're just leveraging versioned CM scripts. Plus, if you're deploying across multiple providers, you don't have to worry about either exporting the template from one provider and importing it into your others, or doing something like configuring lots of templates with Packer (or a similar tool) and importing them to all your providers.
2
u/sensedeep May 16 '17
You can still deploy to a single vanilla image, but just don't upgrade it, instead rebuild using an up to date underlying single image. That way the image is (relatively) immutable, but still shared across multiple applications.
We do this. We have one single AMI with docker. Then we install the docker application at provision time. But the running Linux image is immutable thereafter and any mutations are signals of compromise.
39
u/stephen_neuville May 15 '17
OP did not disclose they are selling a product that supports the topic of discussion.