Running over 20 top-notch cybersecurity tools with API • Hacker News Board

RexM wrote: post #3

wepple wrote: post #2

This page renders terribly in mobile; am I the only one? It’s unreadable

I had to hold my phone sideways to get it readable.

See postman collection - https://www.postman.com/munsirado/workspace/penteston-api-v1...

Re: Running over 20 top-notch cybersecurity tools with API

#15

Post by fHr » Sat, Sep 09, 2023, 4:56 PM UTC

palikero93 wrote: post #5

20 cybersecurity tools, 0 frontend developers on the payroll

0 QAs as well...

Re: Running over 20 top-notch cybersecurity tools with API

#16

Post by dang » Sat, Sep 09, 2023, 5:08 PM UTC

palikero93 wrote: post #5

20 cybersecurity tools, 0 frontend developers on the payroll

"Don't be snarky."

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."

https://news.ycombinator.com/newsguidelines.html

Re: Running over 20 top-notch cybersecurity tools with API

#17

Post by penteston » Sat, Sep 09, 2023, 6:12 PM UTC

wepple wrote: post #2

This page renders terribly in mobile; am I the only one? It’s unreadable

Yes, css problems on site. For more info see postman page. https://www.postman.com/munsirado/workspace/penteston-api-v1...

Re: Running over 20 top-notch cybersecurity tools with API

#18

Post by nannal » Sun, Sep 10, 2023, 9:57 AM UTC

microphp wrote: post #9

nannal wrote: post #4

I wasn't clear on the verification performed to ensure the client had authority to perform testing against the chosen target.

You have to verify user.

I think you misunderstand the concern, suppose a user enters gov.mil as a domain to test with which they are unaffiliated.

The tools test it and with disastrous affect all governmental and military services go offline.

It would be reasonable to then take legal action against the platform rather than the user, as the user did not confirm they had permission to perform testing or that they understood the risks involved.