Operations · Intermediate
Verified
Automated verification
- Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
- Drafted by deepseek-flash via DeepSeek API.
- Second-model review: kimi-code/k3.1-pro (no critical or high findings).
- Verified .
- Automated checks and AI review only, not human review.
Scheduled trusted root certificate store audit
Flag unexpected root CAs before they weaken TLS trust
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- On a scheduleWeekly certificate audit
- ThenCompare roots against baseline
- ResultReview report with flagged roots
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.
Prompt to start with
BotBentoRecommended
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.