r/Pentesting • • Jun 30 '26

I made a reusable tamper-evident jar for storing sensitive items

Post image
913 Upvotes

Hey guys, for the past few years, I have been working on a reusable tamper-evident jar for storing physical items.

The idea is that the lid creates a random physical “fingerprint” every time you close it. Inside the lid are thousands of tiny black and white balls. When you twist the jar open or closed, they mix. Once the jar is closed, the unique pattern is locked in place.

You can take a photo of that pattern with your phone, and later compare it to check whether the jar has been opened. If someone opens it, the pearls mix again and the original pattern is gone.

I made it because I wanted a simple physical way to store things like hard drives, USB sticks, authentication keys, documents, etc. Basically anything that you would do want to know if someone has accessed it.

After a lot of hard work and prototyping, I'm happy to announce it's finally complete! Check it out on https://www.entropyseal.com/.

Happy to hear feedback. I’m especially interested in whether the concept is clear and what use cases come to mind. :)

UPDATE

After taking a look again we agree the price of 100 USD / 93EUR was a bit too steep. So we reduced the price to 70 USD / 61 EUR. We want to make this product as accessible to everyone as possible, so we don't want price getting in the way.


r/Pentesting • • Aug 12 '25

I did the unthinkable and made a pentesting toolkit that works on iPhone!

Post image
692 Upvotes

It runs on iSH Shell, available on the app store. I modified some existing tools to work within it, made a few of my own and put it all together as a toolkit. Kinda like a Lazy Script for iPhone. I haven’t been able to test everything thoroughly but always looking for community feedback & suggestions!


r/Pentesting • • Aug 06 '26

Just for fun

Post image
434 Upvotes

r/Pentesting • • Jul 02 '26

This is ARGUS, my semi-autonomous, multi-computer, local-AI-driven pentesting platform.

Post image
408 Upvotes

r/Pentesting • • Feb 05 '26

BitDefender vs. My ransomware

387 Upvotes

UAC bypass + Persistence + Encryption

Evasion is a game, my ransomware won!

I will be posting the entire project on my github page soon:
https://github.com/xM0kht4r


r/Pentesting • • Apr 02 '25

Attracting too many furries NSFW

340 Upvotes

Hey everyone,

I'm a penetration tester at a security firm making $195k in Seattle.

Every time I go to a bar, party, or any social event in general, I try my best to avoid telling people what I do. Every time I tell a furry (male, or female) I'm a pentester they start hitting on me.

Last week I went to a friend's birthday party, and told his brother I did pentesting. He kept asking me "can you wireshark my packets?" and "wanna inject sql into my backend?" in a flirtatious manner.

This is a recurring problem. It's gotten so bad that I tell furries that I’m a product manager at Google so they will stop hitting on me all the time.

Any advice on how to stop attracting so many furries as a pentester?


r/Pentesting • • Feb 25 '26

red teaming at its peak

330 Upvotes

One of the funniest memes about red team engagements, and I just discovered it now


r/Pentesting • • Mar 06 '25

My perspective on getting starting in pentesting based on 20+ years doing it.

281 Upvotes

I co-founded and run (there are 3 managing partners) a ~30 person pentesting company. Someone in another thread asked me how to get started in the field. Here are some of my unsolicited thoughts on getting into the field.

I'll do my best to answer as there is no one main path that folks take to become a pentester. You will also get different answers from other people like me, but this is my perspective. We have a mix of people that were sysadmins, developers, NOC/SOC people, auditors, a nuclear submarine guy, etc. Some are college educated and some have almost no formal education. Some have a lot of certs, some have long-expired ones. We're a smaller company (US-based, 34 employees) so we don't have an "HR filter" where we need to see certs. When I get a resume, the certs are nice to see because it shows dedication/respect/interest/curiosity/drive. I don't look at certs as "Oh wow this person really knows how to pentest!". It also doesn't tell me anything about a personality, or how you will treat our customers, etc. But it does enhance a candidate's "curbside appeal" :)

