Search for existing rules that match the following requirement:

$ARGUMENTS

Follow these steps:

Extract key concepts from the requirement text. Identify:
- Technical terms (e.g., "TLS", "audit", "encryption", "RBAC")
- Component references (e.g., "API server", "kubelet", "etcd", "SSH")
- Specific settings or parameters mentioned
- Any reference IDs (SRG-xxx, CIS section numbers, STIG IDs, NIST controls)
Respect scope constraints. If the user specifies a scope (e.g., "only OpenShift control plane", "only node-level"), restrict results to that scope. Do not return rules outside the requested scope. OCP4/Kubernetes rules live under applications/openshift/ and Linux rules live under linux_os/guide/. If no scope is specified, search both.
Search broadly across rule titles, descriptions, and template configurations:
- Search applications/openshift/ and linux_os/guide/ for rule.yml files
- Search for keywords in titles, descriptions, template vars, and reference fields
- If reference IDs were provided, search for those exact IDs in rule.yml files

find-rule