Vulnerable items that route, prioritize, and hit their remediation clock on their own.

The configuration that decides how findings are prioritized and routed — the assignment, scoring, and remediation rules that turn raw scanner output into work your team can act on. The vulnerable items and remediation tasks themselves are live records created when scanners run; Phyllis reads them but never fabricates them.

Yes. Vulnerability findings route through their own path, separate from general incident routing, and Phyllis targets the right one for the kind of finding so rules actually take effect. That means fewer misrouted findings and less silent failure.

Vulnerability Response has to be active, with at least one scanner integration and enough asset data for findings to resolve to real systems. Phyllis confirms what's installed and how your security setup is arranged before proposing a single rule.

Phyllis discovers, proposes, and only builds on your approval. Every change is staged for review before anything deploys, and nothing writes to your instance until you click approve.

Every finding is cited to a real rule or setting read live from your instance. She works from what your instance actually exposes, not plausible-sounding guesses, and validates before writing anything.