I wrote this whole post, reviewed it, and came back to edit in this: Out of school just get any job in IT. MSPs are good because you’ll get exposed to a lot of different customer environments and technology. You will also learn some customer service skills. Maybe you start out as tech support or a developer. Fine, work hard and get involved with as many projects as you can. Keep your eye on pentesting, tinker at night and on weekends, but suck up as much enterprise IT knowledge as you can. Do your best to get into the conference room where meetings are taking place that make you feel like you don’t belong. I spent a lot of my early career standing in the 2nd row, behind those seated in the conference room nodding my head even though I didn’t understand WTF was being talked about. The panic of “needing to figure what the hell they were talking about so I don’t get fired” is a fantastic motivator. Once you feel like you are no longer a complete imposter, make the pivot to pentesting.

Coming out of school with a degree in CS will give you advantages in some areas of pentesting/assessment work. Specifically, you will likely be better at application security, code reviews, automation/tooling, etc. I don't know you or how you spend your time, so forgive my assumptions here... folks that are newer to IT, enterprise environments, etc. often don't yet have an understanding of how these environments work. So having a foundational understanding of networking, operating systems, cloud environments, applications/software work will make you a better pentester. Understanding how enterprises work and how businesses operate will make you a great consultant. This is the reason people are telling you being a sysadmin (or tech support) is a great path to being a good pentester. Pulling off an exploit is one thing, understanding what happens beyond that is very important. After you compromise a machine or whatever, you need to understand what happens next not only to know how to go deeper to fully understand/demonstrate the risk, but also knowing when to NOT go deeper (e.g., crash a prod machine, go out of scope, etc.) So it's the foundational understanding of how things work that will make you really good at this work.

“But how do I learn about enterprise networks if I’m fresh out of school?” Great question. Build a home lab. Run your own domain, DNS servers, run a Plex server, run a personal blog on AWS with an environment created by terraform or Cloudformation. Protect your blog with Cloudflare AWS WAF, Cloudfront, etc. Standup a DIY backup system for your NAS. Make your own personal DIY VPN server. Deploy a NIDS (even though they are useless these days) to watch your dorm/home network traffic. Buy a single $20/month M365 Business Premium lic and deploy MS Defender to every computer you own and then do threat hunting. Sign up for AWS and run something cool with all the bells and whistles. They have a free tier. Sometimes people make a home lab or deploy a database server but don’t really have a purpose. For me, I run a lot of low-cost/free stuff at my house because I find it very stimulating and I learn a ton. Basically you are trying to speed run a career in enterprise IT by faking it at home.

I have been in IT since 1996, in a security role since 1997, and a security consultant that performs assessments since 2002, and doing actual pentesting (professionally, heh) since 2004. By this I mean I had jobs that required me to look at an environment, network, application, etc., compare it to something (e.g., a standard, a framework, my own subjective opinion, etc.) and then tell the customer what is wrong with the situation and make recommendations on how to be better. Early in my career, I was "just a pentester". I'd point out flaws, identify risks, exploit things, etc. and then dump the report on to the customer to go fix. It was only later in my career that I started being able to give good advice on how to fix things. I'm not saying I would get involved with the actual remediation, but rather being able to articulate a given risk, why it matters, contextualize it with what we see in the wild, and giving the customer options on ways to mitigate the things I'd found. I tell our team that we often win the renewal (80% of our business are repeat customers or referrals) during the report review call.

Pentesting is changing fast. At least in the US, the classic on-prem AD Windows environment with servers and workstations is quickly disappearing. We still do a lot of externals but our IPTs are sort of a check-the-box since most on-prem networks are glorified hotspots. We are doing more internals within AWS/Azure, but it's not like it used to be. We are also doing a lot more red team or simulation-shaped engagements where customers send us their laptop and we operate from there. Also, most of our work these days is application security. Organizations have 1 network, and a lot of apps. Everyone has a big M365 footprint. Also lots of AWS, but you don’t really “pentest” AWS as it's more either pentesting inside an environment that happens to be running on AWS or doing AWS security reviews (config review). 


Get more than my perspective on this. I’m biased based on my experience and what worked out. Getting a diverse set perspectives from graybeards like me will help you figure things out.


r/Pentesting • • Feb 02 '25

I made my own RAT, written entirely in python.

260 Upvotes

https://github.com/lioen-dev/Lo4f-Malware/tree/main

This is my first time trying to make pentesting software, is it any good? ive spent days on this so far lmao. It's Windows only as well i might mention.

It can do the following:

  • Handle multiple infected pcs at once

  • Send custom popups

  • Steal Chrome passwords

  • Execute any terminal commands, persistently (changing directory actually changes it for following commands)

  • Take Screenshots

  • Shutdown infected pc at any time

