@astrofoundry/pi-astro 0.37.0 → 0.37.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -59,10 +59,11 @@ function posted(over: Partial<PostedAlert> = {}): PostedAlert {
59
59
  }
60
60
 
61
61
  describe("security classification", () => {
62
- it("pages level 12 and up and our own rules, and keeps the rest for the digest", () => {
62
+ it("pages level 11 and up and our own rules, and keeps the rest for the digest", () => {
63
63
  expect(classify(event({ level: 12, rule: "5712" }), undefined)).toBe("urgent");
64
64
  expect(classify(event({ level: 15, rule: "40112" }), undefined)).toBe("urgent");
65
- expect(classify(event({ level: 11, rule: "521" }), undefined)).toBe("digest");
65
+ expect(classify(event({ level: 11, rule: "521" }), undefined)).toBe("urgent");
66
+ expect(classify(event({ level: 10, rule: "5503" }), undefined)).toBe("digest");
66
67
  expect(classify(event({ level: 10, rule: "100021" }), undefined)).toBe("urgent");
67
68
  expect(classify(event({ level: 10, rule: "100011" }), undefined)).toBe("urgent");
68
69
  expect(classify(event({ level: 10, rule: "100012" }), undefined)).toBe("urgent");
@@ -11,7 +11,7 @@ export type { AlertSummary, VulnEvent, WazuhEvent };
11
11
  export const DAILY_PREFIX = "Security Daily Report:";
12
12
  export const WEEKLY_PREFIX = "Security Weekly Report:";
13
13
  /** Wazuh levels from here on page at once; our own rules page at level 10 by rule id. */
14
- export const URGENT_LEVEL = 12;
14
+ export const URGENT_LEVEL = 11;
15
15
  /** The poller and the reports read Wazuh from this level: every rule of ours is level 10. */
16
16
  export const WATCH_LEVEL = 10;
17
17
  export const ACK_DAYS = 7;
@@ -44,7 +44,7 @@ export interface OriginVerdict {
44
44
  reason: string;
45
45
  }
46
46
 
47
- /** Urgent: level 12 or higher, or a paging rule of ours; a deployment-file change explained by GitOps or our own operation is known. */
47
+ /** Urgent: level 11 or higher, or a paging rule of ours; a deployment-file change explained by GitOps or our own operation is known. */
48
48
  export function classify(e: WazuhEvent, origin: OriginVerdict | undefined): EventClass {
49
49
  if (e.rule === DEPLOYMENT_RULE) return origin?.verdict === "known" ? "known" : "urgent";
50
50
  const own = OWN_RULES[e.rule];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@astrofoundry/pi-astro",
3
- "version": "0.37.0",
3
+ "version": "0.37.1",
4
4
  "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -5,7 +5,7 @@ description: How the security specialist reads Wazuh, CrowdSec, and the remote l
5
5
 
6
6
  # Security specialist
7
7
 
8
- VM 106 (`10.0.90.10`, VLAN 90) runs the Wazuh manager (container `observability-wazuh-manager-1`, agents `identity`, `arcane`, `dmz`, `CORTEX`, `NEXUS`, `hermes`, `frontdoor-1337`, `tailscale`), CrowdSec with its local API for the front-door bouncer, and rsyslog, which archives remote logs under `/var/log/remote/<host>/<program>.log` (14 days). The Discord bridge on Cortex reads Wazuh through this tool every two minutes and posts urgent alerts at once (level 12 or higher, and rules 100011, 100012, 100020, 100021; a deployment-file change that a GitOps commit or our own operation explains is not urgent), with Investigate and Acknowledge buttons for the owners; everything else goes into the Security Daily Report (06:00) and, on Mondays, the Security Weekly Report. The VM itself no longer posts to Discord. Two local CrowdSec scenarios matter: `37pla/pomerium-http-probing` (repeated Pomerium denials) and `37pla/frontdoor-sni-scanning` (rejected SNI at the VPS; bans escalate 4h, 24h, 7d, 30d, 90d). The home WAN address is whitelisted every five minutes; a scan test in August 2026 once banned it.
8
+ VM 106 (`10.0.90.10`, VLAN 90) runs the Wazuh manager (container `observability-wazuh-manager-1`, agents `identity`, `arcane`, `dmz`, `CORTEX`, `NEXUS`, `hermes`, `frontdoor-1337`, `tailscale`), CrowdSec with its local API for the front-door bouncer, and rsyslog, which archives remote logs under `/var/log/remote/<host>/<program>.log` (14 days). The Discord bridge on Cortex reads Wazuh through this tool every two minutes and posts urgent alerts at once (level 11 or higher, and rules 100011, 100012, 100020, 100021; a deployment-file change that a GitOps commit or our own operation explains is not urgent), with Investigate and Acknowledge buttons for the owners; everything else goes into the Security Daily Report (06:00) and, on Mondays, the Security Weekly Report. The VM itself no longer posts to Discord. Two local CrowdSec scenarios matter: `37pla/pomerium-http-probing` (repeated Pomerium denials) and `37pla/frontdoor-sni-scanning` (rejected SNI at the VPS; bans escalate 4h, 24h, 7d, 30d, 90d). The home WAN address is whitelisted every five minutes; a scan test in August 2026 once banned it.
9
9
 
10
10
  The `security` tool is read-only. Every call is a fixed command on the guest; `["--help"]` lists them.
11
11