AI Security
Griffin AI vs Claude Citations: Advisory Work
Claude's citations feature makes the model say where its claims come from. Griffin AI uses it for advisory workflows where traceability is the entire point.
Mar 22, 20262 min read
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Claude's citations feature makes the model say where its claims come from. Griffin AI uses it for advisory workflows where traceability is the entire point.
A senior engineer's threat model for Claude MCP tool poisoning in 2026, covering malicious servers, description hijacking, and the authorization patterns that actually help.
Claude's Computer Use lets an agent drive a GUI. For security, this is powerful and dangerous in equal measure. The architecture around it matters.
Claude's prompt caching gives you 90% discount on cached tokens. Security workloads have massive cacheable surface area. Griffin AI takes advantage; direct API use often does not.
Claude's Batch API gives you 50% off for async workloads. Griffin AI uses it internally. The question is whether your team should use the Batch API directly or consume it through Griffin.
Anthropic's Claude Agent Skills let you package tools and context for Claude. Here's how that primitive compares to Griffin's security-specific workflow scaffolding.
Claude Haiku is the cost-efficient model Griffin uses for high-volume scan interpretation. Here's how raw Haiku compares to Haiku inside Griffin's bulk pipeline.
Claude Sonnet is the workhorse model Griffin leans on for remediation. Here's how raw Sonnet compares to Sonnet inside Griffin's remediation pipeline.
Griffin uses Claude Opus as its deepest reasoning engine. Here's what triage looks like with Opus alone versus Opus running inside Griffin's eval harness.
Weekly insights on software supply chain security, delivered to your inbox.