It currently scores a 9/72 detection rate on virustotal, partially being detected because i converted the .py to a .exe using pyinstaller.

This obviously isn't meant to be amazing, just a fun project and learning to do stuff for my job someday hopefully (im too young to get a job currently)


r/Pentesting • • Feb 25 '25

Pentesting is the hardest "cybersecurity" discipline. Change my mind.

250 Upvotes

I've been in "cybersecurity" professionally about 10 years. I use quotations because back when I started, it was really called "infosec" or information security, but cybersecurity became the buzzword. In this field, I started in malware research, moved to application security & security engineering, I then did pentesting and managed a bug bounty program, moved to product security incident response where I did deep analysis on vulnerabilities reported to my company/team, such as testing the proof of concept code, analyzing the vuln to determine severity and score it, and finally helping product engineering to patch it. After this, I have been a full-time pentester for almost 3 years.

I have to say that I left the bias at the door, and from an objective view, pentesting is the most difficult of any of these... I will now explain why:

  1. Pentesting is always technical. Unlike security architects, program managers, and managers, pentesters are always in the trenches, expected to know whatever technology/stack that the current project requires like the back of their hands. Unlike a threat model, what we do is not theory - it is not about what "could" happen, it is about what actually happens. Quite literally, pentesters are expected to take a codebase where engineers have been working on it for 10 years, and learn it and correct said engineers in the course of 1-2 month's time. Oftentimes, the pentesters are the first security personnel to actually sit down with the actual product and security test it.

  2. No matter how good you get and how many findings you have in your report, there is always that nagging feeling that you missed something. There are pentests where you find high and critical vulnerabilities, and others where everything is an informational, low, or maybe moderate. In either case, there is always the feeling that "what if I missed something!?!?" I feel like this feeling is unique to pentesting.

  3. The breadth of knowledge to be a pentester is extremely large. At least where I work in securing products, we are expected to be able to read code, write code (tooling, scripts, and sometimes even aid with patching), become familiar with whatever programming langauge that the current project utilizes, in addition to being capable in network security, DNS, web security, operating systems, compiler hardening, debuggers, configuring and deploying the target, and operating proficiently in systems that range from kubernetes to C code libraries, operating systems deployed on virtual machines, python scripts, internationalization, proprietary cloud environments such as AWS and Azure, and more. In fact, there have been times when my team has been assigned to test a product, and the product engineers themselves have spent 2-3 weeks to just get a stable test environment running for the first time, but we are expected to either do the same, aid them, or pick up where they left off.

  4. Finally, pentesting requires a lot of mental fortitude, grit, and persistence. The systems that we test are not designed to cooperate with us; instead, at least in the best case, they are designed to work against us. As pentesters, we are expected to pick up virtually any system, learn and understand it, and then be capable of finding flaws and advising the engineers and managers assigned to the project, sometimes for many years, on where they messed up, usually in a much smaller amount of time. It is easy to get lost in rabbit holes, find yourself banging your head against the wall or on the keyboard, or be promised information that is never delivered to help facilitate the pentest, but we still have to do it anyway.

So therefore, I feel that pentesting is the hardest cybersecurity discipline. Malware research was also very technical, but the difference was that malware often does the same things over and over again, and I found the scope of malware research to be quite a lot smaller than the scope of pentesting.


r/Pentesting • • Nov 28 '25

Send pop ups to pc's on network

Post image
223 Upvotes

We are getting a pen test currently. A couple things have happened. They sent these pop ups to all pcs. One was for a pin and the other asked for user/pass. They are pretty fake looking coming from the pen test pc ip address.

But I'm curious how this works? I am sure we will hear more in the reports. But I would love to find out now. Is it using LLMNR and a responder?


r/Pentesting • • Sep 10 '25

ToolHunt

Post image
202 Upvotes

Hey everyone,

I wanted to share a project I made called ToolHunt. It's a simple, local search engine that helps you find the right cybersecurity tool from a database of over 3,000.

The cool part is you can just describe what you need in plain language, like "web vulnerability scanner" or "tools for memory analysis", and it finds the best matches.

You don't have to install anything to test it. I made a Google Colab notebook so you can run it on a free GPU and get a public link to try it instantly.

GitHub Repo: https://github.com/cyberytti/ToolHunt

Direct Colab Link: In the repo you will get a script to download and run this automatically on colab.

