CoreD Journal

What to check before an AI workflow goes live

A review checklist for business owners: assets, data access, permissions, logs and what happens if someone needs to take over.

Cybersecurity4 min read

A metal keyring beside neatly organized network cables

Short answer

Before launch, list the tools and data the workflow can reach, limit permissions, define which actions need approval, and test how the team can stop it. Turn gaps into a fix list with owners and closure checks.

Write down what the workflow can reach

List the systems, owners, accounts and kinds of data the workflow can use. Include connections that are easy to forget, such as email, a shared drive, a calendar or an export. Mark where customer data leaves one service and enters another.

Give each integration the narrowest permissions it needs. Separate testing from production and avoid shared administrator accounts. Review who can change permissions and how the team can revoke them if something goes wrong.

Review decisions and write activity down

For each action, decide whether the system may do it automatically or a person should approve it. Put payment, deletion and broad changes behind explicit review. Treat incoming documents, messages and model output as untrusted input when deciding what actions are allowed.

Keep enough activity history to answer what happened, when and under whose authority. Avoid storing credentials or unnecessary personal data in logs. Run through a staff takeover and make sure the workflow stops using the old approval once access is withdrawn.

Get findings you can act on

A readiness review should leave you with a prioritised fix list, an owner for each item and a way to verify what changed. Ask whether remediation, follow-up checks and ongoing support are included in the scope.

If you need formal security testing, get written approval from the asset owner and agree which assets, environments and test windows are in scope. Keep customer-facing systems and production data out of any work that has not been approved.

Walk through one real business task on paper

Take a support agent that reads help documents and drafts an answer. List what comes in, where data goes, what the workflow reads and who approves the result. Repeat for an exception, such as a customer asking to change account information. Exceptions often expose permissions or handoff decisions that normal cases hide.

Check the credentials used at each step and who can rotate or revoke them. Start with read-only access where it meets the requirement. Make sure a test environment has its own credentials and uses approved test data. Give every connection a named owner.

Treat approvals and handover as part of the system

Write the permitted actions in plain English. A CRM assistant might be allowed to read a record and create a draft. Sending an email or updating an account can require a person to approve. Keep the approval beside the specific action, record and version it covers.

Test a missing approval, an expired approval and a staff member taking over midway. Verify that the workflow waits or stops instead of continuing with an old decision. Check that someone on duty knows where to find the activity log and who can pause the integration.

Use findings to decide whether to launch

For each finding, write down the affected asset, business impact, owner, next action and closure check. If an agent uses a shared administrator account, for example, name the IT owner, plan an individual service account with limited rights and verify that shared access can be removed.

Agree which findings block launch and which the owner can accept temporarily. Save the approval and review date. The decision record helps the team reopen the review when it adds another action or provider.

Is a readiness review the same as a penetration test?

A readiness review checks whether controls, owners and handover are ready for the workflow. Penetration testing is a separate engagement that requires written authorization and agreed assets and methods. Ask for the scope and deliverables in writing.

References

Explore cybersecurity assessment services

Keep reading