
The Network Security Test Lab
Beschreibung
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
Weitere Details
Weitere Ausgaben
Andere Ausgaben


Person
Inhalt
Introduction xxi
Chapter 1 Building a Hardware and Software Test Platform 1
Why Build a Lab? 2
Hardware Requirements 4
Physical Hardware 5
Equipment You Already Have 6
New Equipment Purchases 7
Used Equipment Purchases 7
Online Auctions 8
Thrift Stores 9
Company Sales 10
Virtual Hardware 10
VMware 12
VirtualBox 15
Hacker Hardware 16
Software Requirements 18
Operating Systems 19
Microsoft Windows 19
Linux 20
Navigating in Linux 23
Linux Basics 25
Mac Os X 28
Software and Applications 28
Learning Applications 29
Hacking Software 31
Summary 32
Key Terms 33
Exercises 34
Equipment Checklist 34
Installing VMware Workstation 35
Exploring Linux Operating System Options 35
Using VMware to Build a Windows Image 35
Using VMware Converter to Create a Virtual Machine 36
Exploring Other Operating System Options 37
Running Kali from VMware 37
Installing Tools on Your Windows Virtual Machine 38
Chapter 2 Passive Information Gathering 39
Starting at the Source 40
Scrutinizing Key Employees 43
Dumpster Diving (Electronic) 45
Analyzing Web Page Coding 48
Exploiting Website Authentication Methods 51
Mining Job Ads and Analyzing Financial Data 53
Using Google to Mine Sensitive Information 56
Exploring Domain Ownership 57
Whois 59
Regional Internet Registries 61
Domain Name System 63
Identifying Web Server Software 66
Web Server Location 69
Summary 70
Key Terms 70
Exercises 72
IP Address and Domain Identification 72
Information Gathering 72
Google Hacking 74
Banner Grabbing 74
Telnet 75
Netcat 75
VisualRoute 76
Chapter 3 Analyzing Network Traffic 77
Why Packet Analysis Is Important 77
How to Capture Network Traffic 78
Promiscuous Mode 78
Hubs and Switches 79
Hubbing Out and Using Taps 79
Switches 79
Capturing Network Traffic 82
Managed and Unmanaged Switches 83
ARP Cache Poisoning 85
Flooding 91
DHCP Redirection 92
Redirection and Interception with ICMP 94
Preventing Packet Capture 94
Dynamic Address Inspection 95
DHCP Snooping 95
Preventing VLAN Hopping 96
Detecting Packet Capture 97
Wireshark 99
Wireshark Basics 99
Filtering and Decoding Traffic 102
Basic Data Capture-A Layer-by-Layer Review 108
Physical-Data-Link Layer 108
Network-Internet Layer 110
Transport-Host-Host Layer 111
Application Layer 115
Other Network Analysis Tools 115
Summary 118
Key Terms 118
Exercises 119
Fun with Packets 119
Packet Analysis with tcpdump 120
Packet Filters 121
Making a One-Way Data Cable 122
Chapter 4 Detecting Live Systems and Analyzing Results 125
TCP/IP Basics 125
The Network Access Layer 127
The Internet Layer 128
The Host-to-Host Layer 132
Transmission Control Protocol 132
User Datagram Protocol 134
The Application Layer 134
Detecting Live Systems with ICMP 138
ICMP-Ping 138
Traceroute 142
Port Scanning 147
TCP and UDP Port Scanning 147
Advanced Port-Scanning Techniques 151
Idle Scan 151
Analyzing Port Scans 155
Port-Scanning Tools 156
Nmap 157
SuperScan 160
Other Scanning Tools 161
OS Fingerprinting 161
Passive Fingerprinting 162
Active Fingerprinting 164
How Nmap OS Fingerprinting Works 165
Scanning Countermeasures 167
Summary 171
Key Terms 171
Exercises 172
Understanding Wireshark 172
Interpreting TCP Flags 174
Performing an ICMP Packet Decode 175
Port Scanning with Nmap 176
Traceroute 177
An Analysis of a Port Scan 178
OS Fingerprinting 179
Chapter 5 Enumerating Systems 181
Enumeration 181
Router and Firewall Enumeration 182
Router Enumeration 182
Firewall Enumeration 187
Router and Firewall Enumeration Countermeasures 191
Windows Enumeration 191
Server Message Block and Interprocess Communication 194
Enumeration and the IPC$ Share 195
Windows Enumeration Countermeasures 195
Linux/Unix Enumeration 196
Enumeration of Application Layer Protocols 197
Simple Network Management Protocol 197
SNMP Enumeration Countermeasures 200
Enumeration of Other Applications 200
Advanced Enumeration 202
SCADA Systems 202
User Agent Strings 210
Mapping the Attack Surface 213
Password Speculation and Cracking 213
Sniffing Password Hashes 216
Exploiting a Vulnerability 218
Protecting Passwords 221
Summary 221
Key Terms 222
Exercises 223
SNMP Enumeration 223
Enumerating Routing Protocols 225
Enumeration with DumpSec 227
Identifying User Agent Strings 227
Browser Enumeration 229
Chapter 6 Automating Encryption and Tunneling Techniques 231
Encryption 232
Secret Key Encryption 233
Data Encryption Standard 235
Triple DES 236
Advanced Encryption Standard 237
One-Way Functions (Hashes) 237
md Series 238
Sha 238
Public Key Encryption 238
Rsa 239
Diffie-Hellman 239
El Gamal 240
Elliptic Curve Cryptography 240
Hybrid Cryptosystems 241
Public Key Authentication 241
Public Key Infrastructure 242
Certificate Authority 242
Registration Authority 242
Certificate Revocation List 243
Digital Certificates 243
Certificate Distribution System 244
Encryption Role in Authentication 244
Password Authentication 245
Password Hashing 246
Challenge-Response 249
Session Authentication 250
Session Cookies 250
Basic Authentication 251
Certificate-Based Authentication 251
Tunneling Techniques to Obscure Traffic 252
Internet Layer Tunneling 252
Transport Layer Tunneling 254
Application Layer Tunneling 256
Attacking Encryption and Authentication 259
Extracting Passwords 259
Password Cracking 260
Dictionary Attack 261
Brute-Force Attack 261
Rainbow Table 263
Other Cryptographic Attacks 263
Summary 264
Key Terms 264
Exercises 266
CrypTool 266
Extract an E-mail Username and Password 268
RainbowCrack 268
John the Ripper 270
Chapter 7 Automated Attack and Penetration Tools 273
Why Attack and Penetration Tools Are Important 274
Vulnerability Assessment Tools 274
Source Code Assessment Tools 275
Application Assessment Tools 276
System Assessment Tools 276
Attributes of a Good System Assessment Tool 278
Nessus 279
Automated Exploit Tools 286
Metasploit 286
Armitage 287
Metasploit Console 288
Metasploit Command-Line Interface 289
Updating Metasploit 290
BeEF 290
Core Impact 291
Canvas 292
Determining Which Tools to Use 292
Picking the Right Platform 292
Summary 293
Key Terms 294
Exercises 294
Exploring N-Stalker, a Vulnerability Assessment Tool 294
Exploring Searchsploit on Kali Linux 295
Metasploit Kali 296
Chapter 8 Securing Wireless Systems 299
Wi-Fi Basics 300
Wireless Clients and NICs 301
Wireless Access Points 302
Wireless Communication Standards 302
Bluetooth Basics 304
Wi-Fi Security 305
Wired Equivalent Privacy 305
Wi-Fi Protected Access 307
802.1x Authentication 309
Wireless LAN Threats 310
Wardriving 310
NetStumbler 312
Kismet 314
Eavesdropping 314
Rogue and Unauthorized Access Points 318
Denial of Service 319
Exploiting Wireless Networks 320
Finding and Assessing the Network 320
Setting Up Airodump 321
Configuring Aireplay 321
Deauthentication and ARP Injection 322
Capturing IVs and Cracking the WEP KEY 322
Other Wireless Attack Tools 323
Exploiting Bluetooth 324
Securing Wireless Networks 324
Defense in Depth 325
Misuse Detection 326
Summary 326
Key Terms 327
Exercises 328
Using NetStumbler 328
Using Wireshark to Capture Wireless Traffic 329
Chapter 9 An Introduction to Malware 331
History of Malware 331
Types of Malware 334
Viruses 334
Worms 337
Logic Bombs 338
Backdoors and Trojans 338
Packers, Crypters, and Wrappers 340
Rootkits 343
Crimeware Kits 345
Botnets 347
Advanced Persistent Threats 350
Spyware and Adware 350
Common Attack Vectors 351
Social Engineering 351
Faking It! 352
Pretending through Email 352
Defenses against Malware 353
Antivirus 353
File Integrity Verification 355
User Education 355
Summary 356
Key Terms 356
Exercises 357
Virus Signatures 357
Building Trojans 358
Rootkits 358
Finding Malware 362
Chapter 10 Detecting Intrusions and Analyzing Malware 365
An Overview of Intrusion Detection 365
IDS Types and Components 367
IDS Engines 368
An Overview of Snort 370
Platform Compatibility 371
Limiting Access to the IDS 371
Verification of Configuration 372
Building Snort Rules 373
The Rule Header 374
Logging with Snort 375
Rule Options 376
Advanced Snort: Detecting Buffer Overflows 377
Responding to Attacks and Intrusions 379
Analyzing Malware 381
Tracking Malware to Its Source 382
Identifying Domains and Malicious Sites 382
Building a Testbed 386
Virtual and Physical Targets 386
Operating Systems 387
Network Isolation 387
Testbed Tools 388
Malware Analysis Techniques 390
Static Analysis 390
Dynamic Analysis 394
Summary 397
Key Terms 397
Exercises 398
Building a Snort Windows System 398
Analyzing Malware Communication 400
Analyzing Malware with VirusTotal 401
Chapter 11 Forensic Detection 403
Computer Forensics 404
Acquisition 405
Drive Removal and Hashing 407
Drive-Wiping 409
Logical and Physical Copies 410
Logical Copies 411
Physical Copies 411
Imaging the Drive 412
Authentication 413
Trace-Evidence Analysis 416
Browser Cache 418
Email Evidence 419
Deleted or Overwritten Files and Evidence 421
Other Trace Evidence 422
Hiding Techniques 422
Common File-Hiding Techniques 423
Advanced File-Hiding Techniques 425
Steganography 426
Detecting Steganographic Tools 429
Antiforensics 430
Summary 431
Key Terms 431
Exercises 432
Detecting Hidden Files 432
Basic File-Hiding 432
Advanced File-Hiding 433
Reading Email Headers 433
Use S-Tools to Embed and Encrypt a Message 435
Index 439
CHAPTER 1
Building a Hardware and Software Test Platform
This book is designed for those who need to better understand the importance of IT security. This chapter walks you through what you need to set up a hardware/software test platform. As a child, you may have loved to take things apart, TVs, radios, computers, and so on, in a quest to better understand how they worked. Your tools probably included soldering irons, screwdrivers-maybe even a hammer! That is similar to what you will be doing throughout this book. While you won't be using a hammer, you will be looking at protocols and applications to understand how they work. You will also examine some common tools that will make your analysis easier. The objective is to help you become a better network analyst, and improve and sharpen your IT security skills.
Because no two networks are the same, and because they change over time, it is impossible to come up with a one-size-fits-all list of hardware and software that will do the job for you. Networks serve the enterprises that own them, and enterprises must change over time. In addition, the scale of operation impacts security considerations. If you pursue a career as a security consultant, your goals (and inevitably your needs) will differ, depending on whether you work for a large multinational corporation (and even here, your goals and needs will depend on the type of industry) or a small office/home office (SOHO) operation or a small business. Clearly, a whole spectrum of possibilities exists here.
This chapter provides the first step in building your own network security lab. You will start to examine the types of hardware and gear that you can use to build such a test environment, and then look at the operating systems and software you should consider loading on your new equipment.
Why Build a Lab?
A laboratory is as vital to a computer-security specialist as it is to a chemist or biologist. It is the studio in which you can control a large number of variables that come to bear upon the outcome of your experiments. And network security, especially, is a field in which the researcher must understand how a diverse range of technologies behave at many levels. For a moment, just consider the importance of the production network to most organizations. They must rely on an always-on functioning, which means that many tests and evaluations must be developed in a lab on a network that has been specifically designed for such experiments.
NOTE A laboratory is a controlled environment in which unexpected events are nonexistent or at least minimized. Having a lab provides a consequence-free setting in which damage that might result from experimentation is localized (and can, it is hoped, be easily corrected).
Consider something as basic as patch management. Very few organizations move directly from downloading a patch to installing it in the production environment. The first step is to test the patch. The most agreed-upon way to accomplish this is to install it on a test network or system. This allows problems to be researched and compatibility ensured. You might also want to consider a typical penetration test. It may be that the penetration-testing team has developed a new exploit or written a specific piece of code for this unique assignment. Will the team begin by deploying this code on the client's network? Hopefully not. The typical approach would be to deploy the code on a test network to verify that it will function as designed. The last thing the penetration test team needs is to be responsible for a major outage on the client's network. These types of events are not good for future business.
Building a lab requires you to become familiar with the basics of wiring, signal distribution, switching, and routing. You also need to understand how you might tap into a data stream to analyze or, potentially, attack the network. The mix of common network protocols must be understood; only by knowing what is normal on the network can you recognize and isolate strange behavior. Consider some of the other items that might motivate you to construct such a lab:
- Certification
- Job advancement
- Knowledge
- Experimentation
- Evaluation of new tools
To varying degrees, networking- and security-related certifications require knowledge of the hardware and software of modern networks. There is no better vehicle for learning about networking and security issues firsthand than to design and build your own network lab. This provides a place where you can add and remove devices at will and reconfigure hardware and software to your liking. You can observe the interaction between the systems and networking devices in detail.
Advancing in your field is almost never an accident. The IT industry is an area of constant change, and the best way to build a career path in the world of IT is to build your skill set. By mastering these technologies, you will be able to identify the knowledgeable people on the job or at a customer's site, and align yourself with them. You might even uncover some gifts that you did not previously realize you possessed, such as a love for hexadecimal-well, maybe.
Building a lab demonstrates your desire and ability to study and control networks. One key item that potential employers always consider is whether a candidate has the drive to get the job done. Building your own security lab can help demonstrate to employers that you are looking for more than just a job: You want a career. As you use the network resources in your lab, you will invariably add to your knowledge and understanding of the technologies that you employ. Learning is a natural consequence.
Experimentation is a practical necessity if you are to fully understand many of the tools and methods employed by security professionals and hackers alike. Just consider the fact that there are many manuals that explain how Windows Server 2012 works, or how a Check Point firewall works, but no manual can account for every single situation and what is 'unique' to any environment you encounter. Some combinations and interactions are simply unknown. By building your own lab, you will discover that when deployed in complex modern networks, many things do not work the way the documentation says they will. And many times, it does not suffice to simply understand what happens; you need to appreciate the timing and sequence of events. This requires the control that a laboratory environment provides.
Because IT is an industry of continual change, new software, new security tools, new hacking techniques, and new networking gizmos constantly appear. A network security lab provides you with a forum in which to try these things out. You certainly don't want to risk corrupting a computer that you depend on every day to do your job. And you don't want to negatively impact the work of others; doing so is a good way to quickly put the brakes on your budding career.
A laboratory thus provides a place where you can try new things. This is a setting in which you can gain a detailed understanding of how things are put together and how they normally interact. It is an environment in which you can likely predict the outcome of your experiments, and if an outcome is unexpected, you can then isolate the cause.
BUILDING YOUR OWN SECURITY LAB
A common question among students and those preparing for certification is, "How do I really prepare for the job or promotion I am seeking?" The answer is always the same: know the material, but also get all the hands-on experience you can. Many times they don't have enough money in their IT budget, or they are a struggling student. That is totally understandable. Yet the fact remains that there is no way to pick up many of the needed skills by reading alone. And many tests cannot be conducted on a live Internet-connected network.
With a little work and effort, you can find the equipment required to practice necessary skills at a reasonable price-network professionals have been doing this for years. There are even sites such as certificationkits.com that are set up exclusively to provide students with a full set of networking gear needed to complete a Cisco Certified Network Associate (CCNA) or a Cisco Certified Network Professional (CCNP) certification.
Hardware Requirements
Before you can get started with any testing, you need to assemble some hardware. Your goal, as always, will be to do this as inexpensively as possible. Many things might be included in a network security laboratory. Some of these items are mandatory (for example, cables), and some things can be added according to your needs and as they become available or affordable. Although it is possible to contain everything within one computer, your requirements will vary from time to time based on the scenario that you are modeling.
Here are some of the things that will likely end up in your mix:
- Computers
- Networking tools
- Cables
- Network-attached storage (NAS)
- Hubs
- Switches
- Routers
- Removable disk storage
- Internet connection
- Cisco equipment
- Firewalls
- Wireless access points
- Keyboard, video, mouse (KVM) switches
- Surge suppressors and power strips
In your network lab, you will need a wide variety of cables, as this will allow you to configure your test network in many different ways. Specific configurations will be needed for different scenarios. You...
Systemvoraussetzungen
Dateiformat: ePUB
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat ePUB ist sehr gut für Romane und Sachbücher geeignet – also für „fließenden” Text ohne komplexes Layout. Bei E-Readern oder Smartphones passt sich der Zeilen- und Seitenumbruch automatisch den kleinen Displays an.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.