Unit2.pptx
Unit2.pptx
Unit2.pptx
Nathan House , The Complete Cyber Security Course, StationX, First edition,
January 2017
Udemy
The Threat and Vulnerability Landscape
• Cybercrime has exacted a heavy toll on the online community in recent years, as detailed
in this piece by Security Boulevard, which draws its conclusions from several industry
sources.
• Among other things, the report says that data breaches exposed 4.1 billion records in
2019 and that social media-enabled cybercrimes steal $3.25 billion in annual global
revenue.
• According to KnowBe4's 2019 Security Threats and Trends report, 75 percent of
businesses consider insider threats to be a significant concern, 85 percent of
organizations surveyed reported being targeted by phishing and social engineering
attacks, and percent of responders cite email phishing scams as the largest security risk.
Smart organizations and individuals will take advantage of any reliable resources to fight this growing epidemic, and sound threat
modeling designing for security purposes is essential to accomplish this.
Ten Threat Modeling Methodologies
1. STRIDE
A methodology developed by Microsoft for threat modeling, it offers a mnemonic for
identifying security threats in six categories:
• Spoofing: An intruder posing as another user, component, or other system feature
that contains an identity in the modeled system.
• Tampering: The altering of data within a system to achieve a malicious goal.
• Repudiation: The ability of an intruder to deny that they performed some malicious
activity, due to the absence of enough proof.
• Information Disclosure: Exposing protected data to a user that isn't authorized to
see it.
• Denial of Service: An adversary uses illegitimate means to exhaust services
needed to provide service to users.
• Elevation of Privilege: Allowing an intruder to execute commands and functions
that they aren't allowed to.
DREAD
Proposed for threat modeling, but Microsoft dropped it in 2008
due to inconsistent ratings. OpenStack and many other
organizations currently use DREAD. It's essentially a way to rank
and assess security risks in five categories:
• Damage Potential: Ranks the extent of damage resulting from
an exploited weakness.
• Reproducibility: Ranks the ease of reproducing an attack
• Exploitability: Assigns a numerical rating to the effort needed to
launch the attack.
• Affected Users: A value representing how many users get
impacted if an exploit becomes widely available.
• Discoverability: Measures how easy it is to discover the threat.
• P.A.S.T.A
This stands for Process for Attack Simulation and Threat
Analysis, a seven-step, risk-centric methodology.
It offers a dynamic threat identification, enumeration, and scoring
process.
Once experts create a detailed analysis of identified threats,
developers can develop an asset-centric mitigation strategy by
analyzing the application through an attacker-centric view.
OCTAVE
• The Operationally Critical Threat, Asset, and Vulnerability
Evaluation (OCTAVE) process is a risk-based strategic
assessment and planning method. OCTAVE focuses on
assessing organizational risks only and does not address
technological risks. OCTAVE has three phases:
• Building asset-based threat profiles. (Organizational evaluation)
• Identifying infrastructure vulnerabilities. (Information
infrastructure evaluation)
• Developing and planning a security strategy. (Evaluation of risks
to the company's critical assets and decision making.)
Others
• VAST
• Attack Tree
• Common Vulnerability Scoring System (CVSS)
• T-MAP
• Quantitative Threat Modeling Method
This hybrid method combines attack trees, STRIDE, and CVSS methods. It
addresses several pressing issues with threat modeling for cyber-physical systems
that contain complex interdependencies in their components. The first step is
building components attack trees for the STRIDE categories. These trees illustrate
the dependencies in the attack categories and low-level component attributes.
Then the CVSS method is applied, calculating the scores for all the tree's
components.
Risk Assessment – 5 step framework
Practically every organization has internet connectivity and some form of IT
infrastructure, which means nearly all organizations are at risk of a cyber
attack.
To understand how great this risk is and to be able to manage it,
organizations need to complete a cybersecurity risk assessment, a process
that identifies which assets are most vulnerable to the cyber risks the
organization faces.
This is a risk assessment that looks specifically at cyber threats, so risks
such as fire and flooding which would be included in a general risk
assessment are not in scope.
Step 1: Determine the scope of the risk
assessment
• A risk assessment starts by deciding what is in scope of the
assessment.
• It could be the entire organization, but this is usually too big an
undertaking, so it is more likely to be a business unit, location or
a specific aspect of the business, such as payment processing
or a web application.
• A third-party specializing in risk assessments may be needed to
help them through what is a resource-intensive exercise.
Step 2:
How to identify cybersecurity risks
• Identify assets
• Identify threats
• Identify what could go wrong
This task involves specifying the consequences of an identified threat
exploiting a vulnerability to attack an in-scope asset. For example:
• Threat: An attacker performs an SQL injection on an open
database table
• Vulnerability: unpatched
• Asset: web server
• Consequence: customers' private data stolen, resulting
in regulatory fines and damage to reputation.
Step 3: Analyze risks and determine
potential impact
• Now it is time to determine the likelihood of the risk scenarios
documented in Step 2 actually occurring, and the impact on the
organization if it did happen.
• In a cybersecurity risk assessment, risk likelihood -- the
probability that a given threat is capable of exploiting a given
vulnerability -- should be determined based on the
discoverability, exploitability and reproducibility of threats and
vulnerabilities rather than historical occurrences.
Step 4: Determine and prioritize risks
• Using a risk matrix like the one below where the risk level is
"Likelihood times Impact," each risk scenario can be classified.
Step 5: Document all risks
• Risk scenario
• Identification date
• Existing security controls
• Current risk level
• Treatment plan -- the planned activities and timeline to bring the risk within
an acceptable risk tolerance level along with the commercial justification
for the investment
• Progress status -- the status of implementing the treatment plan
• Residual risk -- the risk level after the treatment plan is implemented
• Risk owner -- the individual or group responsible for ensuring that the
residual risks remain within the tolerance level
Risk Assessment Vs Threat Modeling
• A risk assessment considers possible countermeasures; threat
modeling defines and implements them.
• Threat modeling identifies vulnerabilities, as well as potential risks
and mitigation steps, by using scenarios that target system entry
points and data, both at rest and in transit.
• A cyber security risk assessment is the process of identifying,
analysing and evaluating risk.
• It helps to ensure that the cyber security controls you choose are
appropriate to the risks your organization faces.
• Without a risk assessment to inform your cyber security choices, you
could waste time, effort and resources.
Things You Need To Stay Safe Online
• Injection Flaws
Injection flaws result from a classic failure to filter untrusted input. Injection flaws can
happen when we pass unfiltered data to the SQL server (SQL injection), to the browser
(via Cross Site Scripting), to the LDAP server (LDAP injection), or anywhere else. The
problem here is that the attacker can inject commands to hijack clients’ browsers,
resulting in loss of data.
Broken Authentication
• Problems that might occur during broken authentication don’t necessarily stem from the same root cause.
Rolling your own authentication code is not recommended, as it is hard to get right. There are myriad
possible pitfalls, and here are a few:
1. The URL might contain the session ID and leak it in the referer header.
2. Passwords might not be encrypted in storage and/or transit.
3. Session IDs might be predictable, making it a little too easy to gain unauthorized access.
4. Session fixation might be possible.
5. Session hijacking could occur if timeouts are not implemented correctly, or if using HTTP (no SSL security),
etc.
• Cross-Site Scripting (XSS)
An attacker sends on input JavaScript tags to your web application.
When this input is returned to the user unsanitized, the user’s browser
would execute it.
Insecure Direct Object References
This is a classic case of trusting user input and paying the price by
inheriting a resultant security vulnerability. A direct object reference
means that an internal object (e.g., a file or a database key) is exposed
to the user, leaving us vulnerable to attack. The attacker can provide
this reference, and if authorization is either not enforced or broken, the
attacker gets in.
Security Misconfiguration