Lecture1 Introduction
Lecture1 Introduction
Instructor
Abu Sayed Md. Mostafizur Rahaman, PhD
Professor
Department of Computer Science and Engineering
Jahangirnagar University
Textbooks
Sixth Edition
2 Introduction to Information Security, Abu Sayed Md. Mostafizur Rahaman, PhD
Google class
• Class code: kimny67
• It contains
– Lecture Materials
– Schedule Updates
– Additional resources
– Etc
Module 9 Security
Module 8 Security
Technology: Intrusion
Module 7 Security and Technology: Access Module 11 Implementing Module 12 Information
Detection and Prevention Module 10 Cryptography
Personnel Controls, Firewalls, and Information Security Security Maintenance
Systems and Other Security
VPNs
Tools
Date Document
1968 Maurice Wilkes discusses password security in Time - Sharing Computer Systems.
1970 Willis H. Ware author the report Security Controls for Computer Systems: Report of Defense Science Board
Task Force on Computer Security—RAND R.609 which was not declassified until 1979. It became known as
the seminal work identifying the need for computer Security.
1973 Schell, Downey, and Popek examine the need for additional security in military systems in Preliminary Notes
on the Design of Secure Military Computer Systems.
1975 The Federal Information Processing Standards (FIPS) examines DES (Digital Encryption Standard) In the
Federal Register.
1978 Bisbey and Hollingsworth publish their study “Protection Analysis: Final Report,” which discussed the
Protection Analysis project created by ARPA to better understand the vulnerabilities of operating system
security and examine the possibility of automated vulnerability detection techniques in existing system
software.
1979 Dennis Ritchie publishes “On the Security of UNIX” and “Protection of Data File Contents,” which discussed secure user IDs,
secure group IDs, and the problems inherent in the systems.
1982 The US. Department of Defense Computer Security Evaluation Center published the first version of the Trusted Computer Security
(TCSEC) documents, which came to be known as the Rainbow Series.
1982 Grampp and Morris write “The UNIX System: UNIX Operating System Security.” In this report the authors examined four
“important handles to computer security”: physical control of primes and computer facilities, management commitment to security
objectives, education of employees, and administrative procedures aimed at increased security.
1984 Reeds and Weinberger publish “File Security and the UNIX System Crypt Command.” Their premise was: “No technique can be
secure against wiretapping or is equivalent on the computer. Therefore no technique can be secure against the system administrator
or other privileged users... the naive user have no chance.”
1992 Researchers for the Internet Engineering Task force, working at the Naval Research Laboratory, develop the Simple Internet
Protocol Plus (SIPP) Security protocols, creating what is now known as IPSEC security.
Control, safeguard,
Access Asset Attack
or countermeasure
Protection profile or
Exploit Exposure Loss
security posture
Subjects and
Risk objects of Threat Threat agent
attack
To achieve balance, the level of security must allow reasonable access, yet
protect against threats.
Systems development life cycle (SDLC): a methodology for the design and
implementation of an information system
At the end of all phases, a process is undertaken to assess economic, technical, and behavioral feasibilities
and ensure implementation is worth the time and effort.
The organization
Consists of assessments of: Current systems
Capability to support proposed systems
Analysts determine what the new system is expected to do and how it will
interact with existing systems.
The first and driving factor is the business need. Applications are selected to provide needed services.
Data support and structures capable of providing the needed inputs are identified.
Analysts generate estimates of costs and benefits to allow comparison of available options.
Specific technologies are selected to support the alternatives identified and evaluated in the
logical design.
Consists of the tasks necessary to support and modify the system for the remainder of its
useful life
Life cycle continues until the team determines the process should begin again from the
investigation phase
When current system can no longer support the organization’s mission, a new project is
implemented
A national effort is under way to create a common body of knowledge focused on secure software
development.
U.S. Department of Defense and Department of Homeland Security supported the Software
Assurance Initiative, which resulted in the publication of Secure Software Assurance (SwA)
Common Body of Knowledge (CBK).
SwA CBK serves as a strongly recommended guide to developing more secure applications.
Nature of Dangers
SwA CBK, which is a work in progress, contains Fundamental Concepts and Principles
the following sections: Ethics, Law, and Governance
Data owners: senior management responsible for the security and use of a particular set of
information
Data custodians: responsible for the information and systems that process, transmit, and
store it
Data trustees: are individuals appointed by data owners to oversee the management of a particular set of
information and to coordinate with data custodians for its storage, protection, and use
Almost every fault, security hole, and systems malfunction is a result of interaction of
specific hardware and software.
If developers had sufficient time, they could resolve and eliminate faults.
Security begins and ends with the people that interact with the
system, intentionally or otherwise.