PatrowlEngines | Open Source , Free and Scalable Security Operations | Security Testing library

by Patrowl Python Version: 1.5.9-2 License: AGPL-3.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | PatrowlEngines Summary

PatrowlEngines is a Python library typically used in Testing, Security Testing applications. PatrowlEngines has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. However PatrowlEngines build file is not available. You can download it from GitHub.

PatrOwl is a scalable, free and open-source solution for orchestrating Security Operations. PatrowlEngines is the engine framework and the supported list of engines performing the operations (scans, searches, API calls, ...) on due time. The engines are managed by one or several instance of PatrowlManager.

Support

Quality

Security

License

Reuse

Support

PatrowlEngines has a low active ecosystem.

It has 220 star(s) with 70 fork(s). There are 17 watchers for this library.

It had no major release in the last 12 months.

There are 13 open issues and 64 have been closed. On average issues are closed in 299 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of PatrowlEngines is 1.5.9-2

Quality

PatrowlEngines has 0 bugs and 0 code smells.

Security

PatrowlEngines has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

PatrowlEngines code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

PatrowlEngines is licensed under the AGPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

PatrowlEngines releases are available to install and integrate.

PatrowlEngines has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are available. Examples and code snippets are not available.

PatrowlEngines saves you 5998 person hours of effort in developing the same functionality from scratch.

It has 12515 lines of code, 667 functions and 69 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed PatrowlEngines and discovered the below as its top functions. This is intended to give you an instant insight into PatrowlEngines implemented functionality, and help decide if they suit your requirements.

Start a new scan
Validate a subnet
Returns a list of IPs from a subnet
Check the status of the remote service
Load configuration file
This function is called when a scan is started
Determine the cvss severity
Add an issue
Parse the results from the server
Enumerate a subdomain
Load configuration file
Start a scan
Perform SPF check
Helper function to get whois
Start analyzers
Resolve the reverse DNS address
Search for subdomains
Scan for a domain
Internal function to periodically query the server
Return subdomain s subdomain
Scans the given scan
Inner loop for scanning a scan
Spawns a ScanJS thread
Start a new scanner
Get findings
Load the configuration file
Check for GitHub repositories

Get all kandi verified functions for this library.

PatrowlEngines Key Features

No Key Features are available at this moment for PatrowlEngines.

PatrowlEngines Examples and Code Snippets

No Code Snippets are available at this moment for PatrowlEngines.

Community Discussions

Trending Discussions on Security Testing

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

QUESTION

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

Asked 2021-Apr-08 at 01:04

I have not, but shall DAST* security test, out of curiosity, an IoT device; Nodemcu esp8266 www server I built. It's showing a HTML page (on a mobile phone for example) that allows to control and interact with a camera module and a A/C relay. With it I can for example show images captured in the camera I even think it has some image recognition built in, and I can switch on and off a relay for electrical current to a light bulb (110/220v A/C power)

Before I start pentest I though I better start thinking of what types of exploits one would be able to find and detect? Which sinister exploits I will be able to find, or rather ought be able to find given a proper pentest exercise? (And if I do not find exploits, my approach to the pentest of the Iot might be wrong)

I ponder it might be a totally pointless exercise since the esp8266 www server (or rather its LUA programming libraries) might not have any security built into it, so basically it is "open doors" and everything with it is unsafe ?

The test report might just conclude what I can foresee be that the the "user input needs to be sanitized"?

Anyone have any idea what such pentest of a generic IoT device generally reports? Maybe it is possible to crash or reset the IoT device? Buffer overruns, XXS, call own code ?

I might use ZAP or Burpsuite or similar DAST security test tool.

I could of course SAST test it instead, or too, but I think it will be hard to find a static code analyzer for the NodeMCU libraries and NUA scripting language easily ? I found some references here though: https://ieeexplore.ieee.org/abstract/document/8227299 but it seems to be a long read.

So if someone just have a short answer what to expect in a DAST scan/pentest , it would be much appreciated.

Stay safe and secure out there ! Zombieboy

...

ANSWER

Answered 2021-Apr-08 at 01:04

I do my vulnerability scanning with OpenVAS (I assume this is what you mean by pentesting?). I am not aware of any IOT focused Tools.

If your server is running on esp8266, i would imagine that there is no much room for authentication and encryption of http traffic, but correct me if i am wrong).

Vulnerability Scan results might show things like unencrypted http traffic, credentials transmitted in cleartext (if you have any credentials fields in the pages served by the web server) etc. Depending on if there is encryption, you might also see weak encryption findings.

You might get some false positives on your lua webserver reacting like other known webservers when exploits are applied. I have seen this kind of false positive specially on DoS vulnerabilities when a vulnerability scan is testing a vulnerability and the server becomes unresponsive. Depending on how invasive your vulnerability scanner is, you might get a lot of false positives for DoS on such a constrained platform.

Source https://stackoverflow.com/questions/66995125

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install PatrowlEngines

See the Installation guide.

Support

Please see our Code of conduct. We welcome your contributions. Please feel free to fork the code, play with it, make some patches and send us pull requests via issues.

Find more information at: