Protecting what the automation can reach.
WHY IT MATTERS
Automations hold credentials and they can act across systems.
WHAT AN AUTOMATION CAN DO
Whatever the account it uses can do.
WHY THAT IS THE RISK
An automation with broad access, compromised, has broad reach.
WHAT TO ESTABLISH
The minimum access each automation needs.
WHAT TO AVOID
Using an administrator account for convenience.
WHAT TO ESTABLISH ABOUT ACCOUNTS
That automations use accounts belonging to the business, not to individuals.
WHY
Individual accounts leave with the person and the automation stops.
WHAT TO RECORD
Every automation, what it accesses, and what account it uses.
WHAT TO REVIEW
When anyone leaves: which automations used their access.
WHAT TO CONSIDER ABOUT DATA
Where it is stored and who can reach it.
WHY
Customer and employee data moved between systems carries protection obligations.
WHAT TO ESTABLISH
Whether the platform is appropriate for the data you are moving.
WHAT NOT TO AUTOMATE CARELESSLY
Anything involving payments Anything sending to customers without review Anything deleting data Anything touching sensitive personal information
WHY PAYMENTS SPECIFICALLY
Automated payment instructions are a fraud target.
WHAT TO ESTABLISH FOR ANY MONEY MOVEMENT
Human approval.
WHAT TO PROTECT
The automation platform account itself, with strong authentication.
WHY
Access to it is access to everything it connects to.
WHAT TO ENABLE
Two-factor authentication, everywhere.
WHAT TO REVIEW PERIODICALLY
Connections and their permissions.
