This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Cloakwave
Cloakwave detects API security issues at inception
Cloakwave detects API security issues at inception before your first line of code ships. Upload your OpenAPI spec and get a free security report in seconds.
I built Cloakwave because I kept running into the same problem with API security tools, they would tell me my spec had "BOLA risk" or "missing authentication," and I would have no idea whether that was a five minute fix or the kind of thing that ends up in a headline.
A missing auth check on an internal endpoint and a missing auth check on /admin/users are not the same problem. But most scanners treat them the same way.
So I started cataloguing documented API breaches, the ones where the root cause is public and mapped each one back to the OWASP category it belongs to. Now when the scanner flags something, it can tell you this is a technique that has been exploited repeatedly in real incidents or nobody has publicly documented exploitation of this yet, so it's lower priority. Same severity rating, very different urgency.
That's the whole idea. It runs in your browser, it's free, and your spec doesn't go anywhere. I just wanted a tool that tells me what actually matters first.
If you try it and something feels wrong, a finding that's a false positive, a category I got wrong, a gap in the precedent data, please tell me. That feedback is genuinely the most useful thing you can give me right now.
No comment highlights available yet. Please check back later!
About Cloakwave on Product Hunt
“Cloakwave detects API security issues at inception”
Cloakwave was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #155 on the daily leaderboard. Cloakwave detects API security issues at inception before your first line of code ships. Upload your OpenAPI spec and get a free security report in seconds.
Cloakwave was featured in API (98.9k followers), Developer Tools (523.4k followers) and Security (3k followers) on Product Hunt. Together, these topics include over 114.7k products, making this a competitive space to launch in.
Who hunted Cloakwave?
Cloakwave was hunted by Jerry. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Cloakwave stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hello everyone,
I built Cloakwave because I kept running into the same problem with API security tools, they would tell me my spec had "BOLA risk" or "missing authentication," and I would have no idea whether that was a five minute fix or the kind of thing that ends up in a headline.
A missing auth check on an internal endpoint and a missing auth check on /admin/users are not the same problem. But most scanners treat them the same way.
So I started cataloguing documented API breaches, the ones where the root cause is public and mapped each one back to the OWASP category it belongs to. Now when the scanner flags something, it can tell you this is a technique that has been exploited repeatedly in real incidents or nobody has publicly documented exploitation of this yet, so it's lower priority. Same severity rating, very different urgency.
That's the whole idea. It runs in your browser, it's free, and your spec doesn't go anywhere. I just wanted a tool that tells me what actually matters first.
If you try it and something feels wrong, a finding that's a false positive, a category I got wrong, a gap in the precedent data, please tell me. That feedback is genuinely the most useful thing you can give me right now.
Thanks for looking.