Component inclusion request: cs-abuseipdb-bouncer (AbuseIPDB reporting integration)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start by reading the CrowdSec Hub contribution requirements and the component specifications referenced in the issue, then compare them with the linked integration's documentation and compliance matrix. The issue asks whether this outbound reporting integration fits the Remediation Components Hub or another category; done means confirming eligibility and the appropriate category, with any required inclusion changes identified.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Hello CrowdSec team,
I'd like to request inclusion of cs-abuseipdb-bouncer in the CrowdSec Hub as a community-maintained integration.
Repository Information
- Repository: https://github.com/developingchet/cs-abuseipdb-bouncer
- License: MIT
- Status: Stable, actively maintained
- Language: Go
- Latest release: v2.5.3
- Docker Hub: https://hub.docker.com/r/developingchet/cs-abuseipdb-bouncer
- GHCR: ghcr.io/developingchet/cs-abuseipdb-bouncer
- Platforms: Linux AMD64/ARM64, Windows AMD64 binary
Description
cs-abuseipdb-bouncer is a standalone CrowdSec integration that automatically reports qualifying malicious IP addresses detected by CrowdSec to AbuseIPDB.
It consumes CrowdSec Local API decisions, maps scenarios to AbuseIPDB categories, and submits reports with filtering, deduplication, rate limiting, and persistent retry handling.
Key Capabilities
CrowdSec Integration
- Stream-based decision consumption via the official go-cs-bouncer library
- 10-second default polling interval, configurable down to 2 seconds
- API key and mTLS authentication
- Versioned User-Agent identification
- LAPI usage telemetry through /v1/usage-metrics
AbuseIPDB Reporting
- Automatic reporting of qualifying ban decisions
- Scenario mapping covering 22 of 23 AbuseIPDB categories
- Private, reserved, invalid, and whitelisted IP filtering
- Per-IP cooldown and daily API quota enforcement
- Concurrent reporting worker pool
- Persistent retry queue with exponential backoff
- HTTP rate-limit and Retry-After handling
Reliability and Observability
- bbolt-backed persistent state
- Prometheus metrics
- Health and readiness endpoints
- Structured JSON logging
- Graceful shutdown
Security and Supply Chain
- Distroless, non-root Docker container
- Read-only filesystem and dropped capabilities
- Seccomp syscall restrictions
- Credential redaction and TLS enforcement
- Cosign-signed images
- CycloneDX SBOM
- Automated vulnerability scanning
Documentation
- README
- Installation and Uninstallation
- Configuration Reference
- Troubleshooting
- Architecture and Design
- CrowdSec Compliance Matrix
Automated Testing
- CI workflow
- Go unit tests, race detection, and coverage enforcement
- govulncheck and Trivy vulnerability scanning
- Seccomp validation and container integration testing
- Successful v2.5.3 release workflow
Component Classification
This project is an outbound threat intelligence reporting integration, rather than an inline traffic enforcement component.
It consumes CrowdSec decisions and forwards qualifying detections to AbuseIPDB. It does not directly block traffic, enforce firewall rules, or provide CAPTCHA challenges.
The implementation follows the applicable CrowdSec specifications for stream mode, component identification, authentication, and LAPI usage telemetry.
Would this reporting integration be eligible for the Remediation Components Hub, or would another Hub category be more appropriate?
I'm happy to make any adjustments necessary for inclusion.
Thank you for considering the project.
- Lingua principale
- Python
- Stelle
- 257
- Fork
- 235
- Merge medio
- 3g 20h
- PR unite (30g)
- 27
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di crowdsecurity/hub
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
crowdsecurity/hub#1999 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
crowdsecurity/hub#1998 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
traefik-logs: CLF lines with an escaped quote in the User-Agent are droppedForse già presa @stephdl l’ha presa 4 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
crowdsecurity/hub#1977 ·
I maintainer di solito rispondono entro 1 giorno
-
f5-big-ip-cve-2020-5902 and pulse-secure-sslvpn-cve-2019-11510 compile 4 regexes per HTTP line (`Upper(x) matches Upper('...')`)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
crowdsecurity/hub#1964 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(plex-allowlist): allow subtitle transcode bursts on HTTP 400Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 82/100
crowdsecurity/hub#1945 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di crowdsecurity/hub
Issue simili
-
integration: logger
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
home-assistant/core#191147 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
documentation p4
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
MillenniumDawn/focus-tree-creation-tool#417 ·
I maintainer di solito rispondono entro 3 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
CharlesP44/Beem_Energy#96 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
rheeloaded/paperpull#153 ·
I maintainer di solito rispondono entro 1 giorno