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

[Study] How coslty would it be to store start / end times with ports in view #930

Open
p-l- opened this issue Apr 30, 2020 · 5 comments
Open

Comments

@p-l-
Copy link
Member

p-l- commented Apr 30, 2020

It may be interesting in a view result to know when a certain port has been seen open. For now, start and end times are only stored at the host level.

Storing start and stop times for each port would be handy, but may also be expensive (it might be an option). Also, should we set those time values for the first and last time we saw the port open? Or with the same service, product and version identified? Should we also store a timestamp for scripts elements?

This may be discussed here.

@duncrow
Copy link

duncrow commented May 6, 2020

Personally, I'd love to see start/stop time at port levels, including service and product information. The more information the better :)

At the moment, I run various nmap scans periodically which I import in IVRE and addionally store the output of -oX and -oG on disk with its respective date, so I can search for changes over time. If I could see sort of a "timeline of changes" in IVRE,, I'd really love that feature.

@p-l-
Copy link
Member Author

p-l- commented May 6, 2020

Thanks @duncrow, that's helpful for me to know others may be interested in that!

@itnsec
Copy link

itnsec commented Oct 29, 2021

Very usefull feature, that i would use in incidents analysis ... (since when this port was exposed)
An history view of a specific IP on the WebUI would be enough for me. For now, i use the CLI for that.

@p-l-
Copy link
Member Author

p-l- commented Nov 3, 2021

Very usefull feature, that i would use in incidents analysis ... (since when this port was exposed) An history view of a specific IP on the WebUI would be enough for me. For now, i use the CLI for that.

Interesting. Actually this could be done without changing the view: we could create a /history.html endpoint, for one IP address. I like the idea!

@itnsec
Copy link

itnsec commented Nov 5, 2021

I like the idea 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

3 participants