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

Implementation Plan for Wells Fargo: Addressing the 'Dirty Pipe' Vulnerability, Assignments of Computer Security

A comprehensive implementation plan for addressing the 'dirty pipe' vulnerability (cve-2022-0847) in the linux operating system at wells fargo. It includes a problem statement, recommended solution, implementation flow diagram, cost-benefit analysis, solution validation, evaluation and continuous improvement plan, and legal, ethical, and cultural considerations. A detailed approach to mitigating the vulnerability and ensuring the security of sensitive data.

Typology: Assignments

2024/2025

Available from 02/21/2025

Milestonee
Milestonee 🇺🇸

4.4

(22)

3.5K documents

1 / 9

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SEC572
Week 6
Implementation Plan for Wells Fargo
By Ronnie Earnest
pf3
pf4
pf5
pf8
pf9

Partial preview of the text

Download Implementation Plan for Wells Fargo: Addressing the 'Dirty Pipe' Vulnerability and more Assignments Computer Security in PDF only on Docsity!

SEC

Week 6

Implementation Plan for Wells Fargo

By Ronnie Earnest

Rubric

  • Include problem statement slide from previous deliverable Criteria Total
  • Include recommended solution slide from previous deliverable
  • Implementation flow diagram (Malware, BYOD, Encryption)
  • Cost-benefit analysis (CBA)
  • Solution validation
  • Solution evaluation and continuous improvement
  • Decommission
  • Legal, ethical and cultural considerations
  • Total

Recommended Solution

The solution for the dirty pipe vulnerability would be to run a

patch for the version of Linux that is currently being used.

Patches should be uploaded as they are released.

Implementation flow diagram (Malware, BYOD, Encryption)

Solution validation

Prior to deployment in production, test the effectiveness of

the patching lower environments, make sure that servers still

run smoothly.

Do the same with any vendor software patches.

Only deploy to production if servers operate as expected after testing.

Monitor production environment closely after deployment to

ensure there are no issues.

Evaluation and Continuous

Improvement

Once the patch for ‘dirty pipe’ is in place, this hole is fixed.

Systems should be tested regularly for weaknesses, and

any weaknesses should be addressed.

Systems should be monitored and updated frequently.

Any irregular traffic or events should be handled swiftly.