diff --git a/CNAME b/CNAME
index 8b137891791fe..e87187a383ca0 100644
--- a/CNAME
+++ b/CNAME
@@ -1 +1 @@
-
+ben-levin.online
diff --git a/_config.yml b/_config.yml
index d4916414195c9..546c239df8b1d 100644
--- a/_config.yml
+++ b/_config.yml
@@ -1,83 +1,81 @@
-#
-# This file contains configuration flags to customize your site
-#
-
-# Name of your site (displayed in the header)
-name: Your Name
-
-# Short bio or description (displayed in the header)
-description: Web Developer from Somewhere
-
-# URL of your avatar or profile pic (you could use your GitHub profile pic)
-avatar: https://raw.githubusercontent.com/barryclark/jekyll-now/master/images/jekyll-logo.png
-
-#
-# Flags below are optional
-#
-
-# Includes an icon in the footer for each username you enter
-footer-links:
-  dribbble:
-  email:
-  facebook:
-  flickr:
-  github: barryclark/jekyll-now
-  instagram:
-  linkedin:
-  pinterest:
-  rss: # just type anything here for a working RSS icon
-  twitter: jekyllrb
-  stackoverflow: # your stackoverflow profile, e.g. "users/50476/bart-kiers"
-  youtube: # channel/<your_long_string> or user/<user-name>
-  googleplus: # anything in your profile username that comes after plus.google.com/
-
-
-# Enter your Disqus shortname (not your username) to enable commenting on posts
-# You can find your shortname on the Settings page of your Disqus account
-disqus:
-
-# Enter your Google Analytics web tracking code (e.g. UA-2110908-2) to activate tracking
-google_analytics:
-
-# Your website URL (e.g. http://barryclark.github.io or http://www.barryclark.co)
-# Used for Sitemap.xml and your RSS feed
-url:
-
-# If you're hosting your site at a Project repository on GitHub pages
-# (http://yourusername.github.io/repository-name)
-# and NOT your User repository (http://yourusername.github.io)
-# then add in the baseurl here, like this: "/repository-name"
-baseurl: ""
-
-#
-# !! You don't need to change any of the configuration flags below !!
-#
-
+# --- Site basics
+title: Benefit
+name: Benefit
+description: "Generalist aiming to specialise but the curious nature is constantly challenging me to explore and seek out understanding new things."
+url: "https://ben-levin.online"   # if using a custom domain, put that here instead (e.g., https://example.com)
+baseurl: ""                           # "" for user/organization sites; "/repo-name" for project sites
 permalink: /:title/
+timezone: Africa/Johannesburg
+locale: en-ZA
 
-# The release of Jekyll Now that you're using
-version: v1.2.0
+# --- Theme
+remote_theme: "mmistakes/minimal-mistakes@4.27.3"
+minimal_mistakes_skin: "mint"         # try: default, dark, sunrise, sea, neon, etc.
 
-# Jekyll 3 now only supports Kramdown for Markdown
+# --- Plugins (GitHub Pages–compatible)
+plugins:
+  - jekyll-include-cache
+  - jekyll-feed
+  - jekyll-sitemap
+  - jekyll-paginate
+
+# --- Markdown & syntax highlighting
 kramdown:
-  # Use GitHub flavored markdown, including triple backtick fenced code blocks
   input: GFM
-  # Jekyll 3 and GitHub Pages now only support rouge for syntax highlighting
   syntax_highlighter: rouge
   syntax_highlighter_opts:
-    # Use existing pygments syntax highlighting css
-    css_class: 'highlight'
+    css_class: "highlight"
 
-# Set the Sass partials directory, as we're using @imports
+# --- Sass
 sass:
-  style: :expanded # You might prefer to minify using :compressed
-
-# Use the following plug-ins
-gems:
-  - jekyll-sitemap # Create a sitemap using the official Jekyll sitemap gem
-  - jekyll-feed # Create an Atom feed using the official Jekyll feed gem
+  style: :expanded
+
+# --- Theme features
+search: true
+breadcrumbs: true
+
+# --- Author profile (used on posts and /about)
+author:
+  name: "Benefit"
+  avatar: "https://avatars.githubusercontent.com/u/8112969"
+  bio: "Generalist aiming to specialise but the curious nature is constantly challenging me to explore and seek out understanding new things."
+  links:
+    - label: "GitHub"
+      icon: "fab fa-github"
+      url: "https://github.com/Benefit00"
+    - label: "LinkedIn"
+      icon: "fab fa-linkedin"
+      url: "https://www.linkedin.com/in/ben--levin/"
+    - label: "X (Twitter)"
+      icon: "fab fa-x-twitter"
+      url: "https://x.com/B3Liev"
+    - label: "YouTube"
+      icon: "fab fa-youtube"
+      url: "https://www.youtube.com/@B3nefit"
+
+# --- Defaults so existing posts Just Work™
+defaults:
+  - scope:
+      path: ""
+      type: posts
+    values:
+      layout: single
+      author_profile: true
+      read_time: true
+      comments: false
+      share: true
+      related: true
+      show_date: true
+
+# --- Pagination (optional: uncomment to paginate your home blog list)
+paginate: 5
+paginate_path: "/page:num/"
+
+# --- Analytics & comments (fill in later if you use them)
+google_analytics:
+disqus:
 
-# Exclude these files from your production _site
+# --- Excludes (fine to keep from Jekyll Now)
 exclude:
   - Gemfile
   - Gemfile.lock
diff --git a/_data/navigation.yml b/_data/navigation.yml
new file mode 100644
index 0000000000000..1842ef3740de9
--- /dev/null
+++ b/_data/navigation.yml
@@ -0,0 +1,9 @@
+main:
+  - title: "Home"
+    url: /
+  - title: "About"
+    url: /about/
+  - title: "Categories"
+    url: /categories/
+  - title: "Tags"
+    url: /tags/
diff --git a/_data/ui-text.yml b/_data/ui-text.yml
new file mode 100644
index 0000000000000..8b137891791fe
--- /dev/null
+++ b/_data/ui-text.yml
@@ -0,0 +1 @@
+
diff --git a/_layouts/default.html b/_layouts/default.html
index b2939c0bc4483..364239ff6a53a 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -29,6 +29,7 @@ <h1 class="site-name"><a href="{{ site.baseurl }}/">{{ site.name }}</a></h1>
           <nav>
             <a href="{{ site.baseurl }}/">Blog</a>
             <a href="{{ site.baseurl }}/about">About</a>
+            <a href="{{ site.baseurl }}/game">Game</a>
           </nav>
         </header>
       </div>
@@ -47,5 +48,17 @@ <h1 class="site-name"><a href="{{ site.baseurl }}/">{{ site.name }}</a></h1>
     </div>
 
     {% include analytics.html %}
+<!--     <script>
+  document.addEventListener("DOMContentLoaded", function () {
+    const items = document.querySelectorAll(".accordion-item");
+
+    items.forEach(item => {
+      const title = item.querySelector(".accordion-title");
+      title.addEventListener("click", () => {
+        item.classList.toggle("active");
+      });
+    });
+  });
+</script> -->
   </body>
 </html>
