Advanced Computer Networks & Computer and Network Security: Prof. Dr. Hasan Hüseyin BALIK (1 Week)
Advanced Computer Networks & Computer and Network Security: Prof. Dr. Hasan Hüseyin BALIK (1 Week)
Advanced Computer Networks & Computer and Network Security: Prof. Dr. Hasan Hüseyin BALIK (1 Week)
(1st Week)
Outline
• Course Information and Policies
• Course Syllabus
• 1. Overview
Course Information
• Instructor: Prof. Dr. Hasan H. BALIK, hasanbalik@gmail.com,
www.hasanbalik.com
• Class Homepage:
http://www.hasanbalik.com/LectureNotes/Netwo
rkSecurity/
http://www.hasanbalik.com/LectureNotes/AdvN
etwork/
Book: Computer Security: Principles and Practice, 4th
Edition, William Stallings and Lawrie Brown, 2018
Grading: Final Assignment 100%
Course Syllabus
• Overview
• Computer security technology and principles
o Cryptographic Tools
o User Authentication
o Access Control
o Malicious Software
o Denial-of-Service Attacks
o Intrusion Detection
o Firewalls and Intrusion Prevention Systems
• Trusted systems
o Cloud and IoT Security
• Management ıssues
o IT Security Management and Risk Assessment
o IT Security Controls, Plans and Procedures
o Physical and Infrastructure Security
1. Overview
1. Outline
• Computer Security Concepts
• Threats, Attacks, and Assets
• Security Functional Requirements
• Fundamental Security Design Principles
• Attack Surfaces and Attack Trees
• Computer Security Strategy
• Standards
Confidentiality
- data confidentiality
- privacy
Integrity
- data integrity
- system integrity
Availability
2. In developing a particular security mechanism or algorithm, one must always consider potential attacks
on those security features
5. Security mechanisms typically involve more than a particular algorithm or protocol and also require that
participants be in possession of some secret information which raises questions about the creation, distribution, and
protection of that secret information
6. Attackers only need to find a single weakness, while the designer must find and eliminate all weaknesses
to achieve perfect security
7. Security is still too often an afterthought to be incorporated into a system after the design is complete,
rather than being an integral part of the design process
9. There is a natural tendency on the part of users and system managers to perceive little benefit from
security investment until a security failure occurs
10. Many users and even security administrators view strong security as an impediment to efficient and
user-friendly operation of an information system or use of information
Computer Security Terminology, from RFC 2828, Internet Security Glossary, May 2000
Attack
Any kind of malicious activity that attempts to collect, disrupt, deny, degrade, or destroy information system resources
or the information itself.
Countermeasure
A device or techniques that has as its objective the impairment of the operational effectiveness of undesirable or
adversarial activity, or the prevention of espionage, sabotage, theft, or unauthorized access to or use of sensitive information
or information systems.
Risk
A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically a function of
1) the adverse impacts that would arise if the circumstance or event occurs; and 2) the likelihood of occurrence.
Security Policy
A set of criteria for the provision of security services. It defines and constrains the activities of a data processing facility
in order to maintain a condition of security for systems and data.
Threat
Any circumstance or event with the potential to adversely impact organizational operations (including mission,
functions, image, or reputation), organizational assets, individuals, other organizations, or the Nation through an information
system via unauthorized access, destruction, disclosure, modification of information, and/or denial of service.
Vulnerability
Weakness in an information system, system security procedures, internal controls, or implementation that could be
exploited or triggered by a threat source.
Owners Threat agents
value
wish to abuse
wish to impose and/or
minimize may damage
give
rise to
countermeasures assets
to
reduce
to to
risk threats
that
increase
• Threats
• Capable of exploiting vulnerabilities
• Represent potential security harm to an asset
Residual
vulnerabilities
may remain
Goal is to
May itself minimize
introduce new residual level of
vulnerabilities risk to the
assets
Threat Consequence Threat Action (Attack)
Unauthorized Exposure: Sensitive data are directly released to an
Disclosure unauthorized entity.
A circumstance or I nterception: An unauthorized entity directly accesses
event whereby an sensitive data traveling between authorized sources and
entity gains access to destinations.
data for which the I nference: A threat action whereby an unauthorized entity
Threat
entity is not indirectly accesses sensitive data (but not necessarily the Consequences,
authorized. data contained in the communication) by reasoning from
characteristics or byproducts of communications. and the
I ntrusion: An unauthorized entity gains access to sensitive
data by circumventing a system's security protections. Types of
Deception M asquerade: An unauthorized entity gains access to a
A circumstance or system or performs a malicious act by posing as an
Threat Actions
event that may result authorized entity. That Cause
in an authorized entity Falsification: False data deceive an authorized entity.
receiving false data Repudiation: An entity deceives another by falsely denying Each
and believing it to be responsibility for an act.
true. Consequence
Disruption I ncapacitation: Prevents or interrupts system operation by
A circumstance or disabling a system component.
event that interrupts Corruption: Undesirably alters system operation by Based on
or prevents the correct adversely modifying system functions or data.
operation of system Obstruction: A threat action that interrupts delivery of RFC 4949
services and system services by hindering system operation.
functions.
Usurpation M isappropriation: An entity assumes unauthorized logical
A circumstance or or physical control of a system resource.
event that results in M isuse: Causes a system component to perform a function
control of system or service that is detrimental to system security.
services or functions
by an unauthorized
entity.
Computer System Computer System
4 Sensitive files
must be secure
Data (file security) Data
Least
astonishment
Attack Surfaces
Consist of the reachable and exploitable vulnerabilities in
a system
Examples:
Vulnerabilities created by
personnel or outsiders, such as
social engineering, human
error, and trusted insiders
Included in this category are
network protocol vulnerabilities,
such as those used for a denial- Particular focus is Web server
of-service attack, disruption of software
communications links, and
various forms of intruder attacks
Shallow
M edium High
Layering Security Risk Security Risk
Low M edium
Deep
Small Large
Attack Surface