AI for business security
Last week's run of outages was a reminder that security work is speeding up, and most small businesses have never sat down and listed every account they own. AI is a great partner for that audit, as long as you use it the right way: it asks the questions and organizes the answers, and it never sees a password. We run it in Muse, Meta's AI agent, because Muse keeps logins in a secure vault its AI can't read. The prompts work in ChatGPT, Claude and Gemini too.
The one rule
Never paste a password, a two-step code, a recovery key or a full account number into any AI chat, Muse included. The AI works with account names, emails, who has access and yes or no answers. Every prompt below is written so it never needs more than that, and tells the AI to stop you if you start typing one. When Muse needs to sign in somewhere, it asks for the login on a secure entry card that goes to its vault, never into the chat.
Why we use Muse for this
Muse is Meta's AI agent. It's free to start (with a usage limit) at muse.ai, on your phone and on Mac. Three things make it a good fit for a security audit:
- A vault for logins. Usernames and passwords go into Muse's Secure Credentials Store. Muse uses them to finish a task you've approved without the AI ever seeing the password.
- It asks first. Muse checks with you before important actions, and you choose which apps it can connect to.
- It builds the spreadsheet. Muse creates the account list for you and saves it to your Library, so you can download it and keep it updated.
See how Muse protects your logins. Every prompt below also works in ChatGPT, Claude or Gemini if your team already uses one of them.
Jump to a section
Why now
In one week in November, Microsoft, the FAA, Chase, United, Apple and the NSA all had systems go down. Officials said none of it was a cyberattack. Security experts pointed to a common pressure instead: AI is finding flaws in software faster than ever, and companies are racing to patch them. Microsoft alone fixed more than 1,200 vulnerabilities in November, nearly 20 times the year before, according to Qualys.
The same tools that find holes in big companies' code make it cheaper for attackers to find holes in small businesses. And for most small businesses, the easiest way in is a login nobody remembers: the payroll account a former office manager set up with her personal email, the Facebook page an agency still has admin on, the shared password from 2019.
The gateway nobody watches
A former employee who still has access is a risk even if they'd never do anything wrong. If their password leaks in some other company's data breach, and they used it on your account too, that login becomes a door into your business. You won't get an alert, because to the system it looks like a normal sign-in.
Step 1: Build your complete account list
You can't audit what you can't see. The hard part of an account list is remembering everything, so let Muse interview you. It goes category by category and asks the questions that jog your memory: how do you actually get into payroll, which email gets the reset link, what shows up on the credit card statement every month.
Fill in what you know below (anything you skip still copies with a sensible default), then click Open Muse, paste the prompt and answer its questions. Have your credit card statement and your phone open. You'll probably turn up a few you'd forgotten.
Tell Muse about your business
I want a complete list of every software account and login my business uses, so I can audit our security. Interview me to build it. My business: a small local business. Team size: a small team. Password manager: not sure. Accounts I already know about: none listed yet. How to run the interview: - Ask me ONE question at a time and wait for my answer. Keep going until we've covered every category. - Go in this order: email and file storage; banking, credit cards and payment processing; accounting and taxes; payroll, HR and benefits; website (domain registrar, DNS, hosting, website builder, forms, plugins); social media and Google Business Profile; ad accounts; customer tools (CRM, booking, point of sale, online store, email marketing, texting); phones and internet; devices and Wi-Fi; vendor, insurance, utility and government portals; AI tools and browser extensions. - For each category, ask how we actually get in. For example: "When you run payroll, what website do you go to, and which email address gets the password reset link?" - Ask who set each account up, who else logs in, and whether a former employee, contractor or agency ever had access. - Jog my memory: ask what we pay for every month (tell me to look at the credit card statement), what sends us emails, and what we only log into once a year. - Never ask for a password, a two-step code, a recovery key or a full account number. If I start to type one, stop me. When I say "done", build me a spreadsheet I can download (an Excel file), one row per account, sorted by category, with these columns: Account, Category, What it's for, Login email, Owner, Others with access, Former staff or contractors who had access, Two-step on? (yes / no / not sure), Where the password is kept, Who pays for it. If you can't create files, give me the table as CSV in a code block so I can paste it into Google Sheets or Excel. Then, here in the chat, list every account where I answered "not sure", and the 5 accounts that would hurt most if someone else got in, and why.
When you type "done", Muse builds the spreadsheet, shares it in the chat and saves it to the Library tab in your workspace. Download it and save it somewhere your team can find it. (In ChatGPT or Claude you'll get an Excel file to download, and in Gemini a table with an Export to Sheets button. If an AI can't make a file, the prompt has it give you text you can paste into Google Sheets or Excel.) That spreadsheet is the backbone of everything else on this page, and it's the thing to keep updated. Each prompt below takes it as an attachment, and the password and two-step prompts hand it back with new columns filled in.
Step 2: Check your emails for leaked passwords
Checking every password one at a time takes hours. There's a faster way to find the ones that matter: check the email addresses you sign in with. When a company gets breached, the leaked records are tied to an email address, so your emails point you straight to the accounts to fix first.
Add every email you use for work
Your own work email, shared inboxes like info@ or office@, and any personal email you've used to sign up for a business account. Type one, press Next, and keep going until you're done. Nothing you type leaves this page; it only builds the prompt.
I'm checking whether the email addresses my business uses have shown up in known data breaches. These are email addresses only. There are no passwords here, and never ask me for one.
My emails:
- [Add your emails above]
1. Look up each email on haveibeenpwned.com in your browser, one at a time. If the site asks you to prove you're human, pause and ask me to do that step, then carry on.
2. For each email, list every breach it shows up in: the site or company, the date, and what leaked (passwords, phone numbers, addresses, financial details).
3. Ask me which of those sites I still use, which I don't recognize, and which I've closed.
4. Give me a fix list in this order: leaked passwords on sites I still use, my email accounts themselves, anything that leaked financial details or a Social Security number, then everything else. For each one, tell me what to do, and remind me to go to the site directly, not through a link in an email.
5. If I attach my account spreadsheet, add a Breached? column (yes or no, and which breach) and give me the updated file.
Keep it calm: a hit means that company was breached, not that someone is in my account right now.
You will get hits. Don't panic.
If you've had an email address for a few years, expect it to show up in at least one breach, and often several. That's normal. A hit means a company you used was breached, not that someone is in your accounts right now. Treat it as a to-do list, and work through it from the top.
What to do about each hit
- You know the site and still use it. Go to the site yourself (type the address or use your bookmark, never a link in an email), log in and change the password to a new one your password manager creates. Turn on two-step while you're there.
- You used that password anywhere else. Change it everywhere you used it, starting with your email, banking and payroll. A leaked password is a problem on one site. A reused one is a problem on every site that shares it.
- The hit is your email account itself. Change your email password first, since your email can reset everything else. Then sign out of all other sessions and check the recovery phone and email.
- You don't recognize the site, or you stopped using it. Log in and delete the account if you can. If you can't, change the password so the leaked one is useless.
- It leaked your phone number or address. Expect scam texts and calls that sound official. Don't click links in messages about the breach; go to the company's site directly.
- It leaked a Social Security number or financial details. Freeze your credit at Equifax, Experian and TransUnion. It's free, and you can lift it whenever you need to apply for credit.
- It's an old breach and you've changed that password since. You're done with that one, as long as the new password isn't used anywhere else.
When you've worked through the list, the Breached? column in your spreadsheet shows what's fixed. Later, for a deeper check, your password manager's health report (Google Password Checkup, Apple Passwords, 1Password Watchtower or Bitwarden) also flags weak and reused passwords.
Step 3: Find former employees and contractors who still have access
Start with a list of people: who works for you now, your contractors and agencies, and everyone who has left. Then compare it to the users, team or roles page on each account (names, emails and roles only, no passwords). Muse is good at the tedious part: comparing lists and spotting the name that shouldn't be there.
If an account is already connected to Muse, you can ask Muse to open its users page in Muse's own secure browser and copy the names, emails and roles for you. The login comes from the vault, and you can watch or step in at any point. Tell it to look only and change nothing.
Start with the accounts that matter most: email (Google Workspace or Microsoft 365), payroll, banking, your website admin, Meta Business, Google Business Profile and Google Ads. Don't skip recovery info. An old employee's cell number as the recovery phone on your main email is the same as giving them a key.
Who works with you, and who used to
Add one person at a time: their email, a name if you like, and who they are. Press Next and keep going. Include contractors, agencies and anyone who left in the last few years. Already have a list? Upload a CSV file instead. Nothing leaves this page.
I'm checking who still has access to my business accounts. There are no passwords here, and never ask me for one.
[Add your team above]
[Attach your account spreadsheet, or paste it here]
1. Using the Owner, Others with access and Former staff columns, list every account where someone who left, or a contractor or agency, might still have access.
2. If an account is connected to you, open its users or team page in your browser and copy the names, emails and roles. Look only. Don't change anything.
3. For accounts you can't open, tell me exactly where to find the users page, and I'll paste the names, emails and roles here.
4. Flag anyone who isn't on my current team, shared logins (one login several people use), and generic logins like info@ or office@ whose password someone who left could still know.
5. Flag accounts with more admins than they need, and recovery emails or phone numbers that belong to someone who left.
6. Give me a removal list in order of risk. For each person, tell me what to do before removing them: transfer ownership of pages and files, download anything we need, and change any shared password they knew.
Step 4: Audit two-step verification
Two-step verification (2FA) means a stolen password alone isn't enough to get in. It's the single biggest fix on this page. Mark which accounts have it on, then let Muse rank the rest and tell you where to find the setting.
Here's my business account spreadsheet (attached, or pasted below) with a column for two-step verification (yes / no / not sure). [Attach your account spreadsheet, or paste it here] For each account: 1. Tell me whether it offers two-step verification and the strongest option it supports (passkey, security key, authenticator app, text message). If you aren't sure, say so and tell me where to look in its settings. 2. Rank the order to turn it on. Email, password manager, banking, payroll, domain registrar and social media admins go first. 3. Flag any account where the codes go to the phone or email of someone who left, or to one person nobody else can reach. 4. For accounts with an admin console (like Google Workspace, Microsoft 365 or Meta Business), tell me how to see which users have two-step turned on and how to require it for everyone. 5. Add Strongest option and Turn-on order columns to my spreadsheet and give me the updated file. 6. Remind me to store backup codes in our password manager, not in a desk drawer or a notes app.
Watch where the codes go
Two-step only protects you if the codes go to someone who still works for you. Check that every code goes to a current owner's phone or authenticator app, and that at least two people can get into the accounts the business can't run without.
More audits worth running
Once you have the list, each of these takes a few minutes and closes a door people forget about.
- Domain and DNS. Who owns your domain registrar account, when does the domain expire, and is auto-renew on? If you lose your domain, you lose your website and your email at the same time.
- Connected apps. Google, Microsoft and Facebook each show third-party apps that can read your data. Remove anything you don't recognize or no longer use.
- Email forwarding rules. A common trick after someone gets into a mailbox is a quiet rule that forwards invoices or bank emails elsewhere. Check every mailbox's forwarding and filter settings.
- Billing. Which card pays for each account, who gets the invoices, and which subscriptions nobody uses anymore. Forgotten accounts are often still logged in somewhere.
- Payment change requests. Make it a rule: any email asking to change bank details or pay a new account gets a phone call to a number you already have, before any money moves.
- Backups. Can you restore your website, your email and your key files if an account is lost or an update breaks something? Test one restore.
- Devices and updates. Screen locks on, automatic updates on, and a plan for a lost laptop or phone. Keep updates on even when patches cause hiccups; backups are what protect you when one goes wrong.
Build your offboarding checklist
Most access problems start the day someone leaves. Turn your account list into a checklist so the next departure takes 30 minutes instead of being remembered six months later.
Using my account spreadsheet (attached, or pasted below), build an offboarding checklist for when someone leaves my business. [Attach your account spreadsheet, or paste it here] Order it by timing: the day they leave, within 24 hours, and within a week. Include: - Removing them from every account they had, starting with email, money and admin roles - Transferring ownership of pages, files, ad accounts and anything they set up - Changing every shared password they knew - Removing their phone and email from two-step verification and account recovery - Checking their mailbox for forwarding rules and connected apps before it's closed - Collecting devices, keys and key cards - Forwarding their email to a manager Make it a printable checklist with a line for who did each step and the date.
Make it a routine
Put a 20-minute security check on your calendar once a quarter: update the account list, rerun the access check, and look at your password manager's report. You can even have AI remind you; see AI scheduled tasks for small business.
When an AI agent needs to log in for you
Muse can do real work inside your accounts, like posting to your Facebook Page or pulling a user list. To do that it has to sign in, and that's where its vault comes in. The login never has to go into the chat.
- Muse's Secure Credentials Store. When you connect an app, or Muse needs to sign in somewhere, it shows a secure entry card. Enter the username and password there. Meta says the login is kept in a Secure Credentials Store that Muse uses to complete an action you've approved, without the AI model seeing your password, and it never appears in your chat. Muse also works with 1Password, so you can approve each login from your own vault.
- Using Claude instead? 1Password for Claude. Claude's version works through 1Password. When a site asks Claude to sign in, 1Password shows you which login it wants and why, you approve it, and 1Password fills it in on the page. Claude never sees the password or the one-time code. It's in beta for paid Claude plans on Mac with the Claude desktop app and Claude in Chrome. See Anthropic's setup guide.
These cards and approvals are the safe way to do it, and they don't break the one rule: the password goes into a vault, never into the conversation.
Add your AI agents to the audit
Hiding the password doesn't limit what an agent can do once it's signed in. Treat every AI agent with a login like another user: give it only the accounts it needs, keep "show me first and wait for my OK" in your instructions, and list it on your account inventory so it's part of the who-has-access check every quarter.
Questions people ask
Is it safe to use Muse or another AI for a security audit?
Yes, as long as the AI never sees a password, a two-step code, a recovery key or a full account number. Give it account names, login emails, who has access and yes or no answers. Your password manager and Have I Been Pwned do the password checks; the AI organizes the results and tells you what to fix first.
How long does the whole audit take?
The account inventory takes about 30 minutes for most small businesses. Passwords, access and two-step checks take another hour or two the first time. After that, a quarterly pass takes about 20 minutes because the list already exists.
Why do former employees matter if they left on good terms?
Because their old password may not have. If a former employee still has access and their password shows up in a data breach somewhere else, that login is a way into your business that nobody is watching. It has nothing to do with whether they'd ever misuse it.
Which accounts should I lock down first?
Your main email, your password manager, banking, payroll, your domain registrar, and admin access to your social media and Google Business Profile. Whoever controls your email can reset almost everything else.
Is text message two-step verification good enough?
It's far better than nothing. Where an account offers an authenticator app, a passkey or a security key, use that instead, since text codes can be stolen by moving your phone number to another SIM.
Can I let Muse log in to my accounts?
Yes, through its secure entry card, never by typing the password into the chat. The login goes into Muse's Secure Credentials Store, which the AI model can't see. Muse also works with 1Password, and so does Claude, where you approve each login. Once an agent is signed in it can act as you, so give it only the accounts it needs and keep it on your access list.
Is Muse free?
Muse is free to start with a usage limit. If you reach the limit, you can wait for it to refresh or upgrade to a paid plan. For this audit, start free and see how far it gets you.
Do I need IT help to do this?
Not for this audit. Everything here is done from the account settings you already have access to. If the audit turns up something you can't fix yourself, like a domain registered in a former employee's name, that's when to call for help.
Do this with us, live
We'll run this whole audit together in our hour-long workshop. Bring your laptop with Muse open, your phone and your credit card statement, and leave with your complete account list and a fix list for the week.
Follow for more.