-
Notifications
You must be signed in to change notification settings - Fork 456
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
Deploying npcap with Network Packet Capture integration #2132
Labels
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
jamiehynds
added
Workflow_wg: data_onboarding
Epic
Theme: just_ingest_it
and removed
8.0 candidate
Epic
labels
Nov 16, 2021
5 tasks
This was referenced Nov 23, 2021
@efd6 are we ok to close this one or any loose ends remaining? |
I think we can close this. |
Closing as all the development effort is now complete to include npcap with both Packetbeat and the Network Packet Capture integration. Targeting 8.1 for release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our Network Packet Capture integration (based on Packetbeat) requires a packet sniffing library on most platforms. This is a non-issue on most platforms as you can install libpcap, however Windows requires a library such as npcap, which implements the libpcap interfaces.
NPCAP licensing only allows installation on 5 nodes, after which a license is required. This was often a surprise to our users, who ended up having to pay a significant sum for a license, plus annual maintenance cost. NCPAP also has to be installed independently.
We now have an OEM NPCAP license which allows us to distribute npcap and deploy silently. This ensures our users no longer have to incur additional npcap licensing costs and can easily deploy npcap.
Requirements
The text was updated successfully, but these errors were encountered: