Skip to content
Back to skills

Network Legacy And Proxy Services

ASecurity

Interpret the nine legacy and proxy service fixture models and bounded socket observations without treating reachability or simulated conditions as verified protocol findings.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 15, 2026
securitypythonbash

Works with

  • cli

Security analysis

A100/100

Scanned October 15, 2026

npx -y skills add sodejm/copilot-operation-plugin-for-security --skill network-legacy-and-proxy-services --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Network Legacy And Proxy Services?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Network Legacy And Proxy Services
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sodejm-network-legacy-and-proxy-services-copilot-operation-plugin-for-s/badge)](https://www.skillsdirectory.com/skills/sodejm-network-legacy-and-proxy-services-copilot-operation-plugin-for-s)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: network-legacy-and-proxy-services
description: Interpret the nine legacy and proxy service fixture models and bounded socket observations without treating reachability or simulated conditions as verified protocol findings.
---

# Legacy Enterprise, Management, and Proxy Services

The NDMP, iSCSI, IPMI, Cisco Smart Install, TACACS+, IKEv1, PPTP, SOCKS, and Squid models cover fixture-defined scenarios. The CLI defaults to `--mode synthetic`; pass `--offline-targets` with mock target data to exercise those scenarios. Fixture findings, canary records, privilege candidates, and cleanup receipts are simulated and do not establish target behavior or remote cleanup.

`--mode live` uses a bounded socket collector. A TCP connection or UDP send is recorded as `unconfirmed`; an unreachable socket is `inaccessible`, never secure. The collector does not parse protocol responses, test authentication or proxy egress, validate canaries, execute code, change state, or produce privilege candidates or cleanup receipts. Authorization flags do not add those probes.

Use `candidates` and `cleanup` only to export records already present in a report. Confirm any operational finding in an authorized environment before specialist handoff. See the [playbook](../../docs/PLAYBOOK.md) for the report truth boundaries.

```bash
python3 -m cops legacy-services assess --targets 198.51.100.60 --mode synthetic --offline-targets mock_targets.json --output legacy_fixture_report.json
python3 -m cops legacy-services assess --targets 198.51.100.60 --mode live --services ndmp,iscsi --output legacy_socket_report.json
python3 -m cops legacy-services inspect legacy_socket_report.json
python3 -m cops legacy-services candidates legacy_fixture_report.json --output legacy_candidates.json
python3 -m cops legacy-services cleanup legacy_fixture_report.json --output cleanup_receipts.json
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.