diff --git a/_posts/2014-3-3-Hello-World.md b/_posts/2014-3-3-Hello-World.md
deleted file mode 100644
index d4665b6d18e9e..0000000000000
--- a/_posts/2014-3-3-Hello-World.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: post
-title: You're up and running!
----
-
-Next you can update your site name, avatar and other options using the _config.yml file in the root of your repository (shown below).
-
-![_config.yml]({{ site.baseurl }}/images/config.png)
-
-The easiest way to make your first post is to edit this one. Go into /_posts/ and update the Hello World markdown file. For more instructions head over to the [Jekyll Now repository](https://github.com/barryclark/jekyll-now) on GitHub.
\ No newline at end of file
diff --git a/_posts/2024-10-05-house-hijacking.md b/_posts/2024-10-05-house-hijacking.md
new file mode 100644
index 0000000000000..ac8afd44d8c8d
--- /dev/null
+++ b/_posts/2024-10-05-house-hijacking.md
@@ -0,0 +1,71 @@
+---
+layout: post
+title: "When the System Fails Its Citizens: My Story of Being Victimized in My Own Home"
+date: 2025-07-27
+description: "A firsthand account of property hijacking, corruption, and institutional failure in South Africa."
+tags: [South Africa, crime, corruption, property hijacking, victim rights]
+---
+
+> _"A home should be a place of safety and dignity—not a battlefield."_  
+
+South Africa is a country with promise, beauty, and resilience. But for many ordinary citizens like myself, it has also become a place where justice is selective and protection is not guaranteed—even in your own home.
+
+---
+
+## 🏠 My Home Was Hijacked
+
+What happened to me was not just criminal—it was a violation of everything a person holds sacred. My house, a space I worked hard to build and maintain, was taken over by individuals who had no right to be there. They were **foreign nationals**, involved in **coordinated criminal activity**, and I believe they were not acting alone.
+
+They **broke in**, **destroyed property**, and **refused to pay rent**. Fixtures were stolen—**taps, lights, mirrors**, all gone. Even utilities like **water and electricity** were illegally connected and used, leaving me to face financial and legal consequences.
+
+What’s worse? The people who were supposed to help me—**SAPS, local authorities, and housing enforcement units**—**did nothing**. Some were outright dismissive. Others, I suspect, were **on the payroll** of the very criminals they should have been prosecuting.
+
+---
+
+## 🚨 When Crime Is Protected
+
+We often talk about corruption in abstract terms. But when you **see it firsthand**, when you realize that **uniformed officers** or **municipal officials** are **protecting criminals** rather than victims, the betrayal cuts deep.
+
+I followed every legal avenue:
+- Opened cases with SAPS  
+- Contacted local councillors and city officials  
+- Tried to obtain eviction orders through the courts  
+- Reached out to civil society and victim advocacy groups  
+
+Each time, I was met with **delays, excuses, or silence**. I wasn’t just fighting criminals—I was **fighting the system**.
+
+---
+
+## 💔 The Impact
+
+What they stole wasn’t just physical property. They stole:
+- **My peace of mind**
+- **My trust in the law**
+- **My faith in state institutions**
+
+They left emotional and financial scars I still carry. I live in fear—fear that no matter what happens, **I’ll be on my own** again. As a law-abiding, tax-paying citizen, I expected the protection of the Constitution. Instead, I was left to fend for myself.
+
+---
+
+## 📢 A Call for Change
+
+I’m writing this not just to tell my story, but to speak for many others who are going through the same thing in silence.
+
+### What must change:
+- **Transparent oversight of SAPS and local law enforcement**
+- **Proper vetting of government officials and their ties to criminal syndicates**
+- **Fast-tracked legal protection for property owners and victims of hijacking**
+- **More public awareness of how property crime is enabled by state inaction**
+
+If we don’t talk about this, if we don’t hold our institutions accountable, then we are complicit in a cycle of abuse that’s eating away at the soul of this country.
+
+---
+
+## 🙏 To Fellow South Africans
+
+If you’ve been through something similar, I stand with you. You are not alone. Our voices may be ignored by officials, but we can still speak the truth—and in that, we reclaim some of the dignity that was taken from us.
+
+---
+
+**If you are a journalist, legal advisor, or advocacy group willing to investigate or amplify this issue, please reach out.** South Africans deserve better—and it starts with stories like ours being heard.
+
diff --git a/_posts/2025-05-06-how-to-learn-anything.md b/_posts/2025-05-06-how-to-learn-anything.md
new file mode 100644
index 0000000000000..1d2aa1ed178de
--- /dev/null
+++ b/_posts/2025-05-06-how-to-learn-anything.md
@@ -0,0 +1,105 @@
+---
+layout: post
+title: How to learn anything in general!
+date:   2025-07-10 10:00:00 +0000
+categories: learning productivity
+tags: [curiosity, strategy, growth]
+---
+
+<p align="center">
+  <img src="/images/assets/learning.png" alt="Learning is a Lifelong Journey" style="max-width: 600px; width: 30%; height: auto;">
+</p>
+
+Learning is a lifelong journey, and curiosity is your best compass...
+
+## Step 1: Embrace Questions
+
+Ask "why" and "how" relentlessly and of course diligently, show genuine interest and willingness to listen, learn and responsd with input that is accurate and clarifies rather than convoluted, big worded babble.
+
+Don’t just accept things as they are—wonder about them. Ask “Why?” to understand root causes. Ask “How?” to uncover processes and connections. Ask “What if?” to stretch your imagination beyond the boundaries of what’s known. Every question opens a door to a new perspective.
+
+But curiosity is more than just asking. It’s about how you ask—with sincerity, attentiveness, and a desire to grow. When you pose a question, do it not just to sound smart or challenge others, but because you truly care about the answer. Because you want to understand something better.
+
+And when you listen to responses, listen fully. Absorb what’s being said. Let it challenge your assumptions, and follow up with more questions if needed. Great learners don’t just collect facts—they engage with them. They respond with clarity, accuracy, and a drive to simplify, not complicate. Leave the jargon behind; seek explanations that enlighten, not obscure.
+
+This means welcoming input that is accurate, concise, and meaningful. It means choosing clarity over cleverness. And it means recognizing that every conversation is an opportunity to learn—not to impress, but to grow.
+
+---
+
+Keep Going
+
+Curiosity doesn’t stop after one question—or even a hundred. It fuels momentum. It sharpens your ability to think, reflect, and act. So stay curious. Embrace your role as a lifelong learner. The more you ask, the more you see. And the more you see, the farther you’ll go.
+
+## Step 2: Practice Beats Passive Learning
+
+Watching content—tutorials, lectures, how-to videos—can be inspiring and informative. It gives us a sense of understanding and often feels like progress. But here’s the truth: watching alone doesn’t make you proficient.
+
+You can’t become a chef by watching cooking shows. You won’t become a coder by watching hours of programming videos. And you certainly can’t master a musical instrument by just listening to others play. You must practice. You must try.
+
+That means rolling up your sleeves and attempting the task yourself. It means struggling through it—fumbling, failing, learning, fixing, and trying again. Mistakes aren’t setbacks—they’re signposts. They show you where you need to focus, and they shape your growth far more than flawless theory ever could.
+
+Skill is not downloaded. It’s built.
+
+It’s built through action, repetition, reflection, and adjustment. Watching can guide you. It can introduce you to techniques and possibilities. But only doing transforms knowledge into skill.
+
+So next time you feel stuck in the loop of passive learning, stop and ask:
+Have I actually done this yet? Have I failed at it? Have I tried to fix it?
+
+If not, start now.
+Open the code editor.
+Pick up the tool.
+Write the draft.
+Make the call.
+Take the shot.
+
+Whatever your craft or goal is—start practicing. Real learning lives in the doing.
+
+## Step 3: Take Smart Notes That Stay Useful
+
+Learning isn’t just about absorbing information in the moment. It’s about being able to recall and apply that information later—sometimes weeks, months, or even years down the line. That’s where good note-taking becomes a superpower.
+
+But not all notes are created equal.
+
+It’s easy to write down everything and still end up with a page full of clutter that makes no sense when you come back to it. The goal isn’t to copy—it’s to capture meaning. To jot down the essence of what matters, in a way your future self can understand, even after the topic has gone cold.
+
+Smart notes are:
+	•	Brief, not bloated – Summarize ideas in your own words. Aim for clarity, not completeness.
+	•	Contextual – Include cues that remind you why the idea mattered or how you might use it.
+	•	Searchable – Use keywords or headings so you can easily find them later.
+	•	Personalized – Highlight what stood out to you, not just what was presented.
+
+The best test? A week from now, can you glance at your notes and still understand what they mean—and why they mattered?
+
+If not, tweak your approach. Remember: Notes aren’t just for today. They’re for future moments when inspiration strikes, when a challenge arises, or when you want to revisit something you once knew but forgot.
+
+Taking good notes is how you build your own knowledge base—one that stays relevant long after the learning moment has passed.
+
+## Step 4: Reflect and Refine
+
+Learning doesn’t stick just because you practiced or took notes—it sticks when you take time to reflect.
+
+Reflection is the pause between action and improvement. It’s when you look back at what you tried, how it went, and what you’d do differently next time. It’s how you turn scattered experiences into structured insight.
+
+After every session—whether it’s studying, practicing, or working on a real project—ask yourself:
+	•	What did I actually learn?
+	•	Where did I struggle, and why?
+	•	What would I do differently next time?
+	•	What questions still remain?
+
+You don’t need a full journal entry every time—just a few thoughts captured in your notes or mind. This small habit adds compound value: you deepen your understanding, speed up your progress, and stay aware of what’s working (and what’s not).
+
+Refinement is where real growth lives.
+
+Don’t be afraid to revise your approach. Tweak your process. Learn from others. Try a new method. Reflection isn’t about being perfect—it’s about being better, more aware, and more intentional with each iteration.
+
+⸻
+
+To Sum It Up: The Lifelong Learner’s Loop
+	1.	Embrace Questions – Curiosity is your starting point. Ask boldly, listen fully.
+	2.	Practice Relentlessly – Watching isn’t doing. Skill is built by trying, failing, and refining.
+	3.	Take Smart Notes – Keep it short, clear, and useful for your future self.
+	4.	Reflect and Refine – Learning deepens when you pause to understand and improve.
+
+⸻
+
+Curiosity gets you started, but habits like these keep you going—and growing.
diff --git a/_posts/2025-07-10-importance-of-marketing-seo-and-other-awareness.md b/_posts/2025-07-10-importance-of-marketing-seo-and-other-awareness.md
new file mode 100644
index 0000000000000..18aa49e9bebd8
--- /dev/null
+++ b/_posts/2025-07-10-importance-of-marketing-seo-and-other-awareness.md
@@ -0,0 +1,63 @@
+---
+layout: post
+title: "Website Marketing Essentials"
+date: 2025-07-27
+description: "A guide to optimizing your site for visibility and search performance with SEO best practices, Google Analytics, and essential web files."
+tags: [SEO, marketing, meta tags, Google Analytics, Jekyll, GitHub Pages]
+---
+
+> Good SEO isn't just about traffic—it's about *visibility*, *structure*, and *strategy*.
+
+If you're building a personal blog or website with GitHub Pages and Jekyll, you might wonder how to make your site discoverable and useful to both users and search engines. In this post, we'll cover practical ways to enhance your site's **marketing readiness** through:
+
+- SEO optimization
+- Meta tags
+- Keywords
+- Google Analytics
+- Core files like `robots.txt`, `sitemap.xml`, and `llms.txt`
+
+---
+
+## 🚀 SEO Optimization Basics
+
+Search Engine Optimization (SEO) helps search engines understand what your site is about and rank it accordingly.
+
+### ✅ Use Relevant Keywords
+
+1. Research terms your audience might search for using tools like:
+   - [Google Keyword Planner](https://ads.google.com/home/tools/keyword-planner/)
+   - [Ubersuggest](https://neilpatel.com/ubersuggest/)
+   - [Ahrefs](https://ahrefs.com/keywords-explorer)
+
+2. Naturally integrate these keywords in:
+   - Titles (`<h1>`)
+   - Subheadings
+   - Meta descriptions
+   - URLs (slug)
+   - Image `alt` tags
+
+---
+
+## 🏷️ Meta Tags for SEO
+
+Meta tags improve how your pages appear in search results and when shared on social media.
+
+Here’s an example of meta tags in your Jekyll layout (e.g., `_includes/head.html`):
+
+```html
+<meta name="description" content="{{ page.description | default: site.description }}">
+<meta name="keywords" content="SEO, marketing, Jekyll, meta tags, GitHub Pages">
+<meta name="author" content="Your Name">
+
+<!-- Open Graph for social media -->
+<meta property="og:title" content="{{ page.title }}">
+<meta property="og:description" content="{{ page.description }}">
+<meta property="og:type" content="website">
+<meta property="og:url" content="{{ site.url }}{{ page.url }}">
+<meta property="og:image" content="{{ site.url }}/assets/images/seo-thumbnail.png">
+
+<!-- Twitter Card -->
+<meta name="twitter:card" content="summary_large_image">
+<meta name="twitter:title" content="{{ page.title }}">
+<meta name="twitter:description" content="{{ page.description }}">
+```
diff --git a/_posts/2025-09-14-social-awareness-regarding-cyber-security b/_posts/2025-09-14-social-awareness-regarding-cyber-security
new file mode 100644
index 0000000000000..aefccaba7a8ad
--- /dev/null
+++ b/_posts/2025-09-14-social-awareness-regarding-cyber-security
@@ -0,0 +1,21 @@
+---
+layout: post
+title: "Social Awareness Regarding cyber Security"
+date: 2025-09-14
+description: "My book and the journey of writing it. Socail awareness in a broken system."
+tags: [self-publish, book writing, cyber crime, social awareness, meta tags, Google Analytics, Jekyll, GitHub Pages]
+---
+
+*Introduction*
+
+I am writing this book because cybersecurity is no longer just a technical problem—it is a human one. We live in a world where our personal data, identities, and daily interactions are increasingly shaped by the digital space. Yet while we invest in stronger passwords, advanced software, and complex firewalls, the greatest vulnerabilities often come down to human awareness.
+
+Social awareness in the realm of cybersecurity means understanding not only how we interact with technology, but also how we interact with each other through it. Every email we open, every link we click, and every piece of information we share can ripple far beyond what we see. Hackers and malicious actors exploit habits, trust, and even curiosity. That is why building awareness isn’t just about learning to spot a phishing email—it’s about cultivating a mindset of attentiveness, respect, and responsibility in the digital spaces we share.
+
+This book is my attempt to bridge the gap between technical defenses and human behavior. I have seen how easily a simple oversight—an unverified link, a careless download, a misjudged trust—can open the door to serious breaches. But I have also seen the opposite: how a culture of awareness, where people look out for each other and act with caution, can dramatically reduce risks. Just as in face-to-face life, where being socially aware helps us build stronger, more empathetic relationships, in cyberspace it helps us create safer and more resilient communities.
+
+I believe that when we bring the principles of social awareness into cybersecurity, we start to shift the conversation. Instead of focusing only on threats and fear, we begin to see security as something shared—a responsibility and a value we uphold together. That perspective allows us to move beyond individual defense and into collective protection.
+
+This book will not attempt to overwhelm you with jargon or highly technical instructions. Instead, it will explore the human side of cybersecurity: the habits, choices, and mindsets that matter most. My hope is to give readers the tools to recognize risks, but more importantly, to understand that awareness is an ongoing practice—one that strengthens both our digital lives and our relationships with each other.
+
+In the end, cybersecurity is not just about protecting machines and data. It is about protecting people, and the trust that connects us. If this book helps even a few readers pause before clicking, question before sharing, or support someone else in staying safe online, then it will have fulfilled its purpose.
diff --git a/_posts/2025-10-10-entra-tenant-migration.md b/_posts/2025-10-10-entra-tenant-migration.md
new file mode 100644
index 0000000000000..3b777a8823eec
--- /dev/null
+++ b/_posts/2025-10-10-entra-tenant-migration.md
@@ -0,0 +1,32 @@
+---
+layout: post
+title: "Migrating Two Tenants Into One"
+date: 2025-10-10
+description: "Oops, created two tenants and split responsability, now to fix this and migrate the second tenant into the first and then delete the second tenant."
+tags: [Azure, Microsoft, Entra, Migration]
+--- 
+
+South Africa is a country with promise, beauty, and resilience. But for many ordinary citizens like myself, it has also become a place where justice is selective and protection is not guaranteed—even in your own home.
+
+---
+
+## Powershell setup
+
+Microsoft has deprecated AzureAD_Connect to interact with Azure. It has been replaced with Microsoft Graph.
+
+The following are steps to get powershell setup with the requirements to use Microsoft Graph to login and ready for the migration. 
+
+// Allow installing to your user scope
+Set-ExecutionPolicy -Scope CurrentUser RemoteSigned -Force -v
+
+// Microsoft Graph (directory, users, licenses)
+Install-Module Microsoft.Graph -Scope CurrentUser -Force -v
+
+// Exchange Online (mailboxes, EXO migration)
+Install-Module ExchangeOnlineManagement -Scope CurrentUser -Force -v
+
+// Optional: SharePoint/OneDrive admin (if you’ll inventory SPO/OD)
+Install-Module Microsoft.Online.SharePoint.PowerShell -Scope CurrentUser -Force -v
+
+---
+
diff --git a/about.md b/about.md
index bc21f5731bf4b..e380aba8eb68a 100644
--- a/about.md
+++ b/about.md
@@ -1,10 +1,11 @@
 ---
-layout: page
-title: About
+layout: single
+title: "About"
 permalink: /about/
+author_profile: true
 ---
 
-Some information about you!
+Hi my name is Ben AKA Benefit.
 
 ### More Information
 
@@ -12,4 +13,4 @@ A place to include any other types of information that you'd like to include abo
 
 ### Contact me
 
-[email@domain.com](mailto:email@domain.com)
\ No newline at end of file
+[@.com](mailto:email@domain.com)
diff --git a/categories.md b/categories.md
new file mode 100644
index 0000000000000..06701213e64c2
--- /dev/null
+++ b/categories.md
@@ -0,0 +1,6 @@
+---
+layout: categories
+title: "Posts by Category"
+permalink: /categories/
+author_profile: true
+---
diff --git a/game/assets/README.md b/game/assets/README.md
new file mode 100644
index 0000000000000..a89ef66eb2d4d
--- /dev/null
+++ b/game/assets/README.md
@@ -0,0 +1 @@
+Icons, images, and other effect files will be stored in this folder.
diff --git a/game/assets/bird1.png b/game/assets/bird1.png
new file mode 100644
index 0000000000000..f54a7536739bc
Binary files /dev/null and b/game/assets/bird1.png differ
diff --git a/game/assets/bird2.png b/game/assets/bird2.png
new file mode 100644
index 0000000000000..506fbcd377fad
Binary files /dev/null and b/game/assets/bird2.png differ
diff --git a/game/assets/bird3.png b/game/assets/bird3.png
new file mode 100644
index 0000000000000..b1129ff9ac5da
Binary files /dev/null and b/game/assets/bird3.png differ
diff --git a/game/assets/cat.png b/game/assets/cat.png
new file mode 100644
index 0000000000000..4e870cc07a138
Binary files /dev/null and b/game/assets/cat.png differ
diff --git a/game/assets/dog.png b/game/assets/dog.png
new file mode 100644
index 0000000000000..0633afa519fad
Binary files /dev/null and b/game/assets/dog.png differ
diff --git a/game/assets/dog2.png b/game/assets/dog2.png
new file mode 100644
index 0000000000000..ed5d3ea9683ca
Binary files /dev/null and b/game/assets/dog2.png differ
diff --git a/game/assets/mosquito.png b/game/assets/mosquito.png
new file mode 100644
index 0000000000000..811a20a73a771
Binary files /dev/null and b/game/assets/mosquito.png differ
diff --git a/game/assets/princess.png b/game/assets/princess.png
new file mode 100644
index 0000000000000..011335d19d34d
Binary files /dev/null and b/game/assets/princess.png differ
diff --git a/game/assets/soldier.png b/game/assets/soldier.png
new file mode 100644
index 0000000000000..640c282fd85b0
Binary files /dev/null and b/game/assets/soldier.png differ
diff --git a/game/cyber-defense.html b/game/cyber-defense.html
new file mode 100644
index 0000000000000..33ff32cf99538
--- /dev/null
+++ b/game/cyber-defense.html
@@ -0,0 +1,589 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>Cyber Defense - Internet Safety Game</title>
+  <style>
+    * { margin: 0; padding: 0; box-sizing: border-box; }
+    body {
+      overflow: hidden;
+      background: linear-gradient(135deg, #1e3c72 0%, #2a5298 100%);
+      font-family: 'Arial', sans-serif;
+    }
+    canvas {
+      display: block;
+      background: linear-gradient(180deg, #0a0e27 0%, #1a1f3a 100%);
+      box-shadow: 0 0 30px rgba(0, 200, 255, 0.3);
+      margin: 0 auto;
+    }
+    #gameInfo {
+      position: absolute;
+      top: 20px;
+      left: 50%;
+      transform: translateX(-50%);
+      color: white;
+      text-align: center;
+      background: rgba(0, 0, 0, 0.7);
+      padding: 20px;
+      border-radius: 10px;
+      max-width: 600px;
+      z-index: 10;
+    }
+    #gameInfo h1 {
+      color: #00ff88;
+      margin-bottom: 10px;
+      text-shadow: 0 0 10px #00ff88;
+    }
+    #gameInfo button {
+      margin-top: 10px;
+      padding: 10px 20px;
+      font-size: 16px;
+      background: #00ff88;
+      border: none;
+      border-radius: 5px;
+      cursor: pointer;
+      font-weight: bold;
+      transition: all 0.3s;
+    }
+    #gameInfo button:hover {
+      background: #00cc6a;
+      transform: scale(1.05);
+    }
+    .hidden { display: none; }
+
+    /* Touch Controls */
+    #touchControls {
+      position: fixed;
+      bottom: 0;
+      left: 0;
+      right: 0;
+      height: 150px;
+      display: none;
+      z-index: 100;
+    }
+    @media (hover: none) and (pointer: coarse) {
+      #touchControls { display: flex; }
+    }
+    .touch-button {
+      flex: 1;
+      background: rgba(0, 255, 136, 0.3);
+      border: 3px solid rgba(0, 255, 136, 0.8);
+      border-radius: 10px;
+      margin: 10px;
+      font-size: 40px;
+      color: white;
+      display: flex;
+      align-items: center;
+      justify-content: center;
+      user-select: none;
+      -webkit-user-select: none;
+      touch-action: none;
+      font-weight: bold;
+      text-shadow: 0 0 10px rgba(0, 255, 136, 1);
+      transition: all 0.1s;
+    }
+    .touch-button:active {
+      background: rgba(0, 255, 136, 0.6);
+      transform: scale(0.95);
+    }
+    #shootButton {
+      background: rgba(255, 255, 0, 0.3);
+      border-color: rgba(255, 255, 0, 0.8);
+      text-shadow: 0 0 10px rgba(255, 255, 0, 1);
+    }
+    #shootButton:active {
+      background: rgba(255, 255, 0, 0.6);
+    }
+  </style>
+</head>
+<body>
+<div id="gameInfo">
+  <h1>🛡️ Cyber Defense</h1>
+  <p><strong>Mission:</strong> Protect the internet!</p>
+  <p>🎯 <strong>Collect</strong> green items (good security practices)</p>
+  <p>💥 <strong>Shoot</strong> red items (scams and threats)</p>
+  <p><br><strong>Desktop:</strong> ⬅️ ➡️ Move | SPACE Shoot</p>
+  <p><strong>Mobile:</strong> Use on-screen buttons</p>
+  <button onclick="startGame()">Start Game</button>
+</div>
+<canvas id="gameCanvas"></canvas>
+
+<!-- Touch Controls (visible on mobile/tablets) -->
+<div id="touchControls">
+  <div id="leftButton" class="touch-button">⬅️</div>
+  <div id="shootButton" class="touch-button">🔫</div>
+  <div id="rightButton" class="touch-button">➡️</div>
+</div>
+<script>
+const canvas = document.getElementById("gameCanvas");
+const ctx = canvas.getContext("2d");
+canvas.width = window.innerWidth;
+canvas.height = window.innerHeight;
+
+let gameStarted = false;
+let player = {
+  x: canvas.width / 2 - 25,
+  y: canvas.height - 80,
+  width: 50,
+  height: 50,
+  speed: 7,
+  color: "#00ff88"
+};
+
+let keys = {};
+let bullets = [];
+let fallingObjects = [];
+let particles = [];
+let score = 0;
+let lives = 5;
+let level = 1;
+let messageQueue = [];
+let currentMessage = null;
+let messageTimer = 0;
+
+// Good items (collect them!)
+const goodItems = [
+  { name: "🔒 HTTPS", tip: "Always check for HTTPS in URLs!", points: 15, color: "#00ff88" },
+  { name: "🔐 2FA", tip: "Two-Factor Authentication adds extra security!", points: 15, color: "#00ff88" },
+  { name: "🔑 Strong Password", tip: "Use unique, complex passwords for each account!", points: 15, color: "#00ff88" },
+  { name: "🛡️ Antivirus", tip: "Keep your antivirus updated!", points: 15, color: "#00ff88" },
+  { name: "📚 Security Training", tip: "Stay educated about cyber threats!", points: 15, color: "#00ff88" },
+  { name: "✅ Verified", tip: "Look for verification badges on social media!", points: 15, color: "#00ff88" },
+  { name: "🔄 Update", tip: "Always install security updates promptly!", points: 15, color: "#00ff88" }
+];
+
+// Bad items (shoot them!)
+const badItems = [
+  { name: "📧 Phishing", warning: "Don't click suspicious email links!", points: 10, color: "#ff3366" },
+  { name: "🦠 Virus", warning: "Malware can steal your data!", points: 10, color: "#ff3366" },
+  { name: "💳 Scam", warning: "Never share card details via email!", points: 10, color: "#ff3366" },
+  { name: "🔗 Fake Link", warning: "Hover over links before clicking!", points: 10, color: "#ff3366" },
+  { name: "📞 Vishing", warning: "Banks won't call asking for passwords!", points: 10, color: "#ff3366" },
+  { name: "🎣 Social Engineering", warning: "Verify requests for sensitive info!", points: 10, color: "#ff3366" },
+  { name: "💰 Nigerian Prince", warning: "If it's too good to be true, it is!", points: 10, color: "#ff3366" },
+  { name: "🔓 Unsecured WiFi", warning: "Public WiFi can expose your data!", points: 10, color: "#ff3366" }
+];
+
+function showMessage(text, isGood) {
+  messageQueue.push({ text, isGood, timer: 120 });
+}
+
+function createObject() {
+  if (!gameStarted) return;
+
+  const isGood = Math.random() > 0.5;
+  const items = isGood ? goodItems : badItems;
+  const item = items[Math.floor(Math.random() * items.length)];
+
+  fallingObjects.push({
+    x: Math.random() * (canvas.width - 60) + 30,
+    y: -40,
+    width: 40,
+    height: 40,
+    speed: 1.5 + (level * 0.3),
+    isGood: isGood,
+    item: item,
+    rotation: Math.random() * Math.PI * 2
+  });
+}
+
+function createBullet() {
+  bullets.push({
+    x: player.x + player.width / 2 - 3,
+    y: player.y,
+    width: 6,
+    height: 15,
+    speed: 10
+  });
+}
+
+function createParticles(x, y, color, count = 8) {
+  for (let i = 0; i < count; i++) {
+    particles.push({
+      x: x,
+      y: y,
+      vx: (Math.random() - 0.5) * 6,
+      vy: (Math.random() - 0.5) * 6,
+      life: 30,
+      color: color,
+      size: Math.random() * 4 + 2
+    });
+  }
+}
+
+function drawPlayer() {
+  // Draw shield glow
+  ctx.shadowBlur = 20;
+  ctx.shadowColor = player.color;
+
+  // Draw player (shield icon)
+  ctx.fillStyle = player.color;
+  ctx.beginPath();
+  ctx.moveTo(player.x + player.width / 2, player.y);
+  ctx.lineTo(player.x, player.y + player.height * 0.3);
+  ctx.lineTo(player.x, player.y + player.height * 0.7);
+  ctx.quadraticCurveTo(
+    player.x + player.width / 2, player.y + player.height,
+    player.x + player.width, player.y + player.height * 0.7
+  );
+  ctx.lineTo(player.x + player.width, player.y + player.height * 0.3);
+  ctx.closePath();
+  ctx.fill();
+
+  ctx.shadowBlur = 0;
+}
+
+function drawBullets() {
+  ctx.fillStyle = "#ffff00";
+  ctx.shadowBlur = 10;
+  ctx.shadowColor = "#ffff00";
+  for (let bullet of bullets) {
+    ctx.fillRect(bullet.x, bullet.y, bullet.width, bullet.height);
+  }
+  ctx.shadowBlur = 0;
+}
+
+function drawObjects() {
+  for (let obj of fallingObjects) {
+    ctx.save();
+    ctx.translate(obj.x + obj.width / 2, obj.y + obj.height / 2);
+    ctx.rotate(obj.rotation);
+
+    // Draw glow
+    ctx.shadowBlur = 15;
+    ctx.shadowColor = obj.item.color;
+
+    // Draw background circle
+    ctx.fillStyle = obj.item.color;
+    ctx.beginPath();
+    ctx.arc(0, 0, obj.width / 2, 0, Math.PI * 2);
+    ctx.fill();
+
+    // Draw emoji/text
+    ctx.shadowBlur = 0;
+    ctx.fillStyle = "white";
+    ctx.font = "24px Arial";
+    ctx.textAlign = "center";
+    ctx.textBaseline = "middle";
+    ctx.fillText(obj.item.name.split(' ')[0], 0, 0);
+
+    ctx.restore();
+  }
+}
+
+function drawParticles() {
+  for (let p of particles) {
+    ctx.fillStyle = p.color;
+    ctx.globalAlpha = p.life / 30;
+    ctx.fillRect(p.x, p.y, p.size, p.size);
+  }
+  ctx.globalAlpha = 1;
+}
+
+function updateBullets() {
+  for (let i = bullets.length - 1; i >= 0; i--) {
+    bullets[i].y -= bullets[i].speed;
+    if (bullets[i].y < 0) bullets.splice(i, 1);
+  }
+}
+
+function updateObjects() {
+  for (let i = fallingObjects.length - 1; i >= 0; i--) {
+    let obj = fallingObjects[i];
+    obj.y += obj.speed;
+    obj.rotation += 0.02;
+
+    // Check collision with bullets
+    for (let j = bullets.length - 1; j >= 0; j--) {
+      let bullet = bullets[j];
+      if (
+        bullet.x < obj.x + obj.width &&
+        bullet.x + bullet.width > obj.x &&
+        bullet.y < obj.y + obj.height &&
+        bullet.y + bullet.height > obj.y
+      ) {
+        bullets.splice(j, 1);
+
+        if (obj.isGood) {
+          // Shot a good item - penalty!
+          lives--;
+          showMessage("❌ Don't shoot security tools!", false);
+          createParticles(obj.x + obj.width / 2, obj.y + obj.height / 2, "#ff3366", 12);
+        } else {
+          // Shot a bad item - good!
+          score += obj.item.points;
+          showMessage("✅ " + obj.item.warning, true);
+          createParticles(obj.x + obj.width / 2, obj.y + obj.height / 2, "#ffff00", 12);
+        }
+        fallingObjects.splice(i, 1);
+        break;
+      }
+    }
+
+    // Check collision with player
+    if (obj &&
+        obj.y + obj.height >= player.y &&
+        obj.x < player.x + player.width &&
+        obj.x + obj.width > player.x) {
+
+      if (obj.isGood) {
+        // Collected good item - reward!
+        score += obj.item.points;
+        showMessage("💚 " + obj.item.tip, true);
+        createParticles(obj.x + obj.width / 2, obj.y + obj.height / 2, "#00ff88", 12);
+      } else {
+        // Collected bad item - penalty!
+        lives--;
+        showMessage("💔 " + obj.item.warning, false);
+        createParticles(obj.x + obj.width / 2, obj.y + obj.height / 2, "#ff3366", 12);
+      }
+      fallingObjects.splice(i, 1);
+    }
+
+    // Fell off screen
+    if (obj && obj.y > canvas.height) {
+      if (!obj.isGood) {
+        // Missed a bad item
+        lives--;
+        showMessage("⚠️ Threat escaped!", false);
+      }
+      fallingObjects.splice(i, 1);
+    }
+  }
+
+  // Level up
+  if (score >= level * 100) {
+    level++;
+    showMessage("🎊 Level " + level + " - Threats increasing!", true);
+  }
+}
+
+function updateParticles() {
+  for (let i = particles.length - 1; i >= 0; i--) {
+    particles[i].x += particles[i].vx;
+    particles[i].y += particles[i].vy;
+    particles[i].life--;
+    if (particles[i].life <= 0) particles.splice(i, 1);
+  }
+}
+
+function drawUI() {
+  // Score and stats
+  ctx.fillStyle = "rgba(0, 0, 0, 0.5)";
+  ctx.fillRect(10, 10, 250, 100);
+
+  ctx.fillStyle = "#00ff88";
+  ctx.font = "24px Arial";
+  ctx.fillText("Score: " + score, 20, 40);
+
+  // Hearts for lives
+  ctx.fillStyle = "#ff3366";
+  ctx.font = "20px Arial";
+  let heartsText = "❤️".repeat(Math.max(0, lives));
+  ctx.fillText("Lives: " + heartsText, 20, 70);
+
+  ctx.fillStyle = "#ffff00";
+  ctx.fillText("Level: " + level, 20, 100);
+
+  // Display messages
+  if (messageQueue.length > 0 && !currentMessage) {
+    currentMessage = messageQueue.shift();
+  }
+
+  if (currentMessage) {
+    currentMessage.timer--;
+    const alpha = Math.min(1, currentMessage.timer / 30);
+
+    ctx.globalAlpha = alpha;
+    ctx.fillStyle = currentMessage.isGood ? "rgba(0, 255, 136, 0.9)" : "rgba(255, 51, 102, 0.9)";
+    ctx.fillRect(canvas.width / 2 - 250, 120, 500, 60);
+
+    ctx.fillStyle = "white";
+    ctx.font = "18px Arial";
+    ctx.textAlign = "center";
+    ctx.fillText(currentMessage.text, canvas.width / 2, 155);
+    ctx.textAlign = "left";
+    ctx.globalAlpha = 1;
+
+    if (currentMessage.timer <= 0) currentMessage = null;
+  }
+
+  // Game over
+  if (lives <= 0) {
+    ctx.fillStyle = "rgba(0, 0, 0, 0.8)";
+    ctx.fillRect(0, 0, canvas.width, canvas.height);
+
+    ctx.fillStyle = "#ff3366";
+    ctx.font = "60px Arial";
+    ctx.textAlign = "center";
+    ctx.fillText("GAME OVER", canvas.width / 2, canvas.height / 2 - 50);
+
+    ctx.fillStyle = "white";
+    ctx.font = "30px Arial";
+    ctx.fillText("Final Score: " + score, canvas.width / 2, canvas.height / 2 + 20);
+    ctx.fillText("Tap/Click to play again", canvas.width / 2, canvas.height / 2 + 70);
+    ctx.textAlign = "left";
+
+    // Add click/touch to restart
+    canvas.style.cursor = "pointer";
+  }
+}
+
+function handlePlayerMovement() {
+  if (keys["ArrowLeft"] && player.x > 0) player.x -= player.speed;
+  if (keys["ArrowRight"] && player.x + player.width < canvas.width) player.x += player.speed;
+}
+
+function gameLoop() {
+  if (!gameStarted) return;
+
+  ctx.clearRect(0, 0, canvas.width, canvas.height);
+
+  // Draw stars background
+  ctx.fillStyle = "rgba(255, 255, 255, 0.1)";
+  for (let i = 0; i < 50; i++) {
+    const x = (i * 137.5) % canvas.width;
+    const y = (i * 217.3 + Date.now() * 0.05) % canvas.height;
+    ctx.fillRect(x, y, 2, 2);
+  }
+
+  drawParticles();
+  drawPlayer();
+  drawBullets();
+  drawObjects();
+  drawUI();
+
+  if (lives > 0) {
+    updateBullets();
+    updateObjects();
+    updateParticles();
+    handlePlayerMovement();
+  }
+
+  requestAnimationFrame(gameLoop);
+}
+
+// Keyboard controls
+window.addEventListener("keydown", (e) => {
+  if (!gameStarted) return;
+  keys[e.key] = true;
+  if (e.code === "Space" && lives > 0) {
+    e.preventDefault();
+    createBullet();
+  }
+});
+
+window.addEventListener("keyup", (e) => {
+  keys[e.key] = false;
+});
+
+// Touch controls
+const leftButton = document.getElementById("leftButton");
+const rightButton = document.getElementById("rightButton");
+const shootButton = document.getElementById("shootButton");
+
+// Prevent default touch behaviors
+[leftButton, rightButton, shootButton].forEach(button => {
+  button.addEventListener("touchstart", (e) => {
+    e.preventDefault();
+  });
+});
+
+// Left button
+leftButton.addEventListener("touchstart", (e) => {
+  e.preventDefault();
+  if (gameStarted) keys["ArrowLeft"] = true;
+});
+leftButton.addEventListener("touchend", (e) => {
+  e.preventDefault();
+  keys["ArrowLeft"] = false;
+});
+leftButton.addEventListener("touchcancel", (e) => {
+  keys["ArrowLeft"] = false;
+});
+
+// Right button
+rightButton.addEventListener("touchstart", (e) => {
+  e.preventDefault();
+  if (gameStarted) keys["ArrowRight"] = true;
+});
+rightButton.addEventListener("touchend", (e) => {
+  e.preventDefault();
+  keys["ArrowRight"] = false;
+});
+rightButton.addEventListener("touchcancel", (e) => {
+  keys["ArrowRight"] = false;
+});
+
+// Shoot button
+shootButton.addEventListener("touchstart", (e) => {
+  e.preventDefault();
+  if (gameStarted && lives > 0) {
+    createBullet();
+  }
+});
+
+// Also support touch/swipe on the canvas for movement
+let touchStartX = null;
+canvas.addEventListener("touchstart", (e) => {
+  if (!gameStarted || e.touches.length === 0) return;
+  touchStartX = e.touches[0].clientX;
+});
+
+canvas.addEventListener("touchmove", (e) => {
+  if (!gameStarted || touchStartX === null || e.touches.length === 0) return;
+  e.preventDefault();
+
+  const touchX = e.touches[0].clientX;
+  const deltaX = touchX - touchStartX;
+
+  // Move player based on touch position
+  if (Math.abs(deltaX) > 5) {
+    const targetX = player.x + deltaX * 0.5;
+    if (targetX >= 0 && targetX + player.width <= canvas.width) {
+      player.x = targetX;
+    }
+  }
+
+  touchStartX = touchX;
+});
+
+canvas.addEventListener("touchend", (e) => {
+  // Restart game on game over
+  if (lives <= 0) {
+    e.preventDefault();
+    location.reload();
+    return;
+  }
+  touchStartX = null;
+});
+
+// Tap to shoot on canvas
+canvas.addEventListener("touchstart", (e) => {
+  if (!gameStarted || lives <= 0) return;
+  // Only shoot if it's a quick tap (not a drag)
+  setTimeout(() => {
+    if (touchStartX !== null && Math.abs(e.touches[0].clientX - touchStartX) < 10) {
+      createBullet();
+    }
+  }, 100);
+});
+
+// Restart game on game over (desktop)
+canvas.addEventListener("click", () => {
+  if (lives <= 0) {
+    location.reload();
+  }
+});
+
+function startGame() {
+  gameStarted = true;
+  document.getElementById("gameInfo").classList.add("hidden");
+  setInterval(createObject, 1500);
+  showMessage("🛡️ Defend against cyber threats!", true);
+  gameLoop();
+}
+</script>
+</body>
+</html>
diff --git a/game/falling-game.html b/game/falling-game.html
new file mode 100644
index 0000000000000..848f580dc605b
--- /dev/null
+++ b/game/falling-game.html
@@ -0,0 +1,875 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>Cyber Incident Response Simulator</title>
+  <style>
+    * { margin: 0; padding: 0; box-sizing: border-box; }
+    body {
+      font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
+      background: linear-gradient(135deg, #2d3436 0%, #000000 100%);
+      color: white;
+      min-height: 100vh;
+      overflow-x: hidden;
+    }
+    .container {
+      max-width: 900px;
+      margin: 0 auto;
+      padding: 20px;
+    }
+
+    /* Welcome Screen */
+    #welcomeScreen {
+      text-align: center;
+      padding: 50px 20px;
+    }
+    #welcomeScreen h1 {
+      font-size: 3em;
+      color: #00ff88;
+      margin-bottom: 20px;
+      text-shadow: 0 0 20px rgba(0, 255, 136, 0.5);
+    }
+    #welcomeScreen .subtitle {
+      font-size: 1.3em;
+      color: #dfe6e9;
+      margin-bottom: 30px;
+    }
+    .scenario-grid {
+      display: grid;
+      grid-template-columns: repeat(auto-fit, minmax(250px, 1fr));
+      gap: 20px;
+      margin-top: 40px;
+    }
+    .scenario-card {
+      background: linear-gradient(135deg, #2d3436 0%, #1a1f2e 100%);
+      border: 2px solid #00ff88;
+      border-radius: 15px;
+      padding: 30px;
+      cursor: pointer;
+      transition: all 0.3s;
+      box-shadow: 0 5px 15px rgba(0, 0, 0, 0.3);
+    }
+    .scenario-card:hover {
+      transform: translateY(-10px);
+      box-shadow: 0 10px 30px rgba(0, 255, 136, 0.3);
+      border-color: #00ffff;
+    }
+    .scenario-card .icon {
+      font-size: 3em;
+      margin-bottom: 15px;
+    }
+    .scenario-card .title {
+      font-size: 1.4em;
+      margin-bottom: 10px;
+      color: #00ff88;
+    }
+    .scenario-card .description {
+      font-size: 0.95em;
+      color: #b2bec3;
+      line-height: 1.5;
+    }
+    .scenario-card .difficulty {
+      margin-top: 15px;
+      padding: 5px 10px;
+      border-radius: 5px;
+      font-size: 0.85em;
+      display: inline-block;
+    }
+    .difficulty.easy { background: #00b894; }
+    .difficulty.medium { background: #fdcb6e; color: #2d3436; }
+    .difficulty.hard { background: #d63031; }
+
+    /* Game Screen */
+    #gameScreen {
+      display: none;
+    }
+    .game-header {
+      background: rgba(0, 0, 0, 0.5);
+      padding: 20px;
+      border-radius: 10px;
+      margin-bottom: 30px;
+      border: 2px solid #00ff88;
+    }
+    .game-header h2 {
+      color: #00ff88;
+      margin-bottom: 10px;
+      font-size: 2em;
+    }
+    .score-bar {
+      display: flex;
+      justify-content: space-between;
+      margin-top: 15px;
+      font-size: 1.1em;
+    }
+    .score-item {
+      background: rgba(0, 255, 136, 0.2);
+      padding: 8px 15px;
+      border-radius: 5px;
+      border: 1px solid #00ff88;
+    }
+
+    .situation-box {
+      background: linear-gradient(135deg, #1e272e 0%, #0f1419 100%);
+      border-left: 5px solid #ff3366;
+      padding: 25px;
+      border-radius: 10px;
+      margin-bottom: 30px;
+      box-shadow: 0 5px 20px rgba(0, 0, 0, 0.5);
+    }
+    .situation-box h3 {
+      color: #ff3366;
+      margin-bottom: 15px;
+      font-size: 1.5em;
+    }
+    .situation-box p {
+      line-height: 1.8;
+      color: #dfe6e9;
+      font-size: 1.1em;
+    }
+
+    .choices {
+      display: flex;
+      flex-direction: column;
+      gap: 15px;
+    }
+    .choice-btn {
+      background: linear-gradient(135deg, #2d3436 0%, #1a1f2e 100%);
+      border: 2px solid #00ff88;
+      color: white;
+      padding: 20px 25px;
+      border-radius: 10px;
+      font-size: 1.05em;
+      cursor: pointer;
+      transition: all 0.3s;
+      text-align: left;
+      display: flex;
+      align-items: center;
+      gap: 15px;
+    }
+    .choice-btn:hover {
+      background: linear-gradient(135deg, #00ff88 0%, #00cc6a 100%);
+      color: #000;
+      transform: translateX(10px);
+      box-shadow: 0 5px 20px rgba(0, 255, 136, 0.4);
+    }
+    .choice-btn .number {
+      background: #00ff88;
+      color: #000;
+      width: 35px;
+      height: 35px;
+      border-radius: 50%;
+      display: flex;
+      align-items: center;
+      justify-content: center;
+      font-weight: bold;
+      font-size: 1.2em;
+      flex-shrink: 0;
+    }
+
+    .feedback {
+      margin-top: 30px;
+      padding: 25px;
+      border-radius: 10px;
+      animation: slideIn 0.5s ease-out;
+      border-left: 5px solid;
+    }
+    @keyframes slideIn {
+      from { opacity: 0; transform: translateY(20px); }
+      to { opacity: 1; transform: translateY(0); }
+    }
+    .feedback.correct {
+      background: rgba(0, 184, 148, 0.2);
+      border-color: #00b894;
+    }
+    .feedback.partial {
+      background: rgba(253, 203, 110, 0.2);
+      border-color: #fdcb6e;
+    }
+    .feedback.incorrect {
+      background: rgba(214, 48, 49, 0.2);
+      border-color: #d63031;
+    }
+    .feedback h4 {
+      font-size: 1.4em;
+      margin-bottom: 10px;
+    }
+    .feedback.correct h4 { color: #00b894; }
+    .feedback.partial h4 { color: #fdcb6e; }
+    .feedback.incorrect h4 { color: #d63031; }
+    .feedback p {
+      line-height: 1.6;
+      color: #dfe6e9;
+    }
+
+    .next-btn {
+      background: linear-gradient(135deg, #00ff88 0%, #00cc6a 100%);
+      border: none;
+      color: #000;
+      padding: 15px 40px;
+      border-radius: 25px;
+      font-size: 1.1em;
+      font-weight: bold;
+      cursor: pointer;
+      margin-top: 20px;
+      transition: all 0.3s;
+      box-shadow: 0 5px 15px rgba(0, 255, 136, 0.3);
+    }
+    .next-btn:hover {
+      transform: scale(1.05);
+      box-shadow: 0 7px 20px rgba(0, 255, 136, 0.5);
+    }
+
+    /* Results Screen */
+    #resultsScreen {
+      display: none;
+      text-align: center;
+      padding: 50px 20px;
+    }
+    .results-box {
+      background: linear-gradient(135deg, #1e272e 0%, #0f1419 100%);
+      border: 3px solid #00ff88;
+      border-radius: 20px;
+      padding: 50px;
+      box-shadow: 0 10px 40px rgba(0, 0, 0, 0.5);
+    }
+    .results-box h2 {
+      font-size: 3em;
+      color: #00ff88;
+      margin-bottom: 20px;
+    }
+    .final-score {
+      font-size: 4em;
+      color: #00ffff;
+      margin: 30px 0;
+      text-shadow: 0 0 30px rgba(0, 255, 255, 0.8);
+    }
+    .rating {
+      font-size: 2em;
+      margin: 20px 0;
+    }
+    .rating-text {
+      font-size: 1.5em;
+      color: #dfe6e9;
+      margin: 20px 0;
+    }
+    .stats {
+      display: grid;
+      grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
+      gap: 20px;
+      margin: 40px 0;
+    }
+    .stat-item {
+      background: rgba(0, 255, 136, 0.1);
+      padding: 20px;
+      border-radius: 10px;
+      border: 2px solid #00ff88;
+    }
+    .stat-item .label {
+      font-size: 0.9em;
+      color: #b2bec3;
+      margin-bottom: 10px;
+    }
+    .stat-item .value {
+      font-size: 2em;
+      color: #00ff88;
+      font-weight: bold;
+    }
+    .back-btn {
+      background: linear-gradient(135deg, #636e72 0%, #2d3436 100%);
+      border: 2px solid #b2bec3;
+      color: white;
+      padding: 15px 40px;
+      border-radius: 25px;
+      font-size: 1.1em;
+      cursor: pointer;
+      margin-top: 20px;
+      transition: all 0.3s;
+      margin-left: 10px;
+    }
+    .back-btn:hover {
+      background: linear-gradient(135deg, #b2bec3 0%, #636e72 100%);
+    }
+
+    .hidden { display: none; }
+
+    @media (max-width: 768px) {
+      #welcomeScreen h1 { font-size: 2em; }
+      .scenario-grid { grid-template-columns: 1fr; }
+      .game-header h2 { font-size: 1.5em; }
+      .choice-btn { padding: 15px 20px; font-size: 0.95em; }
+    }
+  </style>
+</head>
+<body>
+  <div class="container">
+    <!-- Welcome Screen -->
+    <div id="welcomeScreen">
+      <h1>🎯 Cyber Incident Response Simulator</h1>
+      <p class="subtitle">Test your cybersecurity decision-making skills in realistic scenarios</p>
+
+      <div class="scenario-grid">
+        <div class="scenario-card" onclick="startScenario('ransomware')">
+          <div class="icon">🔐</div>
+          <div class="title">Ransomware Attack</div>
+          <div class="description">Your company's systems are encrypted. Make critical decisions under pressure.</div>
+          <div class="difficulty hard">Hard</div>
+        </div>
+
+        <div class="scenario-card" onclick="startScenario('phishing')">
+          <div class="icon">📧</div>
+          <div class="title">Phishing Investigation</div>
+          <div class="description">An employee clicked a suspicious link. Contain the threat.</div>
+          <div class="difficulty medium">Medium</div>
+        </div>
+
+        <div class="scenario-card" onclick="startScenario('databreach')">
+          <div class="icon">💾</div>
+          <div class="title">Data Breach Response</div>
+          <div class="description">Customer data may be exposed. Handle the crisis properly.</div>
+          <div class="difficulty hard">Hard</div>
+        </div>
+
+        <div class="scenario-card" onclick="startScenario('insider')">
+          <div class="icon">👤</div>
+          <div class="title">Insider Threat</div>
+          <div class="description">Suspicious employee activity detected. Investigate carefully.</div>
+          <div class="difficulty medium">Medium</div>
+        </div>
+
+        <div class="scenario-card" onclick="startScenario('ddos')">
+          <div class="icon">🌐</div>
+          <div class="title">DDoS Attack</div>
+          <div class="description">Your website is under massive attack. Keep services running.</div>
+          <div class="difficulty easy">Easy</div>
+        </div>
+
+        <div class="scenario-card" onclick="startScenario('social')">
+          <div class="icon">📞</div>
+          <div class="title">Social Engineering</div>
+          <div class="description">Someone is impersonating your CEO. Verify and respond.</div>
+          <div class="difficulty easy">Easy</div>
+        </div>
+      </div>
+    </div>
+
+    <!-- Game Screen -->
+    <div id="gameScreen">
+      <div class="game-header">
+        <h2 id="scenarioTitle"></h2>
+        <div class="score-bar">
+          <div class="score-item">
+            📊 Score: <span id="currentScore">0</span>
+          </div>
+          <div class="score-item">
+            📝 Step: <span id="currentStep">1</span>/<span id="totalSteps">5</span>
+          </div>
+          <div class="score-item">
+            ⏱️ Decisions: <span id="decisionsCount">0</span>
+          </div>
+        </div>
+      </div>
+
+      <div class="situation-box">
+        <h3>⚠️ Situation</h3>
+        <p id="situationText"></p>
+      </div>
+
+      <div class="choices" id="choicesContainer"></div>
+
+      <div id="feedbackContainer"></div>
+    </div>
+
+    <!-- Results Screen -->
+    <div id="resultsScreen">
+      <div class="results-box">
+        <h2>🎊 Scenario Complete!</h2>
+        <div class="final-score" id="finalScore">0</div>
+        <div class="rating" id="rating"></div>
+        <div class="rating-text" id="ratingText"></div>
+
+        <div class="stats">
+          <div class="stat-item">
+            <div class="label">Total Score</div>
+            <div class="value" id="statScore">0</div>
+          </div>
+          <div class="stat-item">
+            <div class="label">Decisions Made</div>
+            <div class="value" id="statDecisions">0</div>
+          </div>
+          <div class="stat-item">
+            <div class="label">Success Rate</div>
+            <div class="value" id="statSuccess">0%</div>
+          </div>
+        </div>
+
+        <button class="next-btn" onclick="resetGame()">🎮 Try Another Scenario</button>
+        <button class="back-btn" onclick="location.href='index.html'">⬅️ Back to Games</button>
+      </div>
+    </div>
+  </div>
+
+  <script>
+    // Game State
+    let currentScenario = null;
+    let currentStep = 0;
+    let score = 0;
+    let maxScore = 0;
+    let decisions = 0;
+    let correctDecisions = 0;
+
+    // Scenario Database
+    const scenarios = {
+      ransomware: {
+        title: "🔐 Ransomware Attack",
+        icon: "🔐",
+        steps: [
+          {
+            situation: "At 3:00 AM, your monitoring system alerts you that multiple servers are showing unusual disk activity. Within minutes, workstations start displaying ransom notes demanding 50 Bitcoin ($2M USD). The message says you have 48 hours to pay or all data will be permanently deleted. What's your FIRST action?",
+            choices: [
+              { text: "Immediately pay the ransom to get our systems back quickly", points: 0, feedback: "❌ Incorrect - Paying ransomware encourages attackers and doesn't guarantee data recovery. Many organizations pay and never receive decryption keys.", type: "incorrect" },
+              { text: "Isolate infected systems from the network to prevent spread", points: 25, feedback: "✅ Excellent! Containment is the first priority. Disconnecting infected systems prevents the ransomware from spreading to other machines and systems.", type: "correct" },
+              { text: "Restart all affected servers to clear the ransomware", points: 5, feedback: "⚠️ Dangerous - Restarting may allow the ransomware to complete encryption and could destroy forensic evidence needed for investigation.", type: "incorrect" },
+              { text: "Send a company-wide email warning everyone about the attack", points: 10, feedback: "⚠️ Partially correct - Communication is important, but containment must come first. Also, email systems might be compromised.", type: "partial" }
+            ]
+          },
+          {
+            situation: "You've isolated the infected systems. Your IT team reports that the ransomware entered through a phishing email opened by an employee. You have offline backups from 2 days ago, but they'll need 12 hours to restore. The executive team is pressuring you for a solution. What do you do?",
+            choices: [
+              { text: "Begin restoring from backups immediately - accept the 2-day data loss", points: 25, feedback: "✅ Correct! Using clean backups is the most reliable recovery method. 2 days of data is better than paying criminals with no guarantee.", type: "correct" },
+              { text: "Negotiate with the attackers for more time while restoring backups", points: 15, feedback: "⚠️ Risky - Engaging with attackers can provide intelligence but might encourage future attacks. Focus on recovery instead.", type: "partial" },
+              { text: "Pay the ransom since executives want fast recovery", points: 0, feedback: "❌ Wrong - Even with executive pressure, paying sets dangerous precedent and may fund criminal operations. Explain risks and advocate for backup restoration.", type: "incorrect" },
+              { text: "Try to decrypt the files yourself using online tools", points: 5, feedback: "⚠️ Ineffective - Most modern ransomware uses strong encryption. While free decryption tools exist for some strains, professional incident response is needed.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "During restoration, you discover the attackers had access to your network for 3 weeks before deploying ransomware. They may have stolen sensitive customer data including names, emails, and payment information for 50,000 customers. What's your responsibility?",
+            choices: [
+              { text: "Keep quiet - we're not sure data was actually stolen", points: 0, feedback: "❌ Illegal - Most jurisdictions require breach notification. Hiding breaches can result in massive fines and destroy customer trust.", type: "incorrect" },
+              { text: "Notify affected customers and relevant authorities per GDPR/data protection laws", points: 30, feedback: "✅ Perfect! Legal compliance and transparency are critical. Notify customers within required timeframes (typically 72 hours) and offer credit monitoring.", type: "correct" },
+              { text: "Only notify customers if we confirm data theft occurred", points: 10, feedback: "⚠️ Risky - Waiting for confirmation may violate notification deadlines. When in doubt, notify. Better to over-communicate than face legal consequences.", type: "partial" },
+              { text: "Hire a PR firm to manage the message first", points: 5, feedback: "⚠️ Partially correct - PR help is useful, but legal notifications must happen first. Don't delay compliance for optics.", type: "partial" }
+            ]
+          },
+          {
+            situation: "Systems are restored and customers notified. Now you need to prevent this from happening again. The attack vector was a phishing email, but the attackers exploited multiple security weaknesses. What's your comprehensive prevention strategy?",
+            choices: [
+              { text: "Implement multi-factor authentication (MFA), employee security training, email filtering, and regular backup testing", points: 30, feedback: "✅ Excellent! A layered security approach (defense in depth) addresses multiple attack vectors. MFA alone could have prevented this.", type: "correct" },
+              { text: "Just install better antivirus software", points: 5, feedback: "❌ Insufficient - Antivirus is one layer, but attackers bypass it easily. You need multiple defensive layers and user education.", type: "incorrect" },
+              { text: "Fire the employee who clicked the phishing link", points: 0, feedback: "❌ Wrong approach - Anyone can fall for sophisticated phishing. Focus on systems and training, not blame. That employee likely feels terrible already.", type: "incorrect" },
+              { text: "Block all email attachments company-wide", points: 10, feedback: "⚠️ Too extreme - While reducing risk, this hinders business operations. Use email filtering, sandboxing, and user training instead.", type: "partial" }
+            ]
+          },
+          {
+            situation: "Three months later, you receive another ransom demand - but this time, the attackers claim to have stolen your company's trade secrets and customer database BEFORE you detected them. They threaten to sell this data to competitors unless you pay $500,000. How do you respond?",
+            choices: [
+              { text: "Immediately involve law enforcement and your legal team", points: 25, feedback: "✅ Correct! This is extortion and potentially espionage. FBI/law enforcement have experience with these cases. Document everything for legal action.", type: "correct" },
+              { text: "Pay the ransom to protect trade secrets", points: 0, feedback: "❌ Wrong - Paying doesn't guarantee they'll delete data. They can extort you repeatedly. Report to authorities and prepare for potential data exposure.", type: "incorrect" },
+              { text: "Threaten to counter-hack them", points: 0, feedback: "❌ Illegal - 'Hacking back' is illegal in most jurisdictions and can make you liable. Always work through legal channels.", type: "incorrect" },
+              { text: "Ignore the threat - they're probably bluffing", points: 5, feedback: "❌ Dangerous - Threat actors often carry through on threats. Take it seriously, involve law enforcement, and prepare incident response.", type: "incorrect" }
+            ]
+          }
+        ]
+      },
+
+      phishing: {
+        title: "📧 Phishing Investigation",
+        icon: "📧",
+        steps: [
+          {
+            situation: "An employee in accounting reports clicking a link in an email claiming to be from your CEO requesting an urgent wire transfer. The email looked legitimate with correct logos and signature. The link led to a login page asking for their credentials. They entered their username and password before realizing something was wrong. What's your immediate action?",
+            choices: [
+              { text: "Immediately reset the employee's password and revoke active sessions", points: 30, feedback: "✅ Perfect! Quick credential reset prevents attackers from using the stolen credentials. Time is critical here.", type: "correct" },
+              { text: "Tell the employee to change their password when convenient", points: 5, feedback: "❌ Too slow - Attackers may already be using those credentials. Immediate forced reset is required.", type: "incorrect" },
+              { text: "Monitor the account for suspicious activity", points: 10, feedback: "⚠️ Insufficient - Monitoring is good, but you must assume credentials are compromised. Reset immediately AND monitor.", type: "partial" },
+              { text: "Scold the employee for falling for the phishing attack", points: 0, feedback: "❌ Counterproductive - This discourages future reporting. Phishing is sophisticated. Praise them for reporting it quickly!", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "You've reset credentials. Upon investigation, you discover the employee has access to the company financial system and customer database. The attackers may have had access for up to 20 minutes before the employee reported it. What's your next step?",
+            choices: [
+              { text: "Review all account activity logs for those 20 minutes to identify what was accessed", points: 25, feedback: "✅ Excellent! Forensic analysis of logs shows what data was compromised. Check for downloads, transfers, or privilege escalations.", type: "correct" },
+              { text: "Assume no damage since it was only 20 minutes", points: 0, feedback: "❌ Dangerous assumption - Automated tools can exfiltrate massive amounts of data in seconds. Always investigate.", type: "incorrect" },
+              { text: "Shut down the entire financial system immediately", points: 10, feedback: "⚠️ Too extreme - This disrupts business unnecessarily. Review logs first, then take targeted action based on findings.", type: "partial" },
+              { text: "Only check if any wire transfers were attempted", points: 15, feedback: "⚠️ Too narrow - Check ALL activity: data access, downloads, lateral movement, privilege changes, not just transfers.", type: "partial" }
+            ]
+          },
+          {
+            situation: "Log analysis shows the attacker accessed the customer database and downloaded a file containing 10,000 customer email addresses. No financial transactions occurred. The phishing email came from a spoofed domain (ceroacme.com instead of ceo@acme.com). What technical controls should you implement?",
+            choices: [
+              { text: "Implement DMARC, SPF, and DKIM email authentication to prevent domain spoofing", points: 30, feedback: "✅ Perfect! These email authentication protocols prevent attackers from spoofing your domain. Also add warning banners for external emails.", type: "correct" },
+              { text: "Block all external emails", points: 5, feedback: "❌ Impractical - This would cripple business operations. Use authentication and filtering instead.", type: "incorrect" },
+              { text: "Just tell employees to be more careful", points: 0, feedback: "❌ Insufficient - Technical controls are needed. Human error will always occur; defense must be multi-layered.", type: "incorrect" },
+              { text: "Only allow emails from whitelisted domains", points: 10, feedback: "⚠️ Too restrictive - This prevents legitimate business communication. Use authentication standards and training instead.", type: "partial" }
+            ]
+          },
+          {
+            situation: "You've implemented technical controls. Now you must address the compromised customer email list. The 10,000 emails were downloaded. What's your obligation and best practice?",
+            choices: [
+              { text: "Notify affected customers about the potential compromise and advise them to be alert for phishing", points: 25, feedback: "✅ Correct! Transparency and customer warning helps them protect themselves from follow-up attacks using their data.", type: "correct" },
+              { text: "Don't notify - it's just emails, not financial data", points: 0, feedback: "❌ Wrong - Even email addresses have value and may require notification under data protection laws. It enables future targeted attacks.", type: "incorrect" },
+              { text: "Only notify if they ask", points: 0, feedback: "❌ Unethical and potentially illegal - Proactive notification is required in many jurisdictions and is the right thing to do.", type: "incorrect" },
+              { text: "Send a generic security reminder to all customers", points: 15, feedback: "⚠️ Partially correct - Better than nothing, but affected customers should be specifically informed about the breach.", type: "partial" }
+            ]
+          },
+          {
+            situation: "Final step: Preventing future phishing attacks. Your security audit revealed that 40% of employees failed a simulated phishing test last year. What's your comprehensive approach?",
+            choices: [
+              { text: "Implement regular security awareness training, simulated phishing campaigns, MFA everywhere, and email filtering with link sandboxing", points: 30, feedback: "✅ Perfect! Combining education, testing, technical controls, and MFA creates strong defense. Regular simulation training improves recognition skills.", type: "correct" },
+              { text: "Fire employees who fail phishing tests", points: 0, feedback: "❌ Terrible approach - This creates fear and discourages reporting. Education and support are more effective than punishment.", type: "incorrect" },
+              { text: "Just send out a one-time security memo", points: 5, feedback: "❌ Insufficient - One-time training has minimal impact. Security awareness requires ongoing education and reinforcement.", type: "incorrect" },
+              { text: "Only implement email filtering technology", points: 15, feedback: "⚠️ Incomplete - Technology alone isn't enough. Humans are the last line of defense. Combine tech with regular training.", type: "partial" }
+            ]
+          }
+        ]
+      },
+
+      databreach: {
+        title: "💾 Data Breach Response",
+        icon: "💾",
+        steps: [
+          {
+            situation: "Your security team detects unusual outbound traffic at 2 AM on a Saturday. Investigation reveals an exposed S3 bucket containing 500,000 customer records (names, emails, phone numbers, and hashed passwords). The bucket has been publicly accessible for 6 months. What's your first priority?",
+            choices: [
+              { text: "Immediately secure the S3 bucket and cut off public access", points: 30, feedback: "✅ Excellent! Stop the bleeding first. Securing the exposure prevents further unauthorized access while you investigate the scope.", type: "correct" },
+              { text: "Start notifying customers immediately", points: 10, feedback: "⚠️ Premature - First contain the breach, then investigate scope before notification. You need accurate information for customers.", type: "partial" },
+              { text: "Wait until Monday to brief the executive team", points: 0, feedback: "❌ Dangerous delay - Every minute counts. Secure the data immediately and notify executives urgently, even on weekends.", type: "incorrect" },
+              { text: "Delete the S3 bucket to hide the evidence", points: 0, feedback: "❌ Illegal! This destroys forensic evidence and violates data protection laws. Secure it and preserve evidence for investigation.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "The bucket is secured. Forensic analysis shows the bucket was accessed 847 times from 23 different IP addresses over 6 months. You cannot determine exactly what data was downloaded. Under GDPR and most data protection laws, what's your legal obligation?",
+            choices: [
+              { text: "Notify supervisory authority within 72 hours and affected individuals without undue delay", points: 30, feedback: "✅ Correct! GDPR requires notification to authorities within 72 hours and to individuals when there's high risk. Most data protection laws have similar requirements.", type: "correct" },
+              { text: "Only notify if we can prove data was actually downloaded", points: 0, feedback: "❌ Wrong - When data is exposed and access occurred, you must assume compromise. Waiting for proof violates notification timelines.", type: "incorrect" },
+              { text: "Notify authorities but not customers to avoid panic", points: 5, feedback: "❌ Illegal - Customers must be notified when their data is at high risk. They need to protect themselves from fraud and identity theft.", type: "incorrect" },
+              { text: "Wait 30 days to complete a full investigation", points: 0, feedback: "❌ Violates legal timelines - Most laws require notification within days, not weeks. Delayed notification can result in massive fines.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "You're preparing customer notifications. The passwords were hashed with bcrypt (strong), but some customers may have reused passwords from other sites. What should you tell customers?",
+            choices: [
+              { text: "Explain what happened, what data was exposed, recommend they change passwords and enable MFA everywhere, and offer credit monitoring", points: 30, feedback: "✅ Perfect! Transparency, specific guidance, and support services show you take their security seriously. Clear communication builds trust.", type: "correct" },
+              { text: "Send a vague 'we take security seriously' message without details", points: 0, feedback: "❌ Unacceptable - Customers deserve clear information about what was exposed so they can protect themselves. Vagueness destroys trust.", type: "incorrect" },
+              { text: "Only mention the exposure, no recommendations", points: 10, feedback: "⚠️ Incomplete - Customers need guidance on protecting themselves. Provide specific, actionable steps they should take.", type: "partial" },
+              { text: "Downplay the risk since passwords were hashed", points: 5, feedback: "❌ Misleading - While bcrypt is strong, other data was exposed and sophisticated attackers may crack some hashes. Be honest about risks.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "News media has discovered the breach and published a story. Angry customers are flooding social media. Your stock price dropped 15%. The CEO wants to know who's responsible. How do you handle internal accountability?",
+            choices: [
+              { text: "Conduct a blameless post-mortem to understand system failures and implement preventive measures", points: 25, feedback: "✅ Excellent! Blameless post-mortems focus on fixing systems, not punishing people. This encourages honesty and continuous improvement.", type: "correct" },
+              { text: "Fire the developer who created the S3 bucket", points: 0, feedback: "❌ Counterproductive - This creates fear and discourages reporting. Security failures are usually systemic. Fix processes and systems.", type: "incorrect" },
+              { text: "Blame a third-party vendor to deflect responsibility", points: 0, feedback: "❌ Unethical - If it's your data, it's your responsibility. Shifting blame damages partnerships and doesn't solve the problem.", type: "incorrect" },
+              { text: "Publicly identify the responsible employee to satisfy media pressure", points: 0, feedback: "❌ Terrible - This destroys employee morale and trust. Handle internal accountability privately and focus externally on solutions.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Final step: The breach cost $5.2M in notifications, legal fees, fines, and remediation. Insurance covered $2M. The board wants assurance this won't happen again. What comprehensive security improvements do you propose?",
+            choices: [
+              { text: "Implement automated security scanning, IAM policies, access reviews, security training, and regular penetration testing", points: 30, feedback: "✅ Perfect! This addresses multiple failure points: technology (scanning, IAM), process (reviews), and people (training). Defense in depth.", type: "correct" },
+              { text: "Just implement automated S3 bucket scanning", points: 10, feedback: "⚠️ Too narrow - While scanning helps, you need comprehensive controls covering people, process, and technology across all systems.", type: "partial" },
+              { text: "Move everything to a different cloud provider", points: 5, feedback: "❌ Misguided - The problem was configuration and process, not the provider. Same mistakes can happen anywhere. Fix your practices.", type: "incorrect" },
+              { text: "Hire more security staff without process changes", points: 10, feedback: "⚠️ Insufficient - More people won't help without better processes, tools, and training. Focus on systematic improvements.", type: "partial" }
+            ]
+          }
+        ]
+      },
+
+      insider: {
+        title: "👤 Insider Threat Detection",
+        icon: "👤",
+        steps: [
+          {
+            situation: "Your Data Loss Prevention (DLP) system alerts that a senior developer downloaded the entire customer database to a USB drive at 11 PM on Friday. This employee has authorized access but has never done this before. They gave notice two weeks ago and are leaving for a competitor. What's your first action?",
+            choices: [
+              { text: "Immediately disable their access and secure the USB drive, then investigate calmly", points: 30, feedback: "✅ Correct! Prevent further data exfiltration while preserving your ability to investigate. Act decisively but professionally.", type: "correct" },
+              { text: "Confront the employee angrily and demand the USB drive", points: 5, feedback: "⚠️ Risky - Emotional confrontation may cause them to destroy evidence or become defensive. Handle professionally with HR and legal present.", type: "partial" },
+              { text: "Monitor their activity to gather more evidence", points: 10, feedback: "⚠️ Dangerous - They may exfiltrate more data or destroy evidence. When data theft is detected, immediate action is needed.", type: "partial" },
+              { text: "Ignore it - they have authorized access", points: 0, feedback: "❌ Wrong - Authorized access doesn't mean authorized use. Downloading entire databases to personal devices violates policy.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "You've disabled access and retrieved the USB drive. The employee claims they were 'backing up their code projects for their portfolio.' HR is present. What's your approach to the investigation?",
+            choices: [
+              { text: "Forensically image the USB drive, review access logs, and document everything while treating them respectfully", points: 25, feedback: "✅ Excellent! Professional forensics preserves evidence for potential legal action. Documentation is critical. Treat them with dignity.", type: "correct" },
+              { text: "Immediately call the police and press charges", points: 10, feedback: "⚠️ Premature - Complete investigation first. You need evidence of intent and damage. Consult legal counsel before involving law enforcement.", type: "partial" },
+              { text: "Accept their explanation and return the drive", points: 0, feedback: "❌ Naive - Their explanation doesn't match behavior (customer database isn't code). Investigate thoroughly and preserve evidence.", type: "incorrect" },
+              { text: "Search their personal belongings without consent", points: 0, feedback: "❌ Illegal in most jurisdictions - This violates privacy laws. Work within legal frameworks and involve law enforcement if search is needed.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Forensic analysis reveals the USB contains the customer database, proprietary source code, and strategic business documents. The employee refuses to cooperate. Legal counsel confirms this is likely trade secret theft. What's your next step?",
+            choices: [
+              { text: "Involve law enforcement and seek legal injunction to prevent them from using stolen data at new company", points: 30, feedback: "✅ Perfect! Trade secret theft is criminal. Legal action protects your business and sends message that theft has consequences.", type: "correct" },
+              { text: "Negotiate a settlement where they promise not to use the data", points: 10, feedback: "⚠️ Weak - Without legal enforcement, promises are meaningless. You need legal protections and accountability for theft.", type: "partial" },
+              { text: "Just let them go to avoid bad publicity", points: 0, feedback: "❌ Dangerous - This encourages future theft and damages your business. Protect your assets and hold people accountable.", type: "incorrect" },
+              { text: "Leak their information online as retaliation", points: 0, feedback: "❌ Illegal! This is libel/harassment and makes you liable. Always work through proper legal channels.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Law enforcement is investigating. Meanwhile, you need to prevent similar incidents. Your audit reveals 47 employees have broad database access they don't need for their jobs. What security principle should you implement?",
+            choices: [
+              { text: "Principle of Least Privilege - give users minimum access needed for their role", points: 25, feedback: "✅ Excellent! Least privilege dramatically reduces insider threat risk. Combine with regular access reviews and DLP monitoring.", type: "correct" },
+              { text: "Block all USB drives and external storage company-wide", points: 15, feedback: "⚠️ Helpful but incomplete - This addresses one vector but not cloud uploads, email, or other exfiltration methods. Need comprehensive approach.", type: "partial" },
+              { text: "Monitor all employee communications and computer activity", points: 10, feedback: "⚠️ Privacy concerns - Excessive monitoring has legal and ethical issues. Focus on data access controls and anomaly detection instead.", type: "partial" },
+              { text: "Make all employees sign stricter NDAs", points: 5, feedback: "❌ Insufficient - Legal agreements don't prevent determined theft. Technical controls (access limits, monitoring) are more effective.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Final scenario: Three months later, you notice unusual access patterns from an employee in finance who's viewing executive salary data they shouldn't access. However, they have a legitimate business justification: HR asked them to help with compensation analysis. How do you handle this?",
+            choices: [
+              { text: "Verify the request with HR, grant temporary elevated access with approval trail, then revoke after task completion", points: 30, feedback: "✅ Perfect! This balances security with business needs. Temporary access with approval and auditing is the right approach.", type: "correct" },
+              { text: "Deny access - they should use HR's credentials instead", points: 10, feedback: "⚠️ Poor practice - Sharing credentials violates security policy and removes accountability. Temporary individual access is better.", type: "partial" },
+              { text: "Give them permanent elevated access since they might need it again", points: 0, feedback: "❌ Violates least privilege - Grant minimum access for minimum time needed. Permanent elevated access increases risk unnecessarily.", type: "incorrect" },
+              { text: "Ignore it since HR requested it", points: 0, feedback: "❌ No verification - Always verify unusual access requests directly with the requesting party. Social engineering attacks use fake authorization.", type: "incorrect" }
+            ]
+          }
+        ]
+      },
+
+      ddos: {
+        title: "🌐 DDoS Attack Mitigation",
+        icon: "🌐",
+        steps: [
+          {
+            situation: "Your e-commerce website suddenly becomes unresponsive. Monitoring shows 50,000 requests per second from thousands of different IP addresses worldwide. Legitimate customers can't access your site. This is a Distributed Denial of Service (DDoS) attack during your biggest sales day. What's your immediate response?",
+            choices: [
+              { text: "Enable your DDoS protection service (Cloudflare/AWS Shield) or contact your ISP for mitigation", points: 30, feedback: "✅ Excellent! DDoS mitigation services filter malicious traffic. If you don't have one, ISP-level filtering is next best option.", type: "correct" },
+              { text: "Block all traffic from foreign countries", points: 10, feedback: "⚠️ Too broad - This blocks legitimate international customers and sophisticated attacks use domestic IPs. Use targeted filtering instead.", type: "partial" },
+              { text: "Restart the web server to clear connections", points: 0, feedback: "❌ Ineffective - The attack will immediately overwhelm it again. You need traffic filtering before requests reach your server.", type: "incorrect" },
+              { text: "Do nothing and wait for the attack to stop", points: 0, feedback: "❌ Costly - Every minute down loses revenue and damages reputation. Active mitigation is essential for business continuity.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "DDoS protection is active but attack is evolving. Attackers are now targeting your API endpoints with seemingly legitimate requests that are expensive to process (database queries). Simple rate limiting would block legitimate users too. What's your strategy?",
+            choices: [
+              { text: "Implement CAPTCHA challenges, behavioral analysis, and cache frequently-requested data", points: 25, feedback: "✅ Smart! CAPTCHAs distinguish humans from bots, behavioral analysis detects abnormal patterns, and caching reduces database load.", type: "correct" },
+              { text: "Shut down the API completely until attack ends", points: 5, feedback: "❌ Too extreme - This accomplishes the attacker's goal (denial of service). Use intelligent filtering to allow legitimate traffic.", type: "incorrect" },
+              { text: "Only allow logged-in users to access API", points: 15, feedback: "⚠️ Partially effective - This helps but prevents legitimate guest users. Combine with rate limiting and behavioral analysis.", type: "partial" },
+              { text: "Add more servers to handle the load", points: 10, feedback: "⚠️ Expensive and ineffective - Scaling can't keep up with DDoS attacks. Attackers can always add more bots. Filter before processing.", type: "partial" }
+            ]
+          },
+          {
+            situation: "The attack has been running for 6 hours. Your security team traces it to a botnet of 10,000 compromised IoT devices. Law enforcement says investigation will take weeks. Meanwhile, the attacker emails demanding $100,000 in Bitcoin to stop. How do you respond?",
+            choices: [
+              { text: "Refuse to pay, maintain DDoS mitigation, and coordinate with law enforcement", points: 30, feedback: "✅ Correct! Paying encourages future attacks. Proper DDoS protection makes attacks economically unviable for attackers.", type: "correct" },
+              { text: "Pay the ransom to end it quickly", points: 0, feedback: "❌ Wrong - Payment doesn't guarantee they'll stop and encourages repeat attacks. Invest in proper DDoS protection instead.", type: "incorrect" },
+              { text: "Launch a counter-attack against the botnet", points: 0, feedback: "❌ Illegal - 'Hacking back' is illegal and you'd attack innocent IoT device owners, not the attacker. Use legal channels.", type: "incorrect" },
+              { text: "Threaten to report them if they don't stop", points: 5, feedback: "❌ Ineffective - Anonymous attackers don't fear threats. Focus on technical mitigation and law enforcement cooperation.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "After 12 hours, the attack stops. You've lost $500K in sales. Post-incident analysis needed. What's the most important preventive measure for future DDoS attacks?",
+            choices: [
+              { text: "Implement permanent DDoS protection service, create incident response plan, and conduct regular DDoS drills", points: 25, feedback: "✅ Perfect! Prevention is cheaper than mitigation. DDoS protection, planning, and practice ensure fast response to future attacks.", type: "correct" },
+              { text: "Sue the attackers for damages", points: 5, feedback: "⚠️ Impractical - DDoS attackers are usually anonymous and in different jurisdictions. Focus on technical prevention instead.", type: "partial" },
+              { text: "Buy more bandwidth to absorb future attacks", points: 10, feedback: "⚠️ Expensive and ineffective - Attackers can always overwhelm bandwidth. Filtering and protection services are more cost-effective.", type: "partial" },
+              { text: "Switch to a different hosting provider", points: 5, feedback: "❌ Doesn't solve problem - Any provider can be attacked. You need DDoS protection regardless of where you're hosted.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Final question: Six months later, you notice unusual traffic patterns that might indicate reconnaissance for another attack. Your DDoS protection is active. What ongoing security practices should you maintain?",
+            choices: [
+              { text: "Continuous traffic monitoring, regular security testing, updated response plans, and staff training", points: 25, feedback: "✅ Excellent! Ongoing vigilance and preparedness are key. Regular drills ensure your team responds effectively under pressure.", type: "correct" },
+              { text: "Just rely on the DDoS protection service - they'll handle it", points: 10, feedback: "⚠️ Over-reliant - Protection services are essential but you need monitoring, planning, and trained staff for comprehensive defense.", type: "partial" },
+              { text: "Monitor only during high-traffic periods like sales events", points: 5, feedback: "❌ Insufficient - Attacks can happen anytime. Continuous monitoring detects and mitigates threats faster.", type: "incorrect" },
+              { text: "Nothing - the attack won't happen again", points: 0, feedback: "❌ Naive - DDoS attacks are common and recurring. Maintaining defenses and readiness is essential for any online business.", type: "incorrect" }
+            ]
+          }
+        ]
+      },
+
+      social: {
+        title: "📞 Social Engineering Attack",
+        icon: "📞",
+        steps: [
+          {
+            situation: "You're the IT manager. You receive an urgent call from someone claiming to be your CEO who's traveling abroad. They say they're locked out of their email due to MFA and need you to disable it immediately for an urgent client deal. The caller ID shows the CEO's mobile number. What do you do?",
+            choices: [
+              { text: "Verify through a separate communication channel (call CEO's known number or assistant) before making any changes", points: 30, feedback: "✅ Perfect! Always verify urgent requests through independent channels. Caller ID can be spoofed easily. This is classic social engineering.", type: "correct" },
+              { text: "Disable MFA immediately since it's the CEO and caller ID matches", points: 0, feedback: "❌ Dangerous! Caller ID spoofing is trivial. Attackers research executives and create urgency to bypass security. Always verify.", type: "incorrect" },
+              { text: "Ask security questions like 'what's your employee ID?'", points: 15, feedback: "⚠️ Weak - Attackers often research targets and know personal details. Independent verification through known contact methods is essential.", type: "partial" },
+              { text: "Tell them to contact the help desk", points: 10, feedback: "⚠️ Partially correct - This adds a barrier, but help desk might fall for the same trick. You should personally verify through independent channel.", type: "partial" }
+            ]
+          },
+          {
+            situation: "You call the CEO's assistant who confirms the CEO is indeed traveling but never contacted IT. You've identified a social engineering attack. The attacker calls back, now claiming to be 'calling from IT security' about a critical system breach. They ask for admin credentials to 'secure the systems.' How do you respond?",
+            choices: [
+              { text: "Hang up, report to security team, and issue company-wide alert about the social engineering attempt", points: 30, feedback: "✅ Excellent! Warning others prevents them from falling for the same attack. Document the attempt for security awareness training.", type: "correct" },
+              { text: "Give them fake credentials to track them", points: 10, feedback: "⚠️ Risky - While tempting, this could backfire legally. Report to proper authorities and security team who have legal framework to investigate.", type: "partial" },
+              { text: "Question them to gather information about the attack", points: 15, feedback: "⚠️ Potentially useful but risky - Gathering intelligence is good, but end the call quickly and report it. Don't engage extensively.", type: "partial" },
+              { text: "Provide limited access to see what they're after", points: 0, feedback: "❌ Extremely dangerous! Never give attackers any access. Even limited access can be leveraged for further exploitation.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Company alert sent. An hour later, an employee in HR reports receiving an email appearing to be from you (IT Manager) requesting all employee personal information for a 'security audit.' The email looks legitimate with your signature. What's this attack vector and response?",
+            choices: [
+              { text: "This is email spoofing/phishing. Verify it's fake, warn staff, and implement email authentication (SPF/DKIM/DMARC)", points: 30, feedback: "✅ Perfect! Attackers often chain attacks. Email authentication prevents domain spoofing. Add external email warnings to help users identify spoofing.", type: "correct" },
+              { text: "Reply-all telling everyone the email is fake", points: 15, feedback: "⚠️ Partially correct - Warning is good, but reply-all to phishing emails can alert attackers. Use separate verified communication channel instead.", type: "partial" },
+              { text: "Just tell the HR employee to ignore it", points: 5, feedback: "❌ Insufficient - Other employees may have received it too. Company-wide warning and technical controls are needed.", type: "incorrect" },
+              { text: "Change your email password", points: 10, feedback: "⚠️ Misunderstands attack - This is spoofing, not account compromise. Changing password won't help. Implement email authentication instead.", type: "partial" }
+            ]
+          },
+          {
+            situation: "Investigation reveals the attackers gathered information from your company's LinkedIn profiles and website to make attacks convincing. This is called OSINT (Open Source Intelligence) reconnaissance. How do you balance transparency with security?",
+            choices: [
+              { text: "Train employees on safe social media practices, limit detailed organizational information publicly, implement verification procedures", points: 25, feedback: "✅ Great! You can't eliminate online presence, but training employees and verification procedures defend against reconnaissance-based attacks.", type: "correct" },
+              { text: "Delete all company social media and website information", points: 5, feedback: "❌ Unrealistic - Modern businesses need online presence. Focus on security awareness and verification procedures instead.", type: "incorrect" },
+              { text: "Fire employees who share work information online", points: 0, feedback: "❌ Excessive - Employees need to network professionally. Educate them on safe practices rather than punish normal behavior.", type: "incorrect" },
+              { text: "Post fake information to confuse attackers", points: 5, feedback: "❌ Counterproductive - This confuses legitimate contacts and damages credibility. Honest information with proper security procedures is better.", type: "incorrect" }
+            ]
+          },
+          {
+            situation: "Final scenario: Two months later, an 'IT vendor' arrives at reception with what appears to be a legitimate service appointment to 'upgrade network equipment.' They have forged emails and work orders. The receptionist almost grants them access. What preventive measures should be standard?",
+            choices: [
+              { text: "Maintain vendor registry, require pre-approved appointments, verify all service visits independently, issue visitor badges with escort requirements", points: 30, feedback: "✅ Perfect! Physical security is critical. Verification procedures, visitor management, and escort requirements prevent unauthorized physical access.", type: "correct" },
+              { text: "Just train reception to be suspicious of everyone", points: 10, feedback: "⚠️ Insufficient - Training helps but concrete procedures (verification calls, appointment systems) provide reliable protection.", type: "partial" },
+              { text: "Install cameras to monitor vendor activity", points: 15, feedback: "⚠️ Reactive - Cameras detect problems after access is granted. Prevention (verification before access) is better than detection after.", type: "partial" },
+              { text: "Allow vendors in but monitor them closely", points: 5, feedback: "❌ Too late - Once attackers have physical access, monitoring may not prevent damage. Verify legitimacy before granting access.", type: "incorrect" }
+            ]
+          }
+        ]
+      }
+    };
+
+    // Functions
+    function startScenario(scenarioKey) {
+      currentScenario = scenarios[scenarioKey];
+      currentStep = 0;
+      score = 0;
+      decisions = 0;
+      correctDecisions = 0;
+      maxScore = 0;
+
+      // Calculate max possible score
+      currentScenario.steps.forEach(step => {
+        const maxPoints = Math.max(...step.choices.map(c => c.points));
+        maxScore += maxPoints;
+      });
+
+      document.getElementById('welcomeScreen').classList.add('hidden');
+      document.getElementById('gameScreen').classList.remove('hidden');
+      document.getElementById('scenarioTitle').textContent = currentScenario.title;
+
+      showStep();
+    }
+
+    function showStep() {
+      if (currentStep >= currentScenario.steps.length) {
+        showResults();
+        return;
+      }
+
+      const step = currentScenario.steps[currentStep];
+
+      document.getElementById('situationText').textContent = step.situation;
+      document.getElementById('currentStep').textContent = currentStep + 1;
+      document.getElementById('totalSteps').textContent = currentScenario.steps.length;
+      document.getElementById('currentScore').textContent = score;
+      document.getElementById('decisionsCount').textContent = decisions;
+
+      // Clear previous choices and feedback
+      const choicesContainer = document.getElementById('choicesContainer');
+      const feedbackContainer = document.getElementById('feedbackContainer');
+      choicesContainer.innerHTML = '';
+      feedbackContainer.innerHTML = '';
+
+      // Create choice buttons
+      step.choices.forEach((choice, index) => {
+        const button = document.createElement('button');
+        button.className = 'choice-btn';
+        button.innerHTML = `
+          <span class="number">${index + 1}</span>
+          <span>${choice.text}</span>
+        `;
+        button.onclick = () => selectChoice(index);
+        choicesContainer.appendChild(button);
+      });
+    }
+
+    function selectChoice(choiceIndex) {
+      const step = currentScenario.steps[currentStep];
+      const choice = step.choices[choiceIndex];
+
+      score += choice.points;
+      decisions++;
+
+      if (choice.type === 'correct') {
+        correctDecisions++;
+      }
+
+      // Show feedback
+      const feedbackContainer = document.getElementById('feedbackContainer');
+      feedbackContainer.innerHTML = `
+        <div class="feedback ${choice.type}">
+          <h4>${choice.feedback.split('-')[0]}</h4>
+          <p>${choice.feedback.split('-').slice(1).join('-').trim()}</p>
+          <button class="next-btn" onclick="nextStep()">
+            ${currentStep < currentScenario.steps.length - 1 ? 'Next Situation ➡️' : 'See Results 🎊'}
+          </button>
+        </div>
+      `;
+
+      // Disable choice buttons
+      document.querySelectorAll('.choice-btn').forEach(btn => {
+        btn.style.pointerEvents = 'none';
+        btn.style.opacity = '0.6';
+      });
+
+      // Update score display
+      document.getElementById('currentScore').textContent = score;
+      document.getElementById('decisionsCount').textContent = decisions;
+    }
+
+    function nextStep() {
+      currentStep++;
+      showStep();
+    }
+
+    function showResults() {
+      document.getElementById('gameScreen').classList.add('hidden');
+      document.getElementById('resultsScreen').classList.remove('hidden');
+
+      const percentage = Math.round((score / maxScore) * 100);
+      let rating = '';
+      let ratingText = '';
+
+      if (percentage >= 90) {
+        rating = '🏆🏆🏆';
+        ratingText = 'Expert Security Professional!';
+      } else if (percentage >= 75) {
+        rating = '🏆🏆';
+        ratingText = 'Strong Security Knowledge!';
+      } else if (percentage >= 60) {
+        rating = '🏆';
+        ratingText = 'Good Security Awareness!';
+      } else if (percentage >= 40) {
+        rating = '📚';
+        ratingText = 'Needs Improvement';
+      } else {
+        rating = '⚠️';
+        ratingText = 'High Risk - More Training Needed';
+      }
+
+      document.getElementById('finalScore').textContent = `${score}/${maxScore}`;
+      document.getElementById('rating').textContent = rating;
+      document.getElementById('ratingText').textContent = ratingText;
+      document.getElementById('statScore').textContent = `${score}/${maxScore}`;
+      document.getElementById('statDecisions').textContent = decisions;
+      document.getElementById('statSuccess').textContent = `${percentage}%`;
+    }
+
+    function resetGame() {
+      document.getElementById('resultsScreen').classList.add('hidden');
+      document.getElementById('welcomeScreen').classList.remove('hidden');
+      currentScenario = null;
+      currentStep = 0;
+      score = 0;
+      maxScore = 0;
+      decisions = 0;
+      correctDecisions = 0;
+    }
+  </script>
+</body>
+</html>
diff --git a/game/index.html b/game/index.html
new file mode 100644
index 0000000000000..a71a438d1399c
--- /dev/null
+++ b/game/index.html
@@ -0,0 +1,190 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>Games - Benefit's Collection</title>
+  <style>
+    * { margin: 0; padding: 0; box-sizing: border-box; }
+    body {
+      font-family: 'Arial', sans-serif;
+      background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
+      min-height: 100vh;
+      display: flex;
+      justify-content: center;
+      align-items: center;
+      padding: 20px;
+    }
+    .container {
+      max-width: 1000px;
+      width: 100%;
+    }
+    h1 {
+      text-align: center;
+      color: white;
+      font-size: 3em;
+      margin-bottom: 20px;
+      text-shadow: 2px 2px 4px rgba(0, 0, 0, 0.3);
+    }
+    .subtitle {
+      text-align: center;
+      color: rgba(255, 255, 255, 0.9);
+      font-size: 1.2em;
+      margin-bottom: 50px;
+    }
+    .games-grid {
+      display: grid;
+      grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));
+      gap: 30px;
+      margin-top: 30px;
+    }
+    .game-card {
+      background: white;
+      border-radius: 15px;
+      padding: 30px;
+      box-shadow: 0 10px 30px rgba(0, 0, 0, 0.3);
+      transition: transform 0.3s, box-shadow 0.3s;
+      text-decoration: none;
+      color: inherit;
+      display: block;
+    }
+    .game-card:hover {
+      transform: translateY(-10px);
+      box-shadow: 0 15px 40px rgba(0, 0, 0, 0.4);
+    }
+    .game-icon {
+      font-size: 4em;
+      text-align: center;
+      margin-bottom: 20px;
+    }
+    .game-title {
+      font-size: 1.8em;
+      color: #333;
+      margin-bottom: 10px;
+      text-align: center;
+    }
+    .game-description {
+      color: #666;
+      text-align: center;
+      line-height: 1.6;
+      margin-bottom: 20px;
+    }
+    .game-features {
+      list-style: none;
+      margin-top: 15px;
+      padding-top: 15px;
+      border-top: 2px solid #f0f0f0;
+    }
+    .game-features li {
+      color: #555;
+      margin-bottom: 8px;
+      padding-left: 20px;
+      position: relative;
+    }
+    .game-features li:before {
+      content: "✓";
+      position: absolute;
+      left: 0;
+      color: #667eea;
+      font-weight: bold;
+    }
+    .play-button {
+      display: block;
+      text-align: center;
+      background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
+      color: white;
+      padding: 12px 30px;
+      border-radius: 25px;
+      text-decoration: none;
+      margin-top: 20px;
+      font-weight: bold;
+      transition: all 0.3s;
+    }
+    .play-button:hover {
+      transform: scale(1.05);
+      box-shadow: 0 5px 15px rgba(102, 126, 234, 0.4);
+    }
+    .new-badge {
+      display: inline-block;
+      background: #ff6b6b;
+      color: white;
+      padding: 5px 12px;
+      border-radius: 15px;
+      font-size: 0.7em;
+      margin-left: 10px;
+      animation: pulse 2s infinite;
+    }
+    @keyframes pulse {
+      0%, 100% { transform: scale(1); }
+      50% { transform: scale(1.1); }
+    }
+    .back-link {
+      text-align: center;
+      margin-top: 30px;
+    }
+    .back-link a {
+      color: white;
+      text-decoration: none;
+      font-size: 1.1em;
+      padding: 10px 20px;
+      border: 2px solid white;
+      border-radius: 25px;
+      transition: all 0.3s;
+      display: inline-block;
+    }
+    .back-link a:hover {
+      background: white;
+      color: #667eea;
+    }
+  </style>
+</head>
+<body>
+  <div class="container">
+    <h1>🎮 Game Collection</h1>
+    <p class="subtitle">Fun games with educational value</p>
+
+    <div class="games-grid">
+      <!-- Cyber Defense Game -->
+      <div class="game-card">
+        <div class="game-icon">🛡️</div>
+        <h2 class="game-title">
+          Cyber Defense
+          <span class="new-badge">NEW</span>
+        </h2>
+        <p class="game-description">
+          Learn about internet safety while defending against cyber threats!
+          Shoot scams and collect security best practices.
+        </p>
+        <ul class="game-features">
+          <li>Learn about phishing and scams</li>
+          <li>Understand security best practices</li>
+          <li>Fun shooting mechanics</li>
+          <li>Educational tips throughout gameplay</li>
+        </ul>
+        <a href="cyber-defense.html" class="play-button">🎯 Play Now</a>
+      </div>
+
+      <!-- Cyber Incident Response Simulator -->
+      <div class="game-card">
+        <div class="game-icon">🎯</div>
+        <h2 class="game-title">Cyber Incident Response Simulator</h2>
+        <p class="game-description">
+          Make critical decisions in realistic cybersecurity scenarios. Handle ransomware attacks,
+          phishing incidents, data breaches, and more. Learn through interactive tabletop simulation.
+        </p>
+        <ul class="game-features">
+          <li>6 realistic cybersecurity scenarios</li>
+          <li>Multiple choice decision-making</li>
+          <li>Educational feedback for each choice</li>
+          <li>Score-based performance rating</li>
+        </ul>
+        <a href="falling-game.html" class="play-button">🎮 Play Now</a>
+      </div>
+    </div>
+
+    <div class="back-link">
+      <a href="/">← Back to Main Site</a>
+    </div>
+  </div>
+</body>
+</html>
diff --git a/images/assets/learning.png b/images/assets/learning.png
new file mode 100644
index 0000000000000..d5b5316bab83a
Binary files /dev/null and b/images/assets/learning.png differ
diff --git a/images/assets/test.txt b/images/assets/test.txt
new file mode 100644
index 0000000000000..30e59bf86a4e2
--- /dev/null
+++ b/images/assets/test.txt
@@ -0,0 +1 @@
+he
\ No newline at end of file
diff --git a/index.html b/index.html
index 5e0cb3ee5773d..0fd9067f45850 100644
--- a/index.html
+++ b/index.html
@@ -1,18 +1,5 @@
 ---
-layout: default
+layout: home
+author_profile: true
 ---
 
-<div class="posts">
-  {% for post in site.posts %}
-    <article class="post">
-
-      <h1><a href="{{ site.baseurl }}{{ post.url }}">{{ post.title }}</a></h1>
-
-      <div class="entry">
-        {{ post.excerpt }}
-      </div>
-
-      <a href="{{ site.baseurl }}{{ post.url }}" class="read-more">Read More</a>
-    </article>
-  {% endfor %}
-</div>
\ No newline at end of file
diff --git a/tags.md b/tags.md
new file mode 100644
index 0000000000000..05ebacb63781f
--- /dev/null
+++ b/tags.md
@@ -0,0 +1,6 @@
+---
+layout: tags
+title: "Posts by Tag"
+permalink: /tags/
+author_profile: true
+---