Today there is a seminar organized by Cisco , Data Center 3.0 Statergy event at Meridian. Hopefully I get more info which I can post here. The last Cisco Expo I attended was held two months back. Which was simply outstanding. Ok now lets get back to out Series of Security Policies, today I am going to eloborate the Client Security policy.
“IS” CONSIDERED THE FOLLOWING:
1. If attachment via the Internet is allowed, be absolutely certain that home users who attach via the Internet do not have file sharing turned on. For Windows clients, use automatic scanning software across the range of IP addresses attached to the network to make sure that no clients respond on TCP/IP port 139.
2. Instruct users to avoid inappropriate local access and creating or modifying shares.
3. Remove the remote access and dial-up connection services from clients on the network. There should be no need for remote access outbound connections from computers on networks that are connected to the Internet.
4. Organisation owned computers used by work-at-home telecommuters cannot be connected to the Internet or used by any family member other than the employee.
5. Employees shall use their own computers at home for entertainment or personal interests.
6. Client computers shall not be configured to use any sort of remote access software.
7. Clients shall not be configured to answer dial-in security connections.
8. Do not allow users to install software on their clients. Take removable media drives like floppy,CD-ROM, and Zip drives out of client computers since all authorized software installations can occur over the network.
9. Do not install file and print sharing on clients unless absolutely necessary. Encourage users to store all files on network file servers, and create server pools of resources.
10. Remove all modems and other alternative access devices from client computers.
11. Each client computer should have one-and only one-possible connection to any data network.
12. Restrict logon access to the network to the computers that an employee normally uses. This makes it impossible to exploit an account name and password from anywhere other than the user’s regular computer except nursing stations.
13. Disable all unused I/O ports, especially parallel ports, USB ports that are not attached to printers,since many alternate access devices are capable of attaching through the printer/USB port.
14. Disable unused serial /USB ports in the BIOS of client computers. But strong administrative passwords in the BIOS setup pages of client computers to maintain central control of network security.
My Personel Website:www.yasirirfan.com
Here is one more cool command which shows a summary of port utilization on all ports,including percentage and backplane/fabric utilization:
The show controllers utilization command on the Cisco catalyst 3560 (other IOS switches probably support
this) running Cisco IOS Software Release 12.2(44)SE1
MBGF-DAC-3560-AS02#sho controllers utilization
Port Receive Utilization Transmit Utilization
Gi0/1 0 0
Gi0/2 0 0
Gi0/3 0 0
Gi0/4 0 0
Gi0/5 0 0
Gi0/6 0 0
Gi0/7 0 0
Gi0/8 0 0
Total Ports : 52
Switch Receive Bandwidth Percentage Utilization : 0
Switch Transmit Bandwidth Percentage Utilization : 0
Switch Fabric Percentage Utilization : 0
As promised I am trying to cover the topics I posted in my first post, now we are proceeding towards the User Security. We should consider the following while drafting the User Security policy.
“IS” CONSIDERED THE FOLLOWING:
1. Networked systems shall update regularly with the latest vendor patches for all software executed on Workstations and Servers.
2. Users shall select passwords that cannot be found in a dictionary and that are of sufficient length that the probability of determining the password over a network shall take at least 160 hours. Currently, this is at least 8 characters but shall be automatically increased as technology allows.
3. All users passwords attached to a network wherein a compromise has occurred or is suspect shall be changed immediately.
4. Enable client operating system user profiles so that specific users and groups have their own security settings that reflect their level of trust in the network.
5. Force password changes often. Passwords should be valid for no longer than 30 days.
6. Train users to prevent mishaps, by doing things such as turning off a workstation that holds shared data when it is not required.
7. Execute a virus scanner automatically whenever a user logs onto the computer.
8. Use workstation user accounts and system policies to prevent individual users from controlling the security of their workstations.
9. Disable password caching so passwords do not accumulate on client computers.
10. Client computers shall be restricted such that their network settings may not be modified by nonadministrative personnel. Implement the following specific policies:
* Disable the network control panel for all users except administrator and trusted knowledgeable users.
* Disable the registry editing tools for all users except system administrators.
* Enable the shell restrictions for accounts that serve a particular purpose, such as public e-mail accounts, public word-processing accounts, process control, etc.
* Hide the general and details pages for printers in the network, disable deletion of printers,and disable the addition of printers.
* Hide the remote administration page and the user profiles page for all users except administrators.
11. Disable booting the A: drive in the BIOS and apply a password to the BIOS to keep the user from using a DOS boot floppy.
12. Hide the display settings page from everyone except administrators.
13. Limit the rights of default Administrators group, and create a separate group with full access.
14. Provide periodic security training for new and established employees alike. A periodic refresher keeps users aware of security problems.
15. Require alphanumeric passwords so that a hacker cannot quickly determine the password to a user account simply by performing a “dictionary scan.”
16. Modify the client operating system to boot directly to the allowed application or a menu restricted to allowed applications.
17. All users of workstation and pc’s are to ensure that their screens are blank when not to be used
18. Approving Login procedures must be strictly observed a users leaving their screen unattended must firstly lock access to their workstation because may be unauthorized systems may be gained via a valid user is and password.
19. Managing user access must be authorized by the owner of the system and such access,including the appropriate access rights or privileges must be recorded in an access control list. Such records are to be regarded as high confidential documents.
Personel Web Site:www.yasirirfan.com
Begining with IOS version 12.3, Cisco has finally added a command to the IOS that allows you to view the configuration and statistics from within configuration mode.
Here’s a handy tip when using the show, ping, and telnet commands. Instead of switching back and forth between global configuration mode and privilege mode to use these commands, you can remain in global configuration mode and type the do command with the original syntax.
Switch(config)#do show running-config
Router(config)#do show ip route
Router(config)#do PING 192.168.0.1
Switch(config)#do show vtp status
In my previous post on IT Securty Policy I did discussed about the Physical Security, now we will continue our journey and lets see what things should be considered while drafting the Human Security Policy.
“IS” CONSIDERED THE FOLLOWING:
1. Several studies and experiences indicate that employee and other persons who are authorized to be on the company premises or who are in a trusted relationship commit most computer crimes.
2. Do complete background checks before hiring someone or allowing someone access to Organisaton resources.
3. In new employee indoctrination, stress the importance of proprietary data and that any compromise of proprietary data will result in discipline, termination, or prosecution.
4. Advise departing employees that it is against the law to take proprietary material, and that you will prosecute anyone caught taking any type of proprietary information.
5. Set up an easy-to-use system that allows employees to covertly or anonymously report suspicious behavior.
6. Develop a method to combat the belief by many employees that anyone who has worked on something has a right to take a copy. This feeling of ownership occurs regardless of the signing of non-disclosure agreements and ownership/invention agreements. One of the most common criminal defenses used is that the ex employee just wanted a sample of their work.
7. Control and approve any articles written about the Organization by employees.
8. Access to information shall rise with pay and with proven loyalty.
9. Employees are responsible for immediately reporting lost, misplaced, or unaccounted for networked systems.
10. When audit policy monitoring reveals that an employee is a security risk, that employee’s access to sensitive information shall immediately be downgraded.
11. Off-Site computer usage whether at home or at other locations may only authorized by the Manager.
12. Assignment of portable systems shall be limited to those who require portability to perform their work. Portable equipment is not perquisite due to the inherent security risk and the cost of replacement.
I.S concern is
a. It must be used for business only.
b. The use for unlicensed SW way be put the Organization in critical Condition.
c. Viruses, Worms, Trojans and other malicious code can corrupt both data and the system files.
d. Theft of the portable computer exposed Organization to the threat of disclosure of sensitive data.
e. A laptop connected to any network is open to hacking and is unlikely to have any effective security features enabled. Files and data could be stolen, damaged or corrupted.
f. Where a laptop is used by several persons old/State data may still present, risking unintentional actions / reactions to inaccurate data
13. Sudden changes in Appearance that might indicate an external factor at work in the employee’s life shall be noted and monitored by security personnel. Sudden changes in lifestyle, apparent income, or attitude may necessitate a security evaluation.
14. Personnel issued with Mobile Phones by the Organization are responsible for using them in manner consistent with the confidentially level.
15. Security checks in/check out and name tags are required for all personnel on the premises. Employees shall be issued permanent badges. Visitors shall be issued temporary badges for the duration of their visit only.
16. Employees shall not have access to secret or higher systems or information for a period of ninety days from their initial employment. The purpose of this policy is to prevent the employment of spies from competing organizations.
17. Animosity, aggression, or violence towards the Organization, its assets, or its employees is an indicator of serious security risk. Audit policy shall be used to monitoring the behavior of suspect individuals without alerting them to the fact that they are under observation. Instances of sabotage or other security violations are grounds for immediate dismissal.
18. Sensitive or confidential information must not record in answer machine or voice mail.
If you cut and paste your config onto an IOS-based switch using Hyperterminal, it breaks down about midway. This occurs because Hyperterminal sends the text too quickly for the switch, particularly if a command returns a message, such as portfast. To avoid this, in Hyperterminal, select File – Properties; click the Settings tab, click the ASCII button, and add a character delay of 5 milliseconds. You should now be able to cut and paste your config successfully.
Now I am going to concentrate on the SAMPLE I.T. Security policy for any Organization, I will try to cover in brief some important aspects in the forthcoming weeks, as we all know how important a Security Policy is. I did get an inspiration to draft a sample security policy after reading Network Security Architecture by Sean Convery.
What is a Security Policy?
Security policies are a special type of documented business rule for protecting information and the systems which store and process the information. Information security policies are usually documented in one or more information security policy documents. Within an organization, these written policy documents provide a high-level description of the various controls the organization will use to protect information.
Written information security policy documents are also a formal declaration of management’s intent to protect information, and are required for compliance with various security and privacy regulations. Organizations that require audits of their internal systems for compliance with various regulations will often use information security policies as the reference for the audit.
I am planning to cover following things in coming weeks,
1- PHYSICAL SECURITY
2- HUMAN SECURITY
3- USER POLICY
4- CLIENT SECURITY
5- NETWORK SECURITY
6- SERVER SECURITY
7- DATA SECURITY
8- REMOTE ACCESS SECURITY
9- INTERNET POLICY
First of all I will start with Physical Security policy and later on I will proceed with the next policies.
“IS” CONSIDERED THE FOLLOWING:
1- Make sure that building security is adequate to prevent walk-up access to the workstations.
2- Employ a security officer or an “attack receptionist” to guard the front desk, and don’t allow
non-employees access beyond that point.
3- Physical access to high security areas is to be controlled with strong identification and
authentication techniques. Staffs with authorization to enter such areas are to be provided
with information on the potential security risks involved.
4- Make certain all servers are located in locked and secure rooms. Restrict access to
5- Make certain the servers are stored in an area that is secure from physical compromise under
all reasonable circumstances. Make sure all guests have an escort when they are in the room.
6- Sensitive and value material things must be stored securely. We could use lockable storage
7- Put the sensitive data, material in fire protected storage cabinets
8- The use of safe is must be in mind for saving sensitive material.
Personel Website: www.yasirirfan.com
Secure Shell (SSH) – TCP Port 22
SSH stands for “Secure Shell”. SSH commonly uses port 22 to connect your computer to another computer on the Internet. It is most often used by network administrators as a remote login / remote control way to manage their business servers. Examples would be: your email administrator needs to reboot the company email server from his home, or your network administrator needs to reset your office password while she is away at a conference.
If remote access to a switch is necessary, then consider using SSH instead of telnet. SSH provides encrypted connections remotely. However, only IOS versions that include encryption support SSH. Also, to include SSH capability the switch may need to have its IOS updated.
Before using SSH on the switch, the administrator must configure the switch with the following commands: hostname, ip domain-name, and crypto key generate rsa. The following example sets the hostname to Switch.
Switch(config)# hostname Switch
Refer to the previous subsection on DNS for an example using the ip domain-name command.
The crypto key generate rsa command depends on the hostname and ip domain-name commands. This crypto command generates a Rivest, Shamir, Adleman (RSA) key pair, which includes one public RSA key and one private RSA key.
The following example shows this crypto command, including the two parameters, the name for the keys
(e.g., switch.test.lab) and the size of the key modulus (e.g., 1024), that are prompted for.
Switch(config)# crypto key generate rsa
The name for the keys will be: switch.test.lab
Choose the size of the key modulus in the range of 360 to 2048 for your
General Purpose Keys. Choosing a key modulus greater than 512 may
take a few minutes.
How many bits in the modulus? 1024
Generating RSA keys…. [OK].
To restrict SSH access to the switch, configure an extended access-list (e.g., 101) that allows only the administrators’ systems to make these connections and apply this access-list to the virtual terminal lines. Allow only SSH connections to these lines by using the transport input ssh command. Set the privilege level to 0, and set the exec-timeout period to 9 minutes and 0 seconds to disconnect idle connections to these lines. Finally, use the login local command to enable local account checking at login that will prompt for a username and a password.
The following commands show the example configuration for SSH on the virtual terminal lines.
Switch(config)# no access-list 101
Switch(config)# access-list 101 remark Permit SSH access from
Switch(config)# access-list 101 permit tcp host 10.0.0.2 any eq 22 log
Switch(config)# access-list 101 permit tcp host 10.0.0.4 any eq 22 log
Switch(config)# access-list 101 deny ip any any log
Switch(config)# line vty 0 4
Switch(config-line)# access-class 101 in
Switch(config-line)# transport input ssh
Switch(config-line)# privilege level 0
Switch(config-line)# exec-timeout 9 0
Switch(config-line)# login local
The login local command cannot be used with AAA. Instead, use the login authentication command. Refer to the AAA section of this guide for more details.
Free SSH Clients
List of free SSH servers and Clients
Personal Website: www.yasirirfan.com
Network Documentation Policy
This network documentation policy is an internal IT policy and defines the requirements for
network documentation. This policy defines the level of network documentation required such as
documentation of which switch ports connect to what rooms and computers. It defines who will
have access to read network documentation and who will have access to change it. It also defines
who will be notified when changes are made to the network.
This policy is designed to provide for network stability by ensuring that network documentation
is complete and current. This policy should complement disaster management and recovery by
ensuring that documentation is available in the event that systems should need to be rebuilt. This
policy will help reduce troubleshooting time by ensuring that appropriate personnel are notified
when changes are made to the network.
The network structure and configuration shall be documented and provide the following
1. IP addresses of all devices on the network with static IP addresses.
2. Server documentation on all servers as outlined in the “Server Documentation”
3. Network drawings showing:
a) The locations and IP addresses of all hubs, switches, routers, and firewalls on the
b) The various security zones on the network and devices that control access
c) The locations of every network drop and the associated switch and port on the
switch supplying that connection.
d) The interrelationship between all network devices showing lines running between
the network devices.
e) All subnets on the network and their relationships including the range of IP
addresses on all subnets and net mask information.
f) All wide area network (WAN) or metropolitan area network (MAN) information
including network devices connecting them and IP addresses of connecting
4. Configuration information on all network devices including:
5. Configuration shall include but not be limited to:
a) IP Address
c) Default gateway
d) DNS server IP addresses for primary and secondary DNS servers.
e) Any relevant WINS server information.
6. Network connection information including:
a) Type of connection to the internet or other WAN/MAN including T1,T3, frame
b) Provider of internet/WAN/MAN connection and contact information for sales and
c) Configuration information including net mask, network ID, and gateway.
d) Physical location of where the cabling enters the building and circuit number.
The IT networking and some enterprise security staff shall have full access to all network
documentation. The IT networking staff shall have the ability to read and modify network
documentation. Designated enterprise security staff shall have access to read and change network
documentation but those not designated with change access cannot change it. Help desk staff
shall have read access to network documentation.
5.0 Change Notification
The help desk staff, server administration staff, application developer staff, and IT management
shall be notified when network changes are made including.
a) Reboot of a network device including switches, routers, and firewalls.
b) Changes of rules or configuration of a network device including switches, routers, and
c) Upgrades to any software on any network device.
d) Additions of any software on any network device.
Notification shall be through email to designated groups of people.
6.0 Documentation Review
The network or IT manager shall ensure that network documentation is kept current by
performing a monthly review of documentation or designating a staff member to perform a
review. The remedy or help desk requests within the last month should be reviewed to help
determine whether any network changes were made. Also any current or completed projects
affecting network settings should be reviewed to determine whether there were any network
changes made to support the project.
7.0 Storage Locations
Network documentation shall be kept either in written form or electronic form in a minimum of
two places. It should be kept in two facilities at least two miles apart so that if one facility is
destroyed, information from the other facility may be used to help construct the IT infrastructure.
Information in both facilities should be updated monthly at the time of the documentation
Cacti is one of the great free ware bandwidth monitoring software works with SNMP. It’s RRD based tool, which makes use of MySQL server as a database, and completely driven by PHP.
What is Cacti?
Cacti is a resource monitoring software which used RRDtool to store data & the data is used to create graphs. Cacti’s greatest strength is it provides complex graphs easily. Cacti come with fast poller to collect data from different resources simultaneously & do have many user management features. It’s very user-friendly that even a layman can accustomed to figure out how it works with less effort.
In a single sentence, “Cacti, because it’s easy”. Installing and using Cacti is a very simple task and does not require indepth knowledge in networking or resource management. You can install and configure it in simple steps, which makes it an ideal software for newbie network administrators. Never-the-less , its so powerful and scalable that you can use it even in large networks with hundreds of devices
Cacti can be installed on many platforms like unix, linux and windows. I am concentrating on Windows XP . In order install a Cacti download a full integrated package from following links http://www.disorder.com/~bsod/cacti-0.8.7b.1.8.exe
http://files.davehope.co.uk/cacti/ thanks to Rony and Dave Hope for hosting .
It’s pretty easy to install, make sure IIS is enabled and just follow the steps until you reached the final step where you are suppose to do some modifications which are attached with this post. Cacti Post Installation Instructions
Once you are done with installation then log on to the cacti local web port by following
http://IP Address of the PC/cacti/index.php with default username admin & password cactipw.
For Adding Devices and graphs access this link http://www.cacti.net/downloads/docs/html/graph_howto.html