Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

AuditCore — Network Security Audit Suite

v1.0.0

AuditCore — Suite completa de auditoría de seguridad para infraestructura de red. Cubre 6 vendors (F5, Cisco, Fortinet, Palo Alto, Juniper, Arista), 5 framew...

0· 34·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for santanallen/auditcore-network-audit.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AuditCore — Network Security Audit Suite" (santanallen/auditcore-network-audit) from ClawHub.
Skill page: https://clawhub.ai/santanallen/auditcore-network-audit
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install auditcore-network-audit

ClawHub CLI

Package manager switcher

npx clawhub@latest install auditcore-network-audit
Security Scan
Capability signals
CryptoCan make purchasesRequires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The files and instructions match the stated purpose: vendor knowledge-bases, framework checks, and report generation. Vendor KBs list read-only commands and forbidden write-commands, framework/report skills read and write findings/reports to local MEMORY paths—these are expected for an audit suite.
Instruction Scope
The SKILL.md files consistently instruct read-only evidence collection and saving outputs to MEMORY paths (expected). However remediation formats and example scripts include write actions (e.g., 'set {remediation_cmd}', 'commit', 'tmsh modify', 'configure', 'commit confirmed') and explicit backup/apply/rollback command templates. The core methodology repeatedly forbids auto-executing changes, but the presence of ready-to-run remediation commands and rollback steps increases the chance of accidental or improper execution if operator gating is not enforced. tools-secops explicitly lists many offensive/exploitation and network pivot tools and describes agent execution of local tools (with operator confirmation required for exploitation)—this widens the agent's operational scope and requires careful runtime controls.
Install Mechanism
Instruction-only skill: no install spec, no external downloads, and no code files to execute. This lowers installation risk; the skill assumes existing local tooling and host paths (tools-secops), which is reasonable for a security-audit suite.
Credentials
No environment variables, no external credentials declared, and no required config paths. The skill expects SSH/CLI/API access to target devices (implied by commands) but does not request unrelated secrets. This is proportionate to the stated functionality.
Persistence & Privilege
always:false, no install, and no automatic model-disable flags. The skill writes evidence and reports to local MEMORY paths (part of its function) but does not request persistent elevated privileges or try to change other skills or system-wide agent settings. The main privilege concern is the potential content (sensitive credentials) being saved to disk if sanitization is not correctly enforced.
What to consider before installing
This package appears to be a legitimately structured network-audit suite, but take these precautions before installing or running it: - Review audit-auto-generate: it claims to auto-generate vendor skills — ask for the full content and confirm it does not dynamically create executable code or remote fetchers without human review. - Treat remediation output as advisory only: the skill includes remediation templates that contain 'commit'/'configure'/'tmsh modify' and other write/commit operations. Ensure your agent/platform enforces the 'generate-only' rule and does not auto-apply any remediation scripts. - Run first in an isolated lab: because tools-secops lists many offensive/exploit and pivoting tools (hydra, chisel, ligolo-ng, socat, etc.), test the workflow in a controlled environment to confirm operator confirmation gates and sanitization are effective. - Confirm evidence handling and sanitization: the methodology promises masking of passwords/keys and ephemeral credentials, but verify at runtime that MEMORY/evidence/ paths are secure, that saved files are sanitized, and that you control retention/cleanup. - Verify local tooling expectations: the skill assumes many binaries exist at specific paths; if those tools run under the agent's authority they could perform impactful actions—ensure the agent is allowed to execute only the tools you trust and that destructive tools require explicit operator confirmation. If you want to proceed, ask for the full text of audit-auto-generate and the precise runtime enforcement model (how the platform prevents accidental execution of remediation or exploit tooling).

Like a lobster shell, security has layers — review code before you run it.

auditvk97d7pfn52gzf78w31cknqwfb985m7y8cisvk97d7pfn52gzf78w31cknqwfb985m7y8ciscovk97d7pfn52gzf78w31cknqwfb985m7y8compliancevk97d7pfn52gzf78w31cknqwfb985m7y8f5vk97d7pfn52gzf78w31cknqwfb985m7y8fortinetvk97d7pfn52gzf78w31cknqwfb985m7y8iso27001vk97d7pfn52gzf78w31cknqwfb985m7y8latestvk97d7pfn52gzf78w31cknqwfb985m7y8networkvk97d7pfn52gzf78w31cknqwfb985m7y8nistvk97d7pfn52gzf78w31cknqwfb985m7y8pcidssvk97d7pfn52gzf78w31cknqwfb985m7y8
34downloads
0stars
1versions
Updated 14h ago
v1.0.0
MIT-0

AuditCore — Network Security Audit Suite v2.0

Suite completa de auditoría de ciberseguridad para infraestructura de red crítica. Diseñada para OpenClaw con gestión de contexto por capas.


Arquitectura de Capas

Layer 0 — Siempre cargado (constitución + router)
  system-methodology    → 7 fases, reglas de oro, formato de hallazgos
  system-index          → Routing vendor→skill, framework→skill, rutas de memoria
  memory-ops            → Gestión del sistema de memoria (opcional)

