Thread by @maikroservice

Day 3⃣8⃣

Let's get started with Offensive Security & Bug Bounty -

What do you need to know as a Beginner?

Let me tell you.

No organization in the whole wide world needs people that can just hack.

Why - a 🧵

I believe that purple teaming - a combination of Red - offensive - and Blue - defensive security, is the path of the future, and the ONLY PATH really.

But! Currently we are training people the entirely wrong way.

We train hackers to choose between offensive and defensive sides.

So naturally there is a unwritten conflict between the two - it's a cat & mouse game.

Red Team hacks, Blue Team patches / fixes / forwards issues to the development teams.

See the issue?

IF red teamers only hack and point out vulnerabilities and potential attack paths - WHO has the knowledge to fix those?

You guessed right, not the Red Teamers.
But the Blue Team usually does not know it either

ONLY a sparring between both teams will help

Enter Purple Teaming.

OK - I understand now

but ...

How do you learn how to talk to Blue Teams or Developers as an offensive security person?

- Bug Bounty
- Code Review
- Mitigation Analysis
- Building vulnerable Apps yourself

I think Bug Bounty combined with code review is the easiest way to get started with Purple Teaming.

Now comes the kicker - there is a platform that gives you all that

+ the chance to get CVEs for the Bugs you find!

(Disclaimer: I found my first CVE in Open Source Software)

It's @huntrdev (huntr.dev) and I believe it is the best platform to get started with bug bounty and will also help your offensive security career A LOT.

Why?

1. You need to install & start the application that you want to hack.

Sometimes it's easy, sometimes this takes "a while...", even for seasoned professionals.

2. You can choose the size of the application that you want to hack.
If you want to look at only small applications, be my guest.

If you want to hack Laravel, Drupal or other hugely popular systems, you can do that as well!

3. You have the chance to find bugs in the code first and only hack them afterwards 🤯 - Code Review!

This also gives you the chance to hack first and then identify why it worked directly in the code

Pick your poison, any way works!

The only thing left to do is start.

How to find juicy repositories?

You can use my github search query:

stars:100..500 language:php archived:false

This will give you popular repositories written in php, currently you have more than 2000 to choose from.

Pick any!

@joehelle wrote a blog post that I used to report my first CVE - medium.themayor.tech/how-i-was-bore…

LETS GO - HACK the planet.

If you have questions or need someone to cheer for you - my DMs are open or you can reply here.

#BugBounty #30DaysOfBugBounty