Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Security Control Selection for Wells Fargo: A Case Study of the 'Dirty Pipe' Vulnerability, Assignments of Computer Networks

A case study of the 'dirty pipe' vulnerability in the linux operating system, focusing on its impact on wells fargo. It outlines the problem statement, security controls, and qualitative analysis of patching and monitoring. The document lacks depth and analysis, focusing primarily on a specific vulnerability and its potential impact on a single organization.

Typology: Assignments

2024/2025

Available from 02/21/2025

Milestonee
Milestonee 🇺🇸

4.4

(22)

3.5K documents

1 / 7

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SEC572
Week 4
Security Control Selection for Wells Fargo
By: Ronnie Earnest
pf3
pf4
pf5

Partial preview of the text

Download Security Control Selection for Wells Fargo: A Case Study of the 'Dirty Pipe' Vulnerability and more Assignments Computer Networks in PDF only on Docsity!

SEC

Week 4

Security Control Selection for Wells Fargo By: Ronnie Earnest

Rubric

Criteria Total Include problem statement from previous deliverable 10 Malware 20 Security control selection and justification 30 Qualitative analysis 20 DevSecOps diagram 20 Total 100

(Select one - Malware, Ransomware,

DDoS)

  • Wells^ Fargo has disclosed a data breach caused by the actions of

one of its employees, resulting in the exposure of personal and

mortgage account information for two of its customers.

Security Controls

  • Apology^ must be made to ensure patching is either a weekly biweekly or monthly occurrence.
  • Policy^ should be made to upload critical patches on a time scale that varies based on the circumstance.
  • Patches^ must be provided to all systems.
  • All^ patches and modifications should be filed and kept in records.
  • The^ “Dirty pipe” vulnerability doesn't require physical access which is what makes it vulnerable.
  • Physical^ access is still a threat and should continue to be monitored to ensure security.

Flow Diagram

1 Identify 2 Obtain 3 Test 4 Deploy 5 Monitor