log4shell-tool
Log4Shell Enumeration, Mitigation and Attack Detection Tool (by datto)
Log4Shell-Automated
This is an automated script to scan for Log4J vulnerabilities. This is based off of the Datto script. (by Wdrussell1)
log4shell-tool | Log4Shell-Automated | |
---|---|---|
4 | 3 | |
15 | 13 | |
- | - | |
0.0 | 0.0 | |
10 months ago | over 2 years ago | |
PowerShell | ||
Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
log4shell-tool
Posts with mentions or reviews of log4shell-tool.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-20.
- Lacerte Tax - Log4j
-
Evidence of a log4j attack found - Now what?
Start with confirming that an incident took place. My five-minute understanding of Datto's ComStore log4shell tool is that it does two things:
- Log4j PDQ scan profile
-
Automating with PowerShell: Detecting Log4j
For an in-depth explanation of what variables are required, please check the 'Usage' section of the readme viewable at https://github.com/datto/log4shell-tool. This explains the three variables that need to be set and what values to set them to.
Log4Shell-Automated
Posts with mentions or reviews of Log4Shell-Automated.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-14.
- Let us count the ways this snippet is awful
-
Datto's Log4 Script - Automated for Automate
I have taken Datto's Log4 detection script and automated it for the use for MSPs. You can find my script here: https://github.com/Wdrussell1/Log4Shell-Automated
- Automating with PowerShell: Detecting Log4j
What are some alternatives?
When comparing log4shell-tool and Log4Shell-Automated you can also consider the following projects:
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
CIPP - CIPP is a M365 multitenant management solution
incidentresponse
yara - The pattern matching swiss knife
PowerShellSnippets
signature-base - YARA signature and IOC database for my scanners and tools
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
log4shell-tool vs Get-log4j-Windows.ps1
Log4Shell-Automated vs Get-log4j-Windows.ps1
log4shell-tool vs CIPP
Log4Shell-Automated vs CIPP
log4shell-tool vs incidentresponse
Log4Shell-Automated vs yara
log4shell-tool vs PowerShellSnippets
log4shell-tool vs signature-base
log4shell-tool vs CVE-2021-44228-Log4Shell-Hashes