Czy Wazuh jest bezpieczny?

Wazuh — Nerq Trust Score 48.0/100 (Ocena D). Wynik oparty na 3 independent trust signals.

Wazuh to software tool z wynikiem zaufania Nerq 48.0/100 (D), based on 3 niezależnych wymiarów danych. Konserwacja: 0/100. Popularność: 1/100. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: n/a. Dane odczytywalne maszynowo (JSON).

Czy Wazuh jest bezpieczny?

Szczegóły wyniku zaufania — Wazuh has a Nerq Trust Score of 48.0/100 (D). Measured across 3 independent trust signals.

Analiza bezpieczeństwa → Raport prywatności Wazuh →

Jaki jest wynik zaufania Wazuh?

Wazuh ma Nerq Trust Score 48.0/100 z oceną D. Ten wynik opiera się na 3 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.

Konserwacja
0
Dokumentacja
0
Popularność
1

Jakie są kluczowe ustalenia bezpieczeństwa dla Wazuh?

Najsilniejszy sygnał Wazuh to popularność na poziomie 1/100. Nie wykryto znanych luk w zabezpieczeniach.

⚠Konserwacja: 0/100 — niska aktywność konserwacji
⚠Dokumentacja: 0/100 — ograniczona dokumentacja
⚠Popularność: 1/100 — 135 gwiazdek na pulsemcp

Czym jest Wazuh i kto go utrzymuje?

Autorhttps://github.com/gensecaihq/wazuh-mcp-server
KategoriaBezpieczeństwo
Gwiazdki135
Źródłohttps://github.com/gensecaihq/wazuh-mcp-server

Popularne alternatywy w bezpieczeństwo

bee-san/Ciphey
63.4/100 · C
github
usestrix/strix
64.4/100 · C
github
SWE-agent/SWE-agent
76.9/100 · B
github
promptfoo/promptfoo
82.0/100 · A
github
TecharoHQ/anubis
62.9/100 · C
github

What Is Wazuh?

Wazuh is a bezpieczeństwo tool: Integrates with Wazuh for real-time bezpieczeństwo and threat analysis.. It has 135 GitHub stars. Nerq Trust Score: 48/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.

How Nerq Assesses Wazuh's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Wazuh performs in each:

The overall Trust Score of 48.0/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Wazuh?

Wazuh is commonly evaluated by:

How to read the signals: Wazuh's measured signals (konserwacja 0/100, dokumentacja 0/100, community 1/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.

How to Verify Wazuh's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Wazuh's dependency tree.
  3. Opinia permissions — Understand what access Wazuh requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Wazuh in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=Wazuh
  6. Sprawdź license — Confirm that Wazuh's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
  7. Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Wazuh

When evaluating whether Wazuh is safe, consider these category-specific risks:

Data handling

Understand how Wazuh processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency bezpieczeństwo

Check Wazuh's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.

Update frequency

Regularly check for updates to Wazuh. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Wazuh connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.

License and IP zgodność

Verify that Wazuh's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Wazuh in violation of its license can expose your organization to legal liability.

Best Practices for Using Wazuh Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Wazuh while minimizing risk:

Conduct regular audits

Periodically review how Wazuh is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.

Keep dependencies updated

Ensure Wazuh and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.

Follow least privilege

Grant Wazuh only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for bezpieczeństwo advisories

Subscribe to Wazuh's bezpieczeństwo advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Wazuh is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Wazuh

Nerq's signals are one input. In the following situations, evaluate Wazuh's measured signals against your own requirements before making a decision:

For each situation, compare Wazuh's measured trust score of 48.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Wazuh is suitable for any particular use.

How Wazuh Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among bezpieczeństwo tools, the average Trust Score is 67/100. Wazuh's score of 48.0/100 is below the category average of 67/100.

This suggests that Wazuh trails behind many comparable bezpieczeństwo tools. Organizations with strict bezpieczeństwo requirements should evaluate whether higher-scoring alternatives better meet their needs.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks umiarkowany in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

Trust Score History

Nerq continuously monitors Wazuh and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or konserwacja patterns change, Wazuh's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Wazuh's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Wazuh&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Wazuh are strengthening or weakening over time.

Wazuh vs Alternatywy

In the bezpieczeństwo category, Wazuh scores 48.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Kluczowe wnioski

Często zadawane pytania

Czy Wazuh jest bezpieczny?
Wazuh z wynikiem zaufania Nerq 48.0/100 (D). Najsilniejszy sygnał: popularność (1/100). Wynik oparty na Konserwacja (0/100), Popularność (1/100), Dokumentacja (0/100).
Jaki jest wynik zaufania Wazuh?
Wazuh: 48.0/100 (D). Wynik oparty na Konserwacja (0/100), Popularność (1/100), Dokumentacja (0/100). Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=Wazuh
Jakie są bezpieczniejsze alternatywy dla Wazuh?
W kategorii Bezpieczeństwo, higher-rated alternatives include bee-san/Ciphey (63/100), usestrix/strix (64/100), SWE-agent/SWE-agent (77/100). Wazuh scores 48.0/100.
Jak często aktualizowana jest ocena bezpieczeństwa Wazuh?
Nerq recomputes Wazuh's trust score as new data becomes available. Current: 48.0/100 (D). API: GET nerq.ai/v1/preflight?target=Wazuh
Czy mogę używać Wazuh w środowisku regulowanym?
Wazuh: 48.0/100 (D). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Zobacz także

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

Używamy plików cookie do analiz i buforowania. Prywatność