Shagun-15csp018
SECURITY Shweta-15csp021
Srishti-15csp024
PURPOSE
The purpose of this policy is to establish administrative direction, procedural
requirements, and technical guidance to ensure the appropriate protection of
companys information handled by computer networks.
SCOPE
This policy applies to all who access companys computer networks. Throughout this
policy, the word user will be used to collectively refer to all such individuals. The
policy also applies to all computer and data communication systems owned by or
administered by the company or its partners.
POLICY
All information traveling over companys computer networks that has not been
specifically identified as the property of other parties will be treated as companys
asset. It is the policy to prohibit unauthorized access, disclosure, duplication,
modification, diversion, destruction, loss, misuse, or theft of this information. In
addition, it is the policy to protect information belonging to third parties that have
been entrusted to us in a manner consistent with its sensitivity.
POLICY
Network Access control
1. It is the responsibility of employees with VPN privileges to ensure that
unauthorized users are not allowed access to internal networks.
2. VPN use is to be controlled using either a one-time password authentication such as
a token device or a public/private key system with a strong passphrase.
3. When actively connected to the corporate network, VPNs will force all traffic to
and from the PC over the VPN tunnel: all other traffic will be dropped.
4. Dual (split) tunneling is NOT permitted; only one network connection is allowed.
NETWORK ACCESS CONTROL CONTINUED..
1. All users must be positively identified prior to being able to use any multi-user
computer or communications system resources. Positive identification for internal networks
involves a user ID and password, both of which are unique to an individual user, or an
extended user authentication system.
2. VPN users will be automatically disconnected from the network after thirty minutes of
inactivity. The user must then logon again to reconnect to the network. Pings or other
artificial network processes are not to be used to keep the connection open.
3. The VPN concentrator is limited to an absolute connection time of 24 hours.
SYSTEM ACCESS CONTROL
End-User Passwords
1. The key step is to effectively protect the intellectual property and personal and financial
information entrusted to it by students, employees, partners and others. Using passwords that
are difficult to guess is key step towards effectively fulfilling the condition.
2. Any password used to access information stored and/or maintained by company must be
at least 8 characters long, contain at least one uppercase letter and one number or special
character.
3. Passwords will expire annually every 365 days. When a password expires or a change is
required, users should create a new password that is not identical to the last three passwords
previously employed.
4. Passwords stored electronically may not be stored in readable form where unauthorized
persons might discover them.
5. Passwords may not be written down and left in a place where unauthorized persons might
discover them.
6. Passwords may never be shared or revealed to anyone other than the authorized user.
ACCEPTABLE ENCRYPTION POLICY
Proven, standard algorithms such as DES, Blowfish, RSA, RC5 and IDEA should be used
as the basis for encryption technologies. These algorithms represent the actual cipher
used for an approved application. For example, Network Associate's Pretty Good
Privacy (PGP) uses a combination of IDEA and RSA or DiffieHillman, while Secure
Socket Layer (SSL) uses RSA encryption. Symmetric cryptosystem key lengths must be
at least 56 bits.
SERVER SECURITY GUIDELINES
Operating System configuration should be in accordance with the guidelines.
Services and applications that will not be used must be disabled where practical.
Access to services should be logged and/or protected through access-control methods such
as TCP Wrappers, if possible.
The most recent security patches must be installed on the system as soon as practical, the only
exception being when immediate application would interfere with business requirements.
Always use standard security principles of least required access to perform a function.
Do not use root when a non-privileged account will do.
If a methodology for secure channel connection is available (i.e., technically feasible),
privileged access must be performed over secure channels, (e.g., encrypted network
connections using SSH or IPSec).
Servers should be physically located in an access-controlled environment.
Servers are specifically prohibited from operating from uncontrolled cubicle areas.
SERVER SECURITY GUIDELINES