Why a catalog?
Debates about autonomy stall because they are abstract. A catalog makes them concrete: instead of asking whether software should act alone, you ask whether software may reset this password at 2 a.m. without a person. Most teams find they agree quickly on individual actions.
What goes in each row?
- The action, by name: disable account, revoke session, reset password, isolate host, block hash, quarantine email, block domain.
- The tool that performs it.
- The blast radius: one user, one host, many users, production systems.
- Reversibility: can it be undone in minutes?
- Approval by day, approval by night: none, one analyst, a named lead, or wait until morning.
How do you set the approval levels?
Start from blast radius and reversibility. Quarantining a single phishing email is narrow and reversible. Isolating a production database server is wide and hard to reverse. A common pattern is to let software act alone on narrow, reversible actions for trusted alert categories, require one approval for single-user or single-host actions, and require a named lead for anything wider.
How do products map to the catalog?
Vendors describe their controls in different terms, and the catalog lets you translate them:
- Mate Security describes three modes: Recommend only, Supervised (low-risk steps run, risky changes need approval) and Auto-run for trusted categories under guardrails and audit.
- Prophet Security describes scoped Agent Actions that run autonomously or with your sign-off.
- Cortex AgentiX agents act within existing roles and permissions and can require approval for high-impact actions, according to Palo Alto.
- 7AI describes actions such as revoking a session, resetting a password or isolating a host behind approval gates with a full audit trail.
Ask each vendor to fill in your catalog's approval columns with its own settings. If it cannot express a row, you have found a gap.
How do you pull autonomy back?
Add one more column: what happens when the actor gets it wrong. You want a way to drop an action back to approval-required quickly, and a record of what ran. Mate Security, for example, describes rolling back to Supervised when verdicts drift from analyst reviews. Whatever the product, test the pull-back in a pilot, not in an incident.
How often should you revisit the catalog?
Every quarter, and after any incident in which an action ran when it should not have, or waited when it should have run. Each review should move a few rows: narrow, reversible actions that have run cleanly for months can move toward less approval, and anything that caused trouble moves back. Keep the history of changes; auditors and new team members will ask why an action is allowed.
Words in this lesson: Response action, Response action catalog, Playbook, Alert, Cortex AgentiX
Sources
Source: Mate Security platform page · Read 27 Sep 2026
Source: Prophet Security homepage · Read 27 Sep 2026
Source: Palo Alto Networks: Cortex AgentiX · Read 27 Sep 2026
Source: 7AI: response · Read 27 Sep 2026