Skip to content

Instantly share code, notes, and snippets.

sequence by host.hostname with maxspan=1m
[network where network.direction : ("egress", "outgoing") and
process.name != "spoolsv.exe" and not network.protocol == "dns" and not user.name : "SYSTEM" and
source.port >= 49152 and destination.port >= 49152] by destination.address,source.address, destination.port, source.port
[network where process.name : "spoolsv.exe" and user.name : "SYSTEM" and
network.direction : ("ingress", "incoming") and
not network.protocol == "dns" and
source.port >= 49152 and destination.port >= 49152] by source.address, destination.address, destination.port, source.port
@haram
haram / be_fn.hpp
Last active May 14, 2024 15:37
Replicate BattlEye initialization to dump data out of it
#pragma once
#include <stdint.h>
#include <stdio.h>
namespace be
{
void print_message( const char* msg )
{
printf( "[BATTLEYE] %s\n", msg );
}
@seajaysec
seajaysec / gather.sh
Last active April 29, 2024 16:53
Parses output from CrackMapExec, CrackMapExtreme, Responder, PCredz, and NTLMRelayX.py into aggregate files of hashes and plaintext output
#!/bin/bash
# This script assumes Responder is in /opt/Responder
# Error messages begone!
exec 2>/dev/null
# Hardcoded location for script output files
OUTDIR=${HOME}'/working/loot/gathered'
# Hardcoded location for ntlmrelayx's .sam file output directory
NTLMRELAY=${HOME}'/working/loot/ntlmrelay'
@seajaysec
seajaysec / customqueries.json
Last active June 19, 2024 11:21
bloodhound custom queries
{
"queries": [{
"name": "List all owned users",
"queryList": [{
"final": true,
"query": "MATCH (m:User) WHERE m.owned=TRUE RETURN m"
}]
},
{
"name": "List all owned computers",
@Whipstickgostop
Whipstickgostop / docker-compose.yml
Last active April 20, 2016 03:00
Docker compose for Sentry server with redis and celery workers
redis:
image: redis
sentry-celery-beat:
environment:
SENTRY_SECRET_KEY: 'thisisnotsosecret'
command:
- sentry
- celery
- beat
image: sentry
@vasanthk
vasanthk / System Design.md
Last active July 23, 2024 06:27
System Design Cheatsheet

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

  1. Clarify and agree on the scope of the system
  • User cases (description of sequences of events that, taken together, lead to a system doing something useful)
    • Who is going to use it?
    • How are they going to use it?