Monitorizer | Multithreaded monitoring framework to detect and report | Security Testing library

by BitTheByte Python Version: Current License: No License

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

kandi X-RAY | Monitorizer Summary

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

Multithreaded monitoring framework to detect and report newly found subdomains on a specific target using various scanning tools with support for Acunetix & Nuclei

Support

Quality

Security

License

Reuse

Support

Monitorizer has a low active ecosystem.

It has 120 star(s) with 30 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 6 have been closed. On average issues are closed in 49 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Monitorizer is current.

Quality

Monitorizer has 0 bugs and 0 code smells.

Security

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

Monitorizer code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Monitorizer does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

Monitorizer releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Monitorizer saves you 2448 person hours of effort in developing the same functionality from scratch.

It has 5396 lines of code, 318 functions and 39 files.

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

Top functions reviewed by kandi - BETA

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

General enumeration
Return unique elements
Scrape crt sh
Perform brute reverse lookup
Scrapebing domain
Check for zone transfer
Return a list of all IP addresses found in hostname
Checks if the given address is valid
Construct a zone from the wire protocol
Scrape a domain
Returns a list of the IP addresses
Returns a list of MX records
Find the DNS records in the cache
Extract all subdomain domains from a file
Create sqlite database
Run brute force - force brute force
Run the wordlist algorithm
Parse the XML file
Create a DNS record from a list of dictionaries
Handle DNS results
Write data to a database
Revert TLDs
Searches for nameservers
Print usage
Extract hostnames from a file
Performs a brute reverse lookup
Generate a csv line from a dict
Sets up the domain
Check the existence of a DNS domain

Get all kandi verified functions for this library.

Monitorizer Key Features

No Key Features are available at this moment for Monitorizer.

Monitorizer Examples and Code Snippets

No Code Snippets are available at this moment for Monitorizer.

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 Monitorizer

Before we start you need to install the requirements. After installing the requirements now you're ready to go.
Python >= 3.6 ( python 2 is not supported )
Linux server e.g(Amanzon EC2) [64bit]

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: