COMP 4060 Lecture Number 7 Winter Spring 2023
COMP 4060 Lecture Number 7 Winter Spring 2023
Lecture Number 7
March 6, 2023
Mark W. Baker
Virtually Delivered on Blackboard
Final Exam
• Final Exam Time: 6:00 Pm Last Class, 2023 THE EXAM WILL BE IN CLASS
• Final Exam Duration: 1 hour
• Location: The exam will be in a “Final Exam” Folder. The exam will be visible at 6:00 PM EST last day of classes. I will be setting up the
folder shortly.
• Exam Structure:
a. There will be 4 potential answers only one is correct, choose the best answer.
a. Answer is to be about 150 words. If you write more, I will read it, but you are probably writing too much.
• Blackboard should allow me to run a collaboration session at the same time I have an exam, I will confirm this, so if you are confused
about a question, please chat or question. Of course, I cannot give you the answer, but I may be able to clear up a question.
• Good Luck!!
• Mark W. Baker
Assignment #5
Use the Canadian Method under the sea ?
Would you use the RCMP (Royal Canadian Mounted Police) HTRA (Harmonized
Threat and Risk Assessment). Why or why not? If not, what method do you think
you should use?
Would you add in information from the “Baseline Cyber Security Controls for Small
and Medium Organizations V1.2” (13 certification requirements)?
– https://ico.org.uk/for-organisations/guide-to-the
-general-data-protection-regulation-gdpr/
Threat and Risk Assessments – Privacy
(Around the World)
Can only scratch the surface –
Blink and you miss it
Europe
• The General Data Protection Regulation (GDPR)
– Regulation (EU) 2016/679 on the protection of natural persons with regard to
the processing of personal data and on the free movement of such data. This
text includes the corrigendum published in the OJEU of 23 May 2018.
– http://www.dhs.gov/privacy-impact-assessments
Threat and Risk Assessments - Privacy
Impact Assessment
Canada - PIPEDA -Personal Information Protection and Electronic Documents Act
PIPEDA applies to organizations that are federally regulated and fall under the
legislative authority of the Parliament of Canada, such as the telecommunications
and broadcasting industry, and all local businesses in Yukon, Nunavut, and the
Northwest Territories.
PIPEDA also applies to the private sector of each province unless a province has
enacted its own privacy law that is substantially similar to PIPEDA. Only British
Columbia, Alberta, and Quebec have privacy laws that have been deemed to be
“substantially similar” to PIPEDA.
• Confidentiality –
– roughly equivalent to privacy
– designed to prevent sensitive information from the wrong people,
– ensures right people can in fact get it, Access must be restricted
to those
– Data can be categorized according to the amount and type of
damage. Measures can then be implemented according to those
categories.
– Can involve special training for uses. Includes risks that could
threaten this information and helps familiarize authorized people
with risk factors and how to guard against them.
• Strong passwords and password-related best practices
• Social engineering methods - to prevent them from bending data-
handling rules with good intentions and potentially disastrous results.
Asset Identification and Classification
Another way of looking at risk…what is at risk
• Confidentiality cont.
– account number or routing number when banking online.
– Data encryption is a common method of ensuring confidentiality (can
be broken or avoided)
– User IDs and passwords constitute a standard procedure; (two-factor
authentication is becoming the norm)
– Biometric verification
– security tokens, key fobs or soft tokens.
– Users can take precautions to minimize the number of places where
the information appears and the number of times it is actually
transmitted to complete a required transaction
– Extra measures might be taken in the case of extremely sensitive
documents
• air gapped computers, disconnected storage devices for highly sensitive
information
• hard copy form only (because this has worked so well in the past)
Asset Identification and Classification
Another way of looking at risk…what is at risk
• Integrity:
– Maintaining the consistency, accuracy, and
trustworthiness of data over its entire life cycle
• Data must not be changed in transit,
• data cannot be altered by unauthorized people (These
measures include file permissions and user access controls)
• Erroneous changes or accidental deletion by authorized users
becoming a problem (use version control but this does not
prevent everything)
• There should be means to detect any changes in data that
might occur from other events
– server crash
– Power failure
– Natural events/disasters
– Electomagnetic pulses (solar flare)
Asset Identification and Classification
Another way of looking at risk…what is at risk
• Integrity cont.:
– Backups/redundancies can restore the affected
data to its correct state. Factors include
• Frequency of backup
• Location of backup
• Type of backup/restoration (walk the tapes over)
• Restoration issues
– Testing of restoration
– Testing of restored data
Asset Identification and Classification
Another way of looking at risk…what is at risk
• Availability:
– Can you get the data when you need it?
– Rigorously maintain all hardware
• Performing hardware repairs
– Maintain a correctly functioning operating system
environment that is free of software conflicts
• Keep current with all necessary system upgrades.
– Providing adequate communication bandwidth,
prevent occurrence bottlenecks (especially for
work a home environment and for disaster
management)
Asset Identification and Classification
Another way of looking at risk…what is at risk
• Availability (cont.):
– Redundancy (duplication) not always bad -relates for places to failover
• RAID (Redundant Array of Independent disks) can though not always provide
redundancy
• High-availability clusters - group of hosts that act like a single system and
provide continuous uptime
• To the cloud!!! – has its own problem
• High Quality – IT disaster recovery is essential
– Be able to handle natural disasters and human disasters (good risk assessment)
– Backups to be “stored/located/hosted” in a geographically-isolated location
» Leads to restoration issues
• Fm Nweke, Livinus Obiora, PM World Journal, Using the CIA and AAA Models to explain Vol. VI, Issue XII – December 2017 Cybersecurity
Activities,,www.pmworldjournal.net
Threat Identification
Different ways of classifying a threat (risk)
• Attacker-centric
– Attacker-centric threat modeling starts with an attacker, and evaluates
their goals, and how they might achieve them. Attacker's motivations are
often considered:
• Reading of Email
• Copying and sharing of DVD
• Often starts from either entry points or assets.
• Software-centric
– Software-centric threat modeling (also called 'system-centric,' 'design-
centric,' or 'architecture-centric') starts from the design of the system,
and attempts to step through a model of the system, looking for types of
attacks against each element of the model.
• Asset-centric
– Involves starting from assets entrusted to a system, such as a collection of
sensitive personal information.
Threat Identification
Different ways of classifying a threat (risk)
• Defenders perspective (you)
– Threats are examined and countermeasures, or
security services, identified at the design state of
the application before any code is written.
– Defensive mechanisms are built into the code as it
is written rather than patched in later.
• cost effective and increases security awareness in the
development team.
• However not all threats can not be identified unless the
code is t simple
• threat modeling on a defender's perspective may cause
the development team to falsely believe code is secure.
Threat Identification
Different ways of classifying a threat (risk)
• High level overview defensive perspective threat modeling steps are:
• Define the application requirements:
– Identify business objectives
– Identify user roles that will interact with the application
– Identify the data the application will manipulate
– Identify the use cases for operating on that data that the application will facilitate
• Model the application architecture
– Model the components of the application
– Model the service roles that the components will act under
– Model any external dependencies
– Model the calls from roles, to components and eventually to the data store for each use case as
identified above
• Identify any threats to the confidentiality, availability and integrity of the data and the
application based on the data access control matrix that your application should be
enforcing (there are many possible mistakes here)
• Assign risk values and determine the risk responses (Very subjective)
• Determine the countermeasures to implement based on your chosen risk responses
• Continually update the threat model based on the emerging security landscape.
Threat Identification
Different ways of classifying a threat (risk)
• Other methods of threat identification and
modelling
• https://www.owasp.org/index.php/Threat_Ris
k_Modeling
• https://developer.apple.com/library/mac/doc
umentation/Security/Conceptual/Security_Ov
erview/ThreatModeling/ThreatModeling.html
• https://www.owasp.org/index.php/Definition
_for_Security_Assessment_Techniques
Assignment #6
You are the head of IT Security at the new Atlantean Data Base. Unfortunately, as you swim to the office, you get a
text and are told there is a breach. When you get to work, you see this person’s image on your computer screen.
In a deep voice you hear “All of your databases have been encrypted. We have downloaded the credit card
information on all your clients. If we do not receive 100 bitcoin forwarded to our bank account (Bank of Luthor
1233212332-b) in the Cayman Islands in 2 days, we will sell information on the dark web. If we receive our
Bitcoin we will erase the credit card data and provide you the decryption key. “
Preliminary investigation shows - Only one data base appears to have been encrypted. It has client addresses,
phone numbers and information on what products/services you provide them as well as various linking data to
other databases (these other data bases have not been encrypted or so it seems). The Accounting Department
says there is no credit card info on this data base as this service has been outsourced.
• Create an action list of at least 6 actions as to what you would do to uncover the perpetrator and limit the
damage (IT, human and even legal)
– Provide 3 human based actions – i.e. how would deal with employees, suppliers, the law, etc.
– Provide 3 IT(Computer based actions)
– Would you pay the ransom?
– What would you do about data privacy – Information on the King and Queen of Atlantis in was in the Data Base!