Before starting a new audit, always review similar projects and their previous audits. Most of the time, the same bugs appear in the protocol you're about to audit. Reading these reports also helps you spot weak or soft spots. 🫡
I’ve seen so many advice (I actually think it works) about reading reports of similar protocol to start your (audit) day.
My question is how do I find such reports? Solodit? Manual searching? If yes, how do you do that?
How I stay focused as Security Auditor?
• I speak with myself aloud
• Writing notes helps to enter "flow-state"
• Conduct max. 1.5h session
• One flow/task at a time
• Follow basic To-Do list
A lot of newcomers can't understand that security is not like an educational subject where there are constant rules/infos/docs/stages you do it, you skills improve.
It is like a game, you can watch how to play the game, you know the controls, keys, skills, etc... But what…
Dedicated a while learning and improving my skills In @SwayLang
✅ Managed to find >= 70% of CHM Bugs In the
Swaylend IOP ~ reports.immunefi.com/swaylend_iop
✅ Won the Swaylend Backend & frontend IOP.
With my team ~ immunefi.com/audit-competit…
✅ Written a simple ctf to help anyone dive…
761 Followers 21 FollowingOnboarding the next generation of world-class security researchers through specialized onsite bootcamps offering them valuable hands-on experience in web3sec.
1K Followers 579 FollowingBlockchain Security Researcher @NethermindEth | Lead-judge @codehawks | Auditor at @PashovAuditGrp | Working on 5G x Blockchain
27K Followers 723 FollowingDelivering the latest and most significant updates from your favorite news outlets.
Aggregated from @TreeNewsFeed and internal sources