Hacking For Dummies Cheat Sheet - For Dummies

http://www.dummies.com/how-to/content/hacking-for-dummies-cheat-sheet.html

Hacking For Dummies

Not all hacking is bad. The security testing covered in this book reveals security weaknesses or flaws in your computing setups. This Cheat Sheet provides you with quick references to tools and tips, alerts you to commonly hacked targets — information you need to make your security testing efforts easier.

Hacking Tools You Can't Live Without

As an information security professional, your toolkit is the most critical item you can possess against hacking — other than hands-on experience and common sense. Your hacking tools should consist of the following (and make sure you're never on the job without them):

• Password cracking software, such as ophcrack and Proactive Password Auditor

• Network scanning software, such as Nmap and NetScanTools Pro

• Network vulnerability scanning software, such as LanGuard and Nexpose

• Network analyzer software, such as Cain & Abel and CommView

• Wireless network analyzer and software, such as Aircrack-ng and CommView for WiFi

• File search software, such as FileLocator Pro

• Web application vulnerability scanning software, such as Acunetix Web Vulnerability Scanner and AppSpider

• Database security scanning software, such as SQLPing3

• Exploit software, such as Metasploit

Common Security Weaknesses that Criminal Hackers Target

Information security professionals should know the common security weaknesses that criminal hackers and malicious users first check for when hacking into computer systems. Security flaws, such as the following, should be on your checklist when you perform your security tests:

• Gullible and overly-trusting users

• Unsecured building and computer room entrances

• Discarded documents that have not been shredded and computer disks that have not been destroyed

• Network perimeters with little to no firewall protection

• Poor, inappropriate, or missing file and share access controls

• Unpatched systems that can be exploited using free tools such as Metasploit

• Web applications with weak authentication mechanisms

• Guest wireless networks that allow the public to connect into the corporate network environment

• Laptop computers with no full disk encryption

• Mobile devices with easy to crack passwords or no passwords at all

• Weak or no application, database, and operating system passwords

• Firewalls, routers, and switches with default or easily guessed passwords

Commonly Hacked Ports

Common ports, such as TCP port 80 (HTTP), may be locked down — but other ports may get overlooked and be vulnerable to hackers. In your security tests, be sure to check these commonly hacked TCP and UDP ports:

• TCP port 21 — FTP (File Transfer Protocol)

• TCP port 22 — SSH (Secure Shell)

• TCP port 23 — Telnet

• TCP port 25 — SMTP (Simple Mail Transfer Protocol)

• TCP and UDP port 53 — DNS (Domain Name System)

• TCP port 443 — HTTP (Hypertext Transport Protocol) and HTTPS (HTTP over SSL)

• TCP port 110 — POP3 (Post Office Protocol version 3)

• TCP and UDP port 135 — Windows RPC

• TCP and UDP ports 137–139 — Windows NetBIOS over TCP/IP

• TCP port 1433 and UDP port 1434 — Microsoft SQL Server

Tips for Successful IT Security Assessments

You need successful security assessments to protect your systems from hacking. Whether you're performing security tests against your own systems or for those of a third party, you must be prudent and pragmatic to succeed. These tips for security assessments will help you succeed in your role as an information security professional:

• Set goals and develop a plan before you get started.

• Get permission to perform your tests.

• Have access to the right tools for the tasks at hand.

• Test at a time that's best for the business.

• Keep the key players in the loop during your testing.

• Understand that it's not possible to detect every security vulnerability on every system.

• Study malicious hacker and rogue insider behaviors and tactics. The more you know about how the bad guys work, the better you'll be at testing your systems for security vulnerabilities.

• Don't overlook nontechnical security issues; they're often exploited first.

• Make sure that all your testing is aboveboard.

• Treat other people's confidential information at least as well as you would treat your own.

• Bring vulnerabilities you find to the attention of management and implement the appropriate countermeasures as soon as possible.

• Don't treat every vulnerability discovered in the same manner. Not all weaknesses are bad. Evaluate the context of the issues found before you declare that the sky is falling.

• Show management and customers that security testing is good business and you're the right professional for the job. Security assessments are an investment to meet business goals, find what really matters, and comply with the various laws and regulations — not about silly hacker games.

^ed