jetlib.sec » Penetration Testing » Should or shouldn't block public ping to a website

Feeds

133326 items (0 unread) in 27 feeds

• 1337day (was: Inj3ct0r, 1337db)
• OSVDB Vulnerabilities
• Exploit-DB
• SecurityFocus Vulnerabilities
• Bugtraq
• Full Disclosure
• XSSed
• Packet Storm Security Headlines
• Packet Storm Security Advisories
• Packet Storm Security Exploits
• Packet Storm Security Recent Files
• Packet Storm Security Tools
• Packet Storm Security Misc. Files
• Sophos security news
• Sophos product advisories
• Penetration Testing
• SecuriTeam
• BackTrack Linux Forums
• Threatpost
• SecDocs
• carnal0wnage.attackresearch.com
• Carnal0wnage
• Kernel Fun
• Darknet
• The Exploitant
• Hack a Day
• Wirevolution

Penetration Testing

• September 06, 2011
• 

  Should or shouldn't block public ping to a website

  Posted: September 6th, 2011, 6:43am PDT

  Tags:   

  Posted by ShiYih Lye on Sep 06

  Hi,
  
  All this while I'm not allowing any public ping to the website I'm
  maintaining, but it's making me tougher to troubleshoot should any
  user from the globe having trouble to access our website, as I can't
  make them to send a proper traceroute report.
  
  To your opinion, is it necessary to block public ping to a public
  website ? Is this security practice still relevant in today exploit
  technology ?
  
  And if you think it's...