It's open source and I'd love to get your feedback.
Please give a star if you like the project it means a lot to me.


r/Pentesting • • May 28 '26

I am not getting any call backs at all.

Post image
193 Upvotes

I am open to any suggestions.
I am applying to everything.


r/Pentesting • • Sep 03 '25

almost broke a client’s test setup during my first real pentest

182 Upvotes

had a moment last week during my first legit job- style pentest, wanted to vent/share before i bury the memory. maybe (hopefully) it helps someone else not f up like i did.

what happened: i was testing an internal web app for a small startup. was doing my usual recon, mapping endpoints, and poking for logic bugs. then i saw a weird post endpoint that deleted user accounts. no rate limit, no check if the requester was an admin. okay..

i hit it once, the account vanished. hit it again to confirm, aaand a cascade of account deletions. that early afternoon joy turned into a proper panic attack lol

so how I handled it:

sent a ''heey, might've broken something'' to the client and paused testing.

rolled back via their staging snapshot (they were smart and had that).

took time to write up the process, the severity, and how it could get lost-in-production quick.. decked it out with remediation advice.

what saved me:

my stupid note-taking habit. i had logged that endpoint under “needs checking” earlier but didn’t think it was critical. that note became my safety net.

replaying writeups in my lab helped too. I recognized this as similar to a nasty idor i’d broken before in tryhackme.

i’d also taken a couple structured bug-bounty/pentes intro courses, including content on haxorplus and hackthebox, so i’d trained myself not just to find bugs but poke carefully.

taakeaway: tools and platforms are great for learning but in real tests, slow down and think through what you’re doing. one careless request shouldn’t cascade into chaos :)

what about you guys? any “almost broke production” stories or close-calls that taught you to double-tap your checks before hitting submit?


r/Pentesting • • Feb 20 '26

Pentesting is going to skyrocket in the following years- Lock In Right now !

155 Upvotes

Features will be released quicker than ever due to AI Ai will make terrible mistakes , even if code review is being done there will be new attack surface and new mistakes .

No more low hanging fruits where you can inject <script>alert and it works or a direct idor. But there will be mutation xss where you have to study the WAF very well and keep changing your payload . Or bugs that require chaining and understanding of the whole architecture. This means intuition and curiosity is going to be a huge factor now , not just checklists.

I just submitted a bug in a mobile app that required chaining and 3 weeks of work and no sleep . So lock in , lock in . Lock the fuck in

Get certified, hunt for bugs in bug bounty programs . Learn active directory. Build labs . Market yourself . Pentesting is going nowhere, and AI still have a long road to go to discover blackbox vulnerabilities or even grey box. It's a fucking tool , nothing more . You point it at the right direction, you even correct it when it's wrong.

So study Kings


r/Pentesting • • Jan 19 '25

Bypassing airport security via SQL injection NSFW

Thumbnail
ian.sh
135 Upvotes

r/Pentesting • • Oct 16 '25

Finally got my first bug bounty — thanks to an open bucket behind a CNAME (and a lot of late-night Googling)

131 Upvotes

Hey folks — long time lurker, first-time poster. I wanted to share a small win because I’m still buzzing and figured someone else starting out might find it encouraging.

I’m a junior pentester (been doing this professionally for ~6 months, mostly internal pentests and triage). Last month I was doing an authorized scope sweep for a client on a typical recon pass — passive cert/DNS checks, some OSINT, and a few safe, scoped tools. I’d been collecting subdomains with subfinder/amass and scanning cert logs when I remembered a comment here about s3dns that I’d saved months ago.

Long story short: I spun up s3dns locally, let it watch DNS/CNAME chains while I browsed the client’s public pages and ran some passive queries. s3dns flagged a weird CNAME chain that ultimately resolved to a cloud storage hostname pattern I hadn’t expected. The bucket itself wasn’t directly referenced on the site — it was behind that CNAME — and because the DNS chain didn’t show up in my initial HTTP-only sweeps, I probably would’ve missed it.

I didn’t pull anything or try to access private data. I followed our engagement rules: documented the evidence (DNS records, CNAME chain, public object listing behavior), escalated through the client’s approved triage channel, and submitted a responsible disclosure report with screenshots and concise reproduction steps limited to what’s necessary to verify. The client replied quickly, validated it, and patched the config. A week later I got an email saying the team verified the impact and — to my absolute delight — they awarded me a $1,500 bounty.

