Pinned Tweet
You need to realize that hackers don't see websites the way others do - a thread
Here's what an ordinary person sees when they subscribe to a charity. They only see the user interface and are restricted by it:
Don't give them much to attack in the first place!
Restrict the attack surface to reduce the risk of getting hacked !
Exactly! Why would you not do it?
It's easy, free, and has a lot of advantages.
This must be one of the rare cases where getting hacked was a good thing 😅
My website got HACKED back in 2011.
I lost all my users and all that work was for nothing.
I then started to learn everything I can about cybersecurity and became a penetration tester.
Now I teach developers about cybersecurity
Lets #connect and make internet a safer space!
Devsecurely retweeted
In soccer, the goal is the surface area defined by the goalposts.
The goalkeeper knows exactly what to defend.
You should identify all the websites you own that are accessible on the internet.
Clearly define the attack surface you need to defend.
I have big respect for people who reverse-engineer binary files.
They stare at assembly code and manage to understand what the program is supposed to do.
That takes a big level of focus. Kudos!
You can send an HTTP request to the Office365 server with a basic authentication header. You specify the username and the password in the HTTP header “Authorization”.
The research started with a simple observation: when performing an HTTP request with an invalid username, the server take a longer time to reply compared to when we send a valid username.
We can thus make a simple request and the server will tell us if the username is valid or not.
We can repeat this operation with a list of usernames that we suspect are present. The attack will tell us which of those usernames are valid.
We can use the list of valid usernames later for other attacks (phishing, brute force the password for valid usernames…)
trustedsec.com/blog/kicking-…
Do you see what I'm seeing?
There is something horribly wrong with this login API.
Please explain to our intern Joe what he did wrong.
The obstacles in front of the success you seek is just the price of entry.
If it was easy, everyone would have it. And it wouldn't be special anymore.
Work on that project. Learn that framework. Write that content.
Enjoy the journey. The destination will come eventually.
The faster you take decisions, the more efficient you become.
Having to make a choice takes up memory space. It's an open loop.
You need to close the subject to liberate the mental space.
Sometimes I face difficult choices, and I hate it. It paralyzes me.
Sometimes I code something that works.
But the, I realize there is a better way to do it, so I re-implement the whole thing.
Then I do it again, and again.
I then force myself to stop thinking about it to move on.
Does this happen to anyone else?
Technical writing is the best skill I learned as a pentester.
I remember grumbling because I had to write those pentest reports.
But that taught me how to articulate my thoughts and share my ideas in a comprehensible way.
And I'm grateful for that opportunity.
In case you don't know about it, the service shodan.io scans all the servers on the internet.
You can search for your servers' IP addresses and it will show you all the accessible services on it.
I thought it was possible. But, you can't do it all alone.
Find friends that have the same ambitions as you. Friends who push you. A partner who understands and supports you.
You can go faster in the beginning if you're alone. But other can help you go further.










