Security Hub remediations with GuardDuty Detection | Hands-on walkthrough | Cloud4DevOps

Поделиться
HTML-код
  • Опубликовано: 24 ноя 2024

Комментарии • 7

  • @samahome
    @samahome Год назад +2

    Great illustration & explaining

    • @Cloud4DevOps
      @Cloud4DevOps  Год назад +2

      Glad you liked it!

    • @tejasudheerkumar
      @tejasudheerkumar 11 месяцев назад

      It’s nice but whenever I tried event bridge was not started the action in the security hub.its failed
      Could you please help me out

    • @Cloud4DevOps
      @Cloud4DevOps  11 месяцев назад

      @@tejasudheerkumar help me with error.. Without error i wont be able to comment. Seems either permission or linkage is missing

  • @bhakta_rg
    @bhakta_rg 8 месяцев назад

    Thanks for the video. Couple of questions -
    You hardcoded the instance Id of the compromised instance in the Lambda environment variables? How will this work in a production scenario where any instance can become compromised and tries to communicate with the malicious instance. How would you get the instance ID of the compromised instance then?
    The SG of the compromised instance has ALL outbound access but no inbound access from the malicious IP address correct? If the nmap script is failing, the finding is still generated in Security hub?

  • @Prakash-vb3bp
    @Prakash-vb3bp 11 месяцев назад

    0:17

  • @Prakash-vb3bp
    @Prakash-vb3bp 11 месяцев назад

    0:29