jacquelineomollo / bw-pt-partyplanner-fe

Front end portion of party planner app

Hi 👋, I'm Jacqueline Omollo

A passionate GRC Analyst looking for new career oportunities

• 🔭 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! 💎🔐