Layer 1 — Un vendor a la vez (F1 → F7 completo)
  vendor-kb-f5          → F5 BIG-IP TMOS 13.x-17.x, VELOS, XC
  vendor-kb-cisco       → Cisco IOS / IOS-XE / NX-OS / ACI
  vendor-kb-fortinet    → Fortinet FortiOS 6.x/7.x
  vendor-kb-paloalto    → Palo Alto PAN-OS 9.x/10.x/11.x + Panorama
  vendor-kb-juniper     → Juniper JunOS 18.x-23.x (SRX, QFX, EX, MX)
  vendor-kb-arista      → Arista EOS 4.2x / CloudVision

Layer 2 — Un framework a la vez (cargar → evaluar → descargar)
  fw-checks-nist80053   → NIST SP 800-53 Rev 5 (~187 controles, 20 familias)
  fw-checks-csf         → NIST CSF 2.0 (6 funciones, ~40 subcategorías)
  fw-checks-cis         → CIS Controls v8 (18 controles, 153 safeguards)
  fw-checks-pcidss      → PCI DSS v4.0 (~89 controles técnicos, 12 requisitos)
  fw-checks-iso27001    → ISO/IEC 27001:2022 (Anexo A temas 5, 6, 8)

Layer 3 — Reemplaza Layer 2 en Fase 6 (generación de reportes)
  report-nist80053      → Reporte NIST 800-53: dashboard ejecutivo + POA&M + scripts
  report-csf            → Reporte CSF 2.0: radar chart + scorecard + maturity tier
  report-cis            → Reporte CIS v8: HTML técnico + quick wins + scripts
  report-pcidss         → Reporte PCI DSS: gap matrix + CVE CDE scope + QSA-ready
  report-iso27001       → Reporte ISO 27001: SoA parcial + NC register + cert readiness

Skills especializados (cargar según necesidad):
  audit-diag-health     → Diagnóstico de salud para los 6 vendors (health + logs)
  audit-auto-generate   → Auto-genera skills para vendors sin KB pre-construido
  tools-secops          → Inventario de herramientas SecOps locales instaladas
  community-cybersec-index → Router hacia 754 skills comunitarios de ciberseguridad

Cómo Usar Esta Suite

Inicio de sesión (siempre)

Cargar: system-methodology + system-index

Auditoría de un dispositivo

1. Cargar vendor-kb-{vendor}                    → Layer 1 activo
2. Cargar fw-checks-{framework}                 → Layer 2 activo
3. Ejecutar checks → guardar findings-{fw}.json → disco
4. Descargar fw-checks-{framework}              → Layer 2 vacío
5. Cargar report-{framework}                    → Layer 3 activo
6. Leer findings desde disco → generar reporte  → Layer 3 vacío
7. Repetir pasos 2-6 para cada framework
8. Descargar vendor-kb-{vendor}                 → ciclo completo

Diagnóstico rápido

Cargar: audit-diag-health (cubre todos los vendors)

Vendor sin KB pre-construido

Cargar: audit-auto-generate

Operaciones fuera de red (forensics, threat intel, cloud, etc.)

Cargar: community-cybersec-index → identifica skill específico
Nota: Requiere instalar la librería comunitaria por separado.

Frameworks Cubiertos

FrameworkSkillsAlcance
NIST SP 800-53 Rev 5fw-checks-nist80053 + report-nist80053~187 controles, familias AC/AU/CM/IA/SC/SI
NIST CSF 2.0fw-checks-csf + report-csf6 funciones: GOVERN/IDENTIFY/PROTECT/DETECT/RESPOND/RECOVER
CIS Controls v8fw-checks-cis + report-cis18 controles, 153 safeguards
PCI DSS v4.0fw-checks-pcidss + report-pcidss~89 controles técnicos, 12 requisitos
ISO/IEC 27001:2022fw-checks-iso27001 + report-iso27001Anexo A: temas 5, 6, 8

Vendors Soportados

VendorKBOS/Platform
F5 Networksvendor-kb-f5BIG-IP TMOS 13.x–17.x, VELOS, XC
Ciscovendor-kb-ciscoIOS, IOS-XE, IOS-XR, NX-OS, ACI
Fortinetvendor-kb-fortinetFortiOS 6.x/7.x
Palo Alto Networksvendor-kb-paloaltoPAN-OS 9.x/10.x/11.x, Panorama
Juniper Networksvendor-kb-juniperJunOS 18.x–23.x (SRX, QFX, EX, MX)
Arista Networksvendor-kb-aristaEOS 4.2x, CloudVision
Cualquier otro vendoraudit-auto-generateAuto-generación dinámica

Reglas de Oro

  1. READ-ONLY — Nunca ejecutar comandos de escritura en producción
  2. EVIDENCIA REAL — Nunca inventar ni asumir output de comandos
  3. N/A sobre PASS falso — Sin evidencia = N/A, nunca PASS
  4. CREDENCIALES EFÍMERAS — Nunca persistir en disco
  5. HA WORST-CASE — Resultado del cluster = peor miembro individual
  6. CONFIRMACIÓN SIEMPRE — Resumen de hallazgos antes de generar reportes
  7. SCRIPTS SOLO REVISIÓN — Generar scripts, nunca auto-ejecutar

Gestión de Contexto

LayerSkills~TokensVigencia
0system-methodology + system-index~2,400Siempre
1vendor-kb-{vendor}~1,500F1 → F7
2fw-checks-{framework}~1,200Un framework a la vez
3report-{framework}~800Reemplaza Layer 2 en F6

Pico máximo de contexto: ~5,100 tokens (sin community skills).

Comments

Loading comments...