Showing posts with label Basics. Show all posts
Showing posts with label Basics. Show all posts

VNC Basics

Virtual Network Computing, or "VNC," is software used to connect remotely to a computer system. This allows a user to see and control one computer from multiple locations. Because this control is transmitted over the Internet, the computer can be viewed from anywhere in the world.

VNC software is fairly uncomplicated and easy to use. Many operating systems, including Microsoft Windows, already include simple VNC programs. These applications allow users to connect remotely and operate another computer loaded with the same software.

VNCs allow computers to become remotely sharable. This means that several different users, each in separate locations, can view a computer desktop at the same time. VNC software makes training, monitoring and troubleshooting easy by making remote access flexible.

VNC Interface

Most VNC systems are controlled from a simple graphic user interface. Once the software has been installed on a remote computer, it can be accessed from any location. A server constantly monitors inputs and outputs from one computer, and updates them to the second location.

The interface for most VNCs can operate from any operating system, such as Windows, Macintosh, or Unix. Because information is transmitted over the Internet, the system eliminates many of the traditional cross-platform problems. Just as a website can be viewed on many different operating systems, so can VNC control operate from many different computer types. While "VNC" is a generic term for this type of software, many brands of the software exist, with packages available for all major operating systems.

The connection used to interface data is protected by a password. This prevents unauthorized users from controlling a remote computer. Once the connection is established, information begins to be exchanged. Details on mouse location, keyboard entry, and screen updates are fed over the secure connection, keeping the computers synchronized.

VNC Uses

VNC software began as a way to monitor and troubleshoot systems remotely, and this feature remains a common use. Computer technicians can provide tech support using VNC without being physically present. If a user is having a problem installing software, for example, a support professional can connect to her computer, see the problem, and talk the user through the solution.

Use of VNC software has also expanded to other areas. Remote work has become an increasingly popular option. VNC allows workers to access and control software without being in the office. For instance, using VNC, a programmer in India can easily control a desktop computer in California, collaborating with colleagues and working on a project remotely.

Overview

VNC consists of two components. A server, which runs on the computer you want to remotely access, and a viewer, which runs on the computer you are sitting in front of. There are two important features of VNC:
  • The server and the viewer may be on different machines and on types of computer. The protocol which connects the server and viewer is simple, open, and platform independent.
  • No state is stored at the viewer. Breaking the viewer's connection to the server and then reconnecting will not result in any loss of data. Because the connection can be remade from somewhere else, you have easy mobility.
So to get started with VNC you need to run a server, and then connect to it with a viewer. First of all, you have to download and install the software on the platforms you want to use. The screenshots on this page refer to VNC Free Edition 4.1, but the general concepts apply to all versions of Free Edition and Enterprise Edition.

Networking

VNC software requires a TCP/IP connection between the server and the viewer. This is the standard networking protocol on LANs, WANs, broadband and dialup ISP. Each computer has a unique IP address and may also have a name in the DNS. You will need to know the IP address or name of the server when you connect a viewer to it.
Sometimes the IP address is fixed, and sometimes it is issued to you dynamically by your ISP. If it is allocated dynamically, you might consider using a third party DNS management service. Try typing "dynamic dns management service" into a google.

Running a Windows server

Installing the Windows server, WinVNC, should create a RealVNC group in your Start... menu. Run the VNC server.

If this is the first time you've used a VNC server on this machine you'll be prompted to set a password, which you'll need when you connect to the machine from a remote location. A small icon will appear in the system tray, and by right-clicking on this you can control most aspects of the server.

winvnc4_traymenu

The IP address of the computer running the VNC server can be found by hovering over the tray icon in the system tray. Unless this computer has a DNS name, you will need to specify this number to the viewer when you connect.

winvnc4_ipaddr

You can now go to another machine and connect a viewer to the server.

Running a Unix server

To X applications, a VNC server appears just like the standard X display you sit in front of, but without a physical screen attached. The applications don't know this, they just carry on running whether or not a viewer is connected. You can start a new VNC server on a Unix machine by typing:
 
vncserver

If you haven't run a VNC server before you will be prompted for a password, which you will need to use when connecting to this server. All your servers on the same Unix machine will use the same password, and you can change it at a later date using
 
vncpasswd

With a normal X system, the main X display of a workstation called ’snoopy’ is usually snoopy:0. You can also run as many VNC servers on a Unix machine as you like, and they will appear as snoopy:1, snoopy:2 etc, as if they were just additional displays. Normally vncserver will choose the first available display number and tell you what it is, but you can specify a display number if you always wish to use the same one:
vncserver :2

You can cause applications to use a VNC server rather than the normal X display them by setting the DISPLAY environment variable to the VNC server you want, or by starting the application with the -display option.

For example:
xterm -display snoopy:2 &
You can kill a Unix VNC server using, for example:
vncserver -kill :2

Full instructions for installing and running VNC server for Unix can be found in the RealVNC Site documentation.
Nothing will appear immediately as a result of starting a Unix VNC server. To see anything you need to connect a viewer to the server, see below.

Running a viewer

You can run the Windows viewer the RealVNC group on the Start... menu.
winvncviewer4_startmenu

In this case, you will be prompted for the host name (VNC server name) and display number:


winvncviewer4_display

Enter it and click OK, and you will be prompted for your password, after which you should see the remote display. If you are connecting to a Windows or Mac server, the display number will be 0 unless you have explicitly changed it, and can be omitted.

You can run the viewer on Unix and Windows by typing at the command line:
vncviewer snoopy:2

You need to specify the name of the VNC server and the number of the desktop. If, for example, you have started a server as display 2 on a machine called 'snoopy'. Remember that if you are connecting to a Windows or Mac server, the display number will be 0 unless you have explicitly changed it, and can be omitted.

If the machine running the server does not have a DNS entry, you probably won't be able to use the name and will have to replace snoopy with its IP address, for example something that looks like 123.456.78.9.

Using a web browser as a viewer

The VNC servers also contain a small web server. If you connect to this with a web browser, you can download the Java version of the viewer, and use this to view the server. You can then see your desktop from any Java-capable browser, unless you are using a proxy to connect to the web. The server listens for HTTP connections on port 5800+display number. So to view display 2 on machine 'snoopy', you would point your web browser at:

http://snoopy:5802/

The applet will prompt you for your password, and should then display the desktop.
 



An Overview
Cloud computing is a computing paradigm, where a large pool of systems are connected in private or public networks, to provide dynamically scalable infrastructure for application, data and file storage. With the advent of this technology, the cost of computation, application hosting, content storage and delivery is reduced significantly.
Cloud computing is a practical approach to experience direct cost benefits and it has the potential to transform a data center from a capital-intensive set up to a variable priced environment.
The idea of cloud computing is based on a very fundamental principal of „reusability of IT capabilities'. The difference that cloud computing brings compared to traditional concepts of “grid computing”, “distributed computing”, “utility computing”, or “autonomic computing” is to broaden horizons across
organizational boundaries.
Forrester defines cloud computing as:
“A pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption.” 

Figure 1: Conceptual view of cloud computing

Cloud Computing Models
Cloud Providers offer services that can be grouped into three categories.
1              Software as a Service (SaaS): In this model, a complete application is offered to the customer, as a service on demand. A single instance of the service runs on the cloud & multiple end users are serviced. On the customers‟ side, there is no need for upfront investment in servers or software licenses, while for the provider, the costs are lowered, since only a single application needs to be hosted & maintained. Today SaaS is offered by companies such as Google, Salesforce, Microsoft, Zoho, etc.
2              Platform as a Service (Paas): Here, a layer of software, or development environment is encapsulated & offered as a service, upon which other higher levels of service can be built. The

customer has the freedom to build his own applications, which run on the provider‟s
infrastructure. To meet manageability and scalability requirements of the applications, PaaS providers offer a predefined combination of OS and application servers, such as LAMP platform (Linux, Apache, MySql and PHP), restricted J2EE, Ruby etc. Google‟s App Engine, Force.com, etc are some of the popular PaaS examples.
3. Infrastructure as a Service (Iaas): IaaS provides basic storage and computing capabilities as standardized services over the network. Servers, storage systems, networking equipment, data centre space etc. are pooled and made available to handle workloads. The customer would typically deploy his own software on the infrastructure. Some common examples are Amazon, GoGrid, 3 Tera, etc. 

Figure 2: Cloud models

Understanding Public and Private Clouds
Enterprises can choose to deploy applications on Public, Private or Hybrid clouds. Cloud Integrators can play a vital part in determining the right cloud path for each organization.
Public Cloud
Public clouds are owned and operated by third parties; they deliver superior economies of scale to customers, as the infrastructure costs are spread among a mix of users, giving each individual client an attractive low-cost, “Pay-as-you-go” model. All customers share the same infrastructure pool with limited configuration, security protections, and availability variances. These are managed and supported by the cloud provider. One of the advantages of a Public cloud is that they may be larger than an enterprises cloud, thus providing the ability to scale seamlessly, on demand.
Private Cloud
Private clouds are built exclusively for a single enterprise. They aim to address concerns on data security and offer greater control, which is typically lacking in a public cloud. There are two variations to a private cloud:
-On-premise Private Cloud: On-premise private clouds, also known as internal clouds are hosted within one‟s own data center. This model provides a more standardized process and protection, but is limited in aspects of size and scalability. IT departments would also need to incur the capital and operational costs for the physical resources. This is best suited for applications which require complete control and configurability of the infrastructure and security.
-Externally hosted Private Cloud: This type of private cloud is hosted externally with a cloud provider, where the provider facilitates an exclusive cloud environment with full guarantee of privacy. This is best suited for enterprises that don‟t prefer a public cloud due to sharing of physical resources.
Hybrid Cloud
Hybrid Clouds combine both public and private cloud models. With a Hybrid Cloud, service providers can utilize 3rd party Cloud Providers in a full or partial manner thus increasing the flexibility of computing. The Hybrid cloud environment is capable of providing on-demand, externally provisioned scale. The ability to augment a private cloud with the resources of a public cloud can be used to manage any unexpected surges in workload.

Cloud Computing Benefits
Enterprises would need to align their applications, so as to exploit the architecture models that Cloud Computing offers. Some of the typical benefits are listed below:
1. Reduced Cost
There are a number of reasons to attribute Cloud technology with lower costs. The billing model is pay as per usage; the infrastructure is not purchased thus lowering maintenance. Initial expense and recurring expenses are much lower than traditional computing.
2. Increased Storage
With the massive Infrastructure that is offered by Cloud providers today, storage & maintenance of large volumes of data is a reality. Sudden workload spikes are also managed effectively & efficiently, since the cloud can scale dynamically.
3. Flexibility
This is an extremely important characteristic. With enterprises having to adapt, even more rapidly, to changing business conditions, speed to deliver is critical. Cloud computing stresses on getting applications to market very quickly, by using the most appropriate building blocks necessary for deployment.

Cloud Computing Challenges
Despite its growing influence, concerns regarding cloud computing still remain. In our opinion, the benefits outweigh the drawbacks and the model is worth exploring. Some common challenges are:
1. Data Protection
Data Security is a crucial element that warrants scrutiny. Enterprises are reluctant to buy an assurance of business data security from vendors. They fear losing data to competition and the data confidentiality of consumers. In many instances, the actual storage location is not disclosed, adding onto the security concerns of enterprises. In the existing models, firewalls across data centers (owned by enterprises) protect this sensitive information. In the cloud model, Service providers are responsible for maintaining data security and enterprises would have to rely on them.

2. Data Recovery and Availability
All business applications have Service level agreements that are stringently followed. Operational teams play a key role in management of service level agreements and runtime governance of applications. In production environments, operational teams support
·         Appropriate clustering and Fail over
·         Data Replication
·         System monitoring (Transactions monitoring, logs monitoring and others)
·         Maintenance (Runtime Governance)
·         Disaster recovery
·         Capacity and performance management

If, any of the above mentioned services is under-served by a cloud provider, the damage & impact could be severe.

3. Management Capabilities
Despite there being multiple cloud providers, the management of platform and infrastructure is still in its infancy. Features like „Auto-scaling‟ for example, are a crucial requirement for many enterprises. There is huge potential to improve on the scalability and load balancing features provided today.
4. Regulatory and Compliance Restrictions
In some of the European countries, Government regulations do not allow customer's personal information and other sensitive information to be physically located outside the state or country. In order to meet such requirements, cloud providers need to setup a data center or a storage site exclusively within the country to comply with regulations. Having such an infrastructure may not always be feasible and is a big challenge for cloud providers.
With cloud computing, the action moves to the interface — that is, to the interface between service suppliers and multiple groups of service consumers. Cloud services will demand expertise in distributed services, procurement, risk assessment and service negotiation — areas that many enterprises are only modestly equipped to handle.
IPv6 is the next generation protocol for Internet networking. IPv6 expands on the current Internet Protocol standard known as IPv4. Compared to IPv4, IPv6 offers better addressing, security and other features to support large worldwide networks.

In IPv6, IP addresses change from the current 32-bit standard and dotted decimal notation to a new 128-bit address system. IPv6 addresses remain backward compatible with IPv4 addresses. For example, the IPv4 address "192.168.100.32" may appear in IPv6 notation as "0000:0000:0000:0000:0000:0000:C0A8:6420" or "::C0A8:6420".

