About VivekPAN

VivekPAN · ‎04-19-2023

Thanks for all your responses still I could not find the reason behind how Telnet works even If I don't allow it. Here is another example. I could do Telnet successfully from the source to dest as shown below but I have the policy which allows only the SSL app over port 8443. And there is no other policy which allows "Telnet" app as I checked completely in the FW monitor. Attached the FW logs and security policy snaps for reference. [xxx@ttgnapp0vrhom02 ~]$ telnet ttgnapp1vrhwe02.ttgtpmg.net 8443 Trying 172.20.248.150... Connected to ttgnapp1vrhwe02.ttgtpmg.net. ttgnapp0vrhom02 - is nothing but the server-ttgnapp0vrhom02 object in the FW policy ttgnapp1vrhwe02.ttgtpmg.net - is an object within the address-group grp-pp-mw-eweb-servers in the FW policy I assume only the https over 8443 should work but how come Telnet /tcp 8443 ?

VivekPAN · ‎06-29-2022

Hi Tom, Thanks for your response. 1/ I don't have a firewall rule which allows the tcp/27017 at all but the telnet to the port 27017 from the source goes successful. 2, I have another query which is no way related to above query. For example, I have the below policy in place in my FW. The actual SSL application works fine from the source to the destination. But if I do a "telnet 172.1.1.2 443" from source - 10.1.1.1, the connection gets "TCP timeout" as a result. Do I need to allow "Telnet" application also in the same policy to make this work? And which means telnet'ing the destination with TCP port does not help to verify the 3-way handshake unless we don't have "telnet" app is allowed between them? source - 10.1.1.1 destination - 172.1.1.2 destination port - 443 application - ssl service - application-default action - allow

VivekPAN · ‎06-17-2022

Thanks for your reply but I would like to give more clarity on my issue where telnet to 27017 works even there is no policy and it's not showing in the logs as well. It took me backwards while seeing such occurence when I did a troubleshooting. PS : it's not allowed by any implicit policies also.

VivekPAN · ‎06-13-2022

There is no FW policy which allows the SSL application over port TCP 27017 between the given source/destinations. In fact it shows deny in the monitor -> logs but I'm able to telnet the from the source to the destination - 172.20.249.77 over port 27017 successfully which is weird really. What could be the reason for this? Deny Logs

Member Since	‎06-13-2022 05:50 AM
Date Last Visited	‎05-12-2023 12:46 AM
Posts	4
Total Likes Received	1

Online Status	Offline
Date Last Visited	‎05-12-2023 12:46 AM

About VivekPAN

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Re: Telnet to TCP port works even without a valid implicit/explicit security policy

Telnet to TCP port works even without a valid implicit/explicit security policy