Splunk

Splunk is log analytics and security monitoring software used at enterprise scale, often by security and compliance teams reviewing activity across vendors. This isn’t a claims integration, Splunk is about how your organization runs Polygrade itself as procured enterprise software: audit log visibility for security and compliance review.

What Polygrade does with Splunk

Polygrade logs every search, recommendation, order, and return, along with the confidence level behind each decision. For enterprise clients with compliance requirements, that audit trail can be exported into Splunk alongside logs from your other vendors.

This sits apart from Polygrade’s claim-handling integrations entirely. Splunk doesn’t touch claim data, parts sourcing, or payment execution, it’s the layer that governs how your team accesses and monitors Polygrade as a system, the same way it governs every other vendor you run Splunk against.

How the Splunk connection works

Polygrade’s audit log can be exported to Splunk through a configured integration for enterprise clients.

This is configured during enterprise onboarding rather than left to a self-serve setup, since it touches how your team authenticates or how your operations team gets alerted.

What stays in Splunk

Splunk continues to manage identity, observability, or incident routing exactly as it does for every other tool in your stack. Polygrade is one more system governed by the rules you already have in Splunk, not a special case.

Data handling and security

Polygrade is SOC 2 compliant, with both Type I and Type II audits complete, and each client runs on a company-specific instance, a property directly relevant to how access through Splunk is scoped, since there’s no shared environment to accidentally expose.

Every claim recommendation Polygrade makes is logged with a confidence level and its supporting inputs, independent of whatever visibility Splunk is configured to provide, Splunk adds a second layer of oversight on top of an already-audited system, not a replacement for it.

Setting this up

A dedicated Forward Deployed Engineer configures the Splunk connection as part of enterprise onboarding, working with whoever owns identity or operations tooling on your side.

Frequently asked questions about Polygrade and Splunk

Is Splunk used for claims data, like Polygrade’s other integrations?

No. Splunk governs how your organization accesses or monitors Polygrade itself; claim, parts, and payment data move through Polygrade’s separate category-specific integrations.

How does Polygrade connect to Splunk?

Polygrade’s audit log can be exported to Splunk through a configured integration for enterprise clients.

Is Splunk required to use Polygrade?

No. Splunk is available for enterprise clients who want Polygrade to run under their existing identity, observability, or incident management setup, it isn’t required for Polygrade’s core claims functionality.