Industry
Small & Medium Business
Small and medium businesses need security that fits how they actually work. Start with the accounts, devices, payments, and customer records whose loss would interrupt operations. Clear ownership and a few consistently applied safeguards are more useful than an ambitious checklist nobody has time to maintain.
Field notes · 01
Secure the accounts that control the business
List business email, banking, payroll, accounting, cloud storage, website administration, and other essential services. Record the owner, administrator, recovery method, and provider contact for each. Use separate accounts for each person and strong authentication wherever supported.
The Infosec Lead can help organize priorities in plain language, while Librarian can support an inventory of systems and ownership. Review access when employees leave or a bookkeeper, contractor, or managed-service provider changes. Avoid letting the only recovery method depend on one person's private phone or mailbox.
- Protect the domain registrar and primary email administrator.
- Use a password manager and remove reused or shared passwords.
Field notes · 02
Make payment checks routine
Establish a simple rule for requests involving changed bank details, urgent transfers, payroll changes, or unusual purchases: verify independently before paying. Use a trusted number already held in business records. A familiar invoice format or email conversation does not establish that a change is genuine.
Plutus and Psycher can support payment and suspicious-message review, but an authorized person must still approve consequential actions. Give staff permission to pause a transaction and a clear person to call. Apply the same process when the request appears to come from the owner.
- Separate supplier-bank changes from routine invoice approval.
- Keep a short record of verification and approval.
Field notes · 03
Prepare for a bad day before it arrives
Identify what the business needs to operate if email, accounting, or a major supplier is unavailable. Keep protected backups and test restoration of representative files and records. Write a short incident contact sheet covering IT support, the bank, key providers, and appropriate reporting channels.
Horsemen can support managed-device work within agreed coverage, and Dewey can assist with recovery coordination. Human owners must approve account restrictions, device changes, and external communications. Ask service providers what they actually manage and what remains your responsibility, then document gaps rather than assuming they are covered.
- Enable supported updates and retire unsupported systems.
- Practice one account-compromise or payment-fraud scenario with staff.
Further reading
These links are background sector guidance, not validation of every recommendation or Aktoh capability. Aktoh role descriptions outline possible workflows; confirm supported connections, access, and scope before relying on them. The sources do not endorse Aktoh. Requirements depend on your organization, contracts, and jurisdiction; this page is not legal advice.
What we see here
Use the sector guidance above to identify critical systems, access risks, and recovery priorities. Coverage depends on the systems you connect and the workflows you configure.
How the fleet responds
Agents investigate and prepare recommendations in parallel. System-changing actions require approval by default; you choose which action classes can run automatically.
What you get back
Review plain-language findings and available audit records. Relevant agents can help organize evidence; your team remains responsible for compliance decisions.
Why there are no logos on this page
We do not identify customers without permission. Security scenarios on this site are illustrative unless accompanied by verified supporting evidence; they are not proof of customer outcomes or performance guarantees.
Start free. Add credits only when the work justifies it.
Run the whole fleet across unlimited nodes at zero platform fee — you pay only for tokens. Move to a pooled plan when the usage justifies the lower rate.