The most obvious benefit of IPv6 is the exponentially greater number of IP addresses it can support compared to IPv4. Many countries outside the U.S. suffer from a shortage of IP addresses today. Because IPv6 and IPv4 protocols coexist, those locales with an address shortage can easily deploy new IPv6 networks that work with the rest of the Internet. Experts believe it will take many more years before all networks fully change over to IPv6.

Other benefits of IPv6 are less obvious but equally important. The internals of the IPv6 protocol have been designed with scalability and extensibility in mind. This will allow many different kinds of devices besides PCs, like cell phones and home appliances, to more easily join the Internet in future.
An IP address is a logical address for a network adapter. The IP address uniquely identifies computers on a TCP/IP network.

An IP address can be private - for use on a local area network (LAN) - or public - for use on the Internet or other wide area network (WAN). IP addresses can be determined statically (assigned to a computer by a system administrator) or dynamically (assigned by another device on the network on demand).

Two IP addressing standards are in use today. The IPv4 standard is most familar to people and supported everywhere on the Internet, but the newer IPv6 standard is planned to replace it and starting to be deployed.

IPv4 addresses consist of four bytes (32 bits). Each byte of an IP address is known as an octet. Octets can take any value between 0 and 255. Various conventions exist for the numbering and use of IP addresses.

Common IP (IPv4) Addresses -
  • 10.0.0.1
  • 127.0.0.1
  • 192.168.0.1
  • 192.168.1.1
  • 192.168.2.1
FTP allows you to transfer files between two computers on the Internet. FTP is a simple network protocol based on Internet Protocol and also a term used when referring to the process of copying files when using FTP technology.

To transfer files with FTP, you use a program often called the "client." The FTP client program initiates a connection to a remote computer running FTP "server" software. After the connection is established, the client can choose to send and/or receive copies of files, singly or in groups.

To connect to an FTP server, a client requires a username and password as set by the administrator of the server. Many public FTP archives follow a special convention for that accepts a username of "anonymous."

Simple FTP clients are included with most network operating systems, but most of these clients (such as FTP.EXE on Windows) support a relatively unfriendly command-line interface. Many alternative freeware / shareware third-party FTP clients have been developed that support graphic user interfaces (GUIs) and additional convenience features. In any FTP interface, clients identify the FTP server either by its IP address (such as 192.168.0.1) or by its host name.

FTP supports two modes of data transfer: plain text (ASCII), and binary. You set the mode in the FTP client. A common error when using FTP is attempting to transfer a binary file (such as a program or music file) while in text mode, causing the transfered file to be unusable.
NetBIOS (Network Basic Input/Output System) was originally developed by IBM and Sytek as an Application Programming Interface (API) for client software to access LAN resources. Since its creation, NetBIOS has become the basis for many other networking applications. In its strictest sense, NetBIOS is an interface specification for acessing networking services.

NetBIOS, a layer of software developed to link a network operating system with specific hardware, was originally designed as THE network controller for IBM's Network LAN.

NetBIOS has now been extended to allow programs written using the NetBIOS interface to operate on the IBM token ring architecture. NetBIOS has since been adopted as an industry standard and now, it is common to refer to NetBIOS-compatible LANs.

It offers network applications a set of "hooks" to carry out inter-application communication and data transfer. In a basic sense, NetBIOS allows applications to talk to the network. Its intention is to isolate application programs from any type of hardware dependancies. It also spares software developers the task of developing network error recovery and low level message addressing or routing. The use of the NetBIOS interface does alot of this work for them.

NetBIOS standardizes the interface between applications and a LANs operating capabilities. With this, it can be specified to which levels of the OSI model the application can write to, making the application transportable to other networks. In a NetBIOS LAN enviroment, computers are known on the system by a name. Each computer on the network has a permanent name that is programmed in various different ways.

PC's on a NetBIOS LAN communicate either by establishing a session or by using NetBIOS datagram or broadcast methods. Sessions allow for a larger message to be sent and handle error detection and correction. The communication is on a one-to-one basis.

Datagram and broadcast methods allow one computer to communicate with several other computers at the same time, but are limited in message size. There is no error detection or correction using these datagram or broadcast methods. However, datagram communication allows for communication without having to establish a session.

All communication in these enviroments are presented to NetBIOS in a format called Network Control Blocks (NCB). The allocation of these blocks in memory is dependant on the user program. These NCB's are divided into fields, these are reserved for input and output respectively.




NetBIOS is a very common protocol used in todays enviroments. NetBIOS is supported on Ethernet, TokenRing, and IBM PC Networks. In its original induction, it was defined as only an interface between the application and the network adapter. Since then, transport like functions have been added to NetBIOS, making it more functional over time.

In NetBIOS, connection (TCP) oriented and connectionless (UDP) communication are both supported. It supports both broadcasts and multicasting and supports three distinct services: Naming, Session, and Datagram.
The Virtual Private Network - VPN - has attracted the attention of many organizations looking to both expand their networking capabilities and reduce their costs.
The VPN can be found in workplaces and homes, where they allow employees to safely log into company networks. Telecommuters and those who travel often find a VPN a more convenient way to stay connected to the corporate intranet. No matter your current involvement with VPNs, this is a good technology to know something about. This VPN tutorial involves many interesting aspects of network protocol design, Internet security, network service outsourcing, and technology standards.

What Exactly Is A VPN?

A VPN supplies network connectivity over a possibly long physical distance. In this respect, a VPN is a form of Wide Area Network (WAN). The key feature of a VPN, however, is its ability to use public networks like the Internet rather than rely on private leased lines. VPN technologies implement restricted-access networks that utilize the same cabling and routers as a public network, and they do so without sacrificing features or basic security.
A VPN supports at least three different modes of use:
  • Remote access client connections
  • LAN-to-LAN internetworking
  • Controlled access within an intranet

VPN Pros and Cons

Like many commercialized network technologies, a significant amount of sales and marketing hype surrounds VPN. In reality, VPNs provide just a few specific potential advantages over more traditional forms of wide-area networking. These advantages can be significant, but they do not come for free.

The potential problems with the VPN outnumber the advantages and are generally more difficult to understand. The disadvantages do not necessarily outweigh the advantages, however. From security and performance concerns, to coping with a wide range of sometimes incompatible vendor products, the decision of whether or not to use a VPN cannot be made without significant planning and preparation.

Technology Behind VPNs

Several network protocols have become popular as a result of VPN developments:
  • PPTP
  • L2TP
  • IPsec
  • SOCKS
These protocols emphasize authentication and encryption in VPNs. Authentication allows VPN clients and servers to correctly establish the identity of people on the network. Encryption allows potentially sensitive data to be hidden from the general public. Many vendors have developed VPN hardware and/or software products. Unfortunately, immature VPN standards mean that some of these products remain incompatible with each other.
 

