Canonical: https://botbento.com/usecases/scheduled-trusted-root-certificate-store-audit/
Format: Markdown representation of the public HTML page.

# Scheduled trusted root certificate store audit

[Operations](https://botbento.com/usecases/ops/) · Intermediate

Flag unexpected root CAs before they weaken TLS trust

Run a recurring audit of the trusted root certificate store on selected machines. Record certificate names, issuers, expiry dates and fingerprints, compare them with an approved baseline, and highlight new or mismatched entries for review. Keep a history so changes can be checked over time.

## Quick answers

**What does it do?** Flag unexpected root CAs before they weaken TLS trust. Result: Review report with flagged roots.

**What does it need?** Tools: Terminal, Spreadsheet, Docs, Chat. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** On a schedule: Weekly certificate audit. Copy the prompt below into a bot in BotBento.

## How it works

1. On a schedule: Weekly certificate audit
2. Then: Compare roots against baseline
3. Result: Review report with flagged roots

## Prompt to start with

```text
On the scheduled run, inspect the trusted root certificate store on the machines listed in the audit scope. For each root, capture its display name, issuer, expiry date and fingerprint. Compare the results with the approved baseline and mark any new, removed, renamed or unexpectedly expiring entries. Write a concise report and keep a dated log. You may read certificate stores and write local reports. Do not delete or modify certificates, send messages, post reports, or make payments without the user's approval. Ask before sharing any report outside the workspace.
```

## Tools it uses

Terminal, Spreadsheet, Docs, Chat

## Works with

BotBento

## Tags

security, certificates, audit, tls, operations

## Source

[Tell HN: H&R Block tax software installs a TLS backdoor](https://news.ycombinator.com/item?id=47457162) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Review coding agent command logs for risky entries](https://botbento.com/usecases/review-coding-agent-command-logs-for-risky/) — Flag and summarize shell commands an agent ran, ready for human review
- [Audit data-sharing toggles across developer tool accounts](https://botbento.com/usecases/audit-data-sharing-toggles-across-developer-tool/) — Sweep settings pages weekly and flag any toggle that flipped back on
- [Full codebase security and vulnerability auditing](https://botbento.com/usecases/full-codebase-security-and-vulnerability-auditing/) — Inspect repositories for vulnerabilities, audit dependencies, and prepare remediation plans