Thanks to everyone here who posts tips and mini-guides — I probably learned more from the comments than from any single blog. If anyone’s curious I can post a sanitized timeline of how I documented it (no commands, just the evidence checklist I used). Feels great to finally close one with a positive outcome — and even better that it reinforced doing things by the book.

Cheers and keep hacking (ethically)!


r/Pentesting • • Jul 20 '25

Wanting to get your first pentesting role? I'm a manager for a large red team, here are my thoughts.

126 Upvotes

I'm seeing a lot of posts lately from people trying to break into pentesting and wanting advice on how to land that first role, and this post is mostly in response to that.

I'm a Red Team Manager leading a team of 25 at a Fortune 10 company. about 20 of my team focus on web app pentesting, and the rest are working on full red team engagements and adversarial emulation (MODS, i'm happy to verify this, just send me a chat). I am always looking for talented junior pentesters, and honestly, the candidate pool has pros/cons. I wanted to share some of my experiences about what's working (and what isn't) when it comes to candidates experience.

The reason we look for juniors is because it is significantly cheaper to train a junior and turn them into a mid/senior level tester than it is to poach someone with that skillset from another company. We also don't have to train away "bad habits" they learned at other companies.

I'm seeing a lot of applicants coming from one of three backgrounds: blue team, software development, or bug bounty/CTF/HTB experience. And while I appreciate the drive and skills shown in those areas, I'm finding surprisingly low success rates with the latter two.

Developers, generally, struggle with thinking like an attacker. They’re excellent at building things securely (hopefully!), but often lack the mindset to systematically break things. They can get caught up in code-level thinking and miss broader attack paths. It's not a knock on developers - it's just a different skillset. What's been particularly interesting to observe is that my current interns (who are computer science juniors in college) are aware of potential exploits against the projects they’re working on, but haven’t been explicitly taught how to properly secure their code or how to effectively test it for vulnerabilities. This highlights a concerning gap in a lot of CS education. Over the last 3 years, I've had 7 employees move internally into pentesting from software dev roles, and within 6 months I've had to either send them to additional training or ask them to transition back to an app team. Only 1 has stayed on the team long term, and that's a senior engineer who has been mostly focusing on working with app teams for remediation, and less actual hacking.

The bug bounty/HTB candidates can find vulnerabilities, but often get completely lost when put into a real-world engagement. These platforms provide highly controlled environments. Real environments are messy, complex, and require a lot more than just running a scanner and exploiting a known vulnerability or finding credentials in a text file. They often lack the foundational understanding of networking, system administration, and the broader attack lifecycle to navigate more complex scenarios. It feels like they're missing the "why" behind the exploitation, and struggle with pivoting or adapting to unexpected findings.

The candidates who consistently perform the best are those with backgrounds in IT – particularly those coming from Blue Team roles like SOC analysts, Incident Response, or even Detection Engineers. These candidates already understand how systems work, how networks are configured, how attacks manifest, and how to think like an adversary (even if their job was to stop them). They’ve spent time digging through logs, analyzing network traffic, and understanding the underlying infrastructure. That foundational knowledge translates incredibly well to offensive security. They pick up the technical exploitation skills much faster. 4 members of my team are former blue teamers. 3 of them transitioned from our SOC/detection engineering teams, and one was a SOC analyst at another company.

I'm not saying you NEED a blue team or IT background to be a good pentester, but it provides a significantly smoother transition than someone without that experience. We spend a lot less time on “enterprise hacking 101” and a lot more time on actual testing and fixes. A company is a lot more likely to take the risk on someone with prior IT or security experience than someone with only HTB experience.

I'm seeing this trend amongst several of my other peers who are managers. I'm sure there are exceptions to this, and some of y'all will jump into the comments about how you or a friend got a role with no prior experience. Those are rare cases, and I'd love to see what their progress looks like over a couple of years. If those are positive, I'd be way more willing to take a chance on the HTB/CTF/bug bounty hire.

If you're looking for that first role in pentesting, I have 2 openings that will be posted right after Black Hat/DEFCON. Send me a chat and I'd love to talk to you about your experience.


r/Pentesting • • Sep 28 '26 Bravo

"Rogue AI" is a lie of convenience.

121 Upvotes

