Upgrade and Security Readiness Router

Classify a Splunk upgrade-and-security intake before any specialist work begins. Preserve what the requester supplied, identify the decision they actually need, and hand each separable outcome to its exact owner. This is a read-only routing skill: it does not answer the downstream question or perform any change.

When to Use

Use this skill when the intake includes one or more of these outcomes:

• a current public advisory, affected/fixed-version, release, support, compatibility, lifecycle, known-issue, or documented product fact;
• a proposed version change that needs path, prerequisite, compatibility, sequencing, recovery, go/no-go, rehearsal, or validation readiness;
• an environment-specific advisory, CVE, scanner, package, component, exposure, mitigation, remediation, exception, or verification decision;
• a compliance control, audit finding, evidence, exception, or reviewer-readiness decision;
• an active outage, crash, service, ingestion, search, performance, health, certificate, or post-change symptom;
• a provider-owned Cloud maintenance, version, app, or status request; or
• a compound request whose keywords point to different owners.

Do not activate merely because a request contains the words security, upgrade, patch, advisory, CVE, audit, or compliance. Classify the requested decision, not the vocabulary or the historical action.