How to Secure Environments with Infrastructure Automation

Date Posted: 06.21.21
Read Time: 10 min

<div class=”hs-featured-image-wrapper”>
<a href=”” title=”” class=”hs-featured-image-link”> <img src=”” alt=”How to Secure Environments with Infrastructure Automation” class=”hs-featured-image” style=”width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;”> </a>
<p class=”gd gr aw ay gf b gg gh gs gi gj gt gk gl gu gm gn gv go gp gw gq dx”><span style=”font-family: helvetica;”><span style=”background-color: #ffffff;”>I ha</span>d an interesting conversation with a senior FSI cloud architect, and towards the end of the conversation he made a funny observation. “Do you know what could help Dev and Ops collaborate? A common enemy. They both hate security”.</span></p>
<p class=”gd gr aw ay gf b gg gh gs gi gj gt gk gl gu gm gn gv go gp gw gq dx”><span style=”font-family: helvetica;”>He was kidding, but there’s some truth to it. Attempting to automate can create major security risks. Engineers with automation skills aren’t always security experts, and it’s easy to forget security best practices when automating. And what’s worse, by automating we make things faster, which means security violations are harder to control. Trying to adopt speedy automation we can easily end up with a heap of security issues—from hard coded keys in GitHub to exposed customer data in unintentionally-public development/testing S3 buckets and misconfigured cloud services.</span></p>
<img src=”;k=14&amp;;;bvt=rss” alt=”” width=”1″ height=”1″ style=”min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; “>

Latest Resources