A VPN supplies network connectivity over a possibly long physical distance. In this respect, a VPN is a form of Wide Area Network (WAN). VPNs enable file sharing, video conferencing and similar network services. Virtual private networks generally don't provide any new functionality that isn't already offered through alternative mechanisms, but a VPN implements those services more efficiently / cheaply in most cases.

A key feature of a VPN is its ability to work over both private networks as well as public networks like the Internet. Using a method called tunneling, a VPN use the same hardware infrastructure as existing Internet or intranet links. VPN technologies includes various security mechanisms to protect the virtual, private connections.

Specifically, a VPN supports at least three different modes of use:
  • Internet remote access client connections
  • LAN-to-LAN internetworking
  • Controlled access within an intranet

Internet VPNs for Remote Access

In recent years, many organizations have increased the mobility of their workers by allowing more employees to telecommute. Employees also continue to travel and face a growing need to stay connected to their company networks. A VPN can be set up to support remote, protected access to the corporate home offices over the Internet. An Internet VPN solution uses a client/server design works as follows:
    1. A remote host (client) wanting to log into the company network first connects to any public Internet Service Provider (ISP).
    2. Next, the host initiates a VPN connection to the company VPN server. This connection is made via a VPN client installed on the remote host.
    3. Once the connection has been established, the remote client can communicate with the internal company systems over the Internet just as if it were a local host.
Before VPNs, remote workers accessed company networks over private leased lines or through dialup remote access servers. While VPN clients and servers careful require installation of hardware and software, an Internet VPN is a superior solution in many situations.

VPNs for Internetworking

Besides using virtual private networks for remote access, a VPN can also bridge two networks together. In this mode of operation, an entire remote network (rather than just a single remote client) can join to a different company network to form an extended intranet. This solution uses a VPN server to VPN server connection.

Intranet / Local Network VPNs

Internal networks may also utilize VPN technology to implement controlled access to individual subnets within a private network. In this mode of operation, VPN clients connect to a VPN server that acts as the network gateway. This type of VPN use does not involve an Internet Service Provider (ISP) or public network cabling. However, it allows the security benefits of VPN to be deployed inside an organization. This approach has become especially popular as a way for businesses to protect their WiFi local networks.

VPN Network Scalability

The cost to an organization of building a dedicated private network may be reasonable at first but increases exponentially as the organization grows. A company with two branch offices, for example, can deploy just one dedicated line to connect the two locations, but 4 branch offices require 6 lines to directly connect them to each other, 6 branch offices need 15 lines, and so on. Internet based VPNs avoid this scalability problem by simply tapping into the the public lines and network capability readily available. Particularly for remote and international locations, an Internet VPN offers superior reach and quality of service.

Using a VPN

To use a VPN, each client must possess the appropriate networking software or hardware support on their local network and computers. When set up properly, VPN solutions are easy to use and sometimes can be made to work automatically as part of network sign on. VPN technology also works well with WiFi local area networking. Some organizations use VPNs to secure wireless connections to their local access points when working inside the office. These solutions provide strong protection without affecting performance excessively.

Limitations of a VPN

Despite their popularity, VPNs are not perfect and limitations exist as is true for any technology. Organizations should consider issues like the below when deploying and using virtual private networks in their operations:
    1. VPNs require detailed understanding of network security issues and careful installation / configuration to ensure sufficient protection on a public network like the Internet. 
    2. The reliability and performance of an Internet-based VPN is not under an organization's direct control. Instead, the solution relies on an ISP and their quality of service.
    3. Historically, VPN products and solutions from different vendors have not always been compatible due to issues with VPN technology standards. Attempting to mix and match equipment may cause technical problems, and using equipment from one provider may not give as great a cost savings.
Virtual private network technology is based on the idea of tunneling. VPN tunneling involves establishing and maintaining a logical network connection (that may contain intermediate hops). On this connection, packets constructed in a specific VPN protocol format are encapsulated within some other base or carrier protocol, then transmitted between VPN client and server, and finally de-encapsulated on the receiving side.

For Internet-based VPNs, packets in one of several VPN protocols are encapsulated within Internet Protocol (IP) packets. VPN protocols also support authentication and encryption to keep the tunnels secure.

Types of VPN Tunneling

VPN supports two types of tunneling - voluntary and compulsory. Both types of tunneling are commonly used.
In voluntary tunneling, the VPN client manages connection setup. The client first makes a connection to the carrier network provider (an ISP in the case of Internet VPNs). Then, the VPN client application creates the tunnel to a VPN server over this live connection.

In compulsory tunneling, the carrier network provider manages VPN connection setup. When the client first makes an ordinary connection to the carrier, the carrier in turn immediately brokers a VPN connection between that client and a VPN server. From the client point of view, VPN connections are set up in just one step compared to the two-step procedure required for voluntary tunnels.

Compulsory VPN tunneling authenticates clients and associates them with specific VPN servers using logic built into the broker device. This network device is sometimes called the VPN Front End Processor (FEP), Network Access Server (NAS) or Point of Presence Server (POS). Compulsory tunneling hides the details of VPN server connectivity from the VPN clients and effectively transfers management control over the tunnels from clients to the ISP. In return, service providers must take on the additional burden of installing and maintaining FEP devices.

VPN Tunneling Protocols

Several computer network protocols have been implemented specifically for use with VPN tunnels. The three most popular VPN tunneling protocols listed below continue to compete with each other for acceptance in the industry. These protocols are generally incompatible with each other.
Point-to-Point Tunneling Protocol (PPTP)
Several corporations worked together to create the PPTP specification. People generally associate PPTP with Microsoft because nearly all flavors of Windows include built-in client support for this protocol. The initial releases of PPTP for Windows by Microsoft contained security features that some experts claimed were too weak for serious use. Microsoft continues to improve its PPTP support, though.
 Layer Two Tunneling Protocol (L2TP)
The original competitor to PPTP for VPN tunneling was L2F, a protocol implemented primarily in Cisco products. In an attempt to improve on L2F, the best features of it and PPTP were combined to create a new standard called L2TP. Like PPTP, L2TP exists at the data link layer (Layer Two) in the OSI model -- thus the origin of its name.

Internet Protocol Security (IPsec)
IPsec is actually a collection of multiple related protocols. It can be used as a complete VPN protocol solution or simply as the encryption scheme within L2TP or PPTP. IPsec exists at the network layer (Layer Three) of the OSI model.

PPTP - Point-to-Point Tunneling Protocol - extends the Point to Point Protocol (PPP) standard for traditional dial-up networking. PPTP is best suited for the remote access applications of VPNs, but it also supports LAN internetworking. PPTP operates at Layer 2 of the OSI model.

