An increasing number of sites are supporting HTTP 2.0 which manifests very different than HTTP 1.* traffic. This analyzer adds an http2 log as well as intel framework extensions. Because it is an analyzer it requires access to the compiled source of Bro to be compiled itself as opposed to a regular bro script.

https://github.com/MITRECND/bro-http2

As the http2 analyzer documentation states

Use this checklist to track logstash wiki and documentation

• Update https://github.com/Cyb3rWard0g/HELK/wiki/Create-Plugins-Offline-Package
• Update HELK overview picture
  • remove alien vault integration
  • update with new indexes #256
• document catch all for windows
• document indexme catch all
• some general guideline on X amount of devices and or X amo

These screenshots in this issue serve as static content linked to tutorials, this is not an issue or flaw with the product.

Issue: There is confusion to our current opportunity labeling structure (e.g. Duck - Open).

Discussion:
These labels are stored within the data hosted on ArcGIS Online. Users don't immediately understand that "open" means the opportunity doesn't have a a limit on hunter numbers or access and that "limited" does. It gets even more confusing when we also append a demographic specific opportunity