Posts

Beyond the Perimeter: Deciphering the Brain of Zero Trust Architecture

Image
As we transition into a cloud first era, AI driven security landscape in 2026, the traditional moat-and-castle defence has collapsed already. Many organizations cliam to "do Zero Trust". Came across the NIST 800-207 (https://csrc.nist.gov/pubs/sp/800/207/final) standards. In this first part of my series on Zero Trust Architecture (ZTA), I want to analyze the most critical—and often misunderstood—components: the Policy Decision Point (PDP) and the Policy Enforcement Point (PEP) . 1. The Policy Decision Point (PDP): The Strategic Brain The PDP is the "intelligence" of your security stack. It doesn't just check passwords; it evaluates a complex trust algorithm based on: Subject Integrity: Is the user's biometric signature consistent? Device Posture: Is the OS patched, and is the EDR (Endpoint Detection and Response) active? Contextual Signals: Is the request coming from an unusual IP or at an atypical time? The Technical Gap: Most current PDPs are too stat...

Cybersecurity

Image

CA Authority? What is that?

Certificate Authority (CA) is essentially the "Root of Trust." In our clubhouse story, the CA is the governing body that issues the official IDs. Setting this up with OpenSSL is a two-step dance: creating a private key and then the self-signed root certificate. 1. Creating the CA Run these commands in your terminal to generate your own "Master Key" and the "Public ID" for your CA: # 1. Create the Private Key (The "Stamp Maker" - Keep this secret!) openssl genrsa -out MyClubhouseCA.key 2048 # 2. Create the Root Certificate (The "Official Seal") openssl req -x509 -new -nodes -key MyClubhouseCA.key -sha256 -days 3650 -out MyClubhouseCA.pem 2. What does the CA Certificate actually say? When you inspect that .pem file (using openssl x509 -in MyClubhouseCA.pem -text -noout ), it’s essentially a digital passport. For a 12-year-old, you can explain that it contains three main "sections": A. The "Who Issued This?" (Subject ...

The Secret Handshake (Identification vs. Authentication)

Image
  1. The Membership Card (Identification) Imagine your son, Sai Krishna, wants to enter a high-tech "Gamers Clubhouse" in San Ramon. Identification is him walking up to the door and saying, "I’m Sai Krishna." * In the tech world, this is the Username or Email . It’s public info. Anyone can say they are him. 2. The Secret Handshake (Authentication) The bouncer at the door doesn't just take his word for it. He says, "If you’re really Sai Krishna, show me the secret handshake." Authentication is the act of proving that identity. It’s the Password . Only the real Sai Krishna and the Clubhouse bouncer know what that handshake looks like. 3. How the "Clubhouse" (Server) Remembers In the old days of the internet, every time you wanted to go to a different room in the clubhouse (like the Snack Bar or the Game Room), the bouncer would stop you and ask for the handshake again. That’s annoying! To fix this, the bouncer gives you a Hand Stamp once y...

Data structure Feast

To help your readers remember the "Big Five" data structures, let’s move away from the computer and imagine we are organizing a massive Tamil Community Feast . Each data structure is simply a different way to handle the guests, the food, and the supplies! 1. The Array: The Fixed Dining Table Imagine a long dining table with exactly 10 chairs bolted to the floor. Each chair has a number (an index) from 0 to 9. The Rule: You know exactly where everyone is sitting. If you want to find the person in chair #4, you walk straight to it. The Catch: If an 11th guest arrives, you can't just "add a chair." You have to buy a whole new, bigger table and move everyone over! Best for: When you know exactly how many items you have and need to find them instantly. 2. The Linked List: The "Follow the Leader" Line Instead of bolted chairs, imagine guests standing in a line. Each person holds a small sign with the name of the person standing behind them. The Rule: To ...

Debth First

In our last post, we explored how BFS ripples out like a pebble in a pond. Today, we’re looking at its more adventurous cousin: Depth-First Search (DFS). If BFS is a "layer-by-layer" explorer, DFS is a "dead-end" explorer. What is DFS? Imagine you are exploring a dark cave with multiple branching tunnels. Instead of checking the entrance of every tunnel first, you pick one path and walk as far as you can until you hit a wall. When you can't go any further, you backtrack to the last fork in the road and try the next path. This "go deep before you go wide" approach is the heart of DFS. The "Stack" Logic: LIFO While BFS uses a Queue (First-In, First-Out), DFS uses a Stack (Last-In, First-Out). Think of a stack of cafeteria trays. The last tray you put on top is the first one you take off. In DFS, the last "branch" you discover is the first one you explore to its very end. A Quick JavaScript Example Because DFS is about going deep and t...

Breadth First Search

In my previous post about Queues, I mentioned that they are the "best friend" of an algorithm called Breadth-First Search (BFS). If you’ve ever wondered how GPS finds the shortest route or how LinkedIn knows someone is a "2nd-degree connection," you’re looking at BFS in action. What is BFS? BFS is a way of "searching" through a tree or a graph. Unlike other methods that dive deep into one branch until they hit the bottom, BFS explores layer by layer. Imagine you drop a pebble into a still pond. The ripples spread out in perfect circles, hitting everything nearby first, then moving to things further away. That is exactly how BFS works. The "Layer" Logic Think of it like searching for a specific book in a library:  * Level 0: You start at your current shelf.  * Level 1: You check all the shelves immediately next to you.  * Level 2: You check the shelves next to those. Because you check everything at Level 1 before moving to Level 2, BFS is guarante...