PTP packages data within PPP packets, then encapsulates the PPP packets within IP packets (datagrams) for transmission through an Internet-based VPN tunnel. PPTP supports data encryption and compression of these packets. PPTP also uses a form of General Routing Encapsulation (GRE) to get data to and from its final destination.
PPTP-based Internet remote access VPNs are by far the most common form of PPTP VPN. In this environment, VPN tunnels are created via the following two-step process:
    1. The PPTP client connects to their ISP using PPP dial-up networking (traditional modem or ISDN).
    2. Via the broker device (described earlier), PPTP creates a TCP control connection between the VPN client and VPN server to establish a tunnel. PPTP uses TCP port 1723 for these connections.
PPTP also supports VPN connectivity via a LAN. ISP connections are not required in this case, so tunnels can be created directly as in Step 2 above.
Once the VPN tunnel is established, PPTP supports two types of information flow:
  • control messages for managing and eventually tearing down the VPN connection. Control messages pass directly between VPN client and server.
  • data packets that pass through the tunnel, to or from the VPN client  
 
PPTP Security
PPTP supports authentication, encryption, and packet filtering. PPTP authentication uses PPP-based protocols like EAP, CHAP, and PAP. PPTP supports packet filtering on VPN servers. Intermediate routers and other firewalls can also be configured to selectively filter PPTP traffic. 

PPTP and PPP
In general, PPTP relies on the functionality of PPP for these aspects of virtual private networking.
  • authenticating users and maintaining the remote dial-up connection
  • encapsulating and encrypting IP, IPX, or NetBEUI packets
PPTP directly handles maintaining the VPN tunnel and transmitting data through the tunnel. PPTP also supports some additional security features for VPN data beyond what PPP provides. 

PPTP Pros and Cons
PPTP remains a popular choice for VPNs thanks to Microsoft. PPTP clients are freely available in all popular versions of Microsoft Windows. Windows servers also can function as PPTP-based VPN servers.
One drawback of PPTP is its failure to choose a single standard for authentication and encryption. Two products that both fully comply with the PPTP specification may be totally incompatible with each other if they encrypt data differently, for example. Concerns also persist over the questionable level of security PPTP provides compared to alternatives. 

Source:compnetworking.about.com

Proxy Servers and Microsoft Internet Explorer

To take advantage of a proxy server's capabilities, Web browsers like Internet Explorer (IE) must be configured to explicitly use it. In many proxied environments, the client computers do not have direct Internet access, and browsers generally are not configured to use proxies "out of the box." Clients will be unable to access public Web sites in this scenario until proxy settings have been correctly made. 


Microsoft Internet Explorer 5 Tools menu

Figure 2: IE5 Tools menu
 
For example, to configure IE5 to use a proxy server, first click on Tools to access the drop-down menu. Click on the Internet Options... menu item to raise the Internet Options dialog. This dialog is a property sheet featuring multiple tabs. 

Clicking on the Connections tab makes available a dialog that includes a button in the bottom-right corner named LAN Settings... . Finally, click this button to raise the Local Area Network (LAN) Settings dialog; here is where proxy information must be entered. 



Microsoft Internet Explorer 5 Options menu, Connections tab

Figure 3: IE5 Internet Options, Connections tab
 
IE5 supports both manual and automatic configuration options. As shown the Figure, the "Use a proxy server" check box must be checked to enable the manual entering of a proxy. 

Either the network host name or the IP address of the proxy server must be typed in the "Address" field. In addition, any internal domains (such as intranet sites) that do not need to go through a proxy can be entered here in order to bypass the server. 


Microsoft Internet Explorer 5 local area network (LAN) settings

Figure 4: IE5 Internet Options, Connections tab
 
Microsoft provides Knowledge Base article Q135982 to assist in manually configuring proxy servers using other versions of Internet Explorer. Using the Automatically detect settings check box invokes the WPAD mechanism (discussed earlier) to auto-discover the proxy configuration. Finally, using the Use automatic configuration script check box allows clients to specify the URL that points to the JavaScript configuration file.

Proxy Servers and Netscape Navigator

Netscape Navigator (NN) may also be configured manually or automatically to work with a proxy server.

Netsape Navigator 4 edit menu

Figure: NN4 Edit menu
 
For example, to manually configure NN4, first click on Edit to access the drop-down menu. Click on the Preferences... menu item to raise the Netscape Preferences dialog. 

This dialog is a property sheet featuring a hierarchical arrangement of buttons in the left channel (as compared to the tabs in IE). Double-clicking on the Advanced item (or single-clicking on the small arrow graphic to the left of this text) displays the Proxies sub-item. Finally, clicking on Proxies displays the proxy server configuration dialog within the window. 


Netscape Navigator 4 Preferences, Proxies dialog

Figure 6: NN4 Preferences, Proxies dialog
 
Within this dialog, use the Direct connection to the Internet option to bypass proxy servers, and use the Automatic proxy configuration option to work with the automation script mechanism discussed earlier. (Navigator does not support WPAD.) 

To manually configure the proxy configuration, choose the middle option and click View to raise another dialog where the proxy server's host name or IP address can be entered. 

Free Web-Based Anonymous Proxy Servers
 
The sites listed below support free, Web-based anonymous proxy servers. 
 
An anonymous Web proxy is a type of proxy server that works through a Web form (also often called a CGI proxy). Instead of configuring the address of the server in the browser as is done for HTTP or SOCKS proxies, you simply navigate to the home page of the Web / CGI proxy, where proxy functionality is then enabled for each browsing session. The top free anonymous Web proxy servers are described below.

1. Proxify

Unlike most other anonymous Web proxies, Proxify supports encryption via the SSL and HTTPS network protocols. Proxify also handles the basic functions of an anonymous proxy server well including hiding your IP address and filtering of cookies.

2. Anonymouse

Anonymouse supports Web, email and Usenet (news) proxies and has existed on the Internet for many years now. In addition to the free open access, a low-cost subscription is available for those who want to upgrade to faster proxy servers and additional services. Anonymouse supports both English and German languages.

3. Anonymizer

Anonymizer may the best-known name among the anonymous Web proxy services. While it does offer a free service, most of the Anonymizer site is decided to "up-selling" various related products. WHen using the free proxy, be prepared to see flashing "UPGRADE NOW!" messages in the status bar of your browser.

4. The Cloak

The Cloak is an HTTP/HTTPS free anonymous proxy. A pay service is also available that avoids the bandwidth throttling used in the free version.

Free Proxy Lists (Anonymous and Elite)

