way2backdoor

CCNA INTRODUCTION AND CERTIFICATION

Sunday, 11 January 2015

INTRODUCTION

CCNA certification is a cornerstone of many IT careers. This book is a comprehensive study guide for the CCNA Intro, CCNA ICND and CCNA Certification exams. Its target audience is a high school student, a first year community college or any adult wanting to understand networking better.

CERTIFICATION
The CCNA certification test can be taken in one of two ways:

You can take the CCNA INTRO Exam (640-822) and the CCNA ICND (640-816)
You can take the combined CCNA Exam (640-801)
The new combined CCNA Exam is the 640-802 and reduces WAN topics in favor of wireless technology.

The CCNA INTRO Exam tests for a shallow understanding of a broad range of basic networking concepts. The CCNA ICND Exam tests for a deeper knowledge of particular areas of networking. The combined CCNA tests all the material covered in the INTRO and ICND Exams. (For information about the exam and your options, see Appendix A.)

The contents of this book are split into two sections (INTRO and ICND) so those who are taking the individual tests can study for them separately. For those who are taking the combined CCNA Exam, study both sections fully.

TOPICS

Ref No.	Topics
	Describe the operation of data networks
1	Describe the purpose and functions of various network devices
2	Select the components required to meet a given network specification
3	Use the OSI and TCP/IP models and their associated protocols to explain how data flows in a network
4	Describe common networking applications including web applications
5	Describe the purpose and basic operation of the protocol in the OSI and TCP model
6	Describe the impact of applications (Voice over IP and Video over IP) on a network
7	Interpret network diagrams
8	Determine the path between two host across a network
9	Describe the components required for network and Internet communications
10	Identify and correct common network problems at Layers 1,2,3 and 7 using a layered model approach
11	Differentiate between LAN/WAN operation and features
	Implement a small switched network
12	Select the appropriate media, cable, ports, and connectors to connect switches to other network devices and hosts
13	Explain the technology and media access control method for Ethernet technologies
14	Explain the network segmentation and basic traffic management concepts
15	Explain the operation of Cisco switches and basic switching concepts
16	Perform, Save, and verify initial switch configuration tasks including remote access management
17	Verify network status and switch operation using basic utilities (including ping, traceroute, telnet, SSH, arp, and IP config) show and Debug commands
18	Implement and verify basic security for a switch (port security, deactivate ports)
19	Identify, prescribe, and resolve common switched network media issues, configuration issues, auto negotiation, and switch hardware failures
	Implement an IP addressing scheme and IP services to meet network requirements for a small branch office
20	Describe the need and role of addressing in a network
21	Create and apply an addressing scheme to a network
22	Assign and verify valid IP addresses to hosts, servers, and networking devices in a LAN environment
23	Explain the basic uses and operation of NAT in a small network connecting to one ISP
24	Describe and verify DNS operation
25	Describe the operation and benefits of using private and public IP addressing
26	Enable NAT for a small network with a single ISP and connection using SDM and verify operation using CLI and ping
27	Configure, verify, and troubleshoot DHCP and DNS operation on a router (including CLI/SDM)
28	Implement static and dynamic addressing services for hosts ina LAN environment
29	Identify and correct IP addressing issues
30	Describe basic routing concepts (including packet forwarding, router lookup process)
31	Describe the operation of Cisco routers (including router bootup process, POST, and router components)
32	Select the appropriate media, cables, ports, and connectors to connect routers to other network devices and hosts
33	Configure, verify, and troubleshoot RIPv2
34	Access and utilize the router CLI to set basic parameters
35	Connect, configure, and verify operation status of a device interface
36	Verify device configuration and network connectivity using ping, traceroute, telnet, SSH, or other utilities
37	Perform and verify routing configuration tasks for a static or default route given specific routing requirements
38	Manage IOS configuration files (including save, edit, upgrade, and restore)
39	Manage Cisco IOS
40	Implement password and physical security
41	Verify network status and router operation using utilities (including ping, traceroute, telnet, SSH, arp, and ipconfig), show and debug commands
42	Describe standards associated with wireless media (including IEEE, WiFi, Alliance, and ITU/FCC)
43	Identify and describe the purpose od the components in a small wireless network. (including SSID, BSS, and ESS)
44	Identify the basic parameters to configure on a wireless network to ensure that devices connect to the correct access point
45	Compare and contrast wireless security features and capabilities of WPA security (including open, WEP, and WPA-1/2)
46	Identify common issues with implementing wireless networks
	Identify security threats to a network and describe general methods to migrate those threats
