Back to skill

Security audit

Ipam Dns Audit

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent IPAM/DNS audit guide, but its remediation advice should be treated as manual change guidance requiring approval.

Install only if you are authorized to audit the target networks and DNS zones. Use scoped read-only credentials, avoid putting real secrets directly into prompts or shell history, do not copy the curl -k pattern unless your organization approves it, and require separate human-reviewed change control before deleting DNS records or changing network ports.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Intent-Code Divergence

Medium
Confidence
94% confidence
Finding
The skill is labeled read-only, but the decision tree includes direct destructive actions such as deleting DNS records. That mismatch can cause operators or downstream agents to perform modifications under the false assumption that the skill is non-destructive, increasing the chance of accidental outages or data loss.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The content recommends deleting A, PTR, and CNAME-related records without an explicit safety warning, validation checklist, rollback guidance, or change-control requirement. In DNS environments, mistaken deletion can break name resolution, mail flow, logging, service discovery, and reverse-DNS-dependent controls.

Static analysis

No suspicious patterns detected.