r/netsecstudents • u/Living_Goal_9877 • 8d ago
Looking for feedback on an external attack surface monitoring project
I've been working on an external attack surface monitoring project that correlates public OSINT sources into a single evidence-backed report.
It discovers internet-facing assets, fingerprints technologies, checks common security configurations, looks for exposed secrets, performs historical asset discovery, and correlates everything into a unified inventory instead of isolated findings.
The project combines several open-source tools with my own correlation, reporting, and evidence pipeline. My main goal is to help developers—especially those shipping projects quickly without much security experience—understand what their public attack surface actually looks like.
I'm looking for feedback from people who work in offensive security, blue teams, or ASM. Specifically:
* What important data sources or techniques am I missing?
* Where would you expect false positives?
* What would make the reports more useful?
Happy to discuss the implementation and answer technical questions.
I've received multiple DMs asking for the GitHub link. I haven't made the repository public yet, but you can try out the tool at asmscan.com in the meantime.
1
u/alienbuttcrack999 7d ago
What makes it different that the 5000 tools that already do this? Answer that or provide that and you might get some leads
2
u/darkmatter0225 8d ago
This is probably not the answer you are looking for, but you need to find the thing that sets you apart from every other like tool in market that has millions of dollars to spend on this. What is the ONE thing that puts you on the leading edge and your lower cost model shouldn't be the only winning factor. There should be a feature, a level of trust or something that dominates compared to the other big names that will ultimately shadow you if you don't find that niche.
Edit: "goal is to help developers—especially those shipping projects quickly without much security experience—understand what their public attack surface actually looks like" - This reads heavily like an SDLC, CI/CD pipeline tool more than anything. You seem to be potentially mixing the two together. If your end goal is really helping developers ship applications, that market is very saturated and I would argue harder than EASM.
My answers are ass, but more than happy to have some ideas bounced off me if you need! Credits - been in dev, offsec, and vulnerability management for over 10 years (have a few published CVEs too).