/threatbutt

:trollface: ThreatButt API PowerShell integration for SIEM automation...

Primary LanguagePowerShellGNU General Public License v2.0GPL-2.0

ThreatButt

PowerShell Attribution Dice

greg . foss [at] owasp . org

v0.1 -- May 2015

[About]

ThreatButt + SIEM Integration = Defense in Derpth(TM)

Currently everyone is being attacked, all the time, by people from all over the world. But, how do we know who is actually attacking our networks? Thankfully the folks at ThreatButt have developed a groundbreaking threaty threat attribution feed. Using their patented Clown Strike technology we are able to harness the raw power of private, hybrid, public and cumulus cloudsystem to bring Viking grade threat intelligence to any enterprise.

With this technology we can know instantly who attacked us, from where, using what tech and most importantly, generate loud and progressively more annoying voice-alerts that provide the SOC with 100% accurate information about the attack throughout the day.

[How To]

This script is super complicated and requires a Computer Science degree to operate:

PS C:\> .\threatbutt.ps1

After you run this once... You can simply invoke the threatbutt to replay the script:

PS C:\> butt

No need to provide real data, the ThreatButt knows who is attacking you and why...

Script

Make sure you have your volume turned up!

Once the script executes, it creates log files. You can use these to find known malicious activity, just search for the EVID 1337!

EVIDs

If you're a ninja, integrate this with your SIEM so that you know when attacks happen and can announce it throughout the company.

SmartResponse

[Use Cases]

  1. Configure as a LogRhythm SmartResponse(TM) to fire for alarms of your choosing!

  2. Run this on infected systems to automatically know what APT resides there

  3. Execute this remotely on unsuspecting user's systems... Better yet, create a scheduled task!

  4. Just run it, yo!

[DISCLAIMER]

  1. This is an Obvious Parody...

  2. LogRhythm does not actually endorse any of this in any way, shape, or form

  3. All attribution data is randomly generated

  4. We don't even send any real data to their API, for obvious reasons

  5. How do you computer?

[LICENSE]

Copyright (c) 2015, Greg Foss All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name of Greg Foss nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.