47	Explain today's increasing network security threats and the need to implement a comprehensive security policy to mitigate the treaths
48	Explain general methods to mitigate common security threats to network devices, hosts, and applications
49	Describe the functions of common security appliances and applications
50	Describe security recommended practices including initial steps to secure network devices
	Implement and verify WAN links
51	Describe different methods for connecting to a WAN
52	Configure and verify a basic WAN serial connection

ICND2 Exam Topics

Ref No.	Topics
	Configure, Verify and Troubleshoot a switch with VLANs and interswitch communications
101	Describe enhanced switching technologies (including VTP,RSTP, VLAN, PVSTP, and 802.1q)
102	Describe how VLANs create logically separate networks and the need for routing between them
103	Configure, verify, and troubleshoot VLANs
104	Configure, verify, and troubleshoot trunking on Cisco switches
105	Configure, verify, and troubleshoot interVLAN routing
106	COnfigure, verify, and troubleshoot VTP
107	Configure, verify, and troubleshoot RSTP operation
108	Interpret the output of various show and debug commands to verify the operation status of a Cisco switched network
109	Implement basic switch security (including port security, unassigned ports, trunk access, etc)
	Implement an IP addressing scheme and IP services to meet network requirements in a medium-sized enterprise branch office network
110	Calculate and apply a VLSM IP addressing design to a network
111	Determine the appropriate classless addressing scheme using VLSM and summarization to satisfy addressing requirements in a LAN/WAN environment
112	Describe the technological requirement for running IPv6 (including protocols, Dual stack, tunneling, etc)
113	Describe IPv6 address
114	Identify and correct common problems associated with IP addressing and host configurations
	Configure and trouble shoot basic operation and routing on Cisco devices
115	Compare and contrast methods of routing and routing protocols
116	Configure, verify, and troubleshoot OSPF
117	Configure, verify and troubleshoot EIGRP
118	Verify configuration and connectivity using ping, traceroute, and telnet or SSH
119	Troubleshoot routing implementation issues
120	Verify router hardware and software operating using show and debug commands
121	Implement basic router security
	Implement, verify, and troubleshoot NAT and ACLs in a medium-size enterprise branch office network
122	Describe the purpose and type of access control lists
123	Configure and apply access control lists based on network filtering requirements
124	Configure and apply an access control list to limit telnet and SSH access to the router
125	Verify and monitor ACL's in a network environment
126	Troubleshoot ACL implementation issues
127	Explain the basic operation of NAT
128	Configure Network Address Translate for a given network requirements using CLI
129	Troubleshoot NAT implementation issues
	Implementation and verify WAN links
130	Configure and verify frame relay on Cisco routers
131	Troubleshoot WAN implementation issues
132	Describe VPN technology (including importance, benefits, role, impact, and components)
133	Configure and verify the PPP connection between Cisco routers

Story of Kali linux

Sunday, 11 January 2015

Where did the idea for Kali come from? Were you trying to solve a problem you'd experienced, or did the inspiration come from somewhere else?

Mati Aharoni: The idea for a Live Linux distribution which contains a bunch of security tools was born out of necessity many years ago, when I faced a perplexing dilemma on a security engagement. I was not allowed to bring any hardware to the engagement—and what's more, I was only allowed to use onsite computers on the condition that I would not touch their hard disks or modify them in any way. (I actually was allowed to bring a laptop onsite, however it would be taken on exit).

After thinking long and hard, I figured that these seemingly impossible work conditions could be met by adding a few tools to an existing bootable Live Linux CD (Knoppix 2.0, to those familiar with ancient history). Once created, I would be able to bring in the CD to the engagement, boot an onsite computer with the CD, and work directly out of RAM. At the end of the engagement, I would be able to destroy the CD without too much heart-ache. And so I started a Linux Security based Distribution, ten years ago!

