<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kilobyte Zero on Medium]]></title>
        <description><![CDATA[Stories by Kilobyte Zero on Medium]]></description>
        <link>https://medium.com/@kilobytezero?source=rss-30a4e0805cf7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BHPVxEhdlvkm9YnfimMDJQ.png</url>
            <title>Stories by Kilobyte Zero on Medium</title>
            <link>https://medium.com/@kilobytezero?source=rss-30a4e0805cf7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:11:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kilobytezero/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Explain Like I’m Five: OWASP API Top 10 — Excessive Data Exposure]]></title>
            <link>https://medium.com/@kilobytezero/explain-like-im-five-owasp-api-top-10-excessive-data-exposure-c10428d483ff?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c10428d483ff</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[owasp]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Mon, 05 Jun 2023 13:01:02 GMT</pubDate>
            <atom:updated>2023-06-05T13:01:02.455Z</atom:updated>
            <content:encoded><![CDATA[<h3>Explain Like I’m Five: OWASP API Top 10 — Excessive Data Exposure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*TBmR0icbXi35_2YsOUBdfw.png" /><figcaption>Marvel’s Inferno</figcaption></figure><p>Imagine you’re a superhero with special powers that let you withstand fires. Firefighters all around the country could really use your help saving lives when people are trapped inside of fiery buildings. To help coordinate your availability and make it easier for firefighters to reach out to you, they use a special tool called APInferno, which is an API you designed just for this purpose.</p><p>Think of APInferno as a digital connection between you and the firefighters. They can use this tool to find out your scheduling information and see if you’re available to help with their firefighting efforts. It’s like a system that allows them to send you a message asking, “Hey, superhero, can you come to the rescue?”</p><p>You’ve got APInferno hooked up to your supersuit, so you can see the requests for your help as they come in. Since it’s already connected to your supersuit, you also decided to give APInferno an extra feature specifically for your medical sidekick so they can monitor your live vitals while you’re out in the field. It includes information like your real name, heart rate, and body temperature.</p><p>You were in a hurry, so you didn’t build APInferno with its own system to filter or control sensitive data like your health information. Instead, it sends out ALL of your scheduling information AND your secret info every time, and it relies on the firefighters’ computers to filter out the secret info when it pops up on their screen. If a firefighter’s computer malfunctions and doesn’t actually filter it out like your API was hoping it would, the firefighters might see all the data, including your real name that you’ve been trying to keep a secret!</p><p>Excessive data exposure isn’t the same thing as getting hacked. It’s not the firefighter’s fault that their computer didn’t filter it right and they saw your name. Instead, it was your fault for sending everything all at once and just hoping their computer would work right.</p><p>To prevent excessive data exposure, never rely on the client side. This means don’t trust the other person’s computer to filter it out and keep the secret things hidden. If you want to keep it hidden from someone, you shouldn’t even send it in the first place! When APInferno is sending out your secret information, you need to put into it’s coding to block everyone else from receiving it except for your sidekick.</p><p>Read more about OWASP’s API Top 10 over at their website: <a href="https://owasp.org/www-project-api-security/">https://owasp.org/www-project-api-security/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10428d483ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain Like I’m Five: OWASP API Top 10 — Broken User Authentication]]></title>
            <link>https://medium.com/@kilobytezero/explain-like-im-five-owasp-api-top-10-broken-user-authentication-7f5fdd5172b2?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f5fdd5172b2</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Fri, 02 Jun 2023 13:02:21 GMT</pubDate>
            <atom:updated>2023-06-02T13:02:21.930Z</atom:updated>
            <content:encoded><![CDATA[<h3>Explain Like I’m Five: OWASP API Top 10 — Broken User Authentication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*szFzAetmm4AfWfUTMZRpiA.png" /><figcaption>Everyman in the DC Comics</figcaption></figure><p>Let’s talk about Everyman, whose real name is Hannibal Bates. He is a villain from DC Universe who has a special power that allows him to change his appearance to look like anyone he wants. Everyman can alter his physical appearance, including his facial features, body shape, and even voice. He can also mimic the DNA of the person he transforms into. This means he can replicate their biological traits, such as fingerprints, retinal patterns, and even genetic markers. It allows him to fool biometric scanners and other identity verification systems that rely on biological characteristics.</p><p>Now, imagine there’s a secret club for superheroes called SuperClub, and they have a guard with a scanner at the doorway that only checks their appearance and biometrics before they’re allowed into the clubs. Everyman could change his appearance and DNA to seem like a real superhero, such as Flash. Since the checking process isn’t robust enough and only checks his biometrics, it wouldn’t recognize that Everyman is actually pretending, and the guard is no help because they think that he does look exactly like Flash. The weak, broken system would let him into SuperClub, thinking he’s a real superhero.</p><p>Once inside, Everyman could cause all sorts of trouble. He might try to steal the special gadgets, secrets, or even try to harm the actual superheroes.</p><p>In the context of an API, someone like Everyman could exploit broken user authentication. Everyman has someone else’s correct and accurate biometrics, the same way an attacker can actually have someone’s correct combination of a username and password. With that information they can pretend to be someone else, like a trusted user or a legitimate program, by tricking the API’s broken security measures. Now they could gain access to the API and try to do things they’re not supposed to, like stealing or manipulating information.</p><p>To prevent this, it’s important to fix the broken user authentication in the API. One way to do this is to implement multi-factor authentication (MFA). For instance, in addition to the biometrics scan, let’s say the second factor is a unique code that the superheroes receive on their registered device. Everyman would have to have the real person’s phone too in order to show the code to the guard, which could be more difficult for him to obtain. Another measure of authentication they could use is to have a set of three special questions that only the superhero would know the answer to that have to be answered properly before entering. For example, Everyman was caught during an episode of The Flash while impersonating Flash because he used his left hand, not realizing that Barry Allen was right-handed.</p><p>Read more about OWASP’s API Top 10 over at their website: <a href="https://owasp.org/www-project-api-security/">https://owasp.org/www-project-api-security/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f5fdd5172b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain Like I’m Five: OWASP API Top 10— Broken Object Level Authorization]]></title>
            <link>https://medium.com/@kilobytezero/explain-like-im-five-owasp-api-top-10-broken-object-level-authorization-67818af4c049?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/67818af4c049</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[computers]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Thu, 01 Jun 2023 13:01:45 GMT</pubDate>
            <atom:updated>2023-06-01T13:01:45.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e6q_Vl-0kqBUWw-3MrWf4Q.jpeg" /></figure><p>You have a big, special toy box with lots of different compartments inside. Your friends don’t have a toy box so they gave you their toys to keep safe in your special box. When they give you their toys to keep safe, you decide to put locks on the compartments and make sure each of your friends have their own key.</p><p>But there’s a problem! Sometimes, the toy box gets a little bit broken, and your friends can open compartments they’re not supposed to. They might take out toys that are meant for someone else or even mess up the toys inside. They could take someone else’s Barbie out of the toybox and dress her in different clothes, which would disappoint your other friend when they come back to see she was changed without them knowing. Or worse, someone could take the Barbie and not give it back!</p><p>In the context of an API, it’s a bit similar. An API is like a special way for different computer programs to talk to each other and share information. The locks and keys you used to secure your toybox are like requiring a username and password to be able to access some information that an API has. But just like the toy box, sometimes the API has a problem, and it allows access to parts of the information that it shouldn’t.</p><p>This problem is called “broken object level authorization.” It means that the API doesn’t properly control who can access specific pieces of information. It’s like the compartments in your toy box being open when they shouldn’t be.</p><p>It’s important to fix this problem in the API and make sure that only the right programs can access the specific information they’re supposed to, just like making sure only your friends play with the right toys in the right compartments. This makes sure that everything stays organized and secure.</p><p>Read more about OWASP’s API Top 10 over at their website: <a href="https://owasp.org/www-project-api-security/">https://owasp.org/www-project-api-security/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67818af4c049" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain Like I’m Five: Hash Functions]]></title>
            <link>https://medium.com/@kilobytezero/explain-like-im-five-hash-functions-2d824bddc40?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d824bddc40</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[computers]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Wed, 31 May 2023 13:02:15 GMT</pubDate>
            <atom:updated>2023-05-31T13:02:15.392Z</atom:updated>
            <content:encoded><![CDATA[<p>You have a bunch of toy ninjas, and each one of them has a unique personality and skillset. The problem is all your ninja toys look the exact same! It’s really hard to tell them apart.</p><p>You find a special machine that does what is called a hash function. It can look at your ninja, take its unique personality and skillset, and give it a super special name (called a hash value). The machine isn’t scrambling up words using a special code or anything, it’s just giving your ninja a really unique name. Even if you have another ninja with a similar personality that can do all the same ninja moves, it doesn’t matter because your special machine is <em>super</em> precise when it’s naming them — it can detect even the tiniest difference in their personalities.</p><p>This is really helpful when your ninjas all come back from their missions. What if one of the bad guys convinced your ninja to become a bad guy too, how would you know? They all look the same, so when they get back from the mission you use your special machine again to check on your ninjas. If the special machine shows you the same hash value for your ninja, then everything is good. But if it prints out a new hash value for one of your ninjas, you know something has changed. Maybe the bad guys did convince him to be bad, or maybe he just picked up a new skill while he was away. But now you know you should look into it more and see.</p><p>The same way you do this with your ninjas, you want to make sure that the files you’re downloading from the internet are safe and that the bad guys haven’t messed them up. Just like your special machine, the hash function is super precise, too. Even if just one letter in a document changes, it prints out an extremely different new name.</p><blockquote>EXAMPLE</blockquote><blockquote>MD5 hash of the word “ninja” — 3899dcbab79f92af727c2190bbd8abc5</blockquote><p>If a good guy tells you the hash value of the file you want to download from their site and it doesn’t match up with the one you download, then you know something could be wrong. Maybe someone hacked into their website and put a bad file on it, or maybe the good guys updated it and forgot to tell you the new hash value. But at least you know you should look at it more closely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d824bddc40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explaining JSON Web Tokens (JWT) with Spider-Man]]></title>
            <link>https://medium.com/@kilobytezero/explaining-json-web-tokens-jwt-with-spider-man-fb4cf2474cf4?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb4cf2474cf4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[computers]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[spider-man]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Fri, 26 May 2023 13:01:44 GMT</pubDate>
            <atom:updated>2023-05-26T21:28:01.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3SJitiB_Vis3L4nuro_FQ.png" /><figcaption>Spider-Man using a computer</figcaption></figure><p>Imagine your name is Peter Parker, and you’re a really normal boy who goes to school and lives with his aunt and uncle. One day you were bitten by a really special spider that gave you cool spider abilities, and now you have a secret superhero identity as Spider-Man. You don’t want anyone except for the other good guy superheroes to know that Peter Parker is actually Spider-Man.</p><p>There’s this secret superhero lair you need to get into. They only let in superheroes who are dressed in their suits and can also prove their identity. There’s a big problem though. The only way into the club is through a door on a really busy street. You could just show them your driver’s license with your real name on it, but if someone walking by on the busy sidewalk sees it then they’d know that Peter Parker is Spider-Man, and that could be bad!</p><p>A cool guy named Tony Stark comes to the rescue. He actually owns the secret superhero club. All of the superheroes know Tony, they know that he is really good with technology, and they trust him with their secret identities. He makes special ID cards for them that we will call a JWT, which is short for JSON Web Token (the cool kids pronounce “JWT” as “jot”). These ID cards mean that you only have to show your driver’s license to Tony once so you can get your JWT created. Now you don’t have to show your real driver’s license over and over again outside the club where someone could walk by, look over your shoulder, and see your real name. It’s much safer for you to prove your identity to the good guys using your JWT.</p><p>Just like Peter Parker and Spiderman, we also have two identities when we are using a web app or a website and they are both very important. We have our regular identity when we sign in with our username and password, and we really want to make sure we share that as few times as possible in case somebody else is on our computer network and sees it. After we sign in with our username and password, the other computer (called a server) gives us back an encrypted, secret identity that we can use to talk to the website, called a JWT.</p><h3>The Components of a JWT</h3><p>A JWT has three components: a header, the payload, and the signature. Let’s take a look at each one.</p><p><strong>Header:</strong></p><pre>{<br>&quot;alg&quot;: &quot;HS256&quot;,<br>&quot;typ&quot;: &quot;JWT&quot;<br>}</pre><p>The JWT header contains information about what encryption algorithm (“alg”) Tony used to create the signature and the type of token it is (“typ”).</p><p><strong>Payload:</strong></p><pre>{<br>&quot;sub&quot;: &quot;Peter Parker&quot;,<br>&quot;iss&quot;: &quot;Stark Industries&quot;,<br>&quot;iat&quot;: 1651158549,<br>&quot;exp&quot;: 1651158649,<br>&quot;isSpiderman&quot;: true,<br>&quot;superpowers&quot;: [&quot;web-slinging&quot;, &quot;superhuman strength&quot;, &quot;spider-sense&quot;]<br>}</pre><p>As he’s making the JWT, Tony puts in some information on it that tells the secret superhero club who you are. All the information about you is called the “payload” of the JWT. Peter Parker is the subject (“sub”) and Stark Industries is the issuer (“”iss”). Tony also added some helpful information, like a verification that you are Spider-Man and your superpowers.</p><p>One time, a villain managed to steal one of the JWTs and used it to get into the superhero club. After that happened, Tony added two timestamp fields to the payload: “iat” (issued at) and “exp” (expiration time). These payloads help to make sure the JWT expires after a short time so that hopefully a thieving villain doesn’t get the chance to use it. It also means that the timestamp values are different every time the JWT is created. That changes the signature of the whole card so that a villain can’t use an expired JWT.</p><p><strong>Signature:</strong></p><pre>HMACSHA256(<br>base64UrlEncode(header) + &quot;.&quot; +<br>base64UrlEncode(payload),<br>secretKey<br>)</pre><p>This is the special calculation Tony uses to make the signature. See how the signature calculation includes both the header and the payload, so it’s super unique for each superhero that has a JWT.</p><p><strong>The Final Product:</strong></p><p>Assuming the secretKey in the signature is “avengersassemble”, the final JWT could look like:</p><pre>eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJQZXRlciBQYXJrZXIiLCJpc3MiOiJTdGFyayBJbmR1c3RyaWVzIiwiaWF0IjoxNjUxMTU4NTQ5LCJleHAiOjE2NTExNTg2NDksImlzU3BpZGVybWFuIjp0cnVlLCJzdXBlcnBvd2VycyI6WyJ3ZWItc2xpbmdpbmciLCJzdXBlcmh1bWFuIHN0cmVuZ3RoIiwic3BpZGVyLXNlbnNlIl19.ZlU8O70paOT8_HoFfWWZCBxJceunUOGZGbMXX9zjhXY</pre><p>Now when you go to the secret superhero club, you can show them your JWT instead of your driver’s license. They’ll make sure it’s valid, and if everything checks out, they know that you’re really Spider-Man and they let you in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb4cf2474cf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain Like I’m Five: How APIs Work with HTTP Requests]]></title>
            <link>https://medium.com/@kilobytezero/explain-like-im-five-how-apis-work-with-http-requests-c7d50b668475?source=rss-30a4e0805cf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7d50b668475</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[computers]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[https]]></category>
            <dc:creator><![CDATA[Kilobyte Zero]]></dc:creator>
            <pubDate>Thu, 25 May 2023 17:28:11 GMT</pubDate>
            <atom:updated>2023-05-25T23:05:28.968Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*kNSA3tNHnOQ0_eKRMvhCDw.png" /></figure><p>You have a lot of toys, and you decide you want to share your toys with your friend. But your friend doesn’t know what toys you have or how to play with them. So you create a list of your toys and their instructions and you give it to your friend.</p><p>This list is like an API — it’s a way for your friend to know what toys are available and how to play with them.</p><p>Now, when your friend decides they want to play with a specific toy, they can ask you for it. This is like making an HTTP GET request — your friend is asking you if they can have that particular toy.</p><p>If your friend wants to play with a toy that you don’t have, they can ask you to buy it for them. This is like making an HTTP POST request — your friend is giving you information (what toy to buy) so that you can create something new (a new toy to add to your collection).</p><p>Let’s say your friend already has a toy, but it’s broken and needs fixing. They can give it to you to fix, and you can repair it for them. This is like making an HTTP PUT request — your friend is giving you information (what toy to fix and how to fix it) so that you can update an existing toy.</p><p>If your friend doesn’t want to play with a toy anymore and wants you to get rid of it, they can ask you to throw it away. This is like making an HTTP DELETE request — your friend is giving you information (what toy to get rid of) so that you can remove it from your toybox.</p><p>Essentially, an API is like a toy list that helps you and your friend communicate about what toys are available and what you can do with them. The different types of requests (like GET, POST, PUT, and DELETE) are like different ways your friend can ask you for a toy or give you information about a toy.</p><p>—</p><p>Want to read more of my content? Visit <a href="https://kilobytezero.wordpress.com/">kilobytezero.wordpress.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7d50b668475" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>