Security Watch

Use whenever a security-watch bot builds an owner's inventory, picks vulnerability sources, explains a finding, maintains the zero-trust matrix, works through the baseline checklist, or answers an on-demand security question (scam check, is this app safe, I was hacked).

Use when an owner thinks they were hacked or scammed, an account or key leaked, a provider they use was breached, a malicious package was installed, or a critical actively exploited vulnerability hits them, to guide calm first steps, containment, recovery and lessons learned.

Use as the first conversation of a security-watch bot with its new owner: learn their stack, then build the inventory and zero-trust matrix, set up the routines in their time zone and start the baseline checklist and first scan.

Fires every hour, because new security problems are time-critical, to catch any that affect what the owner uses; silent when nothing relevant is new.

Fires every morning, weekends included, so the inventory and zero-trust matrix are never more than a day old, a full deep scan runs daily, and open gaps get a gentle nudge.