Individual skill
ids-ips-pro
Deploy and tune intrusion detection/prevention — sensor placement, signature and behavioral detection, and alert quality.
skills/ids-ips-pro/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,797 bytes
Read excerpt
## Overview
IDS/IPS watches network traffic for malicious activity: IDS detects and alerts, IPS detects and blocks. Value comes from placement, tuning, and integration with response — an untuned IDS is a noise generator; an over-aggressive IPS is a self-inflicted outage. This skill covers the defensive practice: where to sense, what to detect, how to tune, and how to keep it effective.
Network detection is an instrument, not an oracle — its value depends entirely on calibration to your environment. The same signature that is gold in one network is noise in another. Treat tuning as a permanent function, not a deployment phase, and measure the instrument continuously: what did it catch, what did it miss, what did it cry wolf about.
## When to use
- Adding network detection at key boundaries (internet edge, data-center core, cloud VPCs).
- Tuning noisy signatures or investigating IPS-caused outages.
- Meeting compliance requirements for intrusion detection (PCI DSS).
- Complementing EDR with network-level visibility (lateral movement, C2, exfiltration).
## Core concepts