Aruba Cx Hardening
v1.0.0Professional network switch security configuration generator compliant with CIS Benchmark standards for Aruba CX switches.
⭐ 0· 56·0 current·0 all-time
byToolWeb@krishnakumarmahadevan-cmd
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description claim to generate CIS-compliant Aruba CX configuration files and the SKILL.md plus openapi.json describe exactly that API surface. There are no unexpected credential, binary, or filesystem requirements that would contradict the stated purpose.
Instruction Scope
SKILL.md contains only API-style request/response examples and endpoint docs; it does not instruct the agent to read local files, system credentials, or external unrelated endpoints. Note: sample configuration snippets include placeholders or potentially insecure defaults (e.g., 'snmp-server community public', 'logging 192.168.1.100') — these appear to be examples but must be reviewed/adjusted before applying to production devices.
Install Mechanism
No install spec and no code files to execute are included; this instruction-only skill does not download or install artifacts, which minimizes install-time risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no evident requests for unrelated secrets or system-wide access.
Persistence & Privilege
Skill is not set to always:true and does not request permanent presence or modify other skills; autonomous invocation is allowed by platform default but is not combined here with broad privileges.
Assessment
This skill appears coherent for generating Aruba CX hardening configs, but before installing or using it: 1) Verify the author/source (no homepage or repository is provided). 2) Never apply generated configs directly to production—inspect and test them in a lab or staging environment. 3) Check that generated settings map to your actual CIS benchmark version and organizational policies. 4) Look for placeholder or hardcoded values (SNMP community strings, IPs, passwords, TACACS/RADIUS secrets) and replace them with secure, audited values. 5) Ask the publisher for provenance (source code or audit) if you require higher assurance; absence of source lowers assurance even though the skill itself is internally consistent.Like a lobster shell, security has layers — review code before you run it.
latestvk977srkx35j1h64as1ffhka88n83x00d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.