I am tired of the hype surrounding AI. It isn't a super-hacker, not even close. If anything, its more like a novice script kid with a wealth of knowledge and serious comprehension issues.

Everyone's calling the OpenAI/Australian Medicare incident "the first case of AI hacking a government." It isn't. Just like the rest of these stories, its about weak security on the victim's side and a sloppy harness on OpenAI's side. Australia's own Acting PM Richard Marles publicly admitted the Medicare portal "didn't have the cyber protections expected for systems with personally held information," and they've since taken it offline.

I wrote a full breakdown and thought some of you might find it interesting.

I'm also happy to debate this. If you believe LLMs are inherently uncontrollable, show me a single documented case where an LLM acted outside the permissions its harness gave it. Not a bad decision within scope, an actual escape. I'll wait.

Comments and feedback always welcome

https://netragard.com/blog/openai-australian-medicare-ai-breach/


r/Pentesting • • Feb 21 '25

Pentest Client: 'If We Use DHCP, You Can’t Hack Us, Right?'

121 Upvotes

 

 In the annals of you can’t make this shit up. Here’s a recent correspondence with a pentest client.

 Client (Dir of IT at a “Technical Advisory Firm”)

“If we were to transition to DHCP for our internet facing devices, does that make Pen Testing not possible?

We concluded that we no longer require static IP addresses at any of our locations so curious what this means to external pen tests?   Conflicted on this as being able to show our clients a Pen Test report is valuable however it would seem that we gain security by removing those static IPs?

I appreciate your patience as we work through this.”

Us

“Great question! Transitioning to dynamic assignments for your internet-facing devices doesn’t eliminate the need for penetration testing because the primary goal of an external pen test isn’t just to target static IPs—it’s to assess your overall attack surface and identify vulnerabilities in your externally exposed services.

Even with dynamic IPs, any public-facing services (e.g., VPNs, web apps, email servers) still need to be reachable, which means they’ll be discoverable through DNS, third-party services, or passive reconnaissance. Attackers don’t rely solely on static IPs—they use a variety of techniques to find targets, including scanning entire IP ranges, leveraging threat intelligence, or identifying assets through misconfigured cloud services.

A penetration test ensures that:

Your externally exposed services are secure, regardless of whether they are on static or dynamic IPs.

DNS, third-party integrations, and cloud configurations are hardened to prevent exposure through other attack vectors.

Attackers can’t easily enumerate and exploit your infrastructure despite IP address changes.

In short, while dynamic IPs may make targeted attacks slightly less convenient, they don’t prevent exposure. A penetration test will confirm that your security posture remains strong despite this change.”

 

Client

“Would the pricing for a pen test using DHCP work the same as with static?  It seems possible that those public facing dynamic IPs may not be discoverable in which case you would not be able to scan them.  If that’s true it would seem that time allocated for those scans would not be used?

Am I missing something here?  Or are you confident you would be able to discover those ip addresses?”

 


r/Pentesting • • Sep 27 '25

A hacker who doesn’t know how to hack

120 Upvotes

I have 3 year experience in web/network pentesting and have got some good money from bug bounty hunting

However I still don’t know how hackers hack someone phone, I don’t mean mobile application I mean the system itself I know how to hack a computer if a specific port open or with malware or exploit a zero day in windows

Any resources for that I feel disappointed for my lack of knowledge in this area


r/Pentesting • • Feb 04 '26

No Pentesting jobs? No problem (Longer post)

113 Upvotes

My fellow pen-testers. I've been reading many many posts over the past year about the lack of opportunity in the field. I have to disagree...you have a skillset so why not use it while you wait for an opportunity...that's if your competent

Im from a country where the OSCP is out of my personal price range. Its the same price as a car and a small house. But I want and need it, so here's what I'm doing (I have a CompTIA Pentest 003, PJPT and a PWPA along with doing many many THM rooms - yes im a noob and I know the dangers, so I tweak what I can offer)

I started a pentesting company and Ive approach small businesses in my town (gyms, schools, coffee shops, restaurants...you name it)

I offer 6 things (A business can choose 1 or have all 6)

1 Phishing campaigns (Im very good at these, tyler Ramsbey has a great course on this)

2 Wifi cracking (Using simple tools like Wifite and Aircrack)

3 Web Site testing (By no means am I the best but Im better than the average script kiddies)

