Skip to content
KitploitKITPLOIT
أدواتعمليات الاستغلالالمدونة
Log in
إرسال
أدواتعمليات الاستغلالالمدونة
إرسال

أدوات الاختراق واختبار الاختراق والأمن السيبراني لترسانتك الأمنية!

Kitploit هو دليل لأدوات الاختراق والأمن السيبراني واختبار الاختراق. اكتشف آخر تحديثات المشاريع للعثور على الثغرات وتحليل الأنظمة وأتمتة الاختبارات وتعزيز أمنك.

الخلاصاتاتصالالخصوصية© 2026 Kitploit

دليل الأدوات

الفئات

عرض جميع الفئات
Loading categories
NcStatusCheck — Monitoring centralisé pour instances Nextcloud multiples | Kitploit
أدوات/GitLabGitLab/jp.louvel/ncstatuscheck
Vulnerability AnalysisConfiguration AuditingCloud Security
GitLabjp.louvel/ncstatuscheck

NcStatusCheck

Monitoring centralisé pour instances Nextcloud multiples

عرض المستودع
2148منذ 22س 36دلم تتم المراجعة بعد
مشاركة
المحتوى غير متوفر باللغة المطلوبة. عرض النسخة الإنجليزية.

NcStatusCheck

Centralized monitoring for multiple Nextcloud instances

NcStatusCheck is a monitoring tool that lets you track the health of multiple Nextcloud servers from a single web interface: Nextcloud and PHP versions against their security floor, branch end of life, reachability, configuration warnings, installed apps, Docker containers and known vulnerabilities.

Dashboard: fleet table, branch lifecycle and synthesis cards

Server detail page: state tiles, version, instance summary and issues by area

Fleet-wide apps watch, sorted by what each finding asks of you

🎯 Features

Monitoring

  • Three data collection modes per server: Basic (NC version only), Extended (full data via the serverinfo API) and Push (data sent by the remote instance)
  • Version analysis for Nextcloud and PHP against a security floor that the cron keeps in sync with official releases, with a grace delay (nc_update_grace_days) so an instance is only flagged a few days after a patch is released
  • Branch lifecycle: end of life of each Nextcloud branch (official schedule), next release dates, and how many of your servers run each branch
  • Up/down tracking: current reachability plus a bounded journal of confirmed transitions, which feeds a 30-day availability % and an incident list
  • SSL certificate expiry, read from the existing HTTPS probe (no extra request)
  • Known vulnerabilities (opt-in): Nextcloud, Collabora and OnlyOffice advisories matched against the versions your fleet actually runs
  • Installed apps audit: cross-checks occ app:list against the Nextcloud app store (upgrade-blocking or incompatible apps, updates available, maturity and turbulence signals)
  • Docker containers: stopped, restarting or unhealthy containers, and image updates checked against the registry tag catalogue (patch in your branch, newer branch). When several watched instances share a machine, containers are attributed to their own instance
  • Proactive alerts (webhook and/or email): up/down state changes, plus slow signals (SSL expiry, vulnerable version, stale Push probe, critical audit report, blocking app finding, broken occ). One alert per new condition, no reminder spam
  • Pause a server (migration, decommissioning): probes and alerts are suspended, the row stays visible
  • Desktop client watch: current version, release candidate in flight, measured release pace

