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

Roadmap #41

Open
6 of 22 tasks
rsmmr opened this issue Apr 22, 2022 · 3 comments
Open
6 of 22 tasks

Roadmap #41

rsmmr opened this issue Apr 22, 2022 · 3 comments

Comments

@rsmmr
Copy link
Member

rsmmr commented Apr 22, 2022

The following is a list of functionality that's on the radar for future versions of the Zeek Agent. Not everything is committed to, or planned out yet; this is primarily a record of ideas. Feedback welcome, just leave comments in this ticket.

Configuration/Deployment/Usage

  • Auto-discovery of upstream Zeek connectivity
  • Communication proxy aggregating and relaying messages
  • Local configuration file (already exists, not yet finalized & documented)
  • Remote agent configuration (other than queries)
  • Provide user-accessible audit log of requested/transmitted information (simple logging in place already)
  • Option to allow user to filter data returned by then agent
  • Switch upstream communication to WebSocket protocol, and remove Broker (Add communication over WebSocket #43)

Tables:

  • Evented versions of current tables through OS-specific APIs
    • Processes
    • File modifications
    • Network connections / sockets
  • Windows system registry modifications
  • System services
  • Module / kernel extensions loads
  • Scripts Loading (Windows)
  • Fileless Script loads (Windows)
  • Cross Process events (?)

Packaging & OS integration

Integrations

  • Export query results as JSON for consumption by external systems
@rsmmr rsmmr pinned this issue Apr 22, 2022
@timwoj
Copy link
Member

timwoj commented Apr 26, 2022

One other I'd add (possibly as part of #40) is installing/running the Windows agent as a service instead of just a regular process.

@rsmmr
Copy link
Member Author

rsmmr commented Apr 27, 2022

One other I'd add (possibly as part of #40) is installing/running the Windows agent as a service instead of just a regular process.

Yeah, that applies in some form to Linux and macOS too: we should provide service definitions Added that all to the list.

@timwoj
Copy link
Member

timwoj commented Jul 22, 2022

I checked off Windows service since the installer already installs it as a service.

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

No branches or pull requests

2 participants