[Owasp-leaders] Bring balance: force verification in scanning tools
johanna curiel curiel
johanna.curiel at owasp.org
Sun May 22 22:55:47 UTC 2016
Definitely Bev :-)
In fact this is the kind of thing we should discuss.Should we start a
formal process to bring this to a panel discussion?
I started developing a tool 'Nmapalyzer':
Is a tool to identify the data packages sent by NMAP probes. Reverse
engineering of nmap TCP sent packages to a target machine
So Bev, there are commercial solutions doing this and some OS but not
extensively. My plan with the Nmapalyzer is to help detect network
traffic(passive) and set the information with a nice dashboard. It is in
research phase right now.
>>But given that it IS open source, a hacker would simply fork it on GitHub
or BitBucket or wherever and just point fellow black hats at the modified
source at some other URL.
Simply?😏 He do you have fellow blackhat friends that give you exploit kits
blackhats don't give anything for free.Which blackhats are developing 'open
source hacking tools' and giving tools for free like we do? No one, wether
you pay 1 dollar or 300 for anything, they need to make a living.
Have you check ZAP code? Maybe this part should not be at all documented .
Believe me he will move to BURP or tamper data faster than just go and take
the time to change this. and give it for free...
Now a professional blackhat will invest his time/money and distribute a
version but it will charge some money for it, just as done with malware
I bet you 100USD than the moment ZAP does this, download of this new
version will decrease by 50% and a blackhat will make a version for sale
for a very good price in the dark web (charge USD20 instead of buying BURP
Want to bet?
On Sun, May 22, 2016 at 6:20 PM, Bev Corwin <bev.corwin at owasp.org> wrote:
> Hi Johanna,
> I was thinking more about possible collaborations between interested OWASP
> Foundation projects and NIST Cloud Computing Forensic Science Working
> Group: http://www.nist.gov/itl/itl-cloud-computing-forensic-science.cfm
> Your questions about social responsibility when developing technologies
> that have potentials for misuse, or to be weaponized, and putting such
> concepts into "security by design-like" and/or "implementing security early
> in development life cycle-like" contexts, could provide interesting
> discussions for collaborative working group discussions, and/or panel
> discussions at future events, i.e.: AppSecUSA, and/or other conferences,
> for example.
> Best wishes,
> On Sat, May 21, 2016 at 10:51 PM, johanna curiel curiel <
> johanna.curiel at owasp.org> wrote:
>> Bev made a question which triggered an idea
>> >>Why couldn't we think about implementing some types of OWASP forensic
>> features into all of our code projects so that we could at least have some
>> way to investigate if / when they are misused?
>> Now, when she said that I though why ZAP does not implement a feature
>> that already exists is SaaS products which REQUIRES that you set a file in
>> the hosting application before in order to be able to pen test it? If the
>> file is not found in the URL domain server hosting the application, you
>> cannot attack it.
>> I don't want to advertise which commercial vendors do that but this is
>> the way they avoid that a hackers go and misuse their services.
>> Building a module into ZAP that requires this file first to verify you
>> own the web app and then attack will make it harder for hackers to just
>> download and use ZAP for evil purpose
>> I know the project is open source and a hacker can go and modify the
>> module but that will be more work for him and will refrain the lazy hackers
>> or the ones without Java knowledge and resources, they will have better to
>> move to another tool without this feature.
>> This way we are helping the white hats and not the black ones. Is not the
>> final solution but I think in this way OWASP builds breakers attempting to
>> also help Applications security.
>> Johanna Curiel
>> OWASP Volunteer
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Leaders