AWS EC2 Instance Involved in Brute Force Attack
Dash が新機能を発表!インシデントマネジメント、Continuous Profiler など多数の機能が追加されました! Dash イベントで発表された新機能!
<  Back to rules search

AWS EC2 Instance Involved in Brute Force Attack

guardduty

Classification:

attack

Tactic:

Technique:

Set up the guardduty integration.

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Overview

Goal

Detect Brute Force Attacks

Strategy

Leverage GuardDuty and detect when an attacker is performing a brute force attack. The following are GuardDuty findings trigger this signal:

Triage & Response

  1. Inspect the role of the EC2 instance in the attack. Find the role in the signal name - either ACTOR or TARGET.
    • If you are the TARGET and the instance is available on the internet, expect to see IPs scanning your systems.
    • If you are the TARGET and the instance is not available on the internet, this means a host on your internal network is scanning your EC2 instance. Open an investigation.
    • If you are the ACTOR, this means that your instance is performing brute force attacks on other systems. Open an investigation.