After you came up with the idea, what was the next step?

I will take the liberty to apply this question to our recently released Kali Linux distribution, the 3rd iteration of the Matrix.

Kali Linux was born out of our understanding that we need to take our eight years of experience in building Linux Security Distributions and apply them to a new, clean canvas. This meant tearing down everything we had done to that point, and starting afresh. This process was both terrifying and liberating—on one hand we had let go of our beloved BackTrack distribution, but on the other, we had the opportunity to rebuild and expand our current systems to create something better.

Once this hard decision was made, we figured that the next step should involve people who actually know what they are doing, and we brought in a Debian developer who helped us build our development infrastructure from the ground up. His assistance proved to be invaluable to our project and crucial to the success of the distribution.

How did you choose which platforms to target and which to ignore or wait on?

I'll answer this in regards to our Kali Linux ARM images.

One of our goals with Kali is to provide images of the operating system for all sorts of exotic hardware—mainly ARM based. This includes everything from Raspberry Pi's to tablets, to Android TV devices, with each piece of hardware having some unique property. For example, the MK808 has a dual-core CPU with a whopping 1GB of RAM, while having the form factor of a medium-sized USB dongle. Imagine that: a powerful hacking computer, battery-powered, in your pocket.

So how do we decide what type of ARM hardware to target ? That depends on several things—availability being the main obstacle. We try to identify interesting hardware that could be used in interesting ways for security assessments—and if such is found, we try to build Kali for it. By now, we have a wide array of hardware supported by Kali, and this list keeps on growing every month.

What was your biggest roadblock and how did you overcome it?

One of our biggest concerns with the move from BackTrack to Kali was the rebranding we had to do. After so many years of being a major force in the security community, "BackTrack" was known by all. To suddenly change this around would undoubtedly be hectic and confusing for our users. I thought long and hard at other major rebranding feats in the open source world, and thought to myself, "Didn't Wireshark rebrand a few years ago? What was their name beforehand?" After having to think for two long minutes before coming to the right answer, I figured that rebranding would be tough, but not impossible.

What was launch like for you?

The launch of Kali Linux went better than we could ever have hoped for. We had good friends to support the effort, and a proper infrastructure to support the mind-boggling amounts of traffic required to allow the gazillion downloads we experienced in the first few days.

We had the good sense to create a knowledge source before the release, as well as some community outlets like forums and a bug tracker.

How do you handle user requests and criticisms effectively?

Over the years we have become much more patient with opinionated users and criticism at large. I think we've learned that sometimes a seemingly silly bug report can actually be a symptom of a serious underlying problem. Treating all of these reports with the respect they deserve is something we are getting better and better at as time goes by.

Now, how do you split time between developing new features and managing existing ones?

In Kali, this question can be applied to the tools and features we provide in our distribution. We don't have a specific methodology for this. If we see a useful security tool, or a relevant security feature we think may be useful, we simply add it. A good example for this was the LUKS NUKEfeature in Kali, which allows the user to "self destruct" their hard drive.

hide drives

Sunday, 25 May 2014

steps:
1. Go to start->run.Type regedit.Now go to:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies
\Explorer

2. In the right pane create a new DWORD item and name it NoDrives(it is case sensitive).

3. Modify it's value and set it to 3FFFFFF (Hexadecimal) .

4. Restart the computer.

5. Now when you click on My Computer, no drives will be shown(all gone...).

To enable display of drives in My Computer, simply delete this DWORD item that you created. Restart your computer. All the drives are back again.

create a folder with no name

Sunday, 25 May 2014

steps:
select any folder
>rename it
>press alt & type 0160 or 255

>enter

copy SAM SYSTEM files

Sunday, 25 May 2014

code:
@echo off
mkdir c:\file
reg save HKLM\SAM C:\file\SAM

reg SAVE HKLM\SYSTEM C:\file\SYSTEM

Get remote MAC address

Sunday, 25 May 2014

code:
On error resume next
strComputer = (InputBox("Enter the name of the computer to get the MAC address", "Computer Name"))
If strComputer <> "" Then
strInput = True
End if
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery _
("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")
For Each objItem in colItems
Wscript.Echo objItem.MACAddress

Next