and you better read the README
This commit is contained in:
parent
2cc4a03090
commit
6d87d11057
13
README.md
13
README.md
@ -8,7 +8,7 @@
|
||||
</p>
|
||||
|
||||
## Abstract
|
||||
Patdown probes DNS servers to determine whether they have resolved domains associated with various EDR/XDR solutions.
|
||||
Patdown probes a network's DNS servers to determine whether they have resolved domains associated with various EDR/XDR solutions.
|
||||
|
||||
**Example**: if a network's resolver has `assets-public.falcon.crowdstrike.com` in its cache, chances are the '*CrowdStrike Falcon*' EDR solution is present somewhere on the network.
|
||||
|
||||
@ -18,17 +18,24 @@ These DNS servers can be specified as arguments (the preferred way), or patdown
|
||||
|
||||
## Installation
|
||||
Retrieve a binary corresponding to your architecture from **Releases**
|
||||
|
||||
*or*
|
||||
`git clone https://git.supernets.org/delorean/patdown.git && cd patdown/cmd/patdown && go build -o patdown main.go`
|
||||
|
||||
`git clone https://git.supernets.org/delorean/patdown.git && cd patdown/cmd/patdown && go build -o patdown main.go && ./patdown`
|
||||
|
||||
## Usage
|
||||
**Help**
|
||||
|
||||
`patdown -h`
|
||||
|
||||
**Targeting specific resolvers**
|
||||
|
||||
**Target specific resolvers**
|
||||
|
||||
`patdown -n ns1.target.resolver -n ns2.another.target.resolver`
|
||||
|
||||
|
||||
**Automatically snoop authoritative nameservers**
|
||||
|
||||
`patdown -t supernets.org`
|
||||
|
||||
- - - -
|
||||
|
Loading…
Reference in New Issue
Block a user