Compliance evidence triage

Use case · Compliance

← All use cases
⛉

Compliance evidence triage

Compliance

Classify each uploaded document/screenshot against the right control (SOC 2 / ISO 27001) and flag whether it's sufficient evidence — at scale.

The routing recipe
Job typeClassification / routingPolicyCheapest that passesConstraintsgroq
routes to
Llama 3.3 70B Versatile groq
groq:llama-3.3-70b-versatile
91.8
match score
80.9
task fit
100
cost
83.4
speed
Why this model from benchmarks & capabilities
  • "Classification / routing" leans hardest on instruction; Llama 3.3 70B Versatile scores 79/100 there — #34 of 54.
  • Strength on this class of work shows up on IFEval, MMLU (zero-shot), where Meta models are competitive.
  • Cost: free tier. Speed: ~394 tok/s on Groq LPU.
  • Chosen over Llama 3.1 8B Instant for higher task-fit (80.9 vs 75.6).
Capability the job needsWeightLlama 3.3 70B VersatileCatalog rank
instruction0.9079#34 of 54
speed0.9083#16 of 54
knowledge0.3080#23 of 54
Relevant benchmarksIFEval MMLU (zero-shot) EconomicsCost: free tier.
Speed: ~394 tok/s on Groq LPU.
vs runner-upChosen over Llama 3.1 8B Instant for higher task-fit (80.9 vs 75.6). (Llama 3.1 8B Instant, score 91.1)
Example result
Sample input ▾
Artifact: 'AWS IAM policy export showing MFA enforced on all root and admin accounts, dated this month.'
control: SOC 2 CC6.1 (Logical access — authentication) evidence_type: configuration export sufficient: yes reason: Demonstrates MFA enforcement on privileged accounts with a current date; maps cleanly to access-control criteria. (Also supports ISO A.5.17 / A.8.5.)
Test it on your own data
Sign in to continue

LLM Switchboard is private — sign in with Authlee to access the control room.

Sign in with Authlee
← Back to home