GithubHelp home page GithubHelp logo

Hi šŸ‘‹, I'm Jacqueline Omollo

A passionate GRC Analyst looking for new career oportunities

jacquelineomollo

  • šŸ”­ Iā€™m currently working on: Studying for ISACA CISA Exam and making videos showcasing my accessing skills with PCI DSS and NIST frameworks

  • šŸŒ± Iā€™m currently learning: Splunk using Linux on a Virtual Machine

  • šŸ‘Æ Iā€™m looking to collaborate: With anyone th

  • šŸ¤ Iā€™m looking for help with: Getting my first engineering job.

  • šŸ‘Øā€šŸ’» All of my old coding projects and new videos on GRC are available at: JacquelineOmollo.com

  • šŸ˜„ Pronouns: She/Her

  • šŸ’¬ Ask me about: Why I decided to switch from a software engineer career to Cybersecurity

  • šŸ“« How to reach me: [email protected] or Linkedin: https://linkedin.com/in/jacquelineomollo

  • āš” Fun fact: Nearly finished building my dream home with the help of my family. Here's a simplified version of the provided code:

My Thought Process on Doing a PCI DSS Assessment as an Internal Security Accessor

Step 1: Getting Familiar with PCI DSS Requirements šŸ“š

Let's kick things off by getting cozy with the magical world of PCI DSS requirements. These are the golden rules designed to shield our payment card data. They cover areas like network security, data encryption, and access controls. šŸŒ

Step 2: Figuring Out What's In Scope šŸ”

Time to put on our detective hats! We'll pinpoint the systems, networks, and processes that dance with payment card data. This laser focus will keep us on the right track. šŸ”¦

Step 3: Taking Stock of Data šŸ—‚ļø

Gather 'round, data wizards! We'll conjure up a list of all the payment card data we handle. Cardholder data (CHD) and sensitive authentication data (SAD) are our enchanting ingredients. šŸ“Š

Step 4: Checking Compliance āœ”ļø

It's audit o'clock! We'll dive into each PCI DSS requirement and give them a thumbs-up or a high-five. Tech inspections, document readings, and friendly chats with fellow wizards might be in store. šŸ•µļøā€ā™‚ļø

Step 5: Finding Weaknesses šŸ•³ļø

Time for some digital spelunking! We're on the hunt for hidden vulnerabilities in our systems and networks. Penetration tests will help us see if any sneaky goblins can break in. ā›ļø

Step 6: Making Things Secure šŸ”’

Wave your magic wand! If we spot any cracks, we'll seal 'em up. Setting up strong boundaries, casting encryption spells, and controlling access are our secret potions. šŸŖ„

Step 7: Keeping Records šŸ“

Let's keep scrolls of wisdom! Detailed notes will chronicle our epic journey. This parchment will show everyone we mean business when it comes to security. šŸ“œ

Step 8: The Questionnaire or Report šŸ“‹

Choose your adventure! Depending on our card data prowess, we'll either complete a "Self-Assessment Questionnaire" (SAQ) or summon a Qualified Security Assessor (QSA) to weave a "Report on Compliance" (ROC). šŸ“œ

Step 9: Fixing Stuff šŸ› ļø

Abracadabra! If anything's amiss, we'll wield our tools and make things right. Swift fixes and rechecks are our spells for safeguarding. šŸ§™

Step 10: Sharing the News šŸ“£

Spread the word like phoenix feathers! We'll tell the card companies and our banking pals that we're in tune with the rules. A special parchment (Attestation of Compliance or AOC) might be the key. šŸ’Œ

Step 11: Keeping Watch šŸ‘ļø

Stay vigilant, guardians! Safety is an ongoing quest. Regular system scans will repel any lurking dragons and keep our castle secure. šŸ°

Step 12: Teaching Everyone šŸŽ“

Empower the tribe! We'll enlighten our team about the ways of PCI DSS, the art of staying safe, and their vital roles in this grand adventure. šŸŒ 

Remember, this guide is your friendly compass. For the full map, consult the wise scrolls of the PCI Security Standards Council and perhaps summon an expert guide to ensure our journey is beyond legendary.

Guardians of the data realm, let's keep the treasure safe! šŸ’ŽšŸ”

Jacqueline L Omollo's Projects

git-for-web-development-project icon git-for-web-development-project

In this project you will be using the concepts learned in the Git for Web Development lesson to fork/clone/push/and submit a PR for each project during this sprint.

graphs icon graphs

Graphs, BFS, DFS, connected components

haircare-app icon haircare-app

Converted my first build weeks project into react and will be building the back-end to it.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    šŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. šŸ“ŠšŸ“ˆšŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ā¤ļø Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.