Internet proxy servers allow you to (mostly) hide your home IP address and navigate anonymously. However, these free public servers often are taken offline without warning, and some may offer a less reputable service than others. If you are interested in using anonymous proxies, you should maintain a free proxy server list on your home network to ensure at least one is accessible at all times.
Follow these links to obtain free proxy list downloads.
These free proxy lists are updated regularly.
Some home networks, corporate intranets, and Internet Service Providers (ISPs) use proxy servers (also known as proxies). Proxy servers act as a "middleman" or broker between the two ends of a client/server network connection. Proxy servers work with Web browsers and servers, or other applications, by supporting underlying network protocols like HTTP.

Key Features of Proxy Servers

Proxy servers provide three main functions:
  1. firewalling and filtering
  2. connection sharing
  3. caching
The features of proxy servers are especially important on larger networks like corporate intranets and ISP networks. The more users on a LAN and the more critical the need for data privacy, the greater the need for proxy server functionality.

Proxy Servers, Firewalling and Filtering

Proxy servers work at the Application layer, layer 7 of the OSI model. They aren't as popular as ordinary firewalls that work at lower layers and support application-independent filtering.
Proxy servers are also more difficult to install and maintain than firewalls, as proxy functionality for each application protocol like HTTP, SMTP, or SOCKS must be configured individually.
However, a properly configured proxy server improves network security and performance. Proxies have capability that ordinary firewalls simply cannot provide.
Some network administrators deploy both firewalls and proxy servers to work in tandem. To do this, they install both firewall and proxy server software on a server gateway.

Because they function at the OSI Application layer, the filtering capability of proxy servers is relatively intelligent compared to that of ordinary routers. For example, proxy Web servers can check the URL of outgoing requests for Web pages by inspecting HTTP GET and POST messages.

Using this feature, network administrators can bar access to illegal domains but allow access to other sites. Ordinary firewalls, in contrast, cannot see Web domain names inside those messages. Likewise for incoming data traffic, ordinary routers can filter by port number or network address, but proxy servers can also filter based on application content inside the messages.

Connection Sharing with Proxy Servers

Various software products for connection sharing on small home networks have appeared in recent years. In medium- and large-sized networks, however, actual proxy servers offer a more scalable and cost-effective alternative for shared Internet access. Rather than give each client computer a direct Internet connection, all internal connections can be funneled through one or more proxies that in turn connect to the outside.

Proxy Servers and Caching

The caching of Web pages by proxy servers can improve a network's "quality of service" in three ways. First, caching may conserve bandwidth on the network, increasing scalability. Next, caching can improve response time experienced by clients. With an HTTP proxy cache, for example, Web pages can load more quickly into the browser. Finally, proxy server caches increase availability. Web pages or other files in the cache remain accessible even if the original source or an intermediate network link goes offline.

Illustration of Web caching using a proxy server.

Figure 1: Web caching with a proxy server
 

Drawbacks of Proxy Caching

It's reasonable to expect that proxy servers handling hundreds or thousands of Web clients can become a network bottleneck. In addition to using servers with power processors and large amounts of memory, administrators may also choose to deploy multiple proxies to help avoid potential bottlenecks. 

A proxy hierarchy creates multiple layers of caching support. Clients connect directly to a first-level caching, and if a Web page is unavailable there locally, the request "misses" and automatically gets passed to a second-level caching server, and so on. 

As with many caching systems, the effectiveness of a multi-proxy server hierarchy is very dependent on the pattern of traffic. In the worst case, all clients will be visiting Web pages completely unrelated to each other, and proxies (the hardware, and the additional network traffic they generate) become pure overhead. One would expect that normal traffic patterns will usually not be worst-case, but every network's use pattern will be different. 

Proxy caching differs from browser caching. Browsers automatically cache pages on the client computer, whereas proxies can also cache pages on a remote Web server. Because browsers already perform their own caching, introducing proxy caching into a network will have only a second-order effect. 

Proxy caches don't help much with refreshed pages. On some sites, Web pages are set with HTML META tags to expire quickly; expired pages force the proxy cache to reload that page. Similarly, caching is rendered ineffective by pages that change content frequently, such as those on news sites, or weblogs. 

Proxy caches also introduce measurement uncertainty into the Internet. Normally, a Web server log will record identifying information of visiting clients such as their IP addresses and domain names. For clients with proxy servers, all public requests are made on behalf of the server, using its IP address and identity. Web sites that carefully track the patterns of use of their visitors have much more difficulty in distinguishing unique client visits through proxies.

Proxy Servers and Browsers

Proxy servers work with specific networking protocols. Obviously HTTP will be the most critical one to configure for Web page access, but browsers also utilize these other protocols:
  • S-HTTP (also called "Secure" or "Security" in the browser)
  • FTP
  • SOCKS
  • Gopher
  • WAIS
S-HTTP (Secure Hypertext Transfer Protocol) supports encrypted HTTP communications. This protocol is becoming more and more common as ecommerce sites, for example, adopt it to make credit card transactions safer. S-HTTP should not be confused with SSL. Although S-HTTP uses SSL "under the covers," SSL is a lower-level protocol that by itself does not impact a browser's proxy setup. 

FTP (File Transfer Protocol) supports the download of files over the Web. Before HTTP was developed, FTP was an even more popular way to share files across the Internet. FTP treats files as either simple text or binary format, and it is still commonly used to download compressed archives of non-HTML data (like MP3 files, for example). 

SOCKS is a firewall security protocol implemented in some proxy configurations. 

Gopher and WAIS (Wide-Area Indexing Service) were two attempts before HTTP to build a standard protocol for indexing and navigating information on the Internet. Both Gopher and WAIS are effectively obsolete today.


Technically, different proxy servers may be used to support these multiple protocols. For example, the hypothetical host 

 http_proxy.about.com
 
may serve HTTP and S-HTTP requests, and another hypothetical host 
 
 other_proxy.about.com
 
may serve FTP, GOPHER, WAIS, and any others except HTTP/S-HTTP. When manually configuring a browser, clients will need to know these details of the proxy server arrangement. Most of the time, network administrators will configure the proxies to serve all protocols to avoid any confusion. 

Host Identifiers and Ports

To manually specify a proxy server in the browser, two pieces of information are required. First, the host identifier is either the host's network name (as configured in DNS, NIS, or similar naming service) or the host's IP address. Second, the port number is the TCP/IP port on which the server listens for requests. 

A single port number is generally used for all of the supported protocols above. This port should not be confused with the standard ports used by the protocols themselves (port 80 for HTTP, port 21 for FTP, and so on). This is a proxy port only, and it should never be assigned to one of the reserved numbers. 

Unfortunately, a single standard port number does not exist. Some numbers like 8000 and 8080 are used more commonly than others, but the number can be any unassigned value up to 65535. Users manually configuring their browsers will need to be told this port number by their network administrator. 

Automatic Proxy Configuration