4 Network - I realize my limits here and the damage I can do. So my only recommendations here are to close certain ports they dont need open like ftp or http etc, patch and update the services they are using and then filter those ports - very simple (unless I see very basic/critical findings like eternalblue/windows 7 stuff)

5 Physical breach - Varies - In one breach I dressed up like a Pest control worker and seeing if the staff allow me access to off limit areas like offices and storage, this works

6 Training - showing them the methods of a hackers, showing them OMG cables, rubber duckies and why not to plug things in. How to notice phishing emails. Showing sites like haveibeenpwned and equipping the staff to deal better with hackers

FYI One of my friends works in law and helped me create the MSA, ROE, SOW, Safe Harbour and NDA from his department.

I understand this might create a bit of anger in the community but its either im proactive or I sit on my backside sending job application after job application. Im halfway to being able to afford the OSCP (unless they have another discount)

Small companies benefit from these tests and you get paid. By no means do i charge alot because of the level Im offering but its helping me get from point A to point B in my career and the changes the business adopt might be enough for a hacker to think this is not worth my time...


r/Pentesting • • Jul 27 '25

Pentest tool set for when I get stuck

Post image
111 Upvotes

Just passed the pentest 003 and did some try hack me rooms. Whenever I learn something new I add it to my toolkit. In this example if Im looking to do some priv escalation and get stuck i refer to this excel sheet. Feel free to copy it and if I need to add anything please feel free to mention the tip.


r/Pentesting • • Sep 09 '24

If you're a beginner or thinking about getting into pentesting, I have some tips for you

97 Upvotes

I've recently started to write a few articles on my spare time, and was thinking it could help out some people here as well. Sorry for using a new account, I want to keep this persona separated from my real name and everyday consultant job.

I know that for me it seemed close to impossible to break into this field when starting out. I have my own way that I recommend people to do this, where the goal is to quickly land an entry-level job by learning the "must haves", and then get paid while learning the "nice to haves". I think way too many guides and roadmaps tell you to learn coding, take certifications and so on. Focus on practical experience, and leverage your soft skills like communication and problem-solving, these are critical in interviews and actual real-world pentests.

Here are the 8 steps from my article that I think will fast-track you to a job in the field:

  1. Dedicate Yourself to the Journey: Pentesting is hard to learn, but not really any harder than learning any other fields. Commit fully to learning and improving. Persistence is key, especially when learning a field as focused on problem-solving as pentesting is.

  2. Understand the Goal of Penetration Testing: A penetration tester is NOT a hacker. Learn the difference, and focus a good amount of your time to learn that difference. In my opinion these are the weakpoints of many pentesters.

  3. Choose a Specialization: Even as a beginner I think this is important. Picking a in-demand specialization will make it much easier to become valuable in a team. Web, Cloud, OT are examples of this. Look around for job postings and such in your area.

  4. Get Hands-On Experience Real-world experience is essential. I know bug bounty programs are scary, but just throw that fear away and get at it. If you have bug bounty experience, I would value this as much, or maybe even more, than work experience.

  5. Choose the Right Certifications (if any): Yes, OSCP is great, but it teaches you general pentest knowledge only. Yes, SANS 560 is great, but it is way too expensive. Start with affordable, respected certifications in your niche. I would recommend certs like Burp Practitioner and CARTP. The expensive ones are for your future employers to pay.

  6. Develop Crucial Soft Skills: Communication is key. Your ability to present findings and write clear reports can absolutely be more important than the technical skills. This is highly undervalued by pentesters, and a great way to stand out from your competition.

  7. Overprepare for Interviews: People show up underprepared for interviews. Study the common interview methods. Talking through a pentest, live demos, talking about specific tools and so on. Prepare for the actual interviews, not just your pentest skills.

  8. Start Applying (Broadly) You need experience from job interviews. If your dream job is the first interview you show up to, you will most likely fail. You will be much better equipped to do well on your 10th interview than your 1st. But focus on what went wrong and improving from interview to interview, or you will be one of the people demonstrating the definition of insanity by saying "I showed up to 5000 interviews and didn't get a single job"

If this seems interesting to you, here is a Friend Link to the full Medium article, so no paywall:
https://medium.com/top-cybersecurity-insights/the-2024-pentesting-roadmap-from-beginner-to-hired-in-8-steps-eb3c24f67a45?sk=11ab96a78b079f8a964fb72fb49f0f37

Good luck on becoming a penetration tester!