QUESTION

I'm running pat validate in CI (pre-merge GitHub Actions), and it takes ~7–10 minutes. Would a larger runner help, or are there ways to speed it up?

ANSWER

Using a larger runner is unlikely to improve performance.

pat validate zips your detection files and sends them to Panther in a single API call, so runtime depends more on network and data size than CPU or memory. Validating the full repo will naturally take longer.

To improve performance, consider:

• Limiting validation scope with --path or --filter to target only relevant files

• Running pat validate in CI only on files changed in the PR instead of the full repo

Refer to Panther documentation on filtering for more details on how to limit validation scope.