Sooty is a tool developed with the task of aiding SOC analysts with automating part of their workflow. One of the goals of Sooty is to perform as much of the routines checks as possible, allowing the analyst more time to spend on deeper analysis within the same time-frame.
Sooty is now proudly supported by Tines.io! The SOAR Platform for Enterprise Security Teams.
- Sanitise URL's to be safe to send in emails
- Perform reverse DNS and DNS lookups
- Perform reputation checks from:
- Check if an IP address is a TOR exit node
- Decode Proofpoint URL's, UTF-8 encoded URLS, Office SafeLink URL's, Base64 Strings and Cisco7 Passwords.
- Get file hashes and compare them against VirusTotal (see requirements)
- Perform WhoIs Lookups
- Check Usernames and Emails against HaveIBeenPwned to see if a breach has occurred. (see requirements)
- Simple analysis of emails to retrieve URL's, emails and header information.
- Extract IP addresses from emails.
- Unshorten URL's that have been shortened by external services. (Limited to 10 requests per hour)
- Query URLScan.io for reputation reports.
- Analyze email addresses for known malicious activity and report on domain reputation utilising EmailRep.io
- Create dynamic email templates that can be used as a base for phishing triage response.(.msg only, .eml coming in future update)
- Perform analysis enrichment on phishing mails using the HaveIBeenPwned database, (Requires API Key).
- Python 3.x
- Install all dependencies from the requirements.txt file.
pip install -r requirements.txt - Several API Keys are required to have full functionality with Sooty, however it will still function without these keys, just without the added functionality they provide, links are found below:
- Replace the corresponding key in the
example_config.yamlfile, and rename the file toconfig.yaml, example layout below:
- If you wish to work on a feature, leave a comment on the issue page and I will assign you to it.
- All code modifications, enhancements or additions must be done through a pull request.
- Once reviewed and merged, contributors will be added to the ReadMe
- If an issue / bug is found please open a ticket in the issue tracker and use the bug report template. Fill in this template and include any additional relevant information.
- If you wish to work on a known bug, leave a comment on the issue page and open a Pull Request to track progress. I will assign you to it.
- If there is an issue with installation or usage, use the supplied template and I will respond asap.
- New features / requests should start by opening an issue. Please use the accompanying template when creating a new issue. This helps track new features and prevent crossover. Attach any additional info that seems relevant if necessary. Before creating a new issue please check the Projects Tab to see if this issue has already been requested, or directly with the other open issues.
- Added first iteration of dynamic email templates that generate based on Sooty's analysis, example below:
- Added first iteration of the Phishing tool.
- Able to analyze an email (outlook / .msg only tested at the moment) and retrieve emails, urls (Proofpoint decode if necessary) and extract info from headers.
- Extract IP's from body of email.
- Reputation check on sender of email, and provide enriched information.
- Improved Rep Checker
- Added HaveIBeenPwned Functionality
- Added DNS Tools and WhoIs Functionality
- Added Hash and VirusTotal Checkers
- Added Abuse IPDB, Tor Exit Node, BadIP's to Reputation Checker
- Initial Release
- URL and ProofPoint Decoder
- Initial implementation of Reputation Checker
- Sanitize links to be safe for email
This is an outline of what features will be coming in future versions.
- Scan email attachments for malicious content, macros, files, scan hashes, etc.
Add dynamic email templates that generate based on Sooty's analysis.Edit: Added- Verify MX Records
- Perform DKIM Verification
- Add ability to analyze .pcap files and provide concise, enriched information.
- Add a 'New Case' Feature, allowing output of the tool to be output to a txt file.
- Aaron J Copley for his modified version of ProofPoint's code to decode ProofPoint URL's
- James Duarte for adding a hash and auto-check option to the hashing function
- mrpnkt for adding the missing whois requirement to requirements.txt
- Gurulhu for adding the Base64 Decoder to the Decoders menu.
- AndThenEnteredAlex for adding the URLScan Function from URLScan.io
- Eric Kelson for fixing pywin32 requirement not necessary on Linux systems in requirements.txt.
- Jenetiks for removing and tidying up duplicate imports that had accumulated over time.
- Nikosch86 for fixing an issue with hexdigest not correctly storing a file hash.
- Naveci for numerous bug fixes, QoL improvements, Cisco 7 Password Decoding, and introduced a workflow to helps with issues in future.
- Paralax for fixing typo's in the readme.