To make the deployment of proxy servers easier, some new technologies were developed to work with browsers in a more automated fashion. Administrators can use a special configuration file, for example, to hide details like port numbering from client users. This file contains JavaScript code and is installed on the proxy server itself or on some other Web server. Clients wishing to use this automatic configuration scheme simply enter into their browser settings the URL of this file. To the client, URLs will look like the following: 

 http://hypothetical_proxy.about.com/proxy.pac
 
For Internet Explorer 5, a new technology called Web Proxy Auto Discovery (WPAD) was introduced in an attempt to generalize the discovery of proxy servers as well as other network services. WPAD uses a lookup service like DNS to automatically construct an auto-configuration URL. Instead of a ".pac" file, WPAD expects a ".dat" file to be installed on a Web server as in the following example: 

 http://wpad.about.com/wpad.dat
 
Instead of users explicitly specifying this URL, the browser automatically constructs it using the network domain name (about.com), a default host name on that network (wpad) and a default configuration filename (wpad.dat). Administrators need only configure their name resolution services to redirect to the proper location.
 
Peer to peer is an approach to computer networking where all computers share equivalent responsibility for processing data. Peer-to-peer networking (also known simply as peer networking) differs from client-server networking, where certain devices have responsibility for providing or "serving" data and other devices consume or otherwise act as "clients" of those servers.

Characteristics of a Peer Network

Peer to peer networking is common on small local area networks (LANs), particularly home networks. Both wired and wireless home networks can be configured as peer to peer environments.
Computers in a peer to peer network run the same networking protocols and software. Peer networks are also often situated physically near to each other, typically in homes, small businesses or schools. Some peer networks, however, utilize the Internet and are geographically dispersed worldwide.
Home networks that utilize broadband routers are hybrid peer to peer and client-server environments. The router provides centralized Internet connection sharing, but file, printer and other resource sharing is managed directly between the local computers involved.

Peer to Peer and P2P Networks

Internet-based peer to peer networks emerged in the 1990s due to the development of P2P file sharing networks like Napster. Technically, many P2P networks (including the original Napster) are not pure peer networks but rather hybrid designs as they utilize central servers for some functions such as search.

Peer to Peer and Ad Hoc Wi-Fi Networks

Wi-Fi wireless networks support so-called ad hoc connections between devices. Ad hoc Wi-Fi networks are pure peer to peer compared to those utilizing wireless routers as an intermediate device.

Benefits of a Peer to Peer Network

You can configure computers in peer to peer workgroups to allow sharing of files, printers and other resources across all of the devices. Peer networks allow data to be shared easily in both directions, whether for downloads to your computer or uploads from your computer. On the Internet, peer to peer networks handle a very high volume of file sharing traffic by distributing the load across many computers. Because they do not rely exclusively on central servers, P2P networks both scale better and are more resilient than client-server networks in case of failures or traffic bottlenecks.

Fundamentals of Internet Information Services 6.0 training


Fundamentals of Internet Information Services 6.0 training
— How to install IIS 6
— What’s changed in IIS 6
— The IIS 6 Metabase
— How to install and configure FTP Sites in IIS 6
— How to install and configure Web Sites in IIS 6
— How to install PHP and Perl on IIS 6
— How to work with Application Pools
— IIS 6 Authentication Methods
— NNTP
— Configuring Logging
— Web Server Security



Hotfile

http://hotfile.com/dl/91876155/c049696/IIS_6.part1.rar.html
http://hotfile.com/dl/91876506/97f64dc/IIS_6.part2.rar.html
http://hotfile.com/dl/91876538/d729beb/IIS_6.part3.rar.html
http://hotfile.com/dl/91876761/70b0961/IIS_6.part4.rar.html
http://hotfile.com/dl/91876795/b168090/IIS_6.part5.rar.html
 


Introduction
As of 2010, there are nearly three million unique forms of known malicious code, and thousands of new ones are discovered daily. The risk of being infected is greater than ever. The damage caused by an infection can range from a minor annoyance to a catastrophic disaster. The old wisdom continues to ring true: an ounce of prevention is worth a pound of cure.
Most computer users are aware of the importance of security to reduce the threats that could potentially harm a computer or network. For example, anti-virus and anti-spyware are essential defenses in the war against malicious code. However, technology cannot compensate for poor and risky behavior. Thus, proper training and understanding, along with behavior changes, are needed to facilitate a reduction of malicious code infections.
The methods, vectors, or paths that malicious code can use to gain access to your system are increasing as new services or types of communications are developed. In fact, every single possible communication method that exists for legitimate data can be used to transmit malicious data as well. Thus, we all need to be vigilant in keeping our protections current as well as avoiding risky activities.
The following are 10 common ways malicious code reach your private network that you need to be aware of.
1. E-Mail Attachments
Attachments to e-mails are a common method of distribution of malicious code. E-mail is inherently insecure due to its use of SMTP, a plain text-forwarding protocol, and its lack of strong authentication of message send­ers. The source of an e-mail address can be easily spoofed or falsified as someone that you trust. Often, this alone is enough to trick a recipient into opening an attachment.
Generally, avoid using attachments as a means to exchange files. Instead, use a third-party file exchange system (such as DropBox, Box.net, Drop.io, MediaFire, Windows Live SkyDrive, Foldershare, RapidShare, MegaUpload, Dropload, YouSendIt, SendThisFile, etc.). Thus, when an attachment does arrive, it is suspicious for being abnor­mal and not the standard method by which common communications take place.
If you receive an attachment and need to determine if it is legitimate, you still need to verify it before opening it. Create a new e-mail (do not reply to the message with the attachment) to the sender and ask for confirma­tion that they sent the file. Maybe even ask the filename, size, and hash value if you are really concerned. Or, call the person and ask if they sent you an attachment on purpose. If the sender does not confirm the attachment, delete it.
2. Portable Media
Portable media includes any device that can store information. This includes optical discs (CD, DVD, HD-DVD, Blu-Ray, etc.), tapes, external hard drives, USB drives, and memory cards. Any storage device can support both benign and malicious content. The less you know about or trust the source of a device, the more you should be cautious about accepting the device and connecting it to your system. Any media from outside the organization should be highly scrutinized, especially if obtained from a questionable or unknown source.
A possible defense is to use a dedicated scanning system. Every new-to-you media can be scanned at this stand­alone system before it is used on any production system. Assuming the stand-alone scanner system is updated regularly, it will greatly reduce the risk of malware distribution via media. Another option would be to limit data exchanges to file sharing services that do not involve portable media.
3.Visiting Malicious Web Sites
The Web browser is the primary tool used to interact with the Internet, which is a dangerous place. Thus, many threats breach our organizations’ defenses through this seemingly innocent client software. Popular and well-known sites are generally not a significant threat; however, any site can be the victim of an attack, which in turn could leave you at risk.
Following hyperlinks sent to you by e-mail or chat could lead to malicious locations. Additionally, some search results might not lead to legitimate locations. Always be cautious about following Web links to domain names you don’t generally recognize.
It is difficult to always be aware of the reputation of a Web site are visiting, but you can reduce the risk by using an updated browser, limiting auto-execute features of mobile code, and running anti-malware scanners.
4. Downloading Files from Web Sites
Even when visiting generally trustworthy Web sites, there may be additional risk if you elect to download con­tent to your local system. Take ever greater caution when choosing to download material from any site. Seek out only those locations that are known to be safe and trustworthy. For example, download.com, managed by CNet, is a safe location to download software, because they test and verify every file available through their service.
When seeking out more esoteric content or unique files, you will likely be visiting non-mainstream download locations. These fringe sites put you at greater risk, because they don’t have a known reputation and may not have any amount of filtering or screening of offered files.

Downloaded Web content includes both generic files, including software, plug-ins, movies, audio files, etc., as well as mobile code, such as ActiveX, Java, JavaScript, Flash, SilverLight, etc. Any code that comes from an out­side source – that is potentially unknown – puts you and your computer system at greater risk.

5. Participation in P2P File Sharing Services
Concern over downloaded, malicious content grows when that code is obtained through a peer file-sharing sys­tem. This is not a condemnation of efficient, distributed transmission solutions, but rather the sources of the files exchanged through them. By not knowing or having control over the source of a file, it is possible that malicious code could be included along with the content being sought.
The risk is lower when the content is downloaded legally, but the risk grows when a P2P sharing system is used to access illegal or infringing content. The risk is greater not because the content becomes malicious when it is exchanged outside of ethical channels, but because the providers of the content often include malicious code in­tentionally. The “poisoning” of the content is a way to further distribute malware, especially remotely controlled tools, through a popular but non-filtered exchange mechanism.
6. Instant Messaging Clients
In many cases, the purveyors of malware look for methods of distribution that will enable them to quickly and broadly transmit their code. The more popular a “thing,” the more attractive it becomes as a vehicle for distribu­tion. Malware can be seen as a form of parasite that attaches itself to any popular communication medium.
One increasingly popular communication medium is that of IM or instant messaging. Through chat systems, especially those using installed software clients instead of Web interfaces, the exchange of files is possible. There have been security breaches that allowed remote hackers to upload and/or download files through holes in IM client software. Even with a patched client, it is possible for a user to accept an offered file from an unknown source or follow an offered hyperlink to a malicious Web site.
7. New Devices and Peripherals
A risk that is often overlooked due to its rarity is malware found on brand new devices, right out of their pack­aging. Mobile phones, digital photo frames, and even media players have been compromised during manufac­turing, resulting in malware that makes its way to a customer’s computer. This has happened with a well-known, commercial, shrink-wrapped, anti-virus product.
Vendors often outsource the actual construction and pre-production of their products to external manufactur­ers and assemblers. When computer parts are the product being constructed, especially those with storage capabilities, malware can make its way onto the new device while it is loaded with its software elements if the manufacturer’s system is infected. One way to reduce this threat is to not be an early adopter of a product nor the first to grab an updated version of an existing product. Give the rest of the market a few days or weeks to discover malware and other concerns before adding the new device or peripheral to your repertoire.

8. Social Networking Sites
Social networking sites offer up several situations that could allow malware to make its way onto your network. First, there are the social engineering attacks that trick users into accepting fraudulent information that, when acted upon, could compromise an account or the security of a computer. Second, with the proliferation of mes­sage posting and exchange services, it is easy to follow hyperlinks to malicious Web sites. Third, some in-site applications, written by malicious entities, attempt to hijack accounts or distribute malicious code.
Many of these threats are discovered by the community or the site moderators within a few hours or days, so these concerns don’t remain static for long. However, new attacks and tricks are crafted by hackers constantly. Be suspicious, don’t accept offered links, especially for file downloads, and don’t be an early adopter of a new application. Give the community a few days to discover the malicious elements and weed them out before you dive in.
9. Social Engineering Attacks
Social engineering is the art of convincing someone to either give up information or perform a task that results in the reduction of security. Large organizations are the most common targets of social engineering attacks; however, mass e-mail-based attacks could show up in anyone’s inbox.
Be aware that attackers are trying to trick you into following hyperlinks, downloading files, performing configu­ration changes, or typing in esoteric commands. Doing so could lead to the direct infection of your system with malware.
Social engineering attacks are often quite subtle. At first glance, or before your second thought, you might not realize that an e-mail or a phone conversation isn’t normal. If the hacker can convince you to act before you think or verify, the social engineering attack is successful. If a hacker can trick you into visiting a malicious Web site, malware could be transmitted to your system through Web-based mobile code.
In other attacks, the hacker may encourage you to download a scanner or utility in order to perform some testing or diagnostic function. The tool you download might do what is claimed, but it also may open a remote control connection granting the hacker partial to full access to your system.
A social engineering attack could even be waged by building auto-launch elements onto USB flash drives and leaving them in various locations, such as the restroom counter, the snack room, or near the smoking area. If someone picks up the drive and plugs it into their computer, they probably won’t even notice the installation of malicious code, which might corrupt the system or grant hackers remote control access.
Be aware; you are a target of social engineering attacks. The question is will you recognize the attack for what it is, or will you be tricked into harming your own environment.

10. Not Following Security Guidelines and Policies
The last and probably most significant cause of how or why malicious code reaches your private network, or even just your personal computer system, is by not following proper security guidelines and policies. Most orga­nizations of moderate size have made the effort to design a secure infrastructure. This includes prescribing user access policies and providing at least some level of security awareness training.
Failing to abide by security guidelines or purposefully violating security policies will lead to compromised security, often the distribution of malicious code. Security policies are written and implemented for a reason – to reduce the likelihood of a security breach. If a worker fails to abide by the company security policy, they put themselves and the entire organization at risk.
Bypassing filters, using storage devices from outside resources, using unauthorized peripherals, blocking soft­ware updates, opening e-mail attachments, participating in unethical file exchanges, and using non-approved software clients are all security policy violations and increase the chance of malicious code infesting the organi­zation.
Every organization and every individual has a vested interest in operating with common sense security guide­lines. This will assist in reducing the risk of malicious code infection and allow the organization to be productive in accomplishing missions, goals, or sales, without having to spend resources on recovery.
Write a security policy. Define the acceptable use policy. Hire competent personnel. Train users on how to per­form their jobs within the confines of security. Use automated tools to detect and defend. Monitor the environ­ment for abuse, misuse, and compromise. Use common sense. Obey the rules.