Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

## Unreleased

- **srx-ips** (0.1.5, draft): shows the security-policy binding (`application-services idp-policy`), says `match application default` belongs only in IDP rules, and names the `Please install the Signature Database` commit-check error. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- **srx-nat** (1.1.4): a from/to context holds one source rule-set; a second one fails `commit check` with only `configuration check-out failed`, so add rules to the existing rule-set. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- **srx-policy** (1.3.3): custom application port ranges are one `low-high` value (`destination-port 8080-8090`); `8080 to 8090` is NAT pool syntax and fails `commit check`. Found by the nightly reposbot commit check.
- **srx-dynamic-ip-feed** (1.1.0): keep dynamic-address feeds on Security Director-managed SRXs by defining the feed and the policy's dynamic-address match in configuration groups behind a placeholder address. Field-reported; not lab-validated here.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ Actionable Junos playbooks — commands, design guidance, verification, troubles

- **[srx-policy](./skills/srx-policy/SKILL.md)** — *(v1.3.3)* Enforced global-policy output with explicit zone-pair opt-outs on 23.x+, now including Branch SRX300/SRX400 after hardware validation, AppID/AppFW, NGWF-first web filtering, SecIntel, ATP, hit-count troubleshooting.
- **[srx-nat](./skills/srx-nat/SKILL.md)** — *(v1.1.4)* Source/destination/static NAT, NAT64/DNS64, CGN/PBA, persistent NAT, hairpin, proxy-ARP, session verification.
- **[srx-ips](./skills/srx-ips/SKILL.md)** — *(v0.1.4, draft)* IPS detection triage and custom signature authoring through a Junos MCP server: build the active rule table, read logs safely, monitor-to-enforce escalation behind an approval gate, and custom signature design with read-only coverage checks, context/direction/binding choice, false-positive-aware patterns, `commit check` validation, and monitor-mode proof before enforcement.
- **[srx-ips](./skills/srx-ips/SKILL.md)** — *(v0.1.5, draft)* IPS detection triage and custom signature authoring through a Junos MCP server: build the active rule table, read logs safely, monitor-to-enforce escalation behind an approval gate, and custom signature design with read-only coverage checks, context/direction/binding choice, false-positive-aware patterns, `commit check` validation, and monitor-mode proof before enforcement.
- **[srx-mnha](./skills/srx-mnha/SKILL.md)** — *(v1.3.8)* Multi-Node High Availability: routed/default-gateway/hybrid modes, SRGs, ICL/ICD, eBGP/BFD failover, VIPs, DHCP caveats.
- **[srx-mnha-builder](./skills/srx-mnha-builder/SKILL.md)** — *(v0.2.7, draft)* Build a new two-node MNHA pair end-to-end through a Junos MCP server (Juniper junos-mcp-server or rust-junosmcp): routing, switching, or hybrid mode selection, dedicated or shared and optionally encrypted ICL, one pair sheet used to write per-node staged configs from a stage reference and checked against a pre-push checklist, with pre-computed undo files, device dry runs, per-stage approval gates, the user-performed HA-activation reboot, formation checks, eBGP signal-route export, and a role-consistency failover test. Works with either MCP server.
- **[srx-cluster-to-mnha](./skills/srx-cluster-to-mnha/SKILL.md)** — *(v1.0.1)* Convert an existing SRX or vSRX chassis-cluster configuration into two node-local MNHA configs through an SRX-architect interview: cluster inventory, per-segment mode choice, SRG and ICL design, a fidelity report, and a cutover runbook. Offline only.
Expand Down
2 changes: 1 addition & 1 deletion skills/CHECKSUMS.sha256
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ e5ddddbd316bd32dcc50f9f050f94815949e91d5a4af0e44cac9344dba2081fb srx-initial-se
1f453a996e02641ad24b6d91cd8300588f49978d828df4fb10ef17efb1332b6e srx-initial-setup/references/stages/screens.md
f2c1e8c26e977ba870d3c7933fc1483669a7958e1ffc4b91768561e8a2ef8cea srx-initial-setup/references/verification.md
b76cf00a271b11516e61e5de5fc92992d78cfe8f7ec92d637d2bdad2935efe3b srx-initial-setup/references/write-safety.md
5a04a7c01d78b183c364cd5a068509e1792cd9a3b1d63313c6f6e9b957e6e887 srx-ips/SKILL.md
ed4d145cf3ba2499d790859940fa22aa71a9a8cc0c68ba37f1f71dfdfcba6252 srx-ips/SKILL.md
e954cf0e1e6e20abd7f672b79417b21a09f0e0efa3cee0e8fcb8c2af3e6223a5 srx-ips/agents/openai.yaml
65db88837afb005ad03e94b21fc5eb9e5f15329afbc57bfedfa076c1b8b13ddb srx-ips/references/commit-and-verification.md
c7ef19f9769b5950964f3882fb5077ead8d2465c9bff0475a940146b066b4667 srx-ips/references/lab-signature-notes.md
Expand Down
14 changes: 13 additions & 1 deletion skills/srx-ips/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
name: srx-ips
description: Manage SRX IPS (Junos IDP) lifecycle through a Junos MCP server - triage detections, propose monitor-to-enforce changes, design and validate custom signatures for findings the predefined database does not cover. Reads IDP policy and logs, reports what fired and each rule's action, stages changes behind approval gates, checks coverage read-only, chooses context/direction/pattern, validates syntax without activating. Use when reviewing IDP logs, investigating suspicious traffic, deciding which no-action rules to enforce, when a scanner finding needs IDP detection, or when extending IDP coverage. Not for attack database updates or IDP license maintenance.
version: 0.1.4
version: 0.1.5
author:
- fastrevmd-lab
- Claude
Expand Down Expand Up @@ -155,6 +155,18 @@ Also confirm the idp-policy is actually attached through
missing binding means **nothing** is inspected, which looks identical to "no
attacks".

```junos
set security policies global policy <policy> match application any
set security policies global policy <policy> then permit application-services idp-policy <idp-policy>
```

`match application default` is valid only inside an IDP rule; in the security
policy it fails `commit check` with `application or application-set must be
defined`. A device without the IDP signature database fails any `commit check`
that references predefined attacks with `Please install the Signature
Database`. That is a content gap for `srx-license-signature-maintenance`, not
a syntax error.

## Step 2 — Pull logs, small and attributable

Prefer a dedicated IDP log file over `messages`, which fills with unrelated
Expand Down
Loading