Dis Unit 1
Dis Unit 1
1.1 History
" By understanding the history of technology security, you might be able to
safeguard against potential threats. Information technology security protects
sensitive assets and property through the use of technology processes and training.
" The examination of the history of information security is important since it
enhances the understanding of the current state of the discipline and helps to
foresee its future.
Security goals form an integral part of the overall information security concept.
Security goals serve as evaluation criteria for information systems and IT security.
Hence, a value of. the goals analysis is in verifying the adequacy of security
evaluation criteria.
Information protection was achieved mainly through the control of physical access
to computers.
" Mainframe computers were protected by using multiple level of security and
maintain the data integrity.
1. Year 1960s
The largest security concerns at this interval were at the points of access. Anyone
with enough knowledge about how to work a computer could break into a facility
and start accessing sensitive data. In order to secure terminals, passwords and
multiple layers of security protection were added to devices.
It was the tine of cold war in the world. For performing complex and
sophisticated task, mainframe computers are connected other machines.
Department of Defense's Advanced Research Project Agency (ARPA) started
project for military. There were need of exchange information with other and
within the military department.
" Larry Roberts, the founder of the Internet, developed the project, which was called
ARPANET.
2. Year 1970s
ARPANET becomes popular and widely used for communication. ARPANET's
facilities
Purpose was always more academic than military, but, as more academic
connected to it.
There was no massive global network connecting every device that wanted to be
Connected, large organizations, especially governments, were starting to link
computers via telephone lines.
Management of
information
security
Computer and
data security
2. Integrity
Integrity ensures that received message has not been altered in any way from
origin. It refers to the trustworthiness of information resources. Integrity should
not be altered without detection.
" It includes the concept of "data integrity" namely, that data have not been changed
inappropriately, whether by accident or deliberately malign activity.
" It also includes "origin" or "source integrity that is, that the data actually came
from the person or entity you think it did, rather than an imposter.
Integrity ensures that information is not changed or altered in transit. Under
certain attack models, an adversary may not have to power to impersonate an
authenticated party or understand a confidential communication, but may have the
ability to change the information being transmitted.
" On amore restrictive view, however, integrity of an information system includes
only preservation without corruption of whatever was transmitted or entered into
the system, right or wrong.
3. Availability
Availability refers, to the availability of information resources. An information
system that is not available when you need it is at least as bad as none at al.
Availability means that people who are authorized to use information are not
prevented from doing so. It may be much worse, depending on how reliant the
organization has become on a functioning computer and communications
infrastructure.
" Almost all moderm organizations are highly dependent on functioning information
systems. Many literally could not operate without them.
Availability, like other aspects of security, may be affected by purely technical
issues (e.g8. a malfurnctioning part of a computer or communications device),
natural phenomena (e.g. wind or water), or human causes (acidental or
deliberate).
atility depends
Confidentiality
of information P o l i
e cdyu c a ttieocnh n o l o g y
Confidentality
estion of utility
pted or stored Integrity
Iintegrity
thief, -but not
for the thief.
hen a control Availabilty Avalability
ed to a named
Storage Processing Transmission Storage Processing Transmission
kuser activity
Fig. 1.4.1 CNSS model
The McCumber Cube as represented in Fig. 1.4.1, shows three
three dimensions of each axis become a 3 x 3 x3 cube with 27 cellsdimensions. The
areas that must be addressed to secure today's information systems. representing
ation Systems
Hthe NSTISSC While the NSTISSCmodel covers the three dimensions of information security, it
Confidentiality, omits discussion of detailed guidelines arnd policies that direct the implementation
SETA) and of controls.
to assign the " Another weakness of using this model with too limited an approach is to view it
t.
from a single perspective.
pable ways : 1.5 Components of an Information System
An information system can be defined technically as a set of interrelated
components that collect (or retrieve), process, store and distribute information to
Support decision making and control in an organization.
TECHNICAL PUBLICA TIONS an up-thrust for
knowledge
introducton
1-10
Data and Information Security
Information systems
Tele
People networks
Procedures
Security Access
Fig. 1.6.1
" It is impossible to obtain perfect security : It's a process, not an
should be considered balance between protection and availability.absolute. Security
To achieve balarnce, level of security must allow reasonable
access, the security
level must allow reasonable access, yet protect against threats.
1.7 System Development Life Cycle (SDLC)
The system development life cycle is a project management model that defines the
stages involved in bringing a project from inception to completion. Software
development teams, for example, deploy a variety of systems development life
cycle models that include waterfall, spiral and agile processes.
The system-development life cycle enables users to transform a newly-developed
project into an operational one.
SDLC is a multistep, iterative process, structured in a methodical way. This
process is used to model or provide a framework for technical and non-technical
activities to deliver a quality system which meets or exceeds a business's
expectations or manage decision-making progression.
Traditionally, the systems-development life cycle consisted of five stages. That has
now increased to seven phases. Increasing the number of steps helped systems
analysts to define clearer actions to achieve specific goals. Fig. 1.7.1 shows SDLC
phases.
" The SDLC highlights different stages (phrases Or steps) of the development
process. The life cycle approach is used So users can see and understand what
activities are involved within a given step. t is also used to let them know that at
any time, steps can be repeated or a previous step can be reworked when needing
to modify or improve the system.
7: Maintenance 1: Planning
6: Implementation, 2: Analysis
SDLC
5: Testing 3: Design
4: Development
2. Systems Analysis and Requirements : The second phase is where businesses will
work on the source of their problem or the need for a change. In the event of a
problem, possible solutions are submitted and analyzed to identify the best fit for
the ultimate goal(s) of the project. This is where teams consider the functional
requirements of the project or solution.
3. Systems Design : This phase describes the necessary specifications, features and
operations that will satisfy the functional requirements of the proposed system
which will be in place. This is the step for end users to discuss and determine
their specific business information needs for the proposed system.
4. Development : The fourth phase is when the real work begins, when a
programmer, network engineer and/or database developer are brought on to do
the major work on the project. This work includes using a flow chart to ensure
that the process of the system is properly organized. The development phase
marks the end of the initial section of the process.
5. Integration and Testing : It is normally carried out by a Quality Assurance (QA)
professional to determine if the proposed design meets the initial set of business
goals. Testing may be repeated, specifically to check for errors, bugs and
interoperability. This testing will be performed until the end user finds it
acceptable.
6. Lmplementation :The sixth phase is when the majority of the code for the program
is written. Additionally, this phase involves the actual installation of the
newly-developed system. This step puts the project into production by moving the
data and components from the old system and placing them in the new system.
TECHNICAL PUBLICATIONS -an up-thrust for knowiedge
Data and Information Security 1-13 Introduction
7. Operations and Maintenance : The seventh and final phase involves maintenance
and regular required updates. This step is when end users can
fine-tune the
system, if they wish, to boost performance, add new capabilities or meet
user
requirements additional
1.7.1 Secure SDLC
Security system development life cycde is defined as the series of
procedures in the software development cycde, designed to enable processes and
teams to create software and applications in a manner that development
security risks, eliminating security vulnerabilities and reducingsignificantly reduces
costs. The process,
like the traditional systems developmernt life cyce, is
phases.
divided into a number of
Security in development and support processes is an essential part of a
comprehernsive quality assurance and production control process and usually
involves training and continuous oversight by the most experienced staff.
" Rules for system and software development should be
developed should be
developed. These rules should incorporate secure software development
such as user authentication, session control, logging and data techniques
sanitization. validation and
Fig. 1.7.2 shows information security life cycle
2 Policy
6. Risk analysis Security mplementation
life
cycle
5. Security 3. Monitor
assessment
4. Intrusion
detection
Fig. 1.7.2
Security life cycle involves following phases :
1. Planning 2. Policy implementation
3. Monitoring 4. Intrusion detection
of
for disruption,
information
message
wledge b
on,
contents or
Q.12 Q.8 0.4
monitoringmodification, and
and information
traffic
of, or
Data and Information Security 1-17 Introduction