Dashboard

  • Fleet table (Server | Nextcloud | PHP | Health) and branch lifecycle table side by side on wide screens
  • Health column following "silence = all good": badges only when there is something to act on
  • What's new: every signal the dashboard shows (warning, app or Docker finding, advisory, version, certificate, outage…) is dated when it appears, changes or goes away. The top of the page lists what moved since your last « mark as seen » (kept per account, so it follows you from one device to another; the last 24 h until you first mark), grouped by fact across servers, with a 30-day history. New items are flagged with a blue dot on the row badges too
  • To deal with: one line of chips, only what asks for something, most urgent first (offline, broken occ, vulnerabilities, Nextcloud updates, warnings, apps, Docker, end-of-life PHP, certificates…). A chip filters the table on the servers it counts; its ▸ opens the details
  • Fleet watch for apps and Docker images, sorted by what you have to do: To review, To do, To plan, and a folded Context group
  • Filters on one line, with counts: Nextcloud status, PHP status, state (new, offline, maintenance, warnings, apps, Docker, vulnerabilities, probe error…), Docker image, tags and text search
  • Tags under each server name, clickable to filter (several tags = all at once): your own tags (client:durand, lab…), plus a 🖥 tag naming the machine when several monitored instances run on the same server (detected from Push, script v12+), one colour per machine. A tag written type:value takes the colour of its type, so every client:… tag shares one colour
  • FR / EN / DE interface

Detail page

  • State tiles above the tabs: reachability, 30-day availability (incident list in a window), SSL certificate, freshness of each probe
  • Overview: version verdict, muted alerts (acknowledgements with their reason and expiry), instance summary (PHP, web server, database, cache, deployment, and satellite tools such as the office suite, Talk HPB or whiteboard, as seen from apps and containers), then issues grouped by area
  • Tabs: technical information, applications, Docker containers, probes
  • Tags under the URL, editable in place, with the other instances running on the same machine
  • Every warning can be acknowledged (reason + optional expiry)
  • Server audit report when the instance pushes its monthly nc-audit.sh report

Administration

  • Servers: add a server by its URL (https:// optional), then configure its probes on its card (serverinfo token with a Test button, Push token and ready-to-use script generator), tag it, pause or remove it
  • Shared hosts: say which Docker compose stack belongs to which instance when several watched Nextclouds share a machine
  • NC / PHP versions: security floors, status rules, resync from official releases
  • App warnings: a manual known-bug list
  • Notifications: the effective alert configuration (set in config.php, shown read-only) and a test button
  • IP filtering: generates nginx / Apache / ufw allowlist rules
  • Silences: audit of every acknowledgement across the fleet, and which ones still hide something
  • Collection modes: help for the three probes
  • "Trigger Push" button on the dashboard: asks every Push server to send its data at its next cron run

🏗️ Architecture

تنزيل الأداة

الأكثر شعبية

عرض الكل →

اكتشف الأدوات الأكثر استخدامًا من قبل مجتمعنا.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 مجموعة أدوات OSINT المثالية: رسم بياني للتحقيق، وتقييم الثقة، وعائلات الأسماء المستعارة، وخريطة، وخط زمني، وتقارير. 49 وحدة، وأكثر من 400 موقع، دون الحاجة إلى مفاتيح API.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # تطبيق GhostLock للتنفيذ بنقرة واحدة (CVE-2026-43499)

    548
  • 3

    redforge

    cybersecurity91/redforge

    مجموعة أدوات الفريق الأحمر في المتصفح مع 102 أداة دون اتصال للاستطلاع، وتوليد الحمولات، وهجمات بيانات الاعتماد، والتشفير، والترميز، وإعداد تقارير المهام.

    366
  • 4

    ARTEX

    baarai/artex

    منصة اختبار اختراق مستقلة متعددة الوكلاء تعتمد على LLM، مع وكلاء تخطيط وتنفيذ، ومخططات للأصول والاستكشاف، وتسجيل حركة مرور MITM، وإعادة اختبار الثغرات.

    362
  • 5

    looking-glass

    anonghosty/looking-glass

    منصة CSIRT تستقبل تقارير Shadowserver في MongoDB وتعيد عرضها كخرائط تفاعلية وتحليلات ونتائج وإرشادات ولوحات معلومات تنفيذية.

    311
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    نظام العمل للأمن السيبراني الأصلي بالذكاء الاصطناعي — حيث تتحول النية إلى تنفيذ محكوم، وتصبح الأدلة ذاكرة تشغيلية، وكل عملية تحسن التي تليها.

    287

استكشف جميع الأدوات

تصفح مجموعتنا من الأدوات

عرض جميع الأدوات →