<?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 Hania Khan on Medium]]></title>
        <description><![CDATA[Stories by Hania Khan on Medium]]></description>
        <link>https://medium.com/@hk6535127?source=rss-ac59cbf01b0b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IiO9DrFxE_o7PKwciP5_Uw.jpeg</url>
            <title>Stories by Hania Khan on Medium</title>
            <link>https://medium.com/@hk6535127?source=rss-ac59cbf01b0b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:12:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hk6535127/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[What Attackers Can Learn About You Using Only Public Data]]></title>
            <link>https://osintteam.blog/what-attackers-can-learn-about-you-using-only-public-data-aa7dbc57c507?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa7dbc57c507</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[data-security]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Fri, 08 May 2026 05:57:39 GMT</pubDate>
            <atom:updated>2026-05-08T05:57:39.560Z</atom:updated>
            <content:encoded><![CDATA[<h4>I searched for myself. What I found was unsettling.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*ExsTQpGvDL8_SjFf" /><figcaption>Social Media Privacy: AI Generated image</figcaption></figure><p>I decided to play attacker for an afternoon. No hacking tools, no illegal methods. Just a browser and public search engines. I searched for myself. Within an hour, I found my home address, my email address, my employer, and a photo of my house from a real estate listing. I found my birthday, my family members’ names, and a password I would reuse across three old accounts that had been breached years ago. None of this was hidden. It was all publicly available. I just never thought to look.</p><h3>Your Social Media Is a Map</h3><p>Attackers start with your social profiles. Your LinkedIn shows your job title, company, and sometimes your direct reports. Your Twitter reveals your opinions, your schedule, and your location. Your Instagram tells them where you eat, where you vacation, and who your friends are.</p><p>A single post about a business trip gives them dates and a hotel name. A photo of your desk shows which computer you use. A comment about a frustrating day makes you more likely to fall for a phishing email. Every post is a clue. Alone, each clue is harmless. Together, they build a profile more detailed than you’d believe.</p><h3>Your Old Accounts Never Die</h3><p>Remember that forum you joined ten years ago? That old shopping account you forgot about? Those profiles still exist. And many of them have been hacked. Attackers buy lists of breached credentials for pennies. They try those same passwords on your email, your bank, and your work accounts. If you reused passwords, they are in.</p><p>I found my own old password in a breach database. I would use it for a gaming site in college. I stopped using it years ago, but until I changed it everywhere, I was still at risk.</p><h3>Your Address Is a Few Clicks Away</h3><p>Search your name plus your city. You will probably find your address on a people search site. These sites aggregate public records, property data, and voter registration. Your address is not secret anymore. Attackers use this for physical threats. They know where you live, what car you drive, and sometimes even your daily routine. All from free public data.</p><h3>Your Employer Leaks More Than You Think</h3><p>Company websites list employees. Job postings reveal technology stacks. Press releases announce partnerships and new office locations. An attacker studying your company might learn that you use Salesforce, run on AWS, and have a data center in Chicago. That is enough to start planning an attack.</p><p>And if you have ever posted about a work problem on social media, you have given them even more.</p><h3>What You Can Do About It</h3><p>You can not make everything private. But you can reduce your exposure.</p><ol><li>Audit your social media. Remove posts that reveal too much.</li><li>Set profiles to private. Do not accept connection requests from strangers.</li><li>Use a password manager with unique passwords everywhere. Check haveibeenpwned (the concept) to see if your emails appear in breaches.</li><li>Remove yourself from people search sites. Most have opt‑out forms. It takes time, but it works.</li><li>Think before you post. Does the world need to know your location, your schedule, or your family’s names?</li></ol><h3>The Bottom Line</h3><p>Attackers do not need to hack you. They just need to search for you. The information you have already published is often enough to steal your identity, trick you into clicking, or even find your front door. You can not control every piece of data about you. But you can stop adding to the pile. And that is a good place to start.</p><p>Have you ever searched for yourself online? Try it. You might be surprised. Clap if you are auditing your digital footprint today, and follow for more practical security advice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa7dbc57c507" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/what-attackers-can-learn-about-you-using-only-public-data-aa7dbc57c507">What Attackers Can Learn About You Using Only Public Data</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Cybersecurity Is Becoming Everyone’s Responsibility]]></title>
            <link>https://meetcyber.net/why-cybersecurity-is-becoming-everyones-responsibility-6dbdae965cb6?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dbdae965cb6</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[online-safety]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Mon, 04 May 2026 20:36:22 GMT</pubDate>
            <atom:updated>2026-05-04T20:36:22.984Z</atom:updated>
            <content:encoded><![CDATA[<h4>It used to be the IT department’s problem. Now it is yours.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*byo5-ytjbDgI-sqz.jpeg" /><figcaption>cyber security is everyone’s responsibility:AI Image</figcaption></figure><p>I used to believe that cybersecurity was another person’s responsibility. I would have poor passwords, click on all links, not update software, and rely on others to do all those things for me. Whenever something happened, I just needed to call IT.<br>And then, I saw my colleague lose all access to his accounts after. One phishing email. One moment of distraction. Her entire digital life was locked, and IT could not undo the damage quickly enough. That is when I realized. The firewall can not protect you from yourself. Security is not something you outsource anymore.</p><h3>The Perimeter Is Gone</h3><p>When we talk about working from an office in the old days, we imagine ourselves sitting at a desk with a computer protected by corporate firewalls. We now access our email using our phone in a café and use a personal device at home to open company files. You share documents through cloud apps that live somewhere on the internet.</p><p>The old castle with a moat is gone. There is no single wall to defend. Every device you own is now a potential entry point. And you are the one holding that device.</p><h3>Attackers Target People, Not Systems</h3><p>Hackers have figured something out. It is easier to trick a person than to break through encryption. They send text messages pretending to be your bank. It refers to social engineering tricks that include creating phishing sites that resemble the real ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3uJvHxWxUThA8O4M" /><figcaption>Photo by <a href="https://unsplash.com/@teamnocoloco?utm_source=medium&amp;utm_medium=referral">Team Nocoloco</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The most sophisticated security tools in the world can not stop you from typing your password into a fake website. That decision happens in your head, not in a firewall. So now, attackers do not bother with the system. They go straight for you.</p><h3>Your Personal Data Is Everywhere</h3><p>You might think, “I do not work for a bank. Nobody wants my data.” But attackers do not just want money. They want your email to reset passwords on other accounts. They want your contacts to send more phishing attacks. They want your location, your habits, your connections.</p><p>Every piece of information you share online becomes a puzzle piece. Alone, it is harmless. Together, it is a blueprint for identity theft or fraud. Protecting that data is not just your company’s responsibility. It is yours.</p><h3>Small Habits Create Big Protection</h3><p>The good news is that basic security is not complicated. You do not need to become an expert.</p><p>1: Use a password manager. One strong master password, and it remembers the rest. No more reusing the same password everywhere.</p><p>2: Turn on two‑factor authentication. That extra step might feel annoying, but it stops almost all automated attacks.</p><p>3: Think before you click. That urgent message can wait while you check the sender’s address. Hover over links before tapping them.</p><p>4: Update your devices. Those notifications fix known holes that attackers are actively exploiting.</p><h3>It is Not About Fear</h3><p>This is said not for the purpose of scaring you. Fear stops everything. Action motivates. The idea here is that the concept of cybersecurity has ceased to remain some sort of esoteric knowledge handled by experts away from public view. Cybersecurity is about taking charge of your habits, taking pause before you reveal too much, and questioning if the message really came from your boss. Everyone making small contributions adds up to building a better system. The attackers move on to easier targets.</p><h3>The Shift Is Already Here</h3><p>Finally, businesses have understood that security training must be incorporated into the company’s culture beyond the annual slide show presentation. But culture does not change because leadership declares it. It changes because individuals decide to care. You decide to lock your screen when you walk away. You decide to report that suspicious text message.</p><p>Cybersecurity is becoming everyone’s responsibility because the threats face everyone. Not just corporations. Not just governments. You. And the sooner we all accept that, the safer we all become.</p><p>What is one small security habit you have changed recently? Share it in the comments; your tip might help someone else. Clap if you believe security is a team sport, and follow for more real talk about staying safe in a connected world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dbdae965cb6" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/why-cybersecurity-is-becoming-everyones-responsibility-6dbdae965cb6">Why Cybersecurity Is Becoming Everyone’s Responsibility</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Silent Rise of Cybersecurity Careers]]></title>
            <link>https://medium.com/write-a-catalyst/the-silent-rise-of-cybersecurity-careers-a6427d3775b7?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6427d3775b7</guid>
            <category><![CDATA[cyber-jobs]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Sun, 03 May 2026 14:46:35 GMT</pubDate>
            <atom:updated>2026-05-03T14:46:35.503Z</atom:updated>
            <content:encoded><![CDATA[<h4>While everyone chases coding bootcamps, another field is quietly booming.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*i6492wP6u2RRiv1s.jpg" /><figcaption>cybersecurity risk:AI Image</figcaption></figure><p>I remember when cybersecurity was not a career. It was a side gig for bored IT guys. Nobody dreamed of becoming a security analyst. Nobody talked about job security or six‑figure salaries. Now, I cannot scroll through LinkedIn without seeing another “I got my first security role” post. The demand is exploding, but most people are not noticing. They are still obsessed with web development and data science. Meanwhile, cybersecurity careers are rising in silence. And there’s never been a better time to jump in.</p><h3>The Attention Is Elsewhere</h3><p>Walk into any career fair. The buzz is all about AI, machine learning, and full‑stack development. Students flock to those booths. The cybersecurity table sits quietly in the corner. That is the opportunity. Everyone is fighting for the same coding jobs while security roles go unfilled. Companies are desperate. They are hiring people with no traditional background because they have no other choice.</p><p>I have seen history majors become threat analysts. Former teachers become compliance officers. Retail managers transition into incident response. The door is wide open.</p><h3>Why Nobody Notices</h3><p>Cybersecurity does not have the glamour of building the next viral app. You were not seen as a security analyst on the cover of a tech magazine. The work is often behind the scenes, preventing disasters that never happen. That is the irony. When security works perfectly, nothing happens. No breaches, no headlines, no drama. So nobody talks about it. But the jobs are there. They are multiplying every year. And the pay keeps climbing because supply can’t keep up with demand.</p><h3>It is Not Just for Hackers</h3><p>People think cybersecurity means living in a hoodie and breaking into systems. That is a tiny slice. Most security roles are not about hacking at all. Governance, risk, and compliance. Security awareness training. Policy writing. Vendor risk assessments. Incident coordination. These are people&#39;s jobs, not just tech jobs.</p><p>I know someone who spends her days teaching employees how to spot phishing emails. She loves it. She never writes a single line of code. But she prevents more breaches than most penetration testers. The field needs communicators, teachers, investigators, and project managers. Not just terminal wizards.</p><h3>The Stability Is Real</h3><p>Tech layoffs make headlines. But security teams are often the last to be cut. When money gets tight, you do not fire the people keeping your company from getting hacked. I have watched friends in development lose jobs while security folks stayed. Companies can delay a feature launch. They can not delay patching a critical vulnerability that is being exploited right now. That stability matters. Especially in an uncertain economy.</p><h3>The Path Is Surprisingly Simple</h3><p>A college degree in Computer Science is not necessary. In fact, I do not have a college degree myself. The majority of my friends who work in cybersecurity do not have one too. The first step you need to take is educate yourself about networks, operating systems, and command line operations. You can do that using free websites like TryHackMe. Pick your favorite topic among cloud security, information governance, or incident response. Do not attempt to master everything at once. Mastering just one particular specialty is enough. Highlight your expertise by making an online portfolio where you can showcase your practical knowledge and configurations of different lab assignments.</p><h3>The Silent Boom Continues</h3><p>The world is not getting less digital. Every new app, every smart device, every line of code creates more attack surface. And every new attack creates more demand for defenders. Cybersecurity careers are not trending on Twitter. They are not the hot topic at tech conferences. But they are growing steadily, quietly, and relentlessly. And for anyone willing to learn, there’s a seat at the table waiting.</p><p>What is holding you back from exploring cybersecurity? Or if you are already in it, what surprised you most? Drop a comment. Clap if you see the opportunity here, and follow for more honest career conversations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6427d3775b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/write-a-catalyst/the-silent-rise-of-cybersecurity-careers-a6427d3775b7">The Silent Rise of Cybersecurity Careers</a> was originally published in <a href="https://medium.com/write-a-catalyst">Write A Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Hackers Use OSINT Before Attacking]]></title>
            <link>https://osintteam.blog/how-hackers-use-osint-before-attacking-94787848e800?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/94787848e800</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[data-protection]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 23:55:33 GMT</pubDate>
            <atom:updated>2026-04-24T23:55:33.587Z</atom:updated>
            <content:encoded><![CDATA[<h4>They do not start with exploits. They start with Google.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZXWJZN0cEvQ71SId.jpeg" /><figcaption>Protect your OSINT investigation: AI-generated</figcaption></figure><p>I used to think hacking began with a terminal full of green text. Then I watched someone break into a company without typing a single exploit command. They just searched.</p><p>For three hours, they browsed LinkedIn, GitHub, and public forums. By the end, they had employee emails, internal server names, and a forgotten PDF with network diagrams. The attack had not even started yet, but they already had everything they needed.</p><p>This is OSINT, open-source intelligence. And it is the first step in almost every real attack.</p><h3>What Attackers Look For First</h3><p>Hackers do not guess passwords randomly. They find them. They search for employee names on LinkedIn, guess email formats, and check if those emails appear in past data breaches.</p><p>They look at job postings to learn what technology a company uses. A listing for a “Kubernetes administrator” tells them you run containers. “Salesforce developer” means customer data lives in Salesforce.</p><p>They browse GitHub for your company name. Developers often accidentally push API keys, internal scripts, or configuration files to public repositories. One search can hand over the keys to your kingdom.</p><h3>The Google Tricks They Use</h3><p>Attackers use advanced search operators to find exposed files. A simple search like this site:company.com ext: pdf might reveal internal reports. intitle: index of can uncover open directories full of logs or backups.</p><p>They look for login pages that are not meant to be public. Staging servers, admin panels, and development environments often have weak passwords or no authentication at all. All of this is legal. Google indexes everything. The attacker is just looking at what you accidentally left outside.</p><h3>Social Media Is a Goldmine</h3><p>A single employee’s social media post can tell an attacker everything. A photo of a badge reveals the access card system. A whiteboard in the background shows part of a network diagram. A comment about a business trip gives dates and locations for a targeted phishing attack. Attackers piece together small clues from dozens of posts. They learn who works where, who has access to what, and who might be easy to trick.</p><h3>The Email Harvest</h3><p>Once attackers have a few employee names, they guess email formats. first.last@company.com Or? They test these on password reset forms. The system either says &quot;user not found&quot; or confirms the account exists.</p><p>With valid emails, they check breach databases to see which passwords have been leaked from other sites. If an employee reused their work password on a hacked forum, the attacker now has a way in.</p><h3>How Defenders Fight Back</h3><p>You can not stop attackers from searching. But you can make their job harder. Audit your public footprint. Search for your own company on GitHub, Google, and social media. Remove anything that shouldn’t be public.</p><p>Train employees not to share sensitive details online. A single photo of a badge or a whiteboard can undo years of security work. Use email formats that aren’t predictable. And monitor for exposed credentials using breach notification services.</p><h3>The Bottom Line</h3><p>Most attacks do not start with a zero‑day exploit. They start with a search bar. Attackers spend hours or days gathering information before they ever touch your network.</p><p>The best defense is knowing what they can find. Run your own OSINT audit. See what is out there. Then clean it up. You can not hide everything. But you can stop giving away the keys.</p><p>Have you ever searched for your own company online? Try it. You might be surprised. Clap if you are auditing your digital footprint today, and follow for more defensive security insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94787848e800" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/how-hackers-use-osint-before-attacking-94787848e800">How Hackers Use OSINT Before Attacking</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Coding Mistakes That Create Security Vulnerabilities]]></title>
            <link>https://medium.com/illumination/5-coding-mistakes-that-create-security-vulnerabilities-1035d0b2f0cf?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1035d0b2f0cf</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[secure-coding]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[vulnerability]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 17:36:07 GMT</pubDate>
            <atom:updated>2026-04-24T17:36:07.837Z</atom:updated>
            <content:encoded><![CDATA[<h4>Small oversights in your daily work can open big doors for attackers.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*jT6BLAV6P3dbAfHv.jpeg" /><figcaption>Coding error</figcaption></figure><p>You write code that works. Tests pass. Features ship. Then someone breaks it in a way you never imagined. After reviewing hundreds of security issues, I have watched the same small mistakes appear across teams, languages, and experience levels.</p><p>Here are five coding habits that quietly invite attackers into your application.</p><h3>1. Trusting Whatever the User Sends</h3><p>You grab a parameter from the request and use it directly. A search term goes into a database query. A filename opens a local file. It works perfectly for normal users.</p><p>But attackers are not normal users. They send SQL instead of search terms. They use it ../../../etc/passwd as a filename. Your code obediently follows their instructions.</p><p>The fix is simple but non-negotiable: treat every piece of external data as hostile. Use parameterized queries for databases. Validate file paths against a whitelist. Never assume input is safe just because it looks normal.</p><h3>2. Hard-Coding Secrets Into Source</h3><p>An API key sits right there in the config file. A database password is hardcoded next to the connection logic. It is convenient for testing. Then the code gets pushed to a repository. Now, anyone with access to that repo, current employees, former contractors, or worse, a public GitHub mistake, has your keys. Rotating them becomes an emergency.</p><p>Keep secrets out of your codebase. Use environment variables or a dedicated secrets manager. Make it a rule from day one, not a cleanup task for later.</p><h3>3. Assuming Authentication Means Authorization</h3><p>You verify that a user is logged in. Great. And then you show them the user’s profile page using an ID in the <strong>URL: /profile?id=1234</strong>.<br>What will happen when the user changes the ID to 1235? If there were no ownership verification, another user’s personal information would be viewed right away.</p><p>This is known as an insecure direct object reference, and it is everywhere. Make sure the authorized user actually possesses the resource they are trying to access. Never assume that an ID is always correct.</p><h3>4. Validating Only on the Frontend</h3><p>Client‑side validation feels fast. You show an error instantly when someone types invalid input. But the browser is not your security boundary. The attacker can turn off JavaScript support in the browser, manipulate HTML, or simply send a POST request to your API without any additional data in the body.<br>When the backend relies on the client-side validation results, it will open a back door for the attackers. Make sure to validate all the data again when processing it on the backend side. The frontend validation serves the purpose of user experience improvement rather than security.</p><h3>5. Logging Too Much (or Too Little)</h3><p>You need logs to investigate incidents. But many developers log sensitive data, passwords, tokens, and credit card numbers because it is helpful for debugging. Now those secrets are sitting in log files, often with weaker access controls than the database.</p><p>The opposite problem is just as bad. Without logs, when something goes wrong, you have no trail to follow. You did not know who accessed what or when. Log what matters: authentication attempts, access to sensitive resources, and configuration changes. Never log secrets. Use structured logging and rotate logs regularly.</p><h3>The One Mindset That Fixes All Five</h3><p>Every mistake on this list comes from the same habit: coding for the happy path. You assume users will behave, secrets will stay secret, and nobody will tamper with requests.</p><p>Security demands a different question: “What is the worst thing someone could do with this code?” Ask that during every code review. Write tests for malicious input. Treat suspicion as a feature.</p><p>The best developers do not write perfect code. They write code that anticipates imperfection.</p><p>Which of these mistakes have you caught in your own code? Share honestly in the comments; we have all been there. Clap if you are committing to one change this week, and follow for more practical, secure coding advice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1035d0b2f0cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/5-coding-mistakes-that-create-security-vulnerabilities-1035d0b2f0cf">5 Coding Mistakes That Create Security Vulnerabilities</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bug Hunting Mistake That Slowed My Progress]]></title>
            <link>https://infosecwriteups.com/the-bug-hunting-mistake-that-slowed-my-progress-5597222e982d?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5597222e982d</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Sun, 19 Apr 2026 03:16:31 GMT</pubDate>
            <atom:updated>2026-04-19T03:16:31.105Z</atom:updated>
            <content:encoded><![CDATA[<h4>I spent months chasing the wrong targets. One change turned everything around.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*8HvRF0LgqbVdHgBK" /><figcaption>Common bug bounty mistakes that hackers exploit. <em>AI-generated image.</em></figcaption></figure><p>For six months, I was stuck. I ran scanners, tested every parameter, and stayed up late hunting bugs. The result? Duplicates aplenty and lots of frustration.<br>It seemed that I was on the right track. I was mastering new software, watching videos, and working my way through the most popular platforms. But nothing clicked.</p><p>Then I realized the mistake that was killing my progress. I was not hunting strategically. I was hunting randomly.</p><h3>The Popular Program Trap</h3><p>I kept joining the biggest programs on the platform. They had huge bounties and famous company names. Surely, that is where the money was.</p><p>But so did everyone else. Hundreds of hunters were scanning the same endpoints, testing the same parameters, submitting the same findings. By the time I found something, three people had already reported it.</p><p>I was competing against full‑time hunters who did this ten hours a day. I never stood a chance.</p><h3>The Shift That Changed Everything</h3><p>I stopped chasing big names. Instead, I looked for smaller programs with fewer hunters. New programs that had just launched. Obscure applications that no one talked about.</p><p>Within two weeks, I found my first valid bug. It was not critical. Just a low‑severity info leak. But it was mine. No duplicate. No rejection. That small win gave me confidence. I kept hunting in that program, learned its ins and outs, and found three more bugs in the next month.</p><h3>Why Depth Beats Breadth</h3><p>I used to jump from target to target. Test a few endpoints, run a scan, then move on. I never really understood any application deeply.</p><p>The hunters who consistently win do the opposite. They pick one program and live inside it for weeks. They map every endpoint, study every feature, and learn how the application thinks. When you know a target that well, you start noticing weird behavior. Things that don’t fit the pattern. Things that scanners would never catch.</p><h3>The Second Mistake: Rushing Reports</h3><p>Even after I started finding bugs, I was losing bounties. I would submit a finding quickly, hoping to beat the competition. But my reports were messy. Missing steps, unclear impact, bad screenshots.</p><p>Triagers would close them as “insufficient” or “needs more info.” Sometimes they would mark them as duplicates because I did not prove the impact clearly enough. I learned to slow down. Take better screenshots. Write reproduction steps that a tired triager could follow in thirty seconds. Explain why the bug actually mattered to the company.</p><p>My acceptance rate went from barely half to almost everything I submitted.</p><h3>The Mistake That Almost Made Me Quit</h3><p>The worst mistake was hunting alone. It seemed that I had to solve everything on my own. Reaching out seemed to be an admission that I wasn’t good enough at it. However, bug hunting can be quite lonely at times. When you struggle for hours, frustration accumulates. And without any help around, it’s difficult to avoid self-doubt.<br>This all changed once I found a community of a few people on Discord. They exchanged ideas, joked about their setbacks, and celebrated their successes. Whenever I struggled, I received some motivation from them. And whenever I received a reward, they rejoiced with me. Such support helped me go through even the hardest days.</p><h3>Three Pieces of Advice to a New Hunter</h3><p>First, ignore the big programs. Hunt where the competition is low. Small targets, new programs, forgotten subdomains.</p><p>Second, go deep on one target. Learn it as you build it. The bugs will reveal themselves when you understand how everything fits together. Third, find your people. The journey is hard enough alone. A good community makes it bearable and fun.</p><h3>The Progress You Can not See</h3><p>I still have dry weeks. Sometimes I go days without finding anything interesting. But I do not panic anymore. I know it is part of the process. The mistake that slowed me down was not a lack of skill. It was a lack of strategy. Once I fixed that, everything changed.</p><p>So if you are stuck right now, stop grinding. Take a step back. Look at where you are hunting and how you are hunting. The answer is probably simpler than you think.</p><p>What is the one mistake that slowed you down the most? Share honestly in the comments; we have all been there. Clap if this hit home, and follow for more real talk about the ups and downs of bug hunting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5597222e982d" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/the-bug-hunting-mistake-that-slowed-my-progress-5597222e982d">The Bug Hunting Mistake That Slowed My Progress</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Digital Security Matters More Than Ever]]></title>
            <link>https://medium.com/illumination/why-digital-security-matters-more-than-ever-5deae9604fca?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5deae9604fca</guid>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[online-safety]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 22:38:46 GMT</pubDate>
            <atom:updated>2026-04-18T22:38:46.849Z</atom:updated>
            <content:encoded><![CDATA[<h4>It is not about protecting data anymore. It is about protecting lives.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DgfLoYBRuEr5Hggj" /><figcaption>digital security importance:AI generated image</figcaption></figure><p>I used to think digital security was a corporate problem. Big companies, big budgets, big headaches. Not my concern. Then my neighbor’s small business got hacked. Ransomware locked every file. She lost customer orders, payroll records, and years of photos. The attackers wanted five thousand dollars. She did not have it. She closed her doors two months later. That is when I realized. Security is not about firewalls and encryption. It is about livelihoods. And at present, almost everyone is going about their business with an unlocked front door.</p><h3>Your Life Is Online Now</h3><p>Consider all that is online. Bank details, medical records, and education data for your kids. Personal photographs, messaging logs, and GPS tracking of where you have been. Even your video intercom and heating controls. Back in the day, a burglar would have needed to kick down your front door to rob you. These days, he could do it from a cafe halfway across the globe. Without even needing a battering ram. They just need one weak password.</p><h3>The Attacks Are not Sophisticated</h3><p>Here is what scares me. Most breaches do not use fancy zero‑day exploits. They use the same old tricks that have worked for years. Phishing emails that look like they are from your bank. Password reuse from a hacked forum. Software that never got updated. These are not genius hacks. They are laziness on the attacker’s part and carelessness on ours. And they still work. Every single day.</p><h3>It is Not Just About Money</h3><p>We focus on financial loss. But the real damage is deeper. Identity theft can take years to fix. Leaked medical records can not be un‑leaked. Stolen private photos can haunt someone forever. I have talked to people who lost their life savings. I have talked to people whose private messages were shared publicly. The shame, the fear, the helplessness, those scars do not heal with a credit monitoring service. Digital security is about protecting human dignity. That is why it matters.</p><h3>The Attackers Are Getting Smarter</h3><p>AI is changing the game. Phishing emails are nearly perfect now. No bad grammar, no strange URLs. They sound exactly like your boss, your bank, your friend. Voice cloning can mimic a family member asking for help. Deepfake videos can show a CEO authorizing a transfer. The old advice, “just look for red flags”, does not work anymore.</p><p>We need to think differently. Assume the message might be fake. Verify through another channel. Call back on a known number. Slow down.</p><h3>Small Habits Make a Big Difference</h3><p>You do not need to be a security expert. You just need a few good habits. Use a password manager. One master password, and it generates unique, strong passwords for every site. No more reuse. Turn on two‑factor authentication everywhere it is offered. That text message or authenticator app is the difference between “account compromised” and “attempt blocked.” Update your software. Those annoying notifications fix known vulnerabilities. Ignoring them is like leaving your front door unlocked.</p><p>Think before you click. That urgent email can wait sixty seconds while you check the sender’s address.</p><h3>The Stakes Keep Rising</h3><p>Every year, more of our lives move online. Healthcare, banking, education, work, relationships. The digital world is not separate from the real world anymore. It is the real world. When a hospital gets hacked, patients die. When a power grid gets hacked, cities go dark. When a school gets hacked, children’s data is sold to strangers. This is not dramatic. It is happening right now.</p><h3>You Have a Role to Play</h3><p>You do not have to become a cybersecurity professional. But you do have to care. Secure your own accounts. Help your family do the same. Talk to your organization about its efforts towards securing customer information. Support political figures who care about the protection of personal information online. The hackers are banking on your lackadaisical attitude or preoccupation. Do not help them. Digital security is now more crucial than ever since we can not live without it anymore. Not sometime in the future, but now.</p><p>What is one little security measure you have been implementing lately? Tell us in the comment section, perhaps you will inspire another person. Clap if you were prompted to evaluate your own cybersecurity practices by this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5deae9604fca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/why-digital-security-matters-more-than-ever-5deae9604fca">Why Digital Security Matters More Than Ever</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cybersecurity Learning Roadmap]]></title>
            <link>https://medium.com/write-a-catalyst/my-cybersecurity-learning-roadmap-def0a1d11781?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/def0a1d11781</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 20:56:21 GMT</pubDate>
            <atom:updated>2026-04-14T20:56:21.887Z</atom:updated>
            <content:encoded><![CDATA[<h4>No degree, no fancy bootcamp. Just curiosity, late nights, and a lot of trial and error.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MOOLOfsRUOTEDL0QwzJtDA.png" /><figcaption>A practical roadmap into cybersecurity. <em>AI-generated.</em></figcaption></figure><p>I did not start with a plan. I started with a question: “How do hackers actually break into things?” That question sent me down a rabbit hole. I watched videos, read forums, and downloaded tools I did not understand. I broke my own computer twice. I got frustrated. I almost quit.</p><p>But I kept going. And eventually, I figured out a path that worked. Here is the roadmap I wish I had from day one.</p><h3>Month One: The Fundamentals I Skipped at First</h3><p>I wanted to hack immediately. So I skipped the boring stuff. Big mistake. After wasting weeks running tools without knowing what they did, I went back to basics. I learned how networks actually work. IP addresses, ports, DNS, HTTP requests. Not deep enough to become a network engineer, just enough to understand what was happening when I typed a command.</p><p>I also forced myself to learn Linux. Not just clicking around, but using the terminal. Navigating directories, reading permissions, piping outputs. It felt slow, but it paid off fast.</p><h3>Month Two: Hands-On Without Real Targets</h3><p>I was not ready for real companies yet. So I practiced on legal playgrounds. I started with OverTheWire’s Bandit game. It taught me basic command-line skills through simple challenges. Then I moved to TryHackMe. Their beginner rooms walked me through actual attacks in a safe environment.</p><p>The key was doing, not watching. I stopped binging tutorials and started breaking things on purpose. Every time I got stuck, I searched for answers instead of looking for a walkthrough.</p><h3>Month Three: My First Real Tool</h3><p>I heard about Burp Suite everywhere. So I installed it and felt completely lost. Instead of giving up, I forced myself to use it for everything. Every website I visited, I sent through Burp. I played with the repeater, watched how parameters changed, and learned to spot weird behavior.</p><p>Within a few weeks, Burp stopped being scary. It became an extension of my hands. That is when I realized tools are not magic. They are just amplifiers. You still need to know what to look for.</p><h3>Month Four: The Certification That Actually Helped</h3><p>I did not chase every cert. I picked one that forced me to prove myself. The eJPT (eLearnSecurity Junior Penetration Tester) was perfect. It was practical, not multiple choice. I had to actually hack a network to pass. Studying for it taught me methodology, not just trivia. I am not saying everyone needs a cert. But having a practical goal kept me focused. Without it, I would have bounced between topics forever.</p><h3>Month Five: My First Bug Bounty</h3><p>I was terrified. Real companies, real money, real competition. I picked a small program with a low bounty and simple scope. I spent a week just mapping the application. I did not run scanners. I clicked everything manually, took notes, and looked for weird behavior. On day five, I found something. A broken access control that let me see another user’s private data. My hands shook as I wrote the report. Three days later, I got my first payout. It was tiny. But it was mine.</p><h3>Month Six: What I Learned About Learning</h3><p>Looking back, the biggest lesson was not technical. It was about consistency. I stopped trying to learn everything at once. I focused on one small thing each week. One vulnerability type. One tool feature. One technique. Small wins added up faster than I expected. I also stopped comparing myself to Twitter hackers. They have been doing this for years. I was just starting. Comparing my day one to their day one thousand was pointless and painful.</p><h3>My Advice to You</h3><p>1: Start with the basics. Networks, Linux, HTTP. You can not skip them.</p><p>2: Practice on legal platforms. TryHackMe, HackTheBox, PentesterLab. Break things in a safe sandbox.</p><p>3: Pick one tool and master it. Burp Suite is worth the time.</p><p>4: Find a community. Discord, Reddit, and local meetups. You do not have to struggle alone.</p><p>5: Be patient. You will feel stuck. That is normal. Push through it.</p><p>6: The roadmap is not magic. It is just showing up, every day, and staying curious. That is what worked for me.</p><p>What does your learning roadmap look like? Share one thing that has helped you recently in the comments. Clap if you are still grinding and learning, and follow for more real talk about this journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=def0a1d11781" width="1" height="1" alt=""><hr><p><a href="https://medium.com/write-a-catalyst/my-cybersecurity-learning-roadmap-def0a1d11781">My Cybersecurity Learning Roadmap</a> was originally published in <a href="https://medium.com/write-a-catalyst">Write A Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Used OSINT to Gather Information Like a Hacker]]></title>
            <link>https://osintteam.blog/how-i-used-osint-to-gather-information-like-a-hacker-a59fdb7a8ffe?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a59fdb7a8ffe</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Fri, 10 Apr 2026 02:59:35 GMT</pubDate>
            <atom:updated>2026-04-10T02:59:35.559Z</atom:updated>
            <content:encoded><![CDATA[<h4>I found my company’s exposed secrets in two hours. No hacking required.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T66AP5gW-2a2tepu.jpg" /><figcaption>OSINT</figcaption></figure><p>I wanted to see what an attacker could learn about my organization without ever touching our network. No exploits, no passwords, no illegal activity. Just a browser and public search engines.</p><p>Within two hours, I had a list of employee emails, internal server names, and a forgotten PDF containing network diagrams. All of it was legally available online. Our team had published it themselves without realizing.</p><p>This is OSINT: open-source intelligence. And it is how hackers build their attack maps before ever sending a single packet.</p><h3>Starting With What You Already Publish</h3><p>I began on our own company website. I viewed the page source and found developer comments revealing internal file paths and staging server URLs. One comment read, “<strong>&lt;!—remove debug=true before launch →</strong>” still there after two years.</p><p>Then I checked image metadata. A photo of our team’s offsite contained GPS coordinates and the camera model. That alone told an attacker where our employees gathered and what devices they use.</p><p>Everything I found was public. We just never thought to look.</p><h3>Harvesting Emails Without Breaking Rules</h3><p>Employee email addresses are everywhere. I searched LinkedIn for our company name and collected job titles and names. Then I guessed the email format, first.last@company.com, and tested it on a password reset form. The system did not send a reset email, but it confirmed the account existed.</p><p>This is not hacking. It is how web forms work. The defensive lesson? Use email confirmation messages that do not reveal whether an account exists.</p><h3>The GitHub Goldmine</h3><p>I searched GitHub for our company domain. A developer had pushed a configuration file with internal API endpoints and a commented‑out admin password. The repository was public for three years.</p><p>I downloaded the file, verified the endpoints, and showed leadership. They were horrified. We rotated credentials and set up automated scanning for secrets in public repos.</p><p>You can do this too. Search for your company name on GitHub right now.</p><h3>Job Postings Leak Everything</h3><p>Job descriptions tell attackers what technology you use. “<strong>Senior AWS Engineer</strong>” means cloud infrastructure. “<strong>Salesforce Administrator</strong>” means customer data in Salesforce. Each listing narrows the attack surface.</p><p>I collected five job postings and built a technology stack map. Then I looked for known vulnerabilities in those specific tools. Attackers do this daily. The fix? Use generic descriptions and avoid naming specific software versions.</p><h3>Social Media and Physical Clues</h3><p>I scrolled through our company’s Instagram and LinkedIn photos. One picture showed an employee’s badge on a desk. The badge format, color, logo placement, and card type reveal the access control system we use.</p><p>Another photo had a whiteboard in the background with part of a network diagram visible. Attackers zoom in on these details. Encourage your team to blur sensitive information before posting. Or better, create a policy against photographing internal spaces.</p><h3>Google Dorks for Defenders</h3><p>Advanced search operators find exposed files. I used site:ourcompany.com ext: pdf and found an internal security policy document with server names. intitle: index of revealed an open directory of log files from an old server.</p><p>These techniques are legal. Google indexes everything. Your job is to find what is public and remove it.</p><h3>Protecting Your Human Perimeter</h3><p>I searched for employee names on social media. One engineer posted about a conference, including his hotel and travel dates. That is enough for a targeted phishing or physical pretexting attack.</p><p>Train your team to limit public sharing of work‑related locations, schedules, and internal projects.</p><h3>What You Should Do Today</h3><p>Run a simple OSINT audit on your own organization. Search your domain on GitHub. Check your website’s source code. Look at your social media photos.</p><p>Make a list of every piece of exposed information. Then close the gaps. The attackers are already doing this. Now you can too defensively.</p><p>What is the most surprising thing you have found about your own company online? Share in the comments. Clap if you are auditing your digital footprint today, and follow for more defensive security techniques.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a59fdb7a8ffe" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/how-i-used-osint-to-gather-information-like-a-hacker-a59fdb7a8ffe">How I Used OSINT to Gather Information Like a Hacker</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Cybersecurity Is a Growing Field]]></title>
            <link>https://meetcyber.net/why-cybersecurity-is-a-growing-field-720ece401042?source=rss-ac59cbf01b0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/720ece401042</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hania Khan]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 15:55:33 GMT</pubDate>
            <atom:updated>2026-04-07T15:55:33.406Z</atom:updated>
            <content:encoded><![CDATA[<h4>I fell into it by accident. Now I can’t imagine doing anything else.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*W4CsGXyenco_jyzh.jpg" /><figcaption>Cybersecurity is one of the fastest-growing fields. <em>AI-generated image.</em></figcaption></figure><p>I did not know at the time that I would be working in the world of cybersecurity. In hindsight, I believe my love of taking things apart was exactly what the field needed.<br>Several years ago, I held a typical IT position. Installing printers, changing passwords, and educating individuals on how they should not click every single link contained within their emails. One day, the office server suffered a ransomware attack. All systems were shut down. Payroll, emails, and customer orders were lost.<br>Over the course of 72 hours, I helped to restore everything. The process was intense and tiring. However, amid the commotion, it became evident that this was important. Not only was it work that had meaning, but it also positively impacted the lives of others. That is when I committed to dedicating my career to security.</p><h3>Attention Has Finally Been Paid</h3><p>I still remember when companies viewed security as nothing but an anti-virus program and password guidelines. It required one person doing all the work for everything labeled as &quot;IT.&quot;</p><p>But those days are long gone. We get a news story every week about some fresh breach. From hospitals that can no longer access their medical records to schools that cannot operate because hackers breached their systems, to gas stations unable to serve fuel because hackers breached the pipeline’s computer systems.</p><p>This is all enough to scare even business owners who will realize that they are not “ifs” but &quot;whens.&quot; More importantly, business owners are willing to spend a lot of money on cybersecurity.</p><h3>The Remote Work Explosion Changed Everything</h3><p>Before the pandemic, most workers operated out of the office environment. There were firewalls, brick-and-mortar buildings, and knowledge of what existed within the network.<br>Now? Employees access systems while sitting at their dining room tables, at cafes, and even in hotel lobbies. I have heard stories about an individual accessing his company’s network via a Thai beach. This is a wonderful scenario for work-life balance, but the implications for cybersecurity are terrible.<br>All of a sudden, all employees’ routers are in the company’s perimeter as well. Every unprotected Wi-Fi hotspot presents a backdoor. Companies need assistance in dealing with the problem of securing data transmitted through the open web.</p><h3>The Ransomware Nightmare Is Real</h3><p>I have heard stories of business owners paying six-figure sums just to recover their files. I have seen charities collapse due to being unable to pay the ransom. I have witnessed the terror that crosses people’s faces once they realize their worst nightmare has become reality.<br>No longer does ransomware feel like an intangible risk; it strikes actual people, actual small businesses, and actual educational institutions. Every single time, the victims only wish they had sought help in advance.<br>This is where we step in. The protectors. The experts excel in creating backups, network segmentation, and educating employees against phishing attempts. Not always the most glamorous task, but it ensures the power stays on.</p><h3>You Do Not Need to Be a Genius.</h3><p>Here is a harsh reality you may not hear often. Most of the cybersecurity field does not require you to be the most intelligent person in the room. Instead, all it needs from you is diligence, curiosity, and consistency.<br>I have seen highly intelligent hackers who cannot communicate effectively with clients. I have seen average programmers who have exceptional communication skills in discussing security threats with non-experts. Which one gets hired more?<br>You do not need a doctoral degree. You do not have to memorize all possible exploits. You only need to possess a passion for getting everything right and a willingness to learn. This is what the industry desperately needs.</p><h3>The Variety Keeps It Interesting</h3><p>I expected that cybersecurity would be a dull activity. Spending my whole day looking at logs and scanning repeatedly. I was mistaken.<br>One minute, I find myself helping a hospital protect its patients’ information. In another, I find myself advising a farmer on how to protect his irrigation system. Then I have to train a group of office workers on how to identify phishing emails.<br>Each client brings something unique to the table. Each problem is unique in itself. Moreover, the enemy finds new ways to attack all the time. So, I keep learning. Sometimes it can be frustrating, but it is never boring.</p><h3>The Money Is Good, Honestly</h3><p>Well, to be frank, the compensation is not too bad. Organizations are very desperate, and desperation makes you rich. In some cases, even entry-level jobs such as cybersecurity can pay better than experienced IT jobs.<br>But there is something else about this industry. Those who work here do not do it for the sake of earning money. People here solve puzzles, protect lives, and always outsmart the criminals.</p><h3>If You are Thinking About It, Just Start</h3><p>A high qualification or certification is not necessary. At first, I used a cheap laptop and free online resources and spent countless hours into the night. I broke stuff, was irritated, and started from scratch again and again.<br>However, I persisted. Now, I get paid to do meaningful work. I enable others to sleep soundly. I prevent disasters. That is much more valuable than any job description could be. The field is prospering because it is needed by our world. If you are intrigued, determined, and hungry for knowledge, there is space for you in here, too.</p><p>What attracted you to security, or what holds you back from getting started? I would love to read about your experience in the comments. Show your appreciation through claps; follow for more authentic discussions on this insane industry!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=720ece401042" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/why-cybersecurity-is-a-growing-field-720ece401042">Why Cybersecurity Is a Growing Field</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>