Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collecting IP Addresses #247

Open
nil0x42 opened this issue Apr 9, 2019 · 8 comments
Open

Collecting IP Addresses #247

nil0x42 opened this issue Apr 9, 2019 · 8 comments

Comments

@nil0x42
Copy link
Contributor

nil0x42 commented Apr 9, 2019

It would be nice to have an option to collect IP Addresses of computers.
And have it in the "Service Principal Names" or even a dedicated "IP Addresses" section

@andyrobbins
Copy link
Contributor

I think our major concern is networks that dynamically assign IPs to systems as opposed to using static addresses. Because we collect FQDNs for each computer, we just use those names to connect to systems, or query DNS if we need an IP. Can you describe a little more what your use-case would be?

@jesseflorig
Copy link
Contributor

It might be cool to display an IP with an ingestion timestamp and put a refresh button next to it that queries DNS for a fresh IP.

@nil0x42
Copy link
Contributor Author

nil0x42 commented Apr 18, 2019

@andyrobbins my use case if for big networks with a lot of tricky firewall rules that allow only certain internal IP ranges to communicate with others.

Having the IP already displayed in the machine attributes would be a big gaing of time for those cases, as we don't need to re-check each time in which subnet range is an IP before choosing the best usable path.

Generally, i think it's always useful to have this information when IPs are statically assigned, as this information helps extrapolating neighbor machines, purposes of each machine, etc..

And when the IP is dinamically assigned, we can simply ignore this field (and maybe there is a way to detect ip IPs are dinamically attributed)

@SpecterOps SpecterOps deleted a comment Apr 25, 2019
@n00py
Copy link

n00py commented Apr 27, 2020

I believe this would be a useful feature. Some entries will go stale (DHCP), but so do other collection attributes, such as sessions. When I'm hunting for a tricky pivot, I find myself constantly manually resolving hostnames.

@sbnas-project
Copy link

I believe this would be a useful feature. Some entries will go stale (DHCP), but so do other collection attributes, such as sessions. When I'm hunting for a tricky pivot, I find myself constantly manually resolving hostnames.

I second this as well, seeing good pivoting points would be very helpful.

@PwnPeter
Copy link

PwnPeter commented Jun 1, 2021

I totally agree, it would be an interesting feature

@randomactsofsecurity
Copy link

Agreed, would be nice to see this as well

@derekkddj
Copy link

any update? i wopuld love this feature too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants