Unrestricted inbound RPC access
Incident Management が一般に使用できるようになりました。 Incident Management が広範に使用できるようになりました。
<  Back to rules search

Unrestricted inbound RPC access

ec2

Classification:

compliance

Set up the ec2 integration.

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

Overview

Description

Reduce the probability of a breach by checking EC2 security groups for inbound rules that allow unfettered access to TCP port 135 (used by Microsoft Message Queuing (MSMQ) and other Windows software) and restrict access to IP addresses that require this port.

Rationale

Malicious activity, such as backdoor command shell hacking and denial-of-service (DoS) attacks, can occur when permitting unfettered access to this port.

Remediation

  1. Run revoke-security-group-ingress to remove inbound rules that allow unrestricted access to port 135.

    revoke-security-group-ingress.sh

        aws ec2 revoke-security-group-ingress
            --group-name group-name
            --protocol tcp
            --port 135
            --cidr 192.0.2.0/24
        
  2. Run authorize-security-group-ingress to add new inbound rules that restrict port 135 access.

    revoke-security-group-ingress.sh

        aws ec2 authorize-security-group-ingress
            --group-name your-group-name
            --protocol tcp
            --port 135
            --cidr 192.0.2.0/24