Although we support automated remediations, either via the console, ChatOps, or full automated, in many situations it makes more sense to manually review and fix something so you are less likely to experience an unintended consequence. For many issues this should be handled by the team that owns the account/subscription/project, which is why we created our advanced ChatOps and ticketing notifications. By sending issues right to teams in the tools they already use in real-time you empower them to fix things more quickly using their preferred technique.
But sometimes, especially if something is exposed to the Internet at large (and maybe in the middle of the night) you will want SecOps to step in and fix it right away. This kind of break glass access should be restricted, used judiciously, and comprehensively logged.
That’s the example in this video. Watch, in real time (really, there aren’t any cuts) an entire response process from misconfiguration to remediation in less than two minutes:
<
div class=”wpb_row vc_row-fluid vc_row”>
<
div class=”row_col_wrap_12 col span_12 dark left”>
<
div class=”vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone “>
<
div class=”vc_column-inner”>
<
div class=”wpb_wrapper”>
<
div class=”wpb_raw_code wpb_content_element wpb_raw_html”>
<
div class=”wpb_wrapper”>
<
div class=”wistia_responsive_padding”>
<
div class=”wistia_responsive_wrapper”>
Read the original article: