Skip to content

Commit

Permalink
Patch 489 (#511)
Browse files Browse the repository at this point in the history
* Update open-telnet.md

* Updated all steps

* Update open-telnet.md

* Apply suggestions from code review

Co-authored-by: alphadev4 <[email protected]>
  • Loading branch information
shuklaalok87 and alphadev4 authored Oct 26, 2022
1 parent 7a30a1c commit 283dcdc
Show file tree
Hide file tree
Showing 9 changed files with 7 additions and 9 deletions.
16 changes: 7 additions & 9 deletions en/azure/networksecuritygroups/open-telnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,14 @@
| **Recommended Action** | Restrict TCP port 23 to known IP addresses |

## Detailed Remediation Steps


1. Log into the Microsoft Azure Management Console.
2. Select the "Search resources, services, and docs" option at the top and search for Network security groups. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step2.png"/>
1. Log in to the Microsoft Azure Management Console.
2. Click the search bar at the top and search for Network security groups. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step2.png"/>
3. Select the "Network security group" that needs to be verified. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step3.png"/>
4. Click on the "Name" of the selected "Network security group" to access the port configurations. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step4.png"/>
5. In the "Overview" tab scroll down the page and check the "Inbound security rules" under the "Settings". </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step5.png"/>
6. If the "Telnet" for port 23 with the protocol "TCP" is showing as "Allow" for all "Source" and "Destination" then the selected "Network security group" has TCP port 23 for Telnet open to the public. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step6.png"/>
7. Repeat steps number 2 - 6 to verify other "Network security group." </br>
8. Navigate to the "Network security group" and select the security group that needs to modify for restricting the "TCP" port for "Telnet" on port 23 to specific IP Address.</br> <img src="/resources/azure/networksecuritygroups/open-telnet/step8.png"/>
6. If the "Telnet" for port 23 with the protocol "TCP" is showing as "Allow" under column "Action" for all "Source" and "Destination" then the selected "Network security group" has TCP port 23 for Telnet open to the public. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step6.png"/>
7. Repeat step number 2 - 6 to verify other "Network security groups". </br>
8. Navigate to the "Network security group" and select the security group that needs to be modified for restricting the "TCP" port for "Telnet" on port 23 to specific IP Address.</br> <img src="/resources/azure/networksecuritygroups/open-telnet/step8.png"/>
9. Scroll down the left navigation panel and choose "Inbound security rules" under "Settings."</br> <img src="/resources/azure/networksecuritygroups/open-telnet/step9.png"/>
10. Click on the "Telnet" protocol in the "Name" column and under "Source" select the "IP Address" from the dropdown menu and enter the "Source IP addresses/CIDR ranges" as per the requirement, select the required Protocol and Action and click on the "Save" option at the top panel. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step10.png"/>
11. Repeat steps number 8 - 10 to restrict TCP port 23 for Telnet to known IP addresses.</br>
10. Click on the "Telnet" protocol in the "Name" column and in the right pane under "Source" select the "IP Address" from the dropdown menu and enter the "Source IP addresses/CIDR ranges" as per the requirement, select the required "Protocol" and "Action" and click on the "Save" option at the top of the pane. </br> <img src="/resources/azure/networksecuritygroups/open-telnet/step10.png"/>
11. Repeat step number 8 - 10 to restrict TCP port 23 for Telnet to known IP addresses.</br>
Binary file modified resources/azure/networksecuritygroups/open-telnet/step10.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step8.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/azure/networksecuritygroups/open-telnet/step9.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 283dcdc

Please sign in to comment.