Consumer lending and pawn / CISO / Security lead / The buyer’s question
The auditor asked for last quarter. We sent a link.
Evidence trails for a regulated lender, answered as a buyer’s question.
Published July 27, 2026/01 / 06
Every CISO in a regulated business knows audit season: screenshots, spreadsheets, a week of engineers proving things the team already believed were true. The evidence exists. Assembling it is the job nobody budgeted.
The buyer’s question we hear from security leads is simple: if agents run my checks, what do I show the auditor? The answer is the audit log itself. Every control check runs on a schedule, and each run writes what was checked, what was found and what changed. Evidence stops being a quarterly project and becomes a byproduct of operating.
F88 runs this today across a regulated hybrid estate. Posture is provable on demand, any day of the quarter. Full case study linked below.
#AISRE #FinServ #Cyber #CloudThinker
02 / 06 The problem
The question: “What do I show the auditor?”
Today
The spreadsheet
Evidence assembled by hand each quarter. Screenshots, exports, sign-off emails.
The gap
Thirteen quiet weeks
Between audits, drift accumulates and nobody can prove posture without repeating the scramble.
The fear
Automation without evidence
If an agent fixes things silently, the audit trail gets worse, not better.
The real requirement
The CISO does not need fewer findings. They need every check and every change to produce its own evidence, continuously.
Audit week is not a deadline problem. It is a data problem.
03 / 06 Why the current answers fail
Two ways to fail: keep doing it by hand, or hand production to an agent on day one
Option A: the status quo
One-off scripts
one per account, none the same
Tribal knowledge
the standard lives in someone’s head
Manual follow-up
tickets chased, dashboards watched
Quarterly evidence
compliant in audit week, unknown after
Resultsafe, does not scale
Option B: AI with full access
Trust on a promise
a demo is not a control
Unscoped credentials
one key for cloud and on-prem alike
Recommendations only
still a human acts, still no evidence
No audit trail
the regulator asks; the chat log answers
Resultscales, nobody signs off
What F88 chose
Neither. Controls encoded as scheduled checks, every run written to a tamper-evident log, human approval on anything that changes a regulated system.
Trust is not granted to a system. It is earned, one audited check at a time.
04 / 06 Frontier Investigation Agents
Four steps from read-only to autonomous. The team decides when to take each one.
Step 1
VerifyRead only
Live inventory, drift, waste and health checks. Nothing changes. Every finding explains what was checked, what was found, why it matters.
Step 2
EncodeStandards as Skills
Naming, tagging, guardrails, cost controls and runbooks written once and run the same way in every account. Tribal knowledge becomes a file.
Step 3
The gateAct with approval
Agents investigate and propose. A person approves where risk, policy or production impact demands it. Every action is written to the audit trail.
Step 4
Auto modeAutonomous under guardrails
Per environment, the team sets Notify, Act-with-Approval or Autonomous. Low-risk remediations run on their own. Production keeps the gate.
The CISO’s question
“Who approved the agent’s change?”
The log answers by name. Every action records what ran, what it touched, and which person approved it. That record is the artifact the auditor reads.
Frontier Investigation Agents for your cloud. They scale the team’s judgment, they do not replace it.
05 / 06 Proof
Audit season at F88, after
Quarterly audit scramble
Any day
Controls checked on a schedule, evidence written to the audit log. Posture provable on demand.
Daily ops by hand
80%
of daily manual operations tasks automated, human approval where risk demands it.
Before
A week of assembly
Evidence gathered by hand across accounts and tools, once a quarter.
After
A link
The auditor reads the scheduled checks and their results directly from the log.
Compliance stopped being a season. It became a property of the system.
06 / 06 One number, and the ask
The only number we ask you to check yourself
Read-only, first 30 days
Zero changes to production
Start the way our customers did. One scoped, read-only key. The engine inventories your estate and reports drift, waste and health. Your team checks the findings against what it already knows. If they hold, you decide the next step.
What you get
1 report
Full inventory, drift and waste findings, each with what was checked and why it matters.
What you risk
1 read key
Scoped and revocable. Every check it runs is in the audit log from day one.
Do not trust the AI. Verify it. Then let it earn the next step.
Pilot shape as run at F88.
Sources
- F88 (Consumer finance): 80% of daily ops automated, AWS spend down 30%, continuous compliance.
- Compliance figures: F88 case study
The evidence
F88
80% of daily ops automated, AWS spend down 30%, continuous compliance.
Read the full evidenceThe module
Cyber
The part of CloudThinker this story runs on, in product terms.
Explore Cyber