Skip to content

Releases: MelonSmasher/browserbeat

v0.0.4-alpha3

24 Jan 19:36
Compare
Choose a tag to compare
v0.0.4-alpha3 Pre-release
Pre-release

v0.0.4-alpha3

Changelog

  • Browser support has been expanded to include Microsoft Edge, Edge Beta, Edge Dev, and Edge Canary

Expanded Browser Support:

  • ✅ Microsoft Edge - (Windows & macOS) - Done #15
    • ✅ Microsoft Edge Beta (Windows & macOS) - Done
    • ✅ Microsoft Edge Dev (Windows & macOS) - Done
    • ✅ Microsoft Edge Canary (Windows & macOS) - Done

v0.0.3-alpha2

12 Nov 02:49
ce8e808
Compare
Choose a tag to compare
v0.0.3-alpha2 Pre-release
Pre-release

v0.0.3-alpha2

Changelog

  • Browser support has been expanded to include many alternative browsers. A list of newly supported browsers is below.
  • Code cleanup: functions have been moved to browser-specific files.

Expanded Browser Support:

  • ✅ Chrome Canary (Windows & macOS) - Done #2
  • ✅ Chrome Beta (linux) - Done #2
  • ✅ Chrome Dev (linux) - Done #2
  • ✅ Chromium (All) - Done #1
  • ✅ Vivaldi (All) - Done #4
  • ✅ Opera (All) - Done #7
  • ✅ K-Meleon (Windows) - Done #9
  • ✅ Brave (All) - Done #11

v0.0.2-alpha1

08 Nov 03:31
Compare
Choose a tag to compare
v0.0.2-alpha1 Pre-release
Pre-release

Change Log

  • Fixed an issue with Firefox on Windows - See #3

v0.0.1-alpha1

07 Nov 02:09
Compare
Choose a tag to compare
v0.0.1-alpha1 Pre-release
Pre-release

About

Browserbeat is a lightweight passive solution for web traffic monitoring based on the Elastic libbeat platform. Browserbeat gives sysadmins the ability to monitor web traffic on managed computers without an HTTP proxy, packet capture, or DNS request monitoring.

Browserbeat compared to:

DNS traffic logs

  • Data obtained by Browserbeat is much less noisy than DNS traffic since traffic created by system services and other protocols will show up in DNS traffic logs.
  • You will know if the browser has visited an IP address directly.
  • You'll know the user who made the request not just the client IP
  • You'll know the computer name that made the request not just the client IP
  • You'll know the web browser used to make the request
  • You'll know the operating system used to make the request

HTTP proxy

  • No need to distribute & maintain custom certificates to monitor HTTPS traffic
  • You'll know the user who made the request not just the client IP
  • If Browserbeat or the output fails, the user's browsing is not interrupted like if a proxy server goes down
  • Less complexity on your network

Packet Sniffing/Capture

  • You'll know the user who made the request not just the client IP
  • Less complexity on your network
  • Depending on the method used for packet sniffing, the user's browsing is not interrupted if a component fails

Features

  • Know the user who made the request
  • Know the IP of the computer
  • Know the hostname of the computer
  • Know the requested hostname
  • Know the URL requested
  • Know the title of the website
  • Know the date & time the request was made
  • Know the host OS
  • Know the browser that made the request
  • Cross-platform support: Windows, macOS, and Linux
  • Cross-browser support: Chrome, Firefox, and Safari
  • Output data to all of the standard Elastic Beat outputs

Browser Support

  • ✅ Chrome - Done
  • ✅ Firefox - Done
  • ✅ Safari - Done
  • 💛 Chromium - Should be similar to Chrome
  • 💛 Opera - Haven't investigated yet
  • 💛 Vivaldi - Haven't investigated yet
  • 🆘 Edge - M$ is too cool and uses an ESE database anyone know of an ESE DB library for go?
  • 🆘 IE 11 - M$ is too cool and uses an ESE database anyone know of an ESE DB library for go?
  • 💛 Chrome Canary - Should be similar to Chrome