Don't Just Search OSINT. Sweep It.
Branch: master
Clone or download
Latest commit 13d93a4 Jan 29, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Update Jan 29, 2019
default Update Dec 28, 2018
etc Show usage and example in comments (#2). Dec 19, 2018
local Move to default Nov 30, 2018
lookups Initial commit Nov 16, 2018
metadata Update Dec 7, 2018
static/assets Add ability to search for specific filetypes Dec 7, 2018
LICENSE Update Dec 28, 2018
README.md Update Dec 29, 2018

README.md

[OSweep™]

Don't Just Search OSINT. Sweep It.

Description

If you work in IT security, then you most likely use OSINT to help you understand what it is that your SIEM alerted you on and what everyone else in the world understands about it. More than likely you are using more than one OSINT service because most of the time OSINT will only provide you with reports based on the last analysis of the IOC. For some, that's good enough. They create network and email blocks, create new rules for their IDS/IPS, update the content in the SIEM, create new alerts for monitors in Google Alerts and DomainTools, etc etc. For others, they deploy these same countermeasures based on provided reports from their third-party tools that the company is paying THOUSANDS of dollars for.

The problem with both of these is that the analyst needs to dig a little deeper (ex. FULLY deobfuscate a PowerShell command found in a malicious macro) to gather all of the IOCs. And what if the additional IOC(s) you are basing your analysis on has nothing to do with what is true about that site today? And then you get pwned? And then other questions from management arise...

See where this is headed? You're about to get a pink slip and walked out of the building so you can start looking for another job in a different line of work.

So why did you get pwned? You know that if you wasted time gathering all the IOCs for that one alert manually, it would have taken you half of your shift to complete and you would've got pwned regardless.

The fix? OSweep™.

Prerequisites

Before getting started, ensure you have the following:
Ubuntu 18.04+

  • Python 2.7.14 ($SPLUNK_HOME/bin/python)
  • Splunk 7.1.3+
  • Deb Packages
    • gcc
    • python-pip

CentOS 7+

  • Python 2.7.14 ($SPLUNK_HOME/bin/python)
  • Splunk 7.1.3+
  • Yum Packages
    • epel-release
    • gcc
    • python-pip

Optional Packages

  • Git

Click HERE to get started.

Gallery

Feed Overview - Dashboard
Feed Overview - Dashboard

The Round Table - Dashboard
The Round Table - Dashboard

Certificate Search - Dashboard crtsh - Dashboard

CyberCrime Tracker - Dashboard CyberCrime Tracker - Dashboard

Cymon - Dashboard Cymon - Dashboard

GreyNoise - Dashboard
GreyNoise - Dashboard

Phishing Catcher - Dashboard
Phishing Catcher - Dashboard

Phishing Kit Tracker - Dashboard
Phishing Kit Tracker - Dashboard

Ransomare Tracker - Dashboard Ransomare Tracker - Dashboard

ThreatCrowd - Dashboard ThreatCrowd - Dashboard

Twitter - Dashboard Twitter - Dashboard

URLhaus - Dashboard URLhaus - Dashboard

urlscan.io - Dashboard urlscanio - Dashboard

Dashboards Coming Soon

  • Alienvault
  • Censys
  • Hybrid-Analysis
  • Malshare
  • PulseDive

Please fork